Repository navigation
docs(spec): harness principles for the runtime agent, adopted from ECC (CLEAN-150) - #24
Open
maksymhryzodub-prog wants to merge 4 commits into
Open
maksymhryzodub-prog wants to merge 4 commits into
maksymhryzodub-prog wants to merge 4 commits into
Conversation
…C (CLEAN-150) SpecKit specification fixing which ECC patterns the runtime adopts for every agent: deterministic guardrails around tool calls, lean always-on context with skills/tools on demand, confidence-weighted teachable memory, compaction at task boundaries, verified completion, delegation with a completion contract. Prioritized user stories, 30 functional requirements, measurable success criteria; ECC itself is not installed. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Spec Kit 0.16.5 skills under .claude/skills/speckit-*, the shared .specify/ templates/scripts/workflows (feature.json stays local), the .worktreeinclude list so .env files follow new worktrees, and .gitignore entries for the local second-agent runtime and .env.project. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…-150) Phase 0/1 artifacts from /speckit-plan: research decisions R1-R15 anchored to the loop, prompt, skill, session and task code; data model (rules, tool-call records, instincts with confidence bands, context budget, compaction checkpoint, Tool.effect, delegated worker); contracts for the new tools, operator commands, config and file formats; quickstart validation per user story. Two new agent slices (guard, instinct), the rest extends the slices that own the behaviour. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…les (CLEAN-150) 90 tasks across setup, foundation, six user-story phases and polish; tests first per phase, file paths per task, one PR and ticket per story. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 12, 2026
feat(loop): verified completion and delegation with a completion contract (CLEAN-156, CLEAN-157)
#30
Open
maksymhryzodub-prog
added this pull request to stack #32
October 12, 2026 15:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
SpecKit specification
specs/001-ecc-agent-principles/spec.md: which patterns from ECC the runtime adopts globally, for every agent built on it, written as prioritized user stories with testable requirements and measurable success criteria.Out of scope: installing ECC (it is a Claude Code plugin), its catalog, Memory Vault / Control Pane / AgentShield.
Sources read: ecc.tools, README,
hooks/hooks.json,continuous-learning-v2,strategic-compact,verification-loop,rules/common/{agents,performance,security,hooks,coding-style}.md.Why
The runtime is itself an agent harness; today its safety and behaviour live in prompt text (50–80% reliable by ECC's numbers), the admin identity file is already truncated at its size cap, and learned notes accumulate without weight or pruning. The spec sharpens existing roadmap items (#4 curator, #6 delegation, #10 safety, #15 hooks) and orders them.
Next
/speckit-planon this spec → implementation tickets per user story.Jira: https://dreamvention.atlassian.net/browse/CLEAN-150
🤖 Generated with Claude Code