Skip to content

E3: document reviewed line-chain operations - #9

Merged
lr00rl merged 2 commits into
integrationfrom
docs/design18-e3-lawful
Aug 17, 2026
Merged

E3: document reviewed line-chain operations#9
lr00rl merged 2 commits into
integrationfrom
docs/design18-e3-lawful

Conversation

@lr00rl

@lr00rl lr00rl commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Outcome

  • document the final E3 semantic authority boundary: PatchSHA256 and server-issued ArtifactSHA256 bind approval and execution, while output file digests remain agent-journal evidence only
  • document durable ordering from exact leased task/protocol through recovery, resolve, result durability, acknowledgement, and outbox cleanup
  • record canonical official sing-box 1.13.18 lifecycle evidence and the final server/agent/plugin version matrix
  • preserve the existing lawful PR history and deliver the final docs commit by non-force fast-forward

Exact delivery

  • previous PR head: 6e9d98ac390050b1540f74cee629a6f399ce9af5
  • exact final docs head: a2ea2dc9890e5c54ccaea63e61f03641bc440ca2
  • target: integration
  • native Lore scan: commits_scanned=1 violations=0 physical=7 escaped=0 parsed=7

Verification

  • design index links docs/designs/design-18-line-chain-builder.md — PASS
  • semantic PatchSHA/ArtifactSHA authority and journal-only output digest wording — PASS
  • durable recovery/resolve/acknowledgement ordering — PASS
  • official sing-box 1.13.18 acceptance evidence — PASS
  • version matrix (alpha-0.2.1a38, semantic floor 0.2.2-alpha.19, node-agent 0.3.4-alpha.1, vpn-core alpha) — PASS
  • credential/URI/key/token canary scan — PASS
  • git diff --check — PASS
  • scripts/test-check-clean.sh — 5/5 PASS
  • clean final worktree — PASS

Boundaries

  • no merge, force push, signing, tag, release, publish, deployment, or fleet mutation

Record the E3 revision-9 public RPC, safety, status, compatibility, and operator recovery semantics so the implementation and operational surfaces share one review model.

Constraint: Documentation follows the stabilized plugin contract and remains alpha-only
Rejected: Document only the happy path | failed replace and remove must visibly preserve the committed edge
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep external vpn-core RPC names distinct from internal network/lines approval bindings
Tested: Markdown diff check, design index linkage, version matrix and credential-canary scans
Not-tested: Hosted docs rendering is outside this implementation lane
The operator contract now names semantic patch and artifact authority, durable Begin/Recover/Resolve/Ack ordering, and the strict canonical sing-box acceptance evidence.

Constraint: Output digests remain agent-journal evidence only
Rejected: Bind host output bytes into approval authority | unstable across runtime paths
Confidence: high
Scope-risk: narrow
Directive: Keep canonical evidence unsimulated and report exact revisions
Tested: git diff --check
Not-tested: rendered docs site
@lr00rl
lr00rl merged commit 8273baf into integration Aug 17, 2026
1 check passed
@lr00rl
lr00rl deleted the docs/design18-e3-lawful branch August 17, 2026 07:50
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