docs(structure): single Gates home and honest scaffold targets #56
Reference in New Issue
Block a user
Delete Branch "docs/structure-pass"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Docs on
mainare the product SoT, but the map made agents invent harness trees and fight UX sources. This pass lowers reader load without changing Gate A lock meaning.Scope
docs/checks/check-structure.shas a re-runnable structure pin.docs/IMPL-PLAN.mdonly. ThinAGENTS.md§0b to a pointer.docs/UX-DESIGN.mdas non-normative. Signeddocs/UX.mdwins on conflict. Listdeploy/INVENTORY.mdin AGENTS §0.frontend/e2e/,backend/tests/, and compose Dockerfiles as Phase 0 deliverable targets until code lands (docs/TEST-SPEC.md,docs/DEPLOYMENT.md,deploy/docker-compose.yml,README.md)..audit/docs-structure-pass.tsv.Out of scope: product lock text changes, app scaffold, gate-b code, verification skill.
Tradeoffs
Demoted UX-DESIGN instead of deleting or folding 486 lines. Keeps sketches available. Forces agents through signed UX first.
Blast Radius
Agents and humans reading
maindocs. Safe for locks: harness requires the same AGENTS lock phrases. Risk is incomplete restatement cleanup elsewhere (UAT/TEST-SPEC may still name gates in passing).Verification
Red baseline before edits failed ownership, UX demotion, Gates home, and TEST-SPEC honesty checks. Green after the four commits on
docs/structure-pass.Ship verdict (parent agent; local worktree + Gitea MCP).
VERDICT: PASS
2c73e5fNote: explore subagents do not receive gitea_mcp_for_ty. Use parent MCP or local git for Gitea PRs.