Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,11 @@ Do not rename these files to non-Spring names such as `common.yml` unless the Co
- `TASK:`
- Use the GitHub issue Type field correctly for every issue, including completed items.
- Keep tasks and stories attached to a relevant epic when one exists.
- Every issue added to Digital Bank Project #1 must have a native parent in the Sprint hierarchy. The only root planning items are the eight Sprint epics (`.github#18` through `.github#25`).
- Before creating or adding work, identify its Sprint and existing parent. If no existing branch fits, create and parent the missing Story or Epic first, then create the child item beneath it.
- A `Parent:` line in an issue body is useful documentation but does not establish hierarchy; use GitHub's native sub-issue relationship and verify it through the API.
- Set the native Issue Type, Project Sprint, assignee, and status when adding an item. Closed or historical items follow the same hierarchy rule.
- After creating or repairing items, audit every Project page and confirm there are no parentless non-Epic issues, no cross-Sprint parent relationships, and no orphaned project items.
- Assign in-progress tasks to `ramioooz`.
- Use dedicated branches, never commit directly to `main`.

Expand Down
8 changes: 8 additions & 0 deletions docs/project-handoff.md
Original file line number Diff line number Diff line change
Expand Up @@ -386,6 +386,14 @@ Consult GitHub Project #1 for the authoritative Sprint hierarchy and current iss

## Update Log

### 2026-09-05 - Enforced Project Sprint parent hierarchy

- Audited all 245 items in Digital Bank Project #1 across its paginated item connection.
- Confirmed that the eight Sprint epics are the only intended root planning items.
- Repaired the two parentless historical tasks: [`.github#202`](https://github.com/digital-bank-java/.github/issues/202) now belongs to Sprint 3, and [`.github#203`](https://github.com/digital-bank-java/.github/issues/203) now belongs to Sprint 4.
- Created the parented governance task [`.github#223`](https://github.com/digital-bank-java/.github/issues/223) under the Sprint 6 engineering-workflow story to make the parent-before-project rule explicit for future agents and contributors.
- The native GitHub sub-issue relationship is authoritative; a `Parent:` line in an issue body alone is not sufficient. New work must be assigned a Sprint, native Issue Type, parent, assignee, and Project status before implementation begins.

### 2026-09-05 - Auth Service SIT database prerequisite

- Created parented task [`.github#214`](https://github.com/digital-bank-java/.github/issues/214) under Auth session Story #46 and moved it to In review.
Expand Down