zara-coding: bind symbolic tasks to fresh repository identity #161

New issue

Closed

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

nsaspy commented

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

Owner

Problem

coding.task.create currently persists goals/constraints/criteria in Prolog but does not bind the task to an allowed repository identity. That leaves symbolic state context-free even though #1 requires coding requests to be repository/worktree-bound.

Required slice

deterministic RED proving task creation requires/accepts one repository path and captures it only through the existing bounded RepositoryInspector;
persist canonical repository root, exact HEAD, and branch in Prolog-owned task state;
fail closed when repository inspection is unavailable or the repository identity cannot be validated;
do not trust caller-supplied HEAD/branch and do not add execution authority;
task get returns the retained repository identity unchanged across protocol operations;
update README contract;
full zara-coding tests, registry/source/install compatibility, nix flake check, and generated package builds.

This advances #1 locally and does not bypass Core #400. Worktree-specific ownership remains a later slice.

## Problem `coding.task.create` currently persists goals/constraints/criteria in Prolog but does not bind the task to an allowed repository identity. That leaves symbolic state context-free even though #1 requires coding requests to be repository/worktree-bound. ## Required slice - deterministic RED proving task creation requires/accepts one repository path and captures it only through the existing bounded `RepositoryInspector`; - persist canonical repository root, exact HEAD, and branch in Prolog-owned task state; - fail closed when repository inspection is unavailable or the repository identity cannot be validated; - do not trust caller-supplied HEAD/branch and do not add execution authority; - task `get` returns the retained repository identity unchanged across protocol operations; - update README contract; - full zara-coding tests, registry/source/install compatibility, `nix flake check`, and generated package builds. This advances #1 locally and does not bypass Core #400. Worktree-specific ownership remains a later slice.

nsaspy closed this issue

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