Bootstrap fallow-ts governance #18

Closed
codex wants to merge 0 commits from codex/prewave-governance-bootstrap into main
Collaborator

Canary Context Pack

Product story

Before Wave 1 locks output contracts and fixtures, fallow-ts needs the same durable agent-governance anchor that made fallow-py resilient after context compaction. Issue #17 identified this as the first pre-wave blocker.

What changed

  • Expanded AGENTS.md from a bootstrap stub into a repo runbook for agents.
  • Added decisions/README.md.
  • Added ADR 0001 for harness identity.
  • Added ADR 0002 for the future three-bucket classification commitment.
  • Added ADR 0003 for schema naming direction before golden output lands.
  • Added ADR 0004 for mandatory non-author review.

Why it changed

Without these docs, future agents would have to reconstruct repo rules from chat scrollback and issue comments. That is exactly the drift pattern the fallow-py ADR convention prevents.

Files touched

  • AGENTS.md
  • decisions/README.md
  • decisions/0001-brand-identity-harness.md
  • decisions/0002-three-bucket-classification-commitment.md
  • decisions/0003-schema-naming-convention.md
  • decisions/0004-mandatory-non-author-reviewer.md

Relevant context

  • Refs #17
  • docs/roadmap.md
  • docs/next-steps.md
  • fallow-py ADR 0007, 0009, 0010, 0012

Runtime evidence

  • npm run build
  • npm test
  • git diff --check

Known constraints

This is a governance-only PR. It records target decisions and repo rules; it does not fix parser bugs or change the JSON schema yet.

Explicit out-of-scope

  • Parser fixes B1-B4 from #17.
  • Symlink/error handling hardening.
  • Deterministic root output.
  • Wave 1 issues #2-#6.

Requested decision

Approve and merge as the first pre-wave PR.

Merge blockers

Factual contradiction with the accepted roadmap, unclear governance obligations, or docs that claim source behavior this PR does not implement.

## Canary Context Pack ### Product story Before Wave 1 locks output contracts and fixtures, fallow-ts needs the same durable agent-governance anchor that made fallow-py resilient after context compaction. Issue #17 identified this as the first pre-wave blocker. ### What changed - Expanded `AGENTS.md` from a bootstrap stub into a repo runbook for agents. - Added `decisions/README.md`. - Added ADR 0001 for harness identity. - Added ADR 0002 for the future three-bucket classification commitment. - Added ADR 0003 for schema naming direction before golden output lands. - Added ADR 0004 for mandatory non-author review. ### Why it changed Without these docs, future agents would have to reconstruct repo rules from chat scrollback and issue comments. That is exactly the drift pattern the fallow-py ADR convention prevents. ### Files touched - `AGENTS.md` - `decisions/README.md` - `decisions/0001-brand-identity-harness.md` - `decisions/0002-three-bucket-classification-commitment.md` - `decisions/0003-schema-naming-convention.md` - `decisions/0004-mandatory-non-author-reviewer.md` ### Relevant context - Refs #17 - `docs/roadmap.md` - `docs/next-steps.md` - fallow-py ADR 0007, 0009, 0010, 0012 ### Runtime evidence - `npm run build` - `npm test` - `git diff --check` ### Known constraints This is a governance-only PR. It records target decisions and repo rules; it does not fix parser bugs or change the JSON schema yet. ### Explicit out-of-scope - Parser fixes B1-B4 from #17. - Symlink/error handling hardening. - Deterministic root output. - Wave 1 issues #2-#6. ### Requested decision Approve and merge as the first pre-wave PR. ### Merge blockers Factual contradiction with the accepted roadmap, unclear governance obligations, or docs that claim source behavior this PR does not implement.
Bootstrap fallow-ts governance
All checks were successful
CI / test (push) Successful in 14s
CI / test (pull_request) Successful in 13s
6228f6ccf0
Port the essential fallow-py agent governance into fallow-ts and record the first ADRs for harness identity, classification direction, schema naming, and mandatory non-author review.

Refs #17.

Verified:

- npm run build

- npm test

- git diff --check
codex closed this pull request 2026-05-17 01:17:25 +02:00
All checks were successful
CI / test (push) Successful in 14s
CI / test (pull_request) Successful in 13s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/fallow-ts!18
No description provided.