Fountain-Store.git · FCIS_COMPLIANCE_PLAN.md

Fountain-Store.git / FCIS_COMPLIANCE_PLAN.md

revision d7dcdabf002c8a4e013b7d86601b9ae0195f5576 · complete file

# FCIS Compliance Plan (RFC 0001)

## Goal and scope
Make Fountain-Store's instruction system compliant with FCIS RFC 0001 by establishing AGENTS/PLANS/skills layers, relocating runbooks, and updating references. No product behavior changes or dependency changes.

## Minimal-change strategy
- Preserve existing guidance by moving it to the correct layer.
- Keep edits limited to instruction files and doc references.
- Avoid touching source code, tests, or build configuration.

## Phased plan with acceptance criteria

### Phase 0: Safety (no behavior change)
- Files: `FCIS_AUDIT.md`, `FCIS_COMPLIANCE_PLAN.md`.
- Edits: add audit and compliance plan artifacts only.
- Acceptance: audit and plan docs exist; no code or build changes.

### Phase 1: Establish required files/structure
- Files: `AGENTS.md`, `PLANS.md`, `.codex/skills/fountainstore-dev-commands/SKILL.md`.
- Edits:
  - Create `AGENTS.md` with invariants and routing (no procedures).
  - Create `PLANS.md` with the long-task intent protocol and acceptance criteria template.
  - Create a skill for build/test commands with purpose, when-to-use, steps, and output contract.
- Acceptance:
  - `AGENTS.md` references `PLANS.md` for multi-step/high-risk work.
  - At least one skill exists for procedural commands.

### Phase 2: Refactor content for orthogonality
- Files: `AGENTS.md`, `README.md`, `docs/LEGACY/ARCHITECTURE.md`, `docs/PROJECT_STATUS.md` (if needed).
- Edits:
  - Move procedural "Commands" content from `AGENTS.md` into the new skill.
  - Relocate milestone/directory guidance into product docs (or remove if already captured) and keep `AGENTS.md` declarative.
  - Update references that point to `agent.md` to point to `AGENTS.md` (and skills where appropriate).
- Acceptance:
  - No runbooks remain outside skills.
  - `AGENTS.md` contains only behavioral law and routing.
  - References to Codex instructions resolve to FCIS layers.

### Phase 3: Validation and enforcement notes
- Files: `FCIS_AUDIT.md`, `FCIS_COMPLIANCE_PLAN.md` (update status if needed).
- Edits:
  - Re-scan for instruction spillover keywords and confirm orthogonality.
  - Note any N/A items with justification.
- Acceptance:
  - Compliance matrix updated with PASS/PARTIAL/FAIL post-remediation.
  - No MCP workflow dependency introduced.