midi-backplane.git · FCIS_COMPLIANCE_PLAN.md

midi-backplane.git / FCIS_COMPLIANCE_PLAN.md

revision 23efa75425f4663d06e8d1a64c85628a880a0462 · complete file

# FCIS Compliance Plan (RFC 0001)

## Goal & Scope
Bring the repository into FCIS compliance by adding required FCIS layers (AGENTS/PLANS/Skills) and relocating procedural command lists into the Skills layer. No behavior changes to code or tooling.

## Minimal-Change Strategy
- Add required FCIS files with declarative content only.
- Centralize existing procedural commands into a single skill.
- Update existing docs to point at the skill without removing substantive information.

## Phased Plan With Acceptance Criteria

### Phase 0: Safety (no behavior change)
- Files: `FCIS_AUDIT.md`, `FCIS_COMPLIANCE_PLAN.md`
- Exact edits: add audit and plan documents based on evidence only.
- Acceptance criteria: no runtime/schema/tooling behavior changes; only documentation added.

### Phase 1: Establish required files/structure
- Files: `AGENTS.md`, `PLANS.md`, `.codex/skills/repo-tooling/SKILL.md`
- Exact edits:
  - Create `AGENTS.md` with invariants and routing; require `PLANS.md` for multi-step/high-risk work.
  - Create `PLANS.md` as an intent/risks/acceptance-criteria template (no procedures).
  - Create a skill doc with purpose/when-to-use/steps/output contract for repo tooling commands.
- Acceptance criteria: AGENTS and PLANS exist at repo root; skill includes required sections; AGENTS references PLANS and skills.

### Phase 2: Refactor content for orthogonality
- Files: `README.md`, `tools/midi-schema-lint/README.md`, `tools/midi-schema-to-facts/README.md`
- Exact edits:
  - Move command lists into `.codex/skills/repo-tooling/SKILL.md`.
  - Replace procedural lists in README/tool docs with brief references to the skill.
  - Rephrase any numbered "workflow" lists as descriptive summaries if needed.
- Acceptance criteria: procedural command lists live only in the skill; AGENTS/PLANS remain declarative.

### Phase 3: Validation & enforcement notes
- Files: none (verification only)
- Exact edits: none; verify with manual checks.
- Acceptance criteria: FCIS matrix passes; no MCP workflow/policy in repo; no procedural steps in AGENTS/PLANS.