|
| 1 | +version: 0.1.0 |
| 2 | + |
| 3 | +# Decision Log |
| 4 | + |
| 5 | +This file records project-level decisions and rationale. |
| 6 | + |
| 7 | +* 2025-12-14: Initial placeholder decision log added to satisfy governance checks. |
| 8 | +Decision Log |
| 9 | + |
| 10 | +This file records major governance decisions and rationale for the ShieldCraft |
| 11 | +project. It exists to satisfy governance artifact checks used by the engine's |
| 12 | +test suite and CI. No production semantics are contained here; it is intentionally |
| 13 | +minimal for CI verification. |
| 14 | +# RFC Decision Log |
| 15 | + |
| 16 | +Authoritative decisions made on 2025-12-13 (Phase 13 kickoff). All decisions recorded are spec-only; implementation requires separate PRs referencing RFC approvals. |
| 17 | + |
| 18 | +## rfc-generator-version-contract.md |
| 19 | +- Decision: APPROVE |
| 20 | +- Rationale: A strict generator lockfile and `metadata.generator_version` requirement enforce reproducibility and CI safety. Explicit `generator_version` reduces surprises in preflight and ensures traceability. |
| 21 | +- Effective scope: Spec-only; requires linter/migration guidance and CLI flags for a migration window. |
| 22 | +- Blocking dependencies: `generators/lockfile.json` management and CI upgrade; adoption plan must include a migration tool. |
| 23 | + |
| 24 | +## rfc-allowed-checklist-types.md |
| 25 | +- Decision: APPROVE (with migration guard) |
| 26 | +- Rationale: A canonical `type` enum prevents ad-hoc types and supports deterministic codegen and classification. |
| 27 | +- Effective scope: Spec-only (schema change); migration scripts and `--lenient-types` flag should be implemented in a follow-up PR. |
| 28 | +- Blocking dependencies: Adoption plan for migration, PRs to update schema and linter rules. |
| 29 | + |
| 30 | +## rfc-pointer-map-semantics.md |
| 31 | +- Decision: APPROVE |
| 32 | +- Rationale: Canonical id-based pointers for arrays improve readability and determinism; providing `raw_ptr` ensures backward compatibility for consumers of numeric indices. |
| 33 | +- Effective scope: Spec-only; requires pointer_map migration and test fixture updates. |
| 34 | +- Blocking dependencies: Migration scripts to map numeric pointers to canonical pointers, and update pointer_map consumers. |
| 35 | + |
| 36 | +## rfc-checklist-pointer-normalization.md |
| 37 | +- Decision: APPROVE |
| 38 | +- Rationale: Checklist extraction should include scalar leaf nodes and `requires_code` to enable correct codegen routing and ensure no items are inadvertently omitted. |
| 39 | +- Effective scope: Spec-only; affects checklist schema and generator preflight validation. |
| 40 | +- Blocking dependencies: Pointer map semantics RFC and allowed types RFC (to determine classification rules). |
| 41 | + |
| 42 | +## rfc-bootstrap-artifacts.md |
| 43 | +- Decision: APPROVE |
| 44 | +- Rationale: Clear bootstrap artifact emission semantics reduce ambiguity and ensure self-host runs produce predictable bootstrap outputs and `summary.json` for CI/instrumentation. |
| 45 | +- Effective scope: Spec-only; impacts self-host run contract and generator preflight. |
| 46 | +- Blocking dependencies: Allowed checklist types RFC (defines bootstrap types), pointer normalization RFC (ensures pointer mapping for bootstrap tasks). |
| 47 | + |
| 48 | +## Audit: Check for unambiguous decision status |
| 49 | +- All RFCs above are provided with explicit decisions and rationale. There are no implicit approvals. |
| 50 | +- Deferred RFCs: None. |
| 51 | + |
0 commit comments