Harness foundation: INTENT, ADR-001, architecture, prototype adoption
- INTENT.md: three-layer model (blueprint/instance/harness), single shared runtime, never-become boundaries - ADR-001 (accepted): DEC-2026-002 resolution — one harness repo for all projects; instances are declarative state in consuming repos - docs/architecture.md: components, contracts (manifest, tool profiles, completion events, credential lanes), deployment shape - agent_harness/: executor-worker prototype adopted and renamed (6/6 tests green); HARNESS-WP-0001 initial workplan (7 tasks) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
87ae78c56a
commit
cfc1b75157
18 changed files with 1204 additions and 1 deletions
10
agent_harness/__init__.py
Normal file
10
agent_harness/__init__.py
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
"""Thin executor worker (BINKY-WP-0004-T04, DEC-2026-002).
|
||||
|
||||
activity-core schedules and emits tasks; this worker executes exactly one
|
||||
task per invocation: load persona orientation (kaizen-agentic schedule
|
||||
prepare), run a bounded agentic coding session via an llm-connect adapter,
|
||||
verify the session committed to the target repo, and report to the
|
||||
Custodian State Hub (progress event + optional task close).
|
||||
"""
|
||||
|
||||
__version__ = "0.1.0"
|
||||
Loading…
Add table
Add a link
Reference in a new issue