pdurlej/platform

Fork 0

docs(deslop): reconcile stale platform docs #748

Merged

pdurlej merged 1 commit from codex/issues/727-docs-reconcile into main

2026-06-10 20:13:40 +02:00

codex commented

2026-06-08 15:27:04 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

Fresh agents should not be steered by stale navigation, phantom ADRs, dead directories, or frozen Apr-30 L3 synthesis. This PR makes the docs point at the current status/roadmap and archives old synthesis as historical evidence.

What changed

Reconciled MAP.md away from phantom ADRs/directories and toward merged context MAPs, modules/INDEX.yaml, current runbook paths, and state/STATUS_NOW.md.
Flipped merged ADRs 0003, 0004, 0005, 0010, 0011, and 0017 from “Proposed; accepted when merged” to Accepted with a 2026-06-08 reconciliation date.
Replaced the Phase-02 known-issues placeholder in 69 module runbooks with No known issues at last review.
Updated stale pointers in README/INDEX/ADR-0023 and historical docs that referenced moved state/L3/* files.
Archived frozen state/L3 files under state/archive/2026-04-30-L0-L4-synthesis/ with a README.
Marked the autonomy tiered execution design as design-target / not-yet-shipped for the live Tier-0 allowlist claim.
Added the requested superseded banner to state/cutover/honcho-gemma-ollama-prep.md.

Why it changed

Issue #727 identifies doc-vs-reality drift as the next mechanical deslop slice after #726.

Files touched

MAP.md, README.md, INDEX.md
decisions/0001, 0003, 0004, 0005, 0010, 0011, 0017, 0023
69 modules/<id>/runbook.md files
Archived state/L3/* into state/archive/2026-04-30-L0-L4-synthesis/
Historical references under docs/specs/ and state/
state/strategy/autonomy-tiered-execution-design-2026-06-02.md
state/cutover/honcho-gemma-ollama-prep.md

Relevant context

Forgejo issue #727
Sanitized #727 packet reviewed via Ollama Cloud and AntiGravity/agy
PRs #746/#747 already merged before this branch was created from fresh main

Runtime evidence

No runtime mutation. Docs-only repository change.

Known constraints

This touches decisions/ and many module runbooks, so canary 3+3 is required by repo policy despite being docs-only.

Explicit out-of-scope

No runtime/deploy changes
No secret-store reads
No resurrection of ADR-0008/0012/0014/0015 or dead directories
No status changes to ADR-0013 or ADR-0025
No architectural implementation for the autonomy allowlist

Requested decision

Review as mechanical docs reconciliation and run full canary before merge.

Merge blockers

Any remaining stale MAP pointer to phantom ADR/dead dirs
Any remaining Phase-02 runbook placeholder
Any live state/L3 file treated as current state
Canary finding that a docs pointer now lies about current repo reality

Model scout disclosure

Ollama Cloud was used on a sanitized #727 packet; DeepSeek-v4-pro returned a mechanical checklist and risks.
AntiGravity agy --sandbox --print was used on the same sanitized packet; Gemini returned a matching checklist and called out the ADR-0013/0025 and dead-link risks.
Raw model transcripts stayed local scratch only and were not committed.

Verification

git diff --check
python3 -m json.tool state/archive/2026-04-30-L0-L4-synthesis/entities.json
rg -n 'STATUS_NOW is currently stale|INDEX\.md \(module catalog\)|docs/runbooks|ADR-00(08|12|14|15)|contracts/|docs/domains/|docs/onboarding/|docs/phase-07/|docs/hermes/|docs/sunset-proposals/' MAP.md || true
rg -l 'TODO Phase 02: pull from L3/OPEN_LOOPS\.md if any apply' runbooks modules -g 'runbook.md' | wc -l
rg -n 'OPEN_LOOPS-2026-05-23|ADR 0001 through 0018' README.md INDEX.md MAP.md decisions docs state modules runbooks || true
find state/L3 -maxdepth 1 -type f -print | sort

Observed:

git diff --check clean
entities-json-ok
MAP forbidden-pattern scan returned no matches
runbook placeholder count: 0
stale snapshot/range scan returned no matches
state/L3 has no tracked files; archived files are under state/archive/2026-04-30-L0-L4-synthesis/

Spec sources read

Forgejo issue #727: scope and acceptance
docs/forgejo-agent-operations.md: write/PR identity contract
MAP.md: target stale pointers and phantom references
README.md, INDEX.md: stale navigation targets
ADR files 0003, 0004, 0005, 0010, 0011, 0017, 0023; plus 0001 only to keep a moved L3 reference non-broken
state/strategy/autonomy-tiered-execution-design-2026-06-02.md
state/cutover/honcho-gemma-ollama-prep.md and state/cutover/honcho-closeout-plan.md
module runbook files matched by the exact Phase-02 placeholder scan

Closes #727

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story Fresh agents should not be steered by stale navigation, phantom ADRs, dead directories, or frozen Apr-30 L3 synthesis. This PR makes the docs point at the current status/roadmap and archives old synthesis as historical evidence. ### What changed - Reconciled `MAP.md` away from phantom ADRs/directories and toward merged context MAPs, `modules/INDEX.yaml`, current runbook paths, and `state/STATUS_NOW.md`. - Flipped merged ADRs 0003, 0004, 0005, 0010, 0011, and 0017 from “Proposed; accepted when merged” to Accepted with a 2026-06-08 reconciliation date. - Replaced the Phase-02 known-issues placeholder in 69 module runbooks with `No known issues at last review.` - Updated stale pointers in README/INDEX/ADR-0023 and historical docs that referenced moved `state/L3/*` files. - Archived frozen `state/L3` files under `state/archive/2026-04-30-L0-L4-synthesis/` with a README. - Marked the autonomy tiered execution design as design-target / not-yet-shipped for the live Tier-0 allowlist claim. - Added the requested superseded banner to `state/cutover/honcho-gemma-ollama-prep.md`. ### Why it changed Issue #727 identifies doc-vs-reality drift as the next mechanical deslop slice after #726. ### Files touched - `MAP.md`, `README.md`, `INDEX.md` - `decisions/0001`, `0003`, `0004`, `0005`, `0010`, `0011`, `0017`, `0023` - 69 `modules/<id>/runbook.md` files - Archived `state/L3/*` into `state/archive/2026-04-30-L0-L4-synthesis/` - Historical references under `docs/specs/` and `state/` - `state/strategy/autonomy-tiered-execution-design-2026-06-02.md` - `state/cutover/honcho-gemma-ollama-prep.md` ### Relevant context - Forgejo issue #727 - Sanitized #727 packet reviewed via Ollama Cloud and AntiGravity/`agy` - PRs #746/#747 already merged before this branch was created from fresh `main` ### Runtime evidence No runtime mutation. Docs-only repository change. ### Known constraints This touches `decisions/` and many module runbooks, so canary 3+3 is required by repo policy despite being docs-only. ### Explicit out-of-scope - No runtime/deploy changes - No secret-store reads - No resurrection of ADR-0008/0012/0014/0015 or dead directories - No status changes to ADR-0013 or ADR-0025 - No architectural implementation for the autonomy allowlist ### Requested decision Review as mechanical docs reconciliation and run full canary before merge. ### Merge blockers - Any remaining stale MAP pointer to phantom ADR/dead dirs - Any remaining Phase-02 runbook placeholder - Any live `state/L3` file treated as current state - Canary finding that a docs pointer now lies about current repo reality ## Model scout disclosure - Ollama Cloud was used on a sanitized #727 packet; DeepSeek-v4-pro returned a mechanical checklist and risks. - AntiGravity `agy --sandbox --print` was used on the same sanitized packet; Gemini returned a matching checklist and called out the ADR-0013/0025 and dead-link risks. - Raw model transcripts stayed local scratch only and were not committed. ## Verification ```bash git diff --check python3 -m json.tool state/archive/2026-04-30-L0-L4-synthesis/entities.json rg -n 'STATUS_NOW is currently stale|INDEX\.md \(module catalog\)|docs/runbooks|ADR-00(08|12|14|15)|contracts/|docs/domains/|docs/onboarding/|docs/phase-07/|docs/hermes/|docs/sunset-proposals/' MAP.md || true rg -l 'TODO Phase 02: pull from L3/OPEN_LOOPS\.md if any apply' runbooks modules -g 'runbook.md' | wc -l rg -n 'OPEN_LOOPS-2026-05-23|ADR 0001 through 0018' README.md INDEX.md MAP.md decisions docs state modules runbooks || true find state/L3 -maxdepth 1 -type f -print | sort ``` Observed: - `git diff --check` clean - `entities-json-ok` - MAP forbidden-pattern scan returned no matches - runbook placeholder count: `0` - stale snapshot/range scan returned no matches - `state/L3` has no tracked files; archived files are under `state/archive/2026-04-30-L0-L4-synthesis/` ## Spec sources read - Forgejo issue #727: scope and acceptance - `docs/forgejo-agent-operations.md`: write/PR identity contract - `MAP.md`: target stale pointers and phantom references - `README.md`, `INDEX.md`: stale navigation targets - ADR files `0003`, `0004`, `0005`, `0010`, `0011`, `0017`, `0023`; plus `0001` only to keep a moved L3 reference non-broken - `state/strategy/autonomy-tiered-execution-design-2026-06-02.md` - `state/cutover/honcho-gemma-ollama-prep.md` and `state/cutover/honcho-closeout-plan.md` - module runbook files matched by the exact Phase-02 placeholder scan Closes #727

codex added 1 commit

2026-06-08 15:27:04 +02:00

docs(deslop): reconcile stale platform docs

canary-required / collect-diff (pull_request) Successful in 4s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 22s

Details

canary-required / canary (pull_request) Successful in 14s

Details

base-is-main / guard (pull_request) Successful in 2s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 5s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / dry-run (pull_request) Successful in 20s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 21s

Details

e589813646

codex added the

tier/full

label

2026-06-08 15:27:26 +02:00

patchwarden commented

2026-06-08 15:28:38 +02:00

First-time contributor

Patchwarden PR sanity

Status: eligible_sanity_clean
PR: 748
Commit: e5898136468c24f9ccd16f382d925bc831d2b684
Security-sensitive label: missing
Authority: advisory model review plus deterministic blockers only
3+3 canary: still alive; this does not replace it

Deterministic findings

info sensitive-path-touched Sensitive path touched — decisions/0001-canary-mandatory-pm-cadence.md
- Evidence: decisions/0001-canary-mandatory-pm-cadence.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0003-agent-access-plane.md
- Evidence: decisions/0003-agent-access-plane.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0004-iskra-tool-telemetry-jsonl-boundary.md
- Evidence: decisions/0004-iskra-tool-telemetry-jsonl-boundary.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0005-agent-coordination-lanes.md
- Evidence: decisions/0005-agent-coordination-lanes.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0010-cousin-role-taxonomy.md
- Evidence: decisions/0010-cousin-role-taxonomy.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0011-domain-promotion-policy.md
- Evidence: decisions/0011-domain-promotion-policy.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0017-no-stacked-prs-to-main.md
- Evidence: decisions/0017-no-stacked-prs-to-main.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.
info sensitive-path-touched Sensitive path touched — decisions/0023-gemini-3-5-flash-reviewer-cousin.md
- Evidence: decisions/0023-gemini-3-5-flash-reviewer-cousin.md
- Next: Route through the existing 3+3/risk-tier process; model review remains advisory.

Model reviewers

`global-glm` / `glm-5.1:cloud`

Status: skipped
Verdict: -
Note: Diff exceeds PR sanity model-review budget; deterministic report only.
Findings: none

`global-deepseek` / `deepseek-v4-pro:cloud`

Status: skipped
Verdict: -
Note: Diff exceeds PR sanity model-review budget; deterministic report only.
Findings: none

`redteam` / `kimi-k2.6:cloud`

Status: skipped
Verdict: -
Note: Diff exceeds PR sanity model-review budget; deterministic report only.
Findings: none

Policy notes

GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
Auto-merge is not enabled here.

# Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `748` - Commit: `e5898136468c24f9ccd16f382d925bc831d2b684` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0001-canary-mandatory-pm-cadence.md` - Evidence: `decisions/0001-canary-mandatory-pm-cadence.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0003-agent-access-plane.md` - Evidence: `decisions/0003-agent-access-plane.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0004-iskra-tool-telemetry-jsonl-boundary.md` - Evidence: `decisions/0004-iskra-tool-telemetry-jsonl-boundary.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0005-agent-coordination-lanes.md` - Evidence: `decisions/0005-agent-coordination-lanes.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0010-cousin-role-taxonomy.md` - Evidence: `decisions/0010-cousin-role-taxonomy.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0011-domain-promotion-policy.md` - Evidence: `decisions/0011-domain-promotion-policy.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0017-no-stacked-prs-to-main.md` - Evidence: `decisions/0017-no-stacked-prs-to-main.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. - **`info` `sensitive-path-touched`** Sensitive path touched — `decisions/0023-gemini-3-5-flash-reviewer-cousin.md` - Evidence: `decisions/0023-gemini-3-5-flash-reviewer-cousin.md` - Next: Route through the existing 3+3/risk-tier process; model review remains advisory. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `skipped` - Verdict: `-` - Note: Diff exceeds PR sanity model-review budget; deterministic report only. - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `skipped` - Verdict: `-` - Note: Diff exceeds PR sanity model-review budget; deterministic report only. - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `skipped` - Verdict: `-` - Note: Diff exceeds PR sanity model-review budget; deterministic report only. - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.