3.0 KiB
Curated documentation snapshot as of 2026-10-24 08:08 UTC. Lane-owner factual review pending unless explicitly stated; not release approval, execution admission, or confirmation that implementation is published.
IndeeHub execution
Current app and native are different evidence sets
- App signed-admission source:
04f9daadd3ea582f7351c9dfd413eeb593d43087(inspected detached HEAD). 127 tests in seven suites passed, zero skipped; raw and outer verdicts both 0. This includes 27 admission, 15 request-proof, 12 response-proof and 73 collateral assertions. Dependencies/inventory and owned parent/child absence were checked. This is isolated app-source qualification, not native/paired/installed acceptance. - Native frozen source:
20cbb722755581693546a379b2692450a04a8e67(inspected detached HEAD). 28 new native cases remain UNRUN. Current source includes signed request/result binding, retained raw evidence, preparation/reservation and separate-open contention coverage. Formatting/models do not prove runtime behavior. - Proposed native sequence: primary 84 invocations (28 new + 56 related), collateral 69 invocations/68 unique. These are proposed counts, not passes. Duplicate names must not receive duplicate completion credit.
- Independent execution-control review rejected the first 20-entry control snapshot for five lifecycle gaps. A successor is under implementation and unreviewed. Native compilation also depends on restored approved capacity; no old admission may be replayed.
Next meaningful integration exit
Authenticated buyer → producer first invoice and original recovery for an admitted revision, including withdrawal, restart and lost reply. Outstanding sub-exits include publication/receipt admission, authenticated app/native transport, producer preparation/create routes, buyer RPC/native UI, and paired-handler fault qualification. A paired fixture draft is separate from the frozen native source. A missing financial driver must remain an explicit missing stage, never a mocked success.
Keys, trust pins, financial routes, creation/payment/Start activation, installed acceptance and public publication are not authorized by these source results. A response-supplied key is not a trust anchor; exact request/result/signature/chronology and restored-state handling require qualification.
Earlier evidence and limitations
Earlier owner records include frontend/backend source suites, disposable storage restart/resume and API authority checks, and private installed UI/identity/upload smoke. A prior operator-visible installed result was withdrawn because the visible source/update state was wrong; its correction required operator retest. Those historical artifacts cannot certify current app/native candidates. Historical fixture-gated skipped suites are not passes. No current whole-plan, two-/three-node, financial, FIPS playback or operator release acceptance is inferred.
The full A01–A13 and inherited T task coverage remains in the matrix. The latest signed-admission work is only part of that scope, not a replacement plan.