docs(v0.3): add ADR-0013 + ADR-0014 + cross-links#269
Merged
Conversation
…raph extraction model gate) + cross-links ADR-0013 — per-agent allow-list at /etc/hal0/agents/<name>.toml; default-deny on server + tool axis; three-tier classification (allow/gated/blocked); filesystem sandbox at /var/lib/hal0/agents/<name>/workspace; ADR-0004 approval-queue integration. Resolves PLAN §1 stream #5 ships-when "at least one MCP-client external source connectable from a bundled agent". ADR-0014 — supersedes ADR-0005 §6 graph bullet. Cognee graph extraction defaults OFF in v0.3; opt-in via dashboard toggle with typed route enum (upstream / primary / agent). Privacy disclosure copy is part of the contract. Eval suite deferred to v0.4. Resolves PLAN §1 stream #5 ships-when "configurable model" requirement. Cross-links: - ADR-0011 Related header now points at ADR-0013 (card schema v2+ may surface a derived allowed_tools projection from the allow-list). - ADR-0005 §6 graph bullet now points at ADR-0014 as the settled v0.3 decision. PLAN.md already references ADR-0013 / ADR-0014 (via #268). Tracker issues #257-#260 + #265 + #261-#264 link these ADR files; landing the files closes the broken-link. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Both ADRs were drafted + accepted on 2026-05-23 while PR #268's cascade was in flight; PR #268 already references both files in PLAN.md (lines 44–47, 341, 348, 1052) but the files themselves only exist locally until this PR lands.
Why now
Tracker issues #257–#260 (ADR-0014 implementation), #265 (v0.4 eval suite), and #261–#264 (ADR-0013 implementation) all link these ADR files. They're broken links until this PR merges.
Test plan
ADR-0012references to my old number (renumbered to ADR-0014 after PR docs(v0.3): ADR-0012 + CHANGELOG + version bump + auth test fixup (Slice D) #267 took the 0012 slot for the auth-removal ADR)🤖 Generated with Claude Code