dongarandClaude Fable 5
94aa51135f
nisse-core's history becomes the repo root; the spec moves to docs/ at top level; nisse-dev and nisse-ops fold in as package directories, their seed histories (pointer files only) discarded. Pointer READMEs and CLAUDE.mds are rewritten for in-tree paths. Rationale: for a solo operator the three-repo split tripled admin surface (tokens, CI, webhooks, permissions, backups) and imposed a version-pinning contract on nisse-core, while the repo boundary was never a trust boundary — the VM is. The spec's Part H is updated in the next commit to record the decision. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
458 B
458 B
nisse-dev
The Dev Agent (Part B of the Nisse system). A thin application over the shared
nisse-core package.
Read the architecture before making design decisions here:
docs/Architecture-Build-Spec.md at the repo root. Part B specifies this agent;
Part A specifies the library contracts it depends on. Requirements that look like
free choices in this package — gating structure, state durability, LLM access
paths — are usually settled there.