Skip to content

Paper VII conformance remediation (tracking) #891

Open

Description

@flyingrobots

Tracking container (not an executable PR). Groups the remediation from the Paper VII conformance audit (AIΩN Paper VII, WARP: Optics, Holograms, and Worldlines over Shared Causal History), recorded below with the owner ruling. Child issues are filed separately with their own acceptance checks and dependency edges.

Audit summary (2026-10-16)

Three read-only audits (Echo transport and settlement, Echo identity and retention, Continuum c33caa3e) classified each Paper VII obligation. The answer: Continuum today delivers identified occurrences; it does not establish comparable causal claims for replica-scale lowering, and Echo only stages imports. Most findings are incomplete implementation, consistent with both repos' own design docs. Four contradictions:

  1. Echo: settle_strand (warp_kernel.rs:1115 → SettlementService::settle, settlement.rs:959) appends provenance outside intent admission, contrary to docs/architecture/continuum-transport.md:108-122 (Causal Mutation Rule).
  2. Echo: dispatch_intent (warp_kernel.rs:975-997) always targets DefaultWriter { default_worldline }, ignoring the import request's target_worldline_id, and records Staged without the library's identity checks.
  3. Echo: submit_intent_inner admits submissions into AuthorOnly strands without any posture or principal check (Paper VII §6.3).
  4. Continuum: SettlementDecisionKind { IMPORT, CONFLICT } cannot express Plural or Obstruction (contradicts Continuum Inv. 12).

Owner ruling, 2026-10-16 (verbatim, abridged to the decisions)

APPROVE the audit. APPROVE local identity hardening. REJECT the existing direct settlement commit path. REQUIRE a proper Continuum transport contract before further import implementation.

Finding / recommendation Ruling Priority
Route settlement through intent admission APPROVE MUST
Define Continuum's comparable-basis transport APPROVE MUST
Separate first-order imports from settlement APPROVE MUST
Enforce strand posture and authorization APPROVE MUST
Support four lawful settlement outcomes APPROVE MUST
Correct wired import dispatch ENHANCE MUST
Define real retention contracts Λ APPROVE MUST for shells claiming those guarantees
Separate braid construction, collapse, admission APPROVE MUST
Resolve source-worldline identity restriction APPROVE MUST
Decision-stable redelivery tests APPROVE MUST
Cross-runtime conformance fixtures UPGRADE MUST
Copy-on-write strand reads DEFER COULD
Plural/Conflict at tick scale DEFER COULD

Implementing the full retention/folding machinery can remain staged. What cannot remain unspecified is which guarantees a shell actually makes.

Wired import: fail closed. Until transport and explicit receiving-context dispatch are implemented, the wired import should return a typed UnsupportedImport or equivalent obstruction without recording a misleading Staged result. Do not silently substitute a default worldline.

Settlement: preserve the existing settlement implementation as a candidate evaluator if it can be made pure and deterministic; remove its ability to commit authoritative history directly; its result becomes a proposed operation subject to ordinary admission. Not every lawful outcome necessarily advances a canonical worldline.

Transport: Continuum defines what a lawful transported causal claim means; Echo implements how it is admitted. Comparability must be demonstrated, never assumed; it need not be literal shared ancestry (an explicit translation or correspondence witness may establish it). Source identity and receiving coordinate are different facts.

Protected strands: a security boundary. AuthorOnly: only an authorized principal can submit or explicitly delegate. Scratch: no automatic admission of live external crossings. Shared: the applicable shared authority policy. Unknown principal, missing authority evidence or ambiguous target posture fail closed. Synthetic fork provenance is not authentication.

Frozen PRs: #885 and #888 directionally approved after normal CI and review. #890 directionally approved provided inherited occurrence decisions are stable at the fork basis, post-fork parent decisions do not leak, and existing receipts remain unchanged. Do not describe any of these as replica-scale conformance.

Execution rules: keep changes atomic and separately reviewable; record dependencies; do not invent Echo-specific protocol semantics in Continuum; no second admission law; fix immediate correctness violations first, then define Continuum's shared transport contract before implementing further replica-import behavior; report concrete implementation evidence separately from design-only claims.

Incomplete: we haven't implemented comparable-basis transport. Incorrect: we claim to import into an explicit worldline but actually dispatch to a default worldline. The former needs a plan. The latter needs a fix.

Activity

  1. flyingrobots commented on Oct 16, 2026

    @flyingrobots
    OwnerAuthor

    Remediation issues and dependency edges (2026-10-16)

    Dependency edges answer "which PRs must already be merged for this one to be correct?". Recorded here as proposals derived from the audit; none are GitHub blocked-by relations yet.

    Immediate correctness (Echo, no prerequisites; can run in parallel):

    Echo follow-ons:

    Continuum contract (owns shared meaning):

    • continuum#80 Transport(F_rep, Σ, F_recv), comparable basis (no prerequisite).
    • continuum#81 Conformance fixtures, first slice (no prerequisite).
    • continuum#82 Settlement four-way outcome algebra (no prerequisite).
    • continuum#83 First-order intent vs settlement ← continuum#80.
    • continuum#84 Preserve source identity / replace target-pinning invariant ← continuum#80.
    • continuum#85 Import shells and retention obligations ← continuum#80.

    Gate: no further Echo replica-import implementation until continuum#80 and #83 are specified (owner ruling).

    Approved local work (not replica-scale conformance): PR #888 (#887), PR #890 (#886, with the owner's conditions), #885.

    Deferred (COULD): copy-on-write strand reads; Plural/Conflict at tick scale.

  2. flyingrobots commented on Oct 16, 2026

    @flyingrobots
    OwnerAuthor

    Status, 2026-10-16

    Landed on main (local identity hardening; none of it is replica-scale conformance):

    Awaiting owner review (design first): #893 settlement through admission; #894 strand authority boundary; #901 whether register_strand may assert lineage without fork evidence.

    Open, unblocked: #895 (decision-stable redelivery tests; #890 is merged), #896 (retention guarantees per shell family), #902 (strand child-worldline index).

    Gated: #898 ← #893; #897 ← continuum#81; any further import implementation ← continuum#80 and continuum#83.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    specSpec/Design document

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions