Skip to content

wip(dns): S7C protected resolver driver (resolvconf + resolved) — design only - #71

Merged
AetherAI3 merged 10 commits into
mainfrom
lane/s7c-dns
Sep 22, 2026
Merged

AetherAI3 merged 10 commits into
mainfrom
lane/s7c-dns

Conversation

@AetherAI3

Copy link
Copy Markdown
Owner

Outcome: WIP, design contract only (session closed before implementation). Stacked on #64 (lane/s5-driver @ 9717079); will be rebased after #64 merges.

What changed: docs/driver-dns.md — binding, probe keys, reason codes, snapshot layout, durable ownership, apply/verify/rollback/recover semantics, planned tests and mutations.

Not done: adapters/dns/resolver package (driver, resolvconf + resolved backends, fake runner, conformance, fault/tamper/captive-portal/netns tests), mutations.

Safety boundary: no host files touched; doc only.

Verification: none (no Go code).

🤖 Generated with Claude Code

AetherAI3 and others added 9 commits August 23, 2026 11:15
Add agent/driver with the ProbeResult type, the Prober interface, shared
AF-PROBE reason codes, validation bounds, and a deterministic SHA-256 digest.
A ProbeResult is evidence produced by driver code on the node; it is never
accepted from a caller, plan, manifest file, or the network. The digest layout
is pinned by test so a layout change cannot silently re-identify stored
manifests and receipts.

This file is the single cross-lane contract for the capability-discovery,
driver-contract, and host-driver lanes; it is frozen at schema version 1.
…rvation floor, store/journal conformance runners, journal compaction
Incomplete: adapters/dns/resolver package, backends, tests, netns proof, mutations.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@AetherAI3
AetherAI3 marked this pull request as ready for review September 21, 2026 23:26
@AetherAI3
AetherAI3 merged commit af8be1c into main Sep 22, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant