|
| 1 | +# Team Backlog, SOD, And EOD Standard |
| 2 | + |
| 3 | +Status: Approved |
| 4 | +Owner: OWNER |
| 5 | + |
| 6 | +## Purpose |
| 7 | + |
| 8 | +Define the required Start of Day briefing, End of Day summary, team backlog ownership, completion percentage tracking, and official military team-name spelling for all active teams. |
| 9 | + |
| 10 | +This standard is governance/documentation only. It does not change runtime behavior, API implementation, storage implementation, database DDL, or secret values. |
| 11 | + |
| 12 | +## Official Team Names |
| 13 | + |
| 14 | +Use military phonetic spelling for active team names: |
| 15 | + |
| 16 | +- OWNER |
| 17 | +- ALFA |
| 18 | +- BRAVO |
| 19 | +- CHARLIE |
| 20 | +- DELTA |
| 21 | + |
| 22 | +Display labels may use title case: |
| 23 | + |
| 24 | +- Team OWNER |
| 25 | +- Team Alfa |
| 26 | +- Team Bravo |
| 27 | +- Team Charlie |
| 28 | +- Team Delta |
| 29 | + |
| 30 | +Do not substitute Greek spelling for team names. Use `Alfa` spelling when referring to Team Alfa. |
| 31 | + |
| 32 | +Historical snapshots, archived references, and non-team phrases such as `Alpha/Beta/User isolation framework` must not be rewritten unless OWNER explicitly scopes that work. |
| 33 | + |
| 34 | +## Team Backlog Ownership |
| 35 | + |
| 36 | +Every active team owns an active backlog when it has assigned work. |
| 37 | + |
| 38 | +Each backlog item must track: |
| 39 | + |
| 40 | +- name |
| 41 | +- description |
| 42 | +- current completion percentage |
| 43 | +- remaining work |
| 44 | +- blocking dependencies |
| 45 | + |
| 46 | +Completion percentages are updated: |
| 47 | + |
| 48 | +- at SOD |
| 49 | +- after each accepted PR |
| 50 | +- at EOD |
| 51 | + |
| 52 | +The backlog is the authoritative source for determining the next PRs. |
| 53 | + |
| 54 | +If the backlog and a generated report conflict, the backlog wins unless OWNER explicitly approves a newer governance decision. |
| 55 | + |
| 56 | +## Start Of Day Team Briefing |
| 57 | + |
| 58 | +When a team is assigned, ChatGPT/Codex must provide this briefing before implementation begins: |
| 59 | + |
| 60 | +- team name |
| 61 | +- active workstream |
| 62 | +- current overall completion percentage |
| 63 | +- assigned backlog items |
| 64 | +- completion percentage for each backlog item |
| 65 | +- remaining work for each backlog item |
| 66 | +- recommended execution order |
| 67 | +- current active branch |
| 68 | +- blocking dependencies, if any |
| 69 | + |
| 70 | +This briefing is required before implementation begins. |
| 71 | + |
| 72 | +## End Of Day Team Summary |
| 73 | + |
| 74 | +At EOD, ChatGPT/Codex must provide: |
| 75 | + |
| 76 | +- team name |
| 77 | +- date |
| 78 | +- PRs completed |
| 79 | +- PRs merged |
| 80 | +- validation summary |
| 81 | +- overall completion percentage |
| 82 | +- remaining backlog |
| 83 | +- completion percentage for each remaining backlog item |
| 84 | +- recommended first PRs for the next day |
| 85 | +- repository status: |
| 86 | + - current branch |
| 87 | + - worktree |
| 88 | + - local/origin sync |
| 89 | + |
| 90 | +## Relationship To Existing Workflow |
| 91 | + |
| 92 | +This standard preserves the existing branch workflow: |
| 93 | + |
| 94 | +- SOD starts from latest `main`. |
| 95 | +- SOD creates or uses the active team branch. |
| 96 | +- All commits go to the active team branch, not `main`. |
| 97 | +- Sequential PRs stay on the active team branch/workstream during the day. |
| 98 | +- EOD merges OWNER-approved work, pushes, returns to `main`, and verifies clean worktree and local/origin sync `0 0`. |
0 commit comments