Skip to content

Reconcile full Stitch implementation & proof evidence suite - #8

Merged
wwwportal merged 28 commits into
mainfrom
staging/stitch-upstream-reconciliation
Nov 13, 2026
Merged

wwwportal merged 28 commits into
mainfrom
staging/stitch-upstream-reconciliation

Conversation

@wwwportal

Copy link
Copy Markdown
Contributor

Summary

This pull request brings in the complete unified Stitch implementation and proof-evidence suite from afflom/stitch.

It incorporates and completes the work initiated in #7 (diagnostic/stitch-candidate-browser) along with the subsequent proof-evidence retention track (work/stitch-proof-evidence).

What's included

  • Browser & Guest Qualification: Integrated Chromium host and v86 Linux guest validation workflows.
  • Model Verification & Contracts: LexLean / Prism formal source and product model definitions, contracts, and generated bindings.
  • Source Evidence Retention: scripts/check-source-evidence.mjs, scripts/retain-source-evidence.mjs, and tests/source-evidence.test.js.
  • Diagnostic Records & Provenance: Evidence records under docs/evidence/native-fixture-writer-466/ and docs/guest-browser-qualification.md.
  • Channel Flow & Recovery: Contextual operator recovery, authenticated peering, and transactional authority controls.

Validation

  • npm test: All 34 test suites (runtime admission, model bindings, product graph, recovery, and source evidence) pass.
  • python3 scripts/verify-custody.py: Independent Python custody verification passes (6 valid vectors, 18 recovery pairs).
  • cargo test --locked: Conformance passes with zero failures.

Review note

If reviewing in sequence:

  1. Review and merge Diagnostic/stitch candidate browser #7 first (which establishes the candidate browser and core model definitions).
  2. Once Diagnostic/stitch candidate browser #7 is merged into main, GitHub will automatically update this PR's diff to show strictly the additive evidence retention and reconciliation delta.

Checkpoint: runtime conformance passed; formal SDK verification remains pending.
Checkpoint exact locally tested tree a2ec17c.
Full 17-module LexLean/Lean/leanchecker/axiom verification passed; 104 JS tests and independent custody vectors passed. Native Prism artifact and real browser/provider qualification remain pending. Expanded standards and operator-experience work continues separately.
Verify 20 actual LexLean modules, 1179 declaration audits and 186 runtime tests. Implement strict JCS/I-JSON, RFC8484 DNS wire transport, bounded relay framing across the supported object range, lifecycle transitions and source-owned operator journeys. Retain explicit native artifact, real-host qualification and operational completeness limitations.
Checkpoint of 227 passing runtime tests, five strata and independent custody checks. Records exact 23-module source verification with 1,221 audits. Native acceptance remains blocked by the separately reproduced Laws compilation issue; no gate is weakened.
Exact source verification: 23 modules, 1232 audits, 79 successful verifier processes. Runtime: 242 tests plus five strata and independent Python vectors. Origin-local keys and cross-tab durable journal do not claim private-key backup or browser qualification. Native gate remains unchanged.
Verified checkpoint: 262 runtime tests, independent recovery vectors, 23-module pinned source proof with 1266 declaration audits. This does not claim native Prism artifact acceptance, real-host qualification or full operational completion. Native Laws compiler fix remains required; no acceptance gate weakened.
Preserve actual attestation and manifest bytes while deriving the existing
source summary from verifier records and current inputs. Check direct
lexicon tree digests and full workspace coverage before replacing outputs,
and replace the summary last. Keep source retention separate from native
Prism acceptance. No SDK lock, model, or retained proof changes.

Validation: 19 focused retention tests, full npm test (383 tests and five
layer checks), independent Python custody verification, and diff checks.
…fication

Preserve diagnostic and work histories. Product files exactly match work/stitch-proof-evidence at fa5b2d0; retain its newer source-evidence helper and diagnostic records. Resolve the additive guest qualification documentation with that complete version.

The sole extra file is the existing host-qualification workflow retargeted to staging/stitch-upstream-reconciliation. It exercises runtime and real Chromium checks without changing or claiming the separately pending native SDK acceptance. No upstream PR head, SDK lock, source/proof bytes, guest image or deployment is changed.
@wwwportal

Copy link
Copy Markdown
Contributor Author

Model-gate carve-out note (reviewed at merge time)

Merging with the model check known-red is a deliberate, recorded decision, not an oversight:

  • model fails with PP5007: application-lean timed out at the same step, same ~10-minute mark, across three consecutive runs (this branch 43353465872, and main after Diagnostic/stitch candidate browser #7 merged in 43355791515 — identical failing line each time).
  • This is the documented pinned-SDK defect: LexLeanRuntime.Laws stalls indefinitely in C emission due to duplicate matcher-splitter reconstruction entries (docs/native-build-diagnosis.md). The SDK-internal budget — not the 55-minute job cap — is what fires. More CI minutes cannot produce a pass; the repo's own diagnostic says a longer timeout is not a fix.
  • Lean/kernel/axiom results are unaffected: prismpm lock check passes, lexlean fmt --check and lexlean lock --check pass, lexlean check reports 25 modules canonical and the attestation records selected modules verified. The stall is the native (C emission) stage only.
  • Candidate compiler LexLean 0.4.0 (LexLean PR #466 @ cc55612) passed the unchanged 25-module closure's cold native build in ~16 s both times, with source evidence retained at docs/evidence/native-candidate-466/. The full gate remains blocked solely on PrismPM publishing that compiler as a qualified SDK (tracking: UOR-Foundation/PrismPM issue #194).
  • browser and runtime checks pass and continue to be enforced.
  • Raising the timeout was considered and rejected per the project's diagnosis; the gate will be re-qualified when the pinned SDK is bumped to a published 0.4.0-class qualified image.

@wwwportal
wwwportal merged commit e1fde2c into main Nov 13, 2026
6 of 8 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.

2 participants