--- schema_version: 1.0.0 id: draft-run-worker-plan-010-2026-09-05 type: founder-narrative-draft from_agent: FYJ Narrator to_agent: FYJ Verifier contract_version: OC-C-1.0.0 updated_at: 2026-09-05T19:59:45Z updated_by_run: narrator-repair-plan-010-trace-2026-09-05 snapshot_id: assessor-plan-010-2026-09-05T19:58:01Z source_verdict: /workspace/fyj-claude/state/handoffs/run-worker-plan-010-2026-09-05-verdict.json assessed_evidence: - EV-plan-010-proposed-rule requirement_ref: REQ-V1 rule_ref: RULE-V1-worker-lock-read-receipt status: pending-verifier-after-trace-repair publish: false --- # Proposed rule: future hours can prove they start from the vision lock **What changed.** Assessor graded a drafted rule that would require Workers to read the vision lock and leave a receipt before other work. The rule is **proposed only** — not switched on, not mid-flight activated. Hours are still **not** demonstrated to start from the lock. Locked vision remains unmet (`exit_met` false). **Why it matters.** You now have a concrete path to make “hour starts from the lock” provable later. Treating the proposal as already live would invent compliance. **Next (recommendation — not done).** Activate this rule only via a contract version bump at the Europe/London **day boundary** (not mid-flight), then collect Assessor-gradable receipt evidence across runs. Until then, do not narrate hours as already starting from the lock. Floor/accept still also wait on your reply. **Links (agent record / assessed sources).** - Assessor verdict: [`run-worker-plan-010-2026-09-05-verdict.json`](/workspace/fyj-claude/state/handoffs/run-worker-plan-010-2026-09-05-verdict.json) (`requirement_effects.REQ-V1.exit_met` false; `operational_hour_starts_from_lock` “not demonstrated”; `rule_status_verified` “proposed”; `mid_flight_activation` false) - Rule object: `RULE-V1-worker-lock-read-receipt` status `proposed`, `activated_at` null — [`rules.json`](/workspace/fyj-claude/state/rules.json) - Assessed evidence: `EV-plan-010-proposed-rule` in [`evidence.json`](/workspace/fyj-claude/state/evidence.json) - In [`requirements.json`](/workspace/fyj-claude/state/requirements.json): `REQ-V1` status `blocked`; `exit_met` false (field present); assessment_note currently records PLAN-011 BLOCKED packaging (`RULE-V1 not activated` among unmet items) — proposed/mid-flight status is on [`rules.json`](/workspace/fyj-claude/state/rules.json) (`status` proposed, `activated_at` null) and the Assessor verdict (`rule_status_verified` / `mid_flight_activation`), not that note’s PLAN-010 phrasing --- snapshot_id: assessor-plan-010-2026-09-05T19:58:01Z Narrator run: narrator-repair-plan-010-trace-2026-09-05 (TRACE repair after veto) Contract: OC-C-1.0.0 — draft only; no publish without Verifier pass. Rule not narrated as active.