ICW Implementation Plan — E6:S07:T115 last-modified stamp forensic integrity guardrails
Plan
Phase 1 — Contract and policy locking
- Publish normative timestamp semantics (
substantivevsnon_substantive) in governance docs. - Specify immutable behavior for rewrite-only board operations.
- Define source-of-truth evidence hierarchy for timestamp derivation.
Phase 2 — Workflow guardrail implementation design
- Add classification layer in board update paths before stamp mutation.
- Gate mutation behind substantive-evidence checks.
- Add anomaly detection for mass stamp churn without source deltas.
- Add integrity audit counters to UKW/RW output summaries.
Phase 3 — Verification and regression
- Add targeted tests for no-op rewrite stability.
- Add tests for legitimate substantive updates.
- Add tests for anomaly detection behavior.
- Validate canonical + alias board paths behave identically.
Risks and Mitigations
- Risk: Overly strict gating suppresses legitimate updates.
- Mitigation: define explicit positive evidence categories and allow-list transitions.
- Risk: Existing workflows depend on rewrite-driven timestamps.
- Mitigation: introduce clear migration note and validator diagnostics before enforcement hardening.
- Risk: Drift between policy text and script behavior.
- Mitigation: require validator-backed checks plus regression tests as release gates.
Completion Definition
Task is implementation-ready complete when policy is explicit, guardrail design is codified, and tests/validators demonstrate rewrite-only operations do not alter row timestamps.