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
4 changes: 4 additions & 0 deletions docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,10 @@ Existing Project Instructions outside `docs_build/dev/ProjectInstructions/` rema
- `docs_build/dev/reports/` owns generated reports, audits, and validation artifacts.
- root `archive/` owns historical reference material only.

## Team Backlog, SOD, And EOD Governance

`docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` defines required Start of Day team briefings, End of Day team summaries, active team backlog fields, completion percentage update points, backlog-driven next PR selection, and official military team-name spelling.

## Environment Governance

`docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md` defines the official environment model, environment invariance rule, shared API/service contract rule, required Supabase/Postgres/R2 services, required R2 prefixes, and SQLite retired status.
Expand Down
1 change: 1 addition & 0 deletions docs_build/dev/ProjectInstructions/README.txt
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,7 @@ READ THIS FIRST

Addendum index:
- Documentation Ownership: docs_build/dev/ProjectInstructions/addendums/documentation_ownership.md
- Team Backlog, SOD, And EOD Standard: docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md
- Single Source and EOD Main Lock: docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md
- Canonical Repository Structure: docs_build/dev/ProjectInstructions/addendums/canonical_repository_structure.md
- Test Structure Standardization: docs_build/dev/ProjectInstructions/addendums/test_structure_standardization.md
Expand Down
13 changes: 13 additions & 0 deletions docs_build/dev/ProjectInstructions/TEAM_START_COMMANDS.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ No team creates a PR branch until all checks pass:
- `HEAD` SHA matches the published EOD SHA

Use `docs_build/dev/ProjectInstructions/` as the only active Project Instructions source.
Read `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` before implementation.

Branch Lifecycle (Canonical):
- Every PR follows exactly three phases: START, WORK, END.
Expand Down Expand Up @@ -166,4 +167,16 @@ git rev-list --left-right --count main...origin/main
git rev-parse HEAD

Publish Branch, HEAD SHA, and Date/time. This becomes tomorrow's official baseline.

Also provide the required EOD team summary:
- Team name
- Date
- PRs completed
- PRs merged
- Validation summary
- Overall completion percentage
- Remaining backlog
- Completion percentage for each remaining backlog item
- Recommended first PRs for the next day
- Repository status
```
13 changes: 13 additions & 0 deletions docs_build/dev/ProjectInstructions/addendums/naming_registry.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,14 +43,27 @@ Capture approved Game Foundry Studio names to reduce rename churn.

Teams must use NATO phonetic naming.

Official active team codes:

- OWNER
- ALFA
- BRAVO
- CHARLIE
- DELTA

Examples:
- Team OWNER
- Team Alfa
- Team Bravo
- Team Charlie
- Team Delta
- Team Echo
- Team Foxtrot

Rule:
- Use `Alfa` spelling when referring to Team Alfa.
- Do not rewrite historical snapshots, archived references, or non-team phrases such as `Alpha/Beta/User isolation framework` unless OWNER explicitly scopes that work.

## Rule

Do not rename approved terms without OWNER approval.
Original file line number Diff line number Diff line change
@@ -0,0 +1,98 @@
# Team Backlog, SOD, And EOD Standard

Status: Approved
Owner: OWNER

## Purpose

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.

This standard is governance/documentation only. It does not change runtime behavior, API implementation, storage implementation, database DDL, or secret values.

## Official Team Names

Use military phonetic spelling for active team names:

- OWNER
- ALFA
- BRAVO
- CHARLIE
- DELTA
Comment on lines +16 to +20

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep Golf in the active team list

This new standard defines the active team names but omits Team Golf. I checked the current active governance in docs_build/dev/ProjectInstructions/team_assignments/TEAM_ASSIGNMENTS.md, which says the active ownership lanes include Team Golf, and docs_build/dev/ProjectInstructions/addendums/team_release_readiness.md, which says current active governance must not exclude Golf. When this addendum is used for SOD/EOD/backlog routing, Golf-assigned work can be treated as invalid or skipped, contradicting the existing active lane rules.

Useful? React with 👍 / 👎.


Display labels may use title case:

- Team OWNER
- Team Alfa
- Team Bravo
- Team Charlie
- Team Delta

Do not substitute Greek spelling for team names. Use `Alfa` spelling when referring to Team Alfa.

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.

## Team Backlog Ownership

Every active team owns an active backlog when it has assigned work.

Each backlog item must track:

- name
- description
- current completion percentage
- remaining work
- blocking dependencies

Completion percentages are updated:

- at SOD
- after each accepted PR
- at EOD

The backlog is the authoritative source for determining the next PRs.

If the backlog and a generated report conflict, the backlog wins unless OWNER explicitly approves a newer governance decision.

## Start Of Day Team Briefing

When a team is assigned, ChatGPT/Codex must provide this briefing before implementation begins:

- team name
- active workstream
- current overall completion percentage
- assigned backlog items
- completion percentage for each backlog item
- remaining work for each backlog item
- recommended execution order
- current active branch
- blocking dependencies, if any

This briefing is required before implementation begins.

## End Of Day Team Summary

At EOD, ChatGPT/Codex must provide:

- team name
- date
- PRs completed
- PRs merged
- validation summary
- overall completion percentage
- remaining backlog
- completion percentage for each remaining backlog item
- recommended first PRs for the next day
- repository status:
- current branch
- worktree
- local/origin sync

## Relationship To Existing Workflow

This standard preserves the existing branch workflow:

- SOD starts from latest `main`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Require the published EOD SHA at SOD

This summary says SOD starts from the latest main, but the canonical START gate in project_instructions_single_source_eod_lock.md requires HEAD to equal the published EOD SHA before any team branch is created. If origin/main advances after EOD because of an unapproved merge or direct commit, following this newer active addendum would let teams start from that unapproved SHA instead of stopping at the baseline check.

Useful? React with 👍 / 👎.

- SOD creates or uses the active team branch.
- All commits go to the active team branch, not `main`.
- Sequential PRs stay on the active team branch/workstream during the day.
- EOD merges OWNER-approved work, pushes, returns to `main`, and verifies clean worktree and local/origin sync `0 0`.
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ Before a team starts, validate:
- work remains with the assigned team until complete or OWNER reassignment
- the team's previous PR is Closed, unless OWNER documented an explicit stacked PR chain

Before implementation begins, ChatGPT/Codex must provide the SOD briefing defined in `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`.

## Current Four-Team Start Set

The current active delivery teams for backlog start commands are:
Expand Down Expand Up @@ -112,6 +114,8 @@ Closed readiness requires:
- backlog updated
- tool state updated when applicable

At EOD, ChatGPT/Codex must provide the team summary defined in `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md`.

## Gate Behavior

Release readiness is a validation gate.
Expand Down
16 changes: 16 additions & 0 deletions docs_build/dev/ProjectInstructions/backlog/BACKLOG_MASTER.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,21 @@
# BACKLOG_MASTER

## Backlog Item Tracking Standard

Every active team owns an active backlog when it has assigned work.

Each backlog item must track:

- Name
- Description
- Current completion percentage
- Remaining work
- Blocking dependencies
Comment on lines +7 to +13

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Either populate or scope required backlog fields

This makes every backlog item in the authoritative backlog require description, per-item completion percentage, remaining work, and blocking dependencies, but the active items below are still plain checkbox rows (for example, Alfa - Game Concept Notes has no remaining-work or dependency field). As soon as SOD/EOD summaries are generated from this file, the new required fields are missing for most items, so the standard either needs to be scoped to assigned/activated items or the existing backlog entries need those fields added.

Useful? React with 👍 / 👎.


Completion percentages are updated at SOD, after each accepted PR, and at EOD.

The backlog is the authoritative source for determining the next PRs.

## Game Journey MVP

### Idea
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -101,14 +101,25 @@ This current rule supersedes any prior permanent discipline ownership assumption

Team names must use NATO phonetic naming.

Official active team codes:

- OWNER
- ALFA
- BRAVO
- CHARLIE
- DELTA

Examples:
- Team OWNER
- Team Alfa
- Team Bravo
- Team Charlie
- Team Delta
- Team Echo
- Team Foxtrot

Use `Alfa` spelling when referring to Team Alfa.

## Assignment Rule

Work stays with the assigned team until either:
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
# PR_26177_OWNER_010-team-backlog-sod-eod-standard

Date: 2026-06-27
Team: OWNER
Branch: PR_26177_OWNER_010-team-backlog-sod-eod-standard

## Purpose

Add active governance for team backlog ownership, Start of Day briefings, End of Day summaries, completion percentage tracking, and official military team-name spelling.

## Scope

Documentation and governance only.

No runtime code, UI code, API code, database code, `start_of_day` files, history snapshots, or unrelated cleanup were changed.

## Changes

- Added `team_backlog_sod_eod_standard.md` as an active Project Instructions addendum.
- Added Start of Day team briefing requirements before implementation begins.
- Added End of Day team summary requirements.
- Defined active team backlog ownership fields:
- name
- description
- current completion percentage
- remaining work
- blocking dependencies
- Defined completion percentage update points at SOD, after each accepted PR, and at EOD.
- Confirmed the backlog is authoritative for determining next PRs.
- Added official active team codes: OWNER, ALFA, BRAVO, CHARLIE, and DELTA.
- Confirmed active team-name spelling uses `Alfa`, while historical snapshots and non-team phrases are not rewritten unless OWNER explicitly scopes that work.
- Linked the addendum from active Project Instructions index and team start guidance.

## Validation

- PASS: `git diff --cached --check -- . :(exclude)docs_build/dev/reports/codex_review.diff`
- PASS: documentation/governance-only changed-file check.
- PASS: SOD briefing rule exists.
- PASS: EOD summary rule exists.
- PASS: backlog ownership rule exists.
- PASS: active team codes include ALFA.
- PASS: active `Alpha` references are limited to the non-team cancelled `Alpha/Beta/User isolation framework` phrase.
- PASS: no runtime files changed.
- PASS: no UI files changed.
- PASS: no API files changed.
- PASS: no database files changed.
- PASS: no `start_of_day` files changed.

## Artifact

- `tmp/PR_26177_OWNER_010-team-backlog-sod-eod-standard_delta.zip`

## Manual Validation Notes

Reviewers should confirm active team work now has a required SOD briefing, required EOD summary, explicit backlog ownership fields, completion percentage update cadence, and the official team spelling standard.
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# PR_26177_OWNER_010 Branch Validation

Date: 2026-06-27
Team: OWNER
Branch: PR_26177_OWNER_010-team-backlog-sod-eod-standard

## Result

PASS

## Checks

- PASS: Work was performed on the active OWNER PR branch, not `main`.
- PASS: Branch is stacked on the active OWNER workstream branch.
- PASS: Changes are limited to active Project Instructions and generated reports.
- PASS: No runtime, UI, API, database, or `start_of_day` files changed.
- PASS: staged whitespace validation passed with generated `codex_review.diff` excluded.
- PASS: Required report files were generated.
- PASS: Repo-structured ZIP artifact path is defined under `tmp/`.

## Notes

This PR remains in the OWNER workstream and must not be merged to `main` until EOD closeout or explicit OWNER approval.
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# PR_26177_OWNER_010 Manual Validation Notes

Date: 2026-06-27
Team: OWNER

## Manual Review

Review `docs_build/dev/ProjectInstructions/addendums/team_backlog_sod_eod_standard.md` and confirm it defines:

- Start of Day team briefing fields.
- End of Day team summary fields.
- Active team backlog ownership.
- Completion percentage update cadence.
- Official team names: OWNER, ALFA, BRAVO, CHARLIE, DELTA.
- Existing SOD, active team branch, stacked PR, and EOD return-to-main workflow.

## Expected Reviewer Outcome

The Product Owner should be able to use the active Project Instructions to start and close a team day with explicit backlog percentages, remaining work, recommended execution order, and repository status.
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# PR_26177_OWNER_010 Requirements Checklist

Date: 2026-06-27
Team: OWNER

## Requirement Results

- PASS: Documentation/governance only.
- PASS: Active Project Instructions reviewed and updated.
- PASS: Active instruction files updated only.
- PASS: Historical snapshots were not rewritten.
- PASS: No runtime changes.
- PASS: Start of Day team briefing rule added.
- PASS: End of Day team summary rule added.
- PASS: Team backlog ownership rule added.
- PASS: Backlog item fields include name, description, current completion percentage, remaining work, and blocking dependencies.
- PASS: Completion percentage update cadence added for SOD, accepted PRs, and EOD.
- PASS: Backlog is documented as authoritative for determining next PRs.
- PASS: Official team names use OWNER, ALFA, BRAVO, CHARLIE, and DELTA.
- PASS: Active team references use `Alfa` spelling.
- PASS: Historical and non-team `Alpha/Beta/User isolation framework` wording was preserved.
- PASS: Required reports were generated.
- PASS: Repo-structured ZIP artifact will be generated under `tmp/`.

## Restrictions

- PASS: No commit was made to `main`.
- PASS: No `start_of_day` folders changed.
- PASS: No unrelated cleanup.
Loading
Loading