[adrianwebb]

Outcome

Require small, cohesive TypeScript capability layers and contextual refactoring in AGENTS.md and release-workflow. Add a development-only checker for twenty canonically formatted body lines, compressed statements, exact baseline debt and reviewed exception records.

Work authority

• Work item / Issue: Part of chore: require readable capability layers and contextual refactoring #102; portfolio feat: deliver seed-driven Agent Capacity Provider infrastructure platform#773.
• Proposal / decision: Maintainer-approved seed-driven Task 3D plan; critical readability policy is the first independent delivery.
• Assignment / checkpoint: Shared policy/helper candidate; runtime implementation remains separate.
• Actor: OpenAI Codex desktop agent in the maintainer-directed migration chat.
• Human authority: @adrianwebb.
• Agent / capacity provider: OpenAI Codex desktop; TreeSeed real Work/model execution remains Task 10.
• Exact base ref: cordis at 96eda9606e5679cbc03b352339fd22ece68941c2.
• Exact head ref: feature/102-readable-capabilities at 6948442b75905589f5bcd692ac206d9ef55ec98c.

Contributor mode:

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Documentation first, actual helper-program cases, canonical formatter/AST enforcement, normal owner wiring, immutable Git baseline read-back, complete owner checks and current-head CI. 9 candidate files; no runtime implementation in this PR.

Changes and commits

Documentation was committed first, followed by outside-in program specifications and implementation. Canonical measurement uses exact prettier@3.6.2. Baseline fingerprints are read back against the verified origin/cordis Git tree; changed methods cannot add baseline debt. Exceptions bind file/symbol/source hash/reason/issue, become stale after changes and still require review. The helper and instruction block are identical across owners; project-specific instructions/licenses remain preserved. Native Cordis and strict class rules remain binding.

Normal checks and CI run the actual helper; checkout retains Git history for provenance. Existing runtime source and frozen archive bytes are unchanged.

Verification

• Existing semantic checker accepted compressed behavior before this gate; control guidance lacked all five new obligations.
• Ten actual checker-program cases cover unchanged/new/changed methods, compressed layout, baseline tampering, exact/stale/unused exceptions, constructors/accessors and declarative data.
• Normal owner check and class/layout verification passed locally.
• Full local owner verify passed: 45 cases (17 acceptance, 10 regression, 12 integration, 6 unit).
• Canonical helper checks itself and exact copied rule blocks match across all nine owners.
• Current-head owner verification read back: run 40577738848 succeeded, including the applicable owner acceptance gates. This development-only change does not qualify the unfinished capacity runtime.
• Maintainer review, including any explicit exception review.

Risk and rollback

Revert this exact change through an issue branch if needed; preserve immutable baseline provenance rather than advancing it to grandfather feature code. This is development tooling, never a runtime dependency on target instructions. Existing Agent/Deployment drafts and SDK PR #483 are retained. No merge, legacy source/service change, production release, cutover or issue closure is authorized. Keep every issue including Platform #678 open.

Completion summary

The critical guidance, copied checker, exact baseline and CI wiring are implemented. Normal checks pass locally. Verification state and remaining runtime/CI/review gates are recorded above; this is a policy review candidate, not Task 3D runtime completion or merge authorization.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.