zara-coding: freeze completed symbolic task state #170

New issue

Closed

opened 2026-09-08 02:03:07 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-08 02:03:07 +00:00

Owner

Follow-up slice under #1.

Completed symbolic coding tasks currently remain mutable: verification evidence can be appended after completion and completion can be requested repeatedly. Completion should be a terminal state so verification evidence and state cannot drift after the decision boundary.

Acceptance:

deterministic RED proving evidence mutation after completion is rejected
deterministic RED proving repeated completion is rejected
completed task and evidence remain unchanged
explicit task-already-completed rejection
focused tests + registry validator + source/install compatibility + nix flake check + package builds
no Core changes or private cross-plugin runtime

Follow-up slice under #1. Completed symbolic coding tasks currently remain mutable: verification evidence can be appended after completion and completion can be requested repeatedly. Completion should be a terminal state so verification evidence and state cannot drift after the decision boundary. Acceptance: - deterministic RED proving evidence mutation after completion is rejected - deterministic RED proving repeated completion is rejected - completed task and evidence remain unchanged - explicit `task-already-completed` rejection - focused tests + registry validator + source/install compatibility + `nix flake check` + package builds - no Core changes or private cross-plugin runtime

nsaspy closed this issue

2026-09-08 02:03:07 +00:00