-
Notifications
You must be signed in to change notification settings - Fork 0
PR_26180_OWNER_003-backlog-startup-assignment-policy #276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
f6cadec
207503c
bb91cbb
3e9f494
0bd5294
75d3792
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -26,29 +26,86 @@ Historical snapshots, archived references, and non-team phrases such as `Alfa/Be | |
|
|
||
| ## Team Backlog Ownership | ||
|
|
||
| Authoritative assigned product work source: | ||
|
|
||
| ```text | ||
| dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md | ||
| ``` | ||
|
|
||
| Tool demand and Owner/Admin priority signal source: | ||
|
|
||
| ```text | ||
| admin/tool-votes.html | ||
| ``` | ||
|
|
||
| The Tool Votes/Admin Owner planning surface informs backlog priority, Owner/Admin review, tool demand, and reprioritization. It does not replace `BACKLOG_MASTER.md` as the authoritative assigned-work source. | ||
|
|
||
| Every active team owns an active backlog when it has assigned work. | ||
|
|
||
| Each backlog item must track: | ||
|
|
||
| - name | ||
| - description | ||
| - product area | ||
| - status | ||
| - current completion percentage | ||
| - active PR, when one exists | ||
| - next milestone | ||
| - remaining work | ||
| - blocking dependencies | ||
| - owning team | ||
| - source or reference | ||
|
|
||
| Completion percentages are updated: | ||
|
|
||
| - at SOD | ||
| - when work changes status | ||
| - after every accepted PR | ||
| - at EOD | ||
|
|
||
| The backlog is the authoritative source for determining the next logical PRs. | ||
|
|
||
| If the backlog and a generated report conflict, the backlog wins unless OWNER explicitly approves a newer governance decision. | ||
|
|
||
| Codex must not invent assigned product work from conversation memory when `BACKLOG_MASTER.md` has a matching product area. | ||
|
|
||
| Teams must update backlog status and percent complete when work changes status. | ||
|
|
||
| Owner must update backlog status, completion percentage, and Tool Votes/Admin Owner status when assigning, reprioritizing, completing, or deferring work. | ||
|
|
||
| When the Product Owner provides a completed PR ZIP, ChatGPT must review that ZIP, update the active team backlog and completion percentages, and recommend the next logical PRs needed to keep moving toward a Product Owner testable outcome. | ||
|
|
||
| ## Team Assignment Startup Review | ||
|
|
||
| During startup, each team must: | ||
|
|
||
| 1. Read `dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md`. | ||
| 2. Locate its assigned team section and assigned product areas. | ||
| 3. Read the Tool Votes/Admin Owner priority signal source at `admin/tool-votes.html` when the work involves tool demand, tool ordering, or Owner/Admin prioritization. | ||
| 4. Display assignments as a table grouped by Team, then Product Area. | ||
| 5. Include Team, Product Area, Status, Percent Complete, Active PR, Next Milestone, and Source / Reference for every assignment row. | ||
|
|
||
| Required startup output: | ||
|
|
||
| ```text | ||
| Team Assignment | ||
| =============== | ||
|
|
||
| Source ............ dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md | ||
| Priority Source ... admin/tool-votes.html | ||
| Team .............. <team> | ||
| Status ............ PASS | ||
|
|
||
| Assignments | ||
| ----------- | ||
|
|
||
| | Team | Product Area | Status | Complete | Active PR | Next Milestone | Source | | ||
| |------|--------------|--------|----------|-----------|----------------|--------| | ||
| | Alfa | Objects Manager | Active | 45% | PR_26179_ALFA_011 | Properties | BACKLOG_MASTER.md | | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This required startup block hard-codes Useful? React with 👍 / 👎. |
||
| ``` | ||
|
|
||
| If the task is not represented in `BACKLOG_MASTER.md` or the Tool Votes/Admin Owner planning source, Codex must flag the missing representation and ask OWNER whether to add or update the backlog before continuing. | ||
|
|
||
| ## Start Of Day Team Briefing | ||
|
|
||
| When a team is assigned, ChatGPT/Codex must provide this briefing before implementation begins: | ||
|
|
@@ -65,6 +122,18 @@ When a team is assigned, ChatGPT/Codex must provide this briefing before impleme | |
|
|
||
| This briefing is required before implementation begins. | ||
|
|
||
| The briefing must include the Team Assignment startup output defined above. | ||
|
|
||
| ## Startup Hard Stops | ||
|
|
||
| STOP before implementation when: | ||
|
|
||
| - `dev/build/ProjectInstructions/backlog/BACKLOG_MASTER.md` cannot be found. | ||
| - the assigned team cannot be found in the backlog, unless OWNER explicitly provided a one-off task. | ||
| - the requested product-area task is not represented in the backlog or Tool Votes/Admin Owner planning source, until OWNER confirms whether to update the backlog. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
As written, this hard stop fires whenever a requested product-area task is absent from either source, so any valid Useful? React with 👍 / 👎. |
||
|
|
||
| If `admin/tool-votes.html` cannot be found, document the missing priority signal source and recommend `admin/tool-votes.html` as the canonical path instead of inventing a replacement. | ||
|
|
||
| ## End Of Day Team Summary | ||
|
|
||
| At EOD, ChatGPT/Codex must provide: | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,16 +4,29 @@ | |
|
|
||
| Canonical backlog tracking owner: `dev/build/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`. | ||
|
|
||
| This file is the authoritative source for assigned product work. | ||
|
|
||
| This document is updated as work status changes, including Owner assignment, reprioritization, completion, deferral, accepted PRs, SOD review, and EOD review. | ||
|
|
||
| `BACKLOG_MASTER.md` is now the canonical team/product-area assignment and status source. Future backlog changes must update this structure directly. | ||
|
|
||
| Each product area must include status and percent complete. | ||
|
|
||
| Every active team owns an active backlog when it has assigned work. | ||
|
|
||
| Backlog entries in this file follow the canonical field list, including: | ||
|
|
||
| - Name | ||
| - Description | ||
| - Product area | ||
| - Status | ||
| - Current completion percentage | ||
| - Active PR, when one exists | ||
| - Next milestone | ||
|
Comment on lines
+21
to
+25
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
These newly mandatory fields are not actually populated for most existing backlog rows below (for example, entries like Useful? React with 👍 / 👎. |
||
| - Remaining work | ||
| - Blocking dependencies | ||
| - Owning team | ||
| - Source or reference | ||
|
|
||
| Completion percentages are updated at SOD, after every accepted PR, and at EOD. | ||
|
|
||
|
|
@@ -181,6 +194,29 @@ The backlog is the authoritative source for determining the next logical PRs. | |
| - OWNER merge approval and EOD merge governance verified. | ||
| - Team ownership governance verified through the authoritative ownership map. | ||
|
|
||
| - [x] Alfa - Team-aware local dev bootstrap runtime complete | ||
|
|
||
| Notes: | ||
| - Completion reference: PR #250 / `PR_26171_ALFA_009-team-aware-bootstrap`. | ||
| - `npm run dev:bootstrap` is the primary team-aware local bootstrap command. | ||
| - `npm run dev:local-api` remains as the legacy API alias. | ||
| - `npm run dev:api` supports API-only startup. | ||
| - `npm run dev:web` supports web-only startup. | ||
| - `dev/bootstrap/start-dev.mjs` owns bootstrap orchestration. | ||
| - `dev/bootstrap/team-port-config.mjs` owns team port resolution. | ||
|
Comment on lines
+205
to
+206
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
These ownership pointers use Useful? React with 👍 / 👎. |
||
| - Team-aware `--team` runtime support is implemented. | ||
| - Bootstrap orchestration, browser launch reporting, and port resolution are implemented. | ||
| - Verified command: `npm run dev:bootstrap -- --team bravo`. | ||
| - Observed verified output includes: | ||
| - `GameFoundry team-aware dev bootstrap` | ||
| - `Mode: bootstrap` | ||
| - `Team: bravo` | ||
| - `Web URL: http://127.0.0.1:5520` | ||
| - `API URL: http://127.0.0.1:5521/api` | ||
| - `Browser launch: http://127.0.0.1:5520/index.html` | ||
| - `Supported teams: owner, alfa, bravo, charlie, delta, echo, foxtrot, golf, hotel` | ||
| - Do not assign team-aware dev bootstrap, `dev:bootstrap`, team-port config, browser launch, bootstrap orchestration, or port resolution as remaining backlog work unless OWNER opens a new enhancement request. | ||
|
|
||
| - [x] OWNER - Repository hygiene governance complete | ||
|
|
||
| Notes: | ||
|
|
@@ -195,11 +231,10 @@ The backlog is the authoritative source for determining the next logical PRs. | |
| Status: CANCELLED / NOT DOING | ||
|
|
||
| Items removed from backlog: | ||
| - Multi-port workspace framework | ||
| - Alfa/Beta/User isolation framework | ||
| - Runtime port management initiative | ||
|
|
||
| Replacement governance: | ||
| - Multi-port workspace framework and runtime port management are no longer cancelled/not doing; they are implemented by the team-aware local dev bootstrap runtime item above. | ||
| - System Health remains one page per deployed environment. | ||
| - Each deployment actively checks only itself. | ||
| - Environment Summary, Database Health, Storage Health, Runtime Health, and Health Check History are Charlie System Health ownership. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a repo-based Start of Day,
admin/tool-votes.htmldoes not contain the vote/order/state rows that would prove tool demand or Owner/Admin priority; the table body is empty and the page loads its snapshot throughadmin/tool-votes.jsfrom/toolbox/votes/snapshot. Agents following this required source can only read the static shell and cannot derive the priority signal, so the instruction should reference the underlying API/data contract or explicitly require running the admin page.Useful? React with 👍 / 👎.