You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Narrow the front-door docs, roadmap, and ADR 0032 language to what the repo can currently prove. Keep owner friction as real evidence only, with a lighter capture path and stricter closure semantics.
Constraint: Harness-first direction descopes external adoption and broad daily-driver claims from current truth until real owner or external evidence exists.
Rejected: Simulated owner friction or adoption proof | would repeat the closed-loop evidence problem this direction pass is trying to stop.
Confidence: high
Scope-risk: narrow
Directive: Do not cite aspirational adoption, hosted/team expansion, or simulated pilots as current roadmap evidence without a new evidence source.
Tested: .venv/bin/python -m pytest tests/test_docs_consistency.py -q; .venv/bin/python scripts/validate_event_spine_wiring.py; .venv/bin/python -m pytest tests/integration/test_audit_sink_isolation.py -q; .venv/bin/python -m pytest tests/acceptance/test_hook_lifecycle_flow.py -q; .venv/bin/python -m pytest tests/test_event_spine_wiring.py tests/lifecycle/test_run_event_spine.py -q; .venv/bin/python scripts/validate_docs_consistency.py; .venv/bin/python scripts/detect_stale_plans.py; git diff --check
Not-tested: Full repository test suite.
> **Direction record:**[Harness-First Direction](docs/strategy/harness-first-direction-2026-06-13.md) (owner-operator harness-first current direction)
6
6
7
7
A personal, local-first governance harness for autonomous coding tasks — built by and for the owner-operator who maintains, uses, and audits his own runs. Thin orchestration layer with tool governance, state boundaries, audit logging, and destructive-tool approval.
Copy file name to clipboardExpand all lines: docs/INDEX.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ follow dated evidence documents only when you need the reasoning trail.
12
12
13
13
| Need | Start here | Status rule |
14
14
| --- | --- | --- |
15
-
| What can a daily user trust today? |[Daily-Driver Current Status](daily-driver-current-status.md)| Current truth; update whenever TUI, chat, agent mode, approval, cost, undo, or resume behavior changes. |
15
+
| What can the owner-operator trust today? |[Daily-Driver Current Status](daily-driver-current-status.md)| Current truth for owner-operated daily use; update whenever TUI, chat, agent mode, approval, cost, undo, or resume behavior changes. |
16
16
| What is the current documentation-state assessment? |[Documentation State Review](analysis/documentation-state-review-2026-06-04.md)| Current dated evidence for corpus shape, drift risks, and consolidation priorities. |
17
17
| What is the documentation operating model? |[Documentation Operating Model](governance/documentation-operating-model-2026-06-04.md)| Governance rulebook for claim types, TTL, owners, supersession, and CI guard targets. |
18
18
| What should be done next? |[Work Direction Execution Index](plans/work-direction-execution-index-2026-06-10.md)| Sprint 1 truth pass (WDA-001, WDB-001, WDB-003, WDG-001/002) after the June 10 critical review. |
@@ -45,15 +45,16 @@ governance ledgers should prefer the canonical set above.
45
45
46
46
| Question | Canonical source |
47
47
| --- | --- |
48
-
| Current daily-driver behavior |[Daily-Driver Current Status](daily-driver-current-status.md)|
48
+
| Current owner-operated daily behavior |[Daily-Driver Current Status](daily-driver-current-status.md)|
|Daily-driver critique and counterarguments |[Daily-Driver Critique And Counterarguments](reviews/daily-driver-critique-and-counterarguments-2026-06-04.md)|
|Historical daily-driver critique and counterarguments |[Daily-Driver Critique And Counterarguments](reviews/daily-driver-critique-and-counterarguments-2026-06-04.md)|
| Trust and audit whitepaper |[Trust and Audit Whitepaper](governance/trust-and-audit-whitepaper.md)|
114
115
| When not to use TeaAgent |[When Not to Use TeaAgent](guides/when-not-to-use-teaagent.md)|
@@ -137,7 +138,7 @@ governance ledgers should prefer the canonical set above.
137
138
|[Work Direction Decomposition](plans/work-direction-decomposition-2026-06-10.md)| Full WD-A … WD-H backlog with acceptance gates. |
138
139
|[Documentation Optimization Master Plan](plans/documentation-optimization-master-plan-2026-06-04.md)| Prioritizing documentation work by stability, UX, risk, and ROI. |
139
140
|[Documentation Optimization Work Items](work-log/documentation-optimization-work-items-2026-06-04.md)| Concrete task execution ledger. |
140
-
|[Daily-Driver Complete Work Plan](plans/daily-driver-complete-work-plan-risk-roi-2026-06-04.md)|Daily-driver risk, feasibility, ROI, and sequence. |
141
+
|[Daily-Driver Complete Work Plan](plans/daily-driver-complete-work-plan-risk-roi-2026-06-04.md)|Historical daily-driver risk, feasibility, ROI, and sequence; use harness-first direction for current persona claims. |
141
142
|[Roadmap Work Items](work-log/roadmap-work-items-2026-06-04.md)| Product roadmap work items and acceptance criteria. |
142
143
|[Phase 0 Priority Work Items](work-log/phase-0-priority-work-items-2026-06-04.md)| Trust-repair tasks derived from project-state review. |
143
144
|[Phase 0 Governance Closure Report](work-log/phase-0-governance-closure-report-2026-06-04.md)| Closure evidence for coverage omit, dependency audit, and ADR-state governance. |
- Each wrapped in try/except (exception logged via logging module, never propagates)
84
-
- Never affect the run (crash-safe)
85
+
- Each wrapped in try/except by default (exception logged via logging module)
86
+
- Non-critical consumers never affect the run (crash-safe)
87
+
- Critical consumers may propagate when their side effect is part of the
88
+
required safety boundary, such as compliance-mode audit durability
85
89
- Used for side effects and derived state
86
90
87
91
### 4. HookRegistry Alignment
88
92
89
-
Existing Claude-Code hook names (SessionStart, PreToolUse, PostToolUse, etc.) are preserved as **aliases** to RunEventType members where semantically equivalent (e.g., PRE_TOOL_USE ← PreToolUse). The public hook API (teaagent/hooks.py) will be re-homed onto the spine in a later migration step (M5).
93
+
Existing Claude-Code hook names (SessionStart, PreToolUse, PostToolUse, etc.) remain the public `teaagent/hooks.py` API. The spine taxonomy includes semantically equivalent typed hook-observability events (for example, `PRE_TOOL_USE`) so later integration can bridge the public hook API without changing hook names.
90
94
91
95
### 5. Compliance with ADR 0030
92
96
@@ -210,7 +214,7 @@ belonged on the spine.
210
214
211
215
```
212
216
RUN_STARTED # Run begins; payload: run_id, task, model, etc.
PRE_TOOL_USE # Hook: before tool execution (alias: PreToolUse)
238
-
POST_TOOL_USE # Hook: after tool execution (alias: PostToolUse)
239
-
PRE_COMPACT # Hook: before context compaction (alias: PreCompact)
241
+
PRE_TOOL_USE # Hook observability: before tool execution; public hook: PreToolUse
242
+
POST_TOOL_USE # Hook observability: after tool execution; public hook: PostToolUse
243
+
PRE_COMPACT # Hook observability: before context compaction; public hook: PreCompact
240
244
```
241
245
242
246
The M0 spike covers RUN_STARTED, ITERATION_STARTED, TOOL_CALL_REQUESTED, TOOL_CALL_COMPLETED, TOOL_CALL_FAILED, RUN_COMPLETED, RUN_FAILED. Extended events are added in later phases as gates migrate.
0 commit comments