foundation-models-adapter-toolkit-ops.git · PLANS.md

foundation-models-adapter-toolkit-ops.git / PLANS.md

revision 44dc547a9ad2c4297bb2abecd87a61710b7e10fd · complete file

# PLANS.md

This file defines the intent protocol for multi-step or high-risk work in this repository.

## When a Plan Is Required
Create or update a plan before changes when work is:
- Multi-step (more than a small, single-file fix).
- Cross-cutting (touches multiple subsystems or repositories).
- High-risk (policy/compliance changes, release-impacting behavior, or distribution controls).
- Safety sensitive (permissions, credentials, or legal/compliance obligations).

## Plan Format (Template)
Use this structure and keep it concise:

Title:
Goal:
Scope:
Non-goals:
Constraints:
Risks:
Plan:
- Step 1 (status: pending | in_progress | done) - intent
- Step 2 (status: pending | in_progress | done) - intent
Validation:
- How you will confirm success (checks, tests, manual verification)

## Acceptance Criteria
- The plan states intent and scope clearly.
- Steps are minimal and ordered.
- Validation is explicit and feasible.
- Deviations are recorded and justified.

---

Title: Initial bootstrap (FCIS-compliant toolkit ops repo)
Goal: Establish a private, FCIS-compliant operations repository for Apple toolkit bootstrap without redistributing Apple Software.
Scope: FCIS baseline files, compliance audit docs, and local toolkit verification/link scripts.
Non-goals: Hosting Apple toolkit bundles or model assets.
Constraints: Keep Apple software out of git; preserve FCIS layer orthogonality.
Risks: Accidental artifact commit; mitigate via `.gitignore` and verification scripts.
Plan:
- Step 1 (status: done) - Create FCIS baseline files (`AGENTS.md`, `PLANS.md`, skill).
- Step 2 (status: done) - Add scripts for local toolkit verification and local symlink wiring.
- Step 3 (status: done) - Add compliance docs (`FCIS_AUDIT.md`, `FCIS_COMPLIANCE_PLAN.md`).
Validation:
- Run `./scripts/fcis_check.sh`
- Run `./scripts/verify_toolkit.sh <local-toolkit-path>`