PR_26180_OWNER_003-backlog-startup-assignment-policy#276
Conversation
ToolboxAid
force-pushed
the
PR_26180_OWNER_003-backlog-startup-assignment-policy
branch
from
8dd6bc4 to
afaaae7
Compare
ToolboxAid
force-pushed
the
PR_26180_OWNER_003-backlog-startup-assignment-policy
branch
from
facdebf to
75d3792
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 75d37927fd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - `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.
As written, this hard stop fires whenever a requested product-area task is absent from either source, so any valid BACKLOG_MASTER.md item that is not also a Toolbox/Admin vote row will stop startup, even though the same standard says Tool Votes only applies when tool demand/Owner prioritization is relevant and does not replace the backlog. This blocks backlog-only assignments such as non-tool Alfa/Delta work; scope the Tool Votes check to tool-demand tasks or require a stop only when the task is missing from both applicable sources.
Useful? React with 👍 / 👎.
| Tool demand and Owner/Admin priority signal source: | ||
|
|
||
| ```text | ||
| admin/tool-votes.html | ||
| ``` |
There was a problem hiding this comment.
For a repo-based Start of Day, admin/tool-votes.html does 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 through admin/tool-votes.js from /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 👍 / 👎.
| - Product area | ||
| - Status | ||
| - Current completion percentage | ||
| - Active PR, when one exists | ||
| - Next milestone |
There was a problem hiding this comment.
These newly mandatory fields are not actually populated for most existing backlog rows below (for example, entries like - [ ] Alfa - Game Concept Notes only have a checkbox/team/name under a journey heading). With the same PR declaring the current BACKLOG_MASTER.md structure canonical and requiring Start of Day to report Status, Active PR, and Next Milestone from it, teams either have to fabricate values or stop on missing evidence; migrate the rows to the required structure or relax the mandatory fields.
Useful? React with 👍 / 👎.
| - `dev/bootstrap/start-dev.mjs` owns bootstrap orchestration. | ||
| - `dev/bootstrap/team-port-config.mjs` owns team port resolution. |
There was a problem hiding this comment.
These ownership pointers use dev/bootstrap/..., but the repository and package.json scripts point to dev/scripts/start-dev.mjs and dev/scripts/team-port-config.mjs; there is no dev/bootstrap copy. When future startup or port-resolution work follows this authoritative backlog note, it will inspect or edit nonexistent paths instead of the real bootstrap scripts, so the completed-item record should use the actual dev/scripts paths.
Useful? React with 👍 / 👎.
|
|
||
| | 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.
This required startup block hard-codes Alfa | Objects Manager | Active | 45% | PR_26179_ALFA_011, but the backlog/ownership docs list Objects under Charlie and there is no Alfa Objects Manager assignment in BACKLOG_MASTER.md. Agents copying the required output can report a nonexistent active Alfa assignment/PR; make this a placeholder row or generate it from the actual backlog instead of shipping a stale example.
Useful? React with 👍 / 👎.
1 participant
Summary
Governance/documentation-only update for team startup assignment policy.
BACKLOG_MASTER.mdas the authoritative assigned product work source during startup.admin/tool-votes.htmlas the Tool Votes/Admin Owner priority signal source for tool demand and Owner/Admin review.Validation
git diff --checknpm run validate:canonical-structureReports
dev/reports/codex_review.diffdev/reports/codex_changed_files.txtdev/reports/PR_26180_OWNER_003-backlog-startup-assignment-policy_report.mddev/reports/PR_26180_OWNER_003-backlog-startup-assignment-policy_branch-validation.mddev/reports/PR_26180_OWNER_003-backlog-startup-assignment-policy_requirement-checklist.mddev/reports/PR_26180_OWNER_003-backlog-startup-assignment-policy_validation-report.mddev/reports/PR_26180_OWNER_003-backlog-startup-assignment-policy_manual-validation-notes.mdZIP
dev/workspace/zips/PR_26180_OWNER_003-backlog-startup-assignment-policy_delta.zip