> 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.

# Provenance and evidence boundaries

## Directly inspected local Git bindings

| Component | Full commit | Local ref state | Evidence boundary |
|---|---|---|---|
| Platform app lane | `9194e2d4a26ae7879188547cc768399c89f28cfd` | `work/uat-cloud-isolation-20261021` | Git HEAD inspected; not public-ref or whole-candidate qualification proof |
| IndeeHub native reservation | `20cbb722755581693546a379b2692450a04a8e67` | detached HEAD | Git HEAD inspected; 28 new native tests unrun |
| IndeeHub signed-admission app | `04f9daadd3ea582f7351c9dfd413eeb593d43087` | detached HEAD | Git HEAD inspected; owner-recorded isolated 127/7 raw/outer pass |

Inspection did not certify clean worktrees or pushed refs. The app owner separately reports the current app source unpublished by that lane, with no canonical proposal/ref receipt; native publication remains unverified. Other local branches and historical sources exist; they must not be mistaken for these latest frozen candidates. No branch is implicitly merged by publishing these docs. Public source URLs/proposals need independent remote verification before inclusion.

## Sources and curation

The private canonical completion execution plan, fixed 48-requirement/30-task ledger, platform UAT ticklist/current handoff, IndeeHub qualification/UAT contract, signed-admission checkpoint and current execution-control review informed this collection. Their historical status fields were not adopted wholesale. Current outcome corrections came from implementation and coordinator messages; factual owner sign-off is still requested.

The independently curated execution-control contribution reports all 20 reviewed control hashes matched and r1 was rejected. Model counts 11 receipt + 8 flow + 8 artifact are model evidence only. Its proposed primary/collateral inventory is not runtime success. Exact operational manifests and failed receipts remain private with the owning lanes; public descriptions preserve their semantics without access details.

## Recent-claim provenance and cutoff

Cutoff: **2026-10-24 08:08 UTC**. Later execution or cleanup outcomes do not silently update this snapshot.

| Claim | Source and verification level |
|---|---|
| Three full source commits/ref states above | Collector read-only Git inspection; clean-tree/remote publication not certified |
| Current app source unpublished by its lane | App implementation owner statement; not a claim about every historical source |
| B03 diagnostic r3 operation 1/outer 90, incomplete correlation and surviving provider | Latest app-owner outcome report before cutoff; collector did not rerun or independently inspect runtime |
| Earlier D09 disposable transport/rollback and remaining installed gates | App canonical handoff/ticklist and implementation outcome reports; bounded source-specific evidence |
| Signed-admission app 127/7 raw/outer pass, native 28 unrun | Native canonical checkpoint plus manager corroboration; not collector runtime execution |
| First native sequence rejected R1–R5; successor unreviewed | Testing owner's curated independent review; testing owner approved these documentation boundaries |
| Fixed 48 requirements, 30 task definitions and mandatory scenarios | Canonical scope ledger, platform ticklist and qualification/UAT contracts; owner reconciliation of current per-scenario evidence remains pending |

A bounded factual review was requested from both implementation owners; no whole-lane approval had arrived by cutoff. The native implementation owner subsequently confirmed the two exact clean detached candidate hashes, app 127/7 zero-skipped raw/outer pass, native 28 UNRUN, proposed 84+69 inventory, rejected r1/unreviewed r2, and missing paired financial driver. That approval covers only these current native/app statements, not the full matrix or historical installed evidence. The platform app owner also approved the bounded source/open-status statements in Non-IndeeHub-Execution and matrix B–E/eight-app rows, correcting pagination to 251 items across a 250-item page boundary and adding the r3 client observations. Both corrections are incorporated. Neither review is full-plan evidence certification or release approval. Unverified evidence stays explicit. Publication of this scoped process does not require waiting for product completion and does not close the remaining review checklist.

## Publication review checklist

- [ ] Both lane owners reconcile full IDs, source bindings, commands, completed/open exits and stale historical wording.
- [x] Testing owner reviewed the execution-control contribution (R1–R5/native evidence boundaries only); command quoting correction applied. This is not full-plan/product approval.
- [ ] Full scenario matrix and remaining process mappings reconciled with implementation owners.
- [x] Final integrator manually reviewed all eight documents, checked all local links and the 48-requirement/30-task inventory, and ran a narrow private-data scan. No raw reports, implementation commits, credentials or operational attachments were imported. These checks are not a guarantee that all possible sensitive information can be detected.
- [x] Initial docs proposal `8ef4306df1b88fcb7275245cf855c993c2170ba423ba2f6ce80758c0e188a8af` published on ngit. Commit `ffa93a041e8667920f9a74ba18b70affd8886ad0` was advertised identically by two Git servers; an independent fresh fetch verified all eight document bytes. Subsequent updates require their own remote verification; this is not a merge into main.
- [ ] Implementation ref visibility separately verified; docs publication is not implementation publication.

Exclude credentials/keys, access URLs, machine identifiers/addresses, home paths, runtime identities/PIDs/CIDs, private logs/screenshots/user/financial/session data and raw handoffs. Retain useful public source commits, test semantics, failure/UNRUN facts and review limits. No private operational attachment is required to read these summaries.