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
12 changes: 12 additions & 0 deletions archive/docs_build/dev/ProjectInstructions/history/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Project Instructions History Reference

This root archive path retains Project Instructions history snapshots that are no longer active but must remain traceable.

## Rules

- Archive instead of delete.
- Keep archived material readable.
- Preserve original meaning and context.
- Do not rewrite archive entries unless the owner explicitly approves.
- Use `archive/docs_build/dev/ProjectInstructions/history/CCYYMMDD_HHMMSS.md` for active-governance history snapshots.
- If archive placement is unclear, stop and request owner approval.
18 changes: 18 additions & 0 deletions docs_build/dev/PR/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# PR Documentation Area

This folder owns reusable PR workflow material and historical PR reference documents.

## Ownership

- `templates/` contains reusable PR planning and build templates.
- `reference/` contains historical or reference PR documents.

Reusable PR templates must not live outside `docs_build/dev/PR/templates/`.
Generated PR reports must live under `docs_build/dev/reports/`.
Permanent governance must live under `docs_build/dev/ProjectInstructions/`.

## Rules

- Do not put active Project Instructions in this folder.
- Do not put generated reports in this folder.
- Do not use lower-case `docs_build/dev/pr/`; this folder is the canonical PR documentation area.
7 changes: 7 additions & 0 deletions docs_build/dev/PR/reference/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# PR Reference

This folder contains historical or reference PR planning documents.

Files here are reference only. They are not active Project Instructions, not reusable templates, and not generated reports.

Use reusable templates from `docs_build/dev/PR/templates/`.
44 changes: 44 additions & 0 deletions docs_build/dev/PR/templates/BUILD_PR.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
# BUILD_PR: <PR_NAME>

## Purpose

Describe the one PR purpose.

## Source Of Truth

Use the current user request, this BUILD_PR, and active Project Instructions under `docs_build/dev/ProjectInstructions/`.

## Exact Scope

- List exact implementation tasks.
- Keep each item testable.

## Exact Targets

- `path/to/file`

## Out Of Scope

- No unrelated cleanup.
- No runtime/product/API/database changes unless explicitly scoped.

## Validation

Run targeted validation only:

```powershell
git diff --check
```

## Reports

Create or update:

- `docs_build/dev/reports/codex_review.diff`
- `docs_build/dev/reports/codex_changed_files.txt`
- PR-specific report under `docs_build/dev/reports/`
- branch validation PASS/FAIL
- requirement checklist PASS/FAIL
- validation lane report
- manual validation notes
- repo-structured ZIP under `tmp/`
30 changes: 30 additions & 0 deletions docs_build/dev/PR/templates/PLAN_PR.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# PLAN_PR: <PR_NAME>

## Purpose

Describe the single PR purpose in one or two sentences.

## Scope

- List the smallest valid scoped changes.
- Include only work required by the PR purpose.

## Out Of Scope

- List explicit exclusions.
- Include runtime, API, database, or UI exclusions when applicable.

## Creator-Testable Outcome

State what Mr. Q can test after applying the ZIP.

## Validation Plan

1. List targeted validation commands.
2. List manual checks.
3. State whether Playwright is impacted.

## Dependencies

- Previous PR: none
- Next PR: none
20 changes: 19 additions & 1 deletion docs_build/dev/ProjectInstructions/PROJECT_INSTRUCTIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,11 @@ The Project Instructions operating system provides additive governance for:
- backlog ownership
- team assignments
- multi-team branch and scope rules
- documentation ownership
- Build Path status synchronization
- tile overlay status behavior
- deprecation workflow
- contract and platform standards
- archive and history preservation
- recognized project instruction/reference files
- environment governance
Expand All @@ -34,13 +36,23 @@ Existing Project Instructions outside `docs_build/dev/ProjectInstructions/` rema
- `addendums/` contains additive governance rules.
- `backlog/` contains the central backlog file, `BACKLOG_MASTER.md`.
- `team_assignments/` contains current team assignment records.
- `standards/` contains active contract, model, and platform standards.
- `deprecation/` contains deprecation workflow documentation.
- Retained reference material belongs under the repository root `archive/` tree, not under `docs_build/dev/`.
- History snapshots belong under `archive/docs_build/dev/ProjectInstructions/history/`.

## Recognized Project Reference Files

`docs_build/dev/ProjectInstructions/addendums/project_reference_files.md` defines additional valid project instruction/reference files that must be included in future Project Instructions reviews when present in `ProjectInstructions.zip`, the active project instruction directory, or `docs_build/dev/admin-notes/`.
`docs_build/dev/ProjectInstructions/addendums/project_reference_files.md` defines additional valid project instruction/reference files that must be included in future Project Instructions reviews when present in `ProjectInstructions.zip`, the active project instruction directory, or the root archive reference tree.

## Documentation Ownership

`docs_build/dev/ProjectInstructions/addendums/documentation_ownership.md` defines the active documentation ownership model:

- `docs_build/dev/ProjectInstructions/` owns governance, team instructions, standards, and addendums.
- `docs_build/dev/PR/` owns PR workflow documents, templates, and examples.
- `docs_build/dev/reports/` owns generated reports, audits, and validation artifacts.
- root `archive/` owns historical reference material only.

## Environment Governance

Expand All @@ -60,6 +72,12 @@ Existing Project Instructions outside `docs_build/dev/ProjectInstructions/` rema

`docs_build/dev/ProjectInstructions/addendums/no_mock_repository_runtime_source.md` defines the Browser → API → Database product-data rule and mock repository technical debt boundary.

## Standards

Active contract, model, and platform standards live under:

`docs_build/dev/ProjectInstructions/standards/`

## Single Source and Main Lock Governance

`docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md` defines the single active Project Instructions source, canonical START / WORK / END branch lifecycle, EOD main lock, next-day reset, team branch creation gate, daily synchronization baseline, and mandatory hard stops.
Expand Down
12 changes: 10 additions & 2 deletions docs_build/dev/ProjectInstructions/README.txt
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
Read this file first.

Folder purpose:
This folder is the only active Project Instructions source for Game Foundry Studio. It organizes active governance, backlog, team assignment, deprecation, and history material under `docs_build/dev/ProjectInstructions/`.
This folder is the only active Project Instructions source for Game Foundry Studio. It organizes active governance, backlog, team assignment, standards, deprecation, and history material under `docs_build/dev/ProjectInstructions/`.

Preservation rules:
Preserve historical Project Instructions material as deprecated reference only. Do not treat root-level copies in `docs_build/dev/`, `project-instructions/`, or archived snapshots as active instruction sources. When a conflict appears, `docs_build/dev/ProjectInstructions/` wins unless OWNER explicitly approves a newer governance change.
Preserve historical Project Instructions material as deprecated reference only. Do not treat root-level copies in `docs_build/dev/`, `project-instructions/`, `archive/`, or archived snapshots as active instruction sources. When a conflict appears, `docs_build/dev/ProjectInstructions/` wins unless OWNER explicitly approves a newer governance change.

Backlog workflow:
Backlog work is tracked under backlog/. BACKLOG_MASTER.md is the planned source for backlog item status, notes, and references. Backlog item text is treated as immutable once created; status and notes may change under the governance addendums.
Expand Down Expand Up @@ -46,6 +46,7 @@ READ THIS FIRST
12. Follow the canonical START / WORK / END lifecycle.

Addendum index:
- Documentation Ownership: docs_build/dev/ProjectInstructions/addendums/documentation_ownership.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 All @@ -61,3 +62,10 @@ Addendum index:
- King of the Iceberg Layout Contract: docs_build/dev/ProjectInstructions/addendums/koti_layout_contract.md
- Tool MVP Stacked PR Standard: docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md
- No Mock Repository Runtime Source: docs_build/dev/ProjectInstructions/addendums/no_mock_repository_runtime_source.md

Standards index:
- Active contract, model, and platform standards: docs_build/dev/ProjectInstructions/standards/

PR documentation:
- Reusable PR templates: docs_build/dev/PR/templates/
- Historical/reference PR documents: docs_build/dev/PR/reference/
Original file line number Diff line number Diff line change
Expand Up @@ -47,11 +47,13 @@ Deprecated Project Instructions material outside `docs_build/dev/ProjectInstruct

## Project Reference File Review

When present in `ProjectInstructions.zip`, the active project instruction directory, or `docs_build/dev/admin-notes/`, Codex must include these recognized project instruction/reference files in the Project Instructions read set:
When present in `ProjectInstructions.zip`, the active project instruction directory, or `archive/docs_build/dev/admin-notes/`, Codex must include these recognized project instruction/reference files in the Project Instructions read set:

- `Installs required.txt`
- `Table layout.txt`

Archived reference files are historical reference only. They must not be treated as active Project Instructions.

Chat instructions may supplement Project Instructions but must not override approved governance without explicit OWNER approval.

## Conflict Handling
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,54 @@
# Documentation Ownership

Status: Approved
Owner: OWNER

## Purpose

Define the ownership model for documentation under `docs_build/dev/` after Project Instructions consolidation.

## Canonical Ownership

`docs_build/dev/ProjectInstructions/` owns:
- permanent governance
- team instructions
- standards
- addendums

`docs_build/dev/PR/` owns:
- PR workflow documentation
- reusable PR templates
- historical or reference PR documents

`docs_build/dev/reports/` owns:
- generated reports
- generated validation artifacts
- audits

The repository root `archive/` owns:
- historical reference material only

## Rules

- No active governance may exist outside `docs_build/dev/ProjectInstructions/`.
- No reusable PR template may exist outside `docs_build/dev/PR/templates/`.
- No generated report may exist outside `docs_build/dev/reports/`.
- No active document may exist outside its owning area.
- Historical reference material must not be treated as active governance.
- `docs_build/dev/start_of_day/` is a protected legacy handoff area and must not become an active Project Instructions source.

## Folder Rules

- `docs_build/dev/ProjectInstructions/standards/` contains active contract, model, and platform standards.
- `docs_build/dev/PR/templates/` contains reusable PR templates.
- `docs_build/dev/PR/reference/` contains historical or reference PR documents.
- `docs_build/dev/reports/audits/` contains audit report outputs.

## Validation

Documentation ownership cleanup PRs must verify:

- no active Project Instructions outside `docs_build/dev/ProjectInstructions/`
- no reusable PR templates outside `docs_build/dev/PR/templates/`
- no generated reports outside `docs_build/dev/reports/`
- no runtime/product/API/database files changed unless explicitly scoped
Original file line number Diff line number Diff line change
Expand Up @@ -5,27 +5,29 @@ Owner: OWNER

## Purpose

Define recognized project instruction and reference documents that may live outside the active `docs_build/dev/ProjectInstructions/` addendum tree but still belong in Project Instructions reviews.
Define recognized project instruction and reference documents that may live in the active `docs_build/dev/ProjectInstructions/` tree or in root `archive/` reference material but still belong in Project Instructions reviews.

## Recognized Files

The following files are valid project instruction/reference documents when present in `ProjectInstructions.zip`, `docs_build/dev/ProjectInstructions/`, or the project instruction/admin-notes directory:
The following files are valid project instruction/reference documents when present in `ProjectInstructions.zip`, `docs_build/dev/ProjectInstructions/`, or the archived project instruction/admin-notes reference tree:

- `Installs required.txt`
- `Table layout.txt`

Canonical repository locations:
Canonical repository reference locations:

- `docs_build/dev/admin-notes/Installs required.txt`
- `docs_build/dev/admin-notes/Table layout.txt`
- `archive/docs_build/dev/admin-notes/Installs required.txt`
- `archive/docs_build/dev/admin-notes/Table layout.txt`

## Review Rule

Future Project Instructions reviews must include these files automatically when they are present in either:

- an extracted `ProjectInstructions.zip` bundle
- the active project instruction directory
- `docs_build/dev/admin-notes/`
- `archive/docs_build/dev/admin-notes/`

Archived reference files are not active governance. If they conflict with active Project Instructions, `docs_build/dev/ProjectInstructions/` wins unless OWNER explicitly approves a newer governance change.

Treat these files the same as existing instruction documents for read-set, review, preservation, and reporting purposes.

Expand Down
6 changes: 4 additions & 2 deletions docs_build/dev/ProjectInstructions/addendums/release_gate.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ Before a governance, documentation, or administrative PR is merged, validate:
- Required source-of-truth files still exist.
- Governance Phase 1 completion guidance remains intact.
- PR workflow guidance remains intact.
- Documentation ownership guidance remains intact.
- Team assignment governance remains intact.
- Active team registry guidance remains compatible with temporary active teams.
- Canonical START / WORK / END branch lifecycle guidance remains intact.
Expand All @@ -38,6 +39,7 @@ The release gate should confirm these files when relevant to the PR:
- `docs_build/dev/ProjectInstructions/addendums/governance_phase1_complete.md`
- `docs_build/dev/ProjectInstructions/addendums/pr_workflow.md`
- `docs_build/dev/ProjectInstructions/addendums/project_instructions_single_source_eod_lock.md`
- `docs_build/dev/ProjectInstructions/addendums/documentation_ownership.md`
- `docs_build/dev/ProjectInstructions/addendums/project_reference_files.md`
- `docs_build/dev/ProjectInstructions/addendums/environment_governance_model.md`
- `docs_build/dev/ProjectInstructions/addendums/environment_configuration_standards.md`
Expand All @@ -47,8 +49,8 @@ The release gate should confirm these files when relevant to the PR:
- `docs_build/dev/ProjectInstructions/addendums/tool_mvp_stacked_pr_standard.md`
- `docs_build/dev/ProjectInstructions/addendums/no_mock_repository_runtime_source.md`
- `docs_build/dev/ProjectInstructions/team_assignments/team_ownership.md`
- `docs_build/dev/admin-notes/Installs required.txt` when present
- `docs_build/dev/admin-notes/Table layout.txt` when present
- `archive/docs_build/dev/admin-notes/Installs required.txt` when present
- `archive/docs_build/dev/admin-notes/Table layout.txt` when present

## Validation Result

Expand Down
12 changes: 0 additions & 12 deletions docs_build/dev/ProjectInstructions/archive/README.md

This file was deleted.

10 changes: 10 additions & 0 deletions docs_build/dev/ProjectInstructions/standards/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# Project Standards

This folder contains active contract, model, and platform standards that belong to the Project Instructions source of truth.

Rules:

- Standards here are active governance.
- Generated validation evidence belongs under `docs_build/dev/reports/`.
- Historical reference material belongs under the root `archive/` tree.
- Reusable PR templates belong under `docs_build/dev/PR/templates/`.
Original file line number Diff line number Diff line change
@@ -1,8 +1,3 @@
Toolbox Aid
David Quesenberry
04/06/2026
docs_build/dev/toolbox/server-dashboard/README.md

# Server Dashboard Foundation (Docs-First)

## Purpose
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# PR_26177_OWNER_008-dev-documentation-ownership-cleanup

Date: 2026-06-26 16:20:09 local
Branch: PR_26177_OWNER_008-dev-documentation-ownership-cleanup
HEAD: 782bcebe39f5469248f2767d8334e4b011059e17
Scope: Documentation ownership cleanup after ProjectInstructions consolidation
Status: PASS

## Summary

- Enforced docs_build/dev/ProjectInstructions/ as the only active governance SSoT.
- Kept reusable PR workflow material under docs_build/dev/PR/templates/.
- Renamed historical PR examples area to docs_build/dev/PR/reference/.
- Flattened ProjectInstructions history snapshots to archive/docs_build/dev/ProjectInstructions/history/.
- Kept generated reports under docs_build/dev/reports/.
- Confirmed no runtime/product/API/database files changed.

## Final Corrections

- PASS: No archive/docs_build/dev/ProjectInstructions/archive/ path remains.
- PASS: docs_build/dev/PR/examples/ was renamed to docs_build/dev/PR/reference/.
- PASS: ProjectInstructions remains the only active governance SSoT.

## Validation

- PASS: Current branch is PR_26177_OWNER_008-dev-documentation-ownership-cleanup.
- PASS: Changed path count is 132 and all changed paths are docs/archive/report scoped.
- PASS: Runtime/product/API/database changed path count is 0.
- PASS: Loose active docs outside approved docs_build/dev ownership folders: 0.
- PASS: git diff --check origin/main -- .
- PASS: Playwright not impacted; no runtime/product files changed.

## Artifact

- tmp/PR_26177_OWNER_008-dev-documentation-ownership-cleanup_delta.zip
Loading
Loading