Every claim, and the line that backs it.

Bounded runtime evidence, current limits

The eight-step browser proof remains a deterministic replay at sts2-gateway@e7bce21. It launches no process and calls no provider. Current owner records below are dated and scoped to named v0.107.1 guests, fixtures, processes, and operations; they do not establish a public release, deployment, or general compatibility. Runtime-v4 expert-state and expert-action paths are present at source/component level, with host legality, settled native effects, provider runs, and broader compatibility still unverified.

Latest acceptance successor — 2026-09-10, 21:27 UTC (post-recovery-fence merges)

confirmed This read-only successor follows gateway PR #39, harness PR #62, and MCP PR #40, merged between 21:20 and 21:21 UTC. It supersedes the 20:02 table only for those three source identities; the protocol artifact, producer snapshot, release, Pages, host, provider, gameplay, observability, and Workshop boundaries remain separate.

Repository	Current main	Tree	Checks and boundary
sts2-gateway	c8be3a7	69b9dc2	CI / policy passed; recovery response direction and unknown-generation fencing are source/component evidence.
sts2-mcp-server	037d10d	53013a3	CI / policy passed; canonical pending-rejoin projection is source/component evidence.
sts2-harness	682c2b5	173be64	CI / policy passed; recovery response generation fencing is serialized source/component evidence.

• confirmed — Recovery source boundary: gateway PR #39 rejects echoed recovery request responses and permits same-generation after only for an accepted rejoin receipt; reconcile and unknown outcomes require a null after. Harness PR #62 applies the same recovery-generation fence, and MCP PR #40 accepts the canonical pending-rejoin receipt while rejecting invalid post-generations on reconcile and unknown responses.
• unverified — Native co-op runtime gate: no live two-peer model-controlled action, vote convergence, shared effect, native checksum settlement, or disconnect/rejoin recovery trace is recorded. These fixes do not establish host loading, live peer identity, or gameplay.
• confirmed — Artifact boundary: the accepted coop-native-v1 artifact at protocol ed8626c remains bound to producer ab702db, gateway de1fe723, MCP 47d63f6, and harness H0 a2cb481. Its schema digest and serialized source_to_consumer: pass record are unchanged; a new artifact capture and conformance refresh is required before the current heads are described as its reviewed consumers.
• unverified — Terminal evidence: no model-controlled Victory or replay is recorded. The named Windows and Linux records are bounded Defeat campaigns; forced Victory fixtures bypass ordinary play.

Latest release successor — 2026-09-10, 21:32 UTC (v0.4.1 source-only prerelease)

confirmed The current sts2-game-mod-v0.4.1 tag/release was published at 2026-09-10T21:32:09Z, is non-draft and marked prerelease, and targets source commit d23ca838 / source tree 23336ca. Source-release workflow 34532717805, CI 34532510095, and policy 34532510190 passed at that commit.

Platform source archive	SHA-256
Windows x86-64	58fdaaf9a6fa243e8a18398bc0d2b90f78eddb228626fbff7b3b5255c3117050
Linux x86-64	174bb1551e26d7693c707f5f9f8989dc0f0d9b83ac34e7e6b9b337c2f03fa78b

confirmed The release manifest records source-policy SHA-256 89a62d755af6c23e09af72768326116a7155a15833b4b61f7295922a52cd561e and included-content digest 1ad28d36b8526dc73da126abc5fe8b3457e809f503daa18d9f09b34b7f6d6b08. Downloaded archives and sidecars passed strict checksum verification in this review. The bundles are source-only and establish no host compatibility, live gameplay, Workshop lifecycle, or platform support. The historical sts2-game-mod-v0.4.0 release remains published at a70a5e5 / tree 0b16693; its earlier hashes remain in the dated historical record.

Latest native artifact successor — 2026-09-10, 22:27 UTC (protocol PR #38)

confirmed Protocol PR #38 merged at 2026-09-10T22:24:58Z. The current protocol artifact is f22dd721 / tree 0e053e68; CI 34537328660 and policy 34537328616 passed. This successor supersedes the 22:04 UTC artifact identity below while preserving the live-runtime boundary.

Artifact role	Reviewed source	Tree	Checks and boundary
Protocol artifact	f22dd721	0e053e68	CI/policy passed; schema and artifact source.
Producer capture input	d23ca838	23336ca8	Exact source bound to r7; source-only.
Producer current main	888b067	1fec63ba	PR #65 digest-helper update; separate from capture input.
Gateway consumer	c8be3a72	69b9dc22	Consumer component identity; live transport unverified.
MCP consumer	037d10de	53013a3f	Consumer component identity; live transport unverified.
Harness consumer	63dc5636	575a84cc	PR #53 runtime-v4/runtime-v3 source corrections; no native wire or serialization files changed.

confirmed The protocol artifact's conformance record binds producer capture input d23ca838 / 23336ca8, gateway c8be3a72 / 69b9dc22, MCP 037d10de / 53013a3f, and harness 63dc5636 / 575a84cc. The current game-mod main is 888b067 / tree 1fec63ba; game-mod PR #65 updated sha2 to 0.11.0 and its digest helpers, with CI 34535163545 and policy 34535163507 passed. That current head is recorded separately from the capture input.

confirmed The fresh producer capture coop-native-source-only-20260910-r7 remains unchanged: it was captured at 2026-09-10T21:39:58Z, has wrapper_count: 9 and projection_match: true, and retains schema digest 2f3bc99e53080fa11b39592b64fb0ab964a16f568719a2622d0b2caf766ab629. The refreshed consumer-conformance record reports component_serialized_conformance / source_to_consumer: pass for those exact identities.

confirmed Harness PR #53 added runtime-v4 expert catalog/composition/transport coverage and corrected runtime-v3 recovery fixtures; its PR CI 34536315640 and PR policy 34536315601 passed, as did merged main CI 34536555216 and policy 34536555229. The protocol refresh records that PR #53 changed no coop-native wire or serialization files, so no producer recapture was needed.

unverified The capture uses a synthetic CapturePort and records native_session_executed: false. No live two-peer action, vote convergence, shared effect, native checksum settlement, or disconnect/rejoin recovery is recorded; live_status remains unverified. The v0.4.1 source-only release and current observability, runtime, provider, Workshop, and platform-support limits remain unchanged.

Latest native artifact successor — 2026-09-10, 22:04 UTC (protocol PR #36)

confirmed Protocol PR #36 merged at 2026-09-10T22:02:17Z. The current protocol artifact is b1d1a86a / tree 57478028; CI 34535371482 and policy 34535371517 passed. This successor supersedes the 21:53 UTC artifact identity below while preserving the live-runtime boundary.

Artifact role	Reviewed source	Tree	Checks and boundary
Protocol artifact	b1d1a86a	57478028	CI/policy passed; schema and artifact source.
Producer sts2-game-mod	d23ca838	23336ca8	Existing capture input; source-only producer.
Gateway consumer	c8be3a72	69b9dc22	Consumer component identity; live transport unverified.
MCP consumer	037d10de	53013a3f	Consumer component identity; live transport unverified.
Harness current consumer	d23b490	8dd448e2	PR #36 sha2 API migration; coop-native wire/serialization semantics unchanged.

confirmed The fresh producer capture coop-native-source-only-20260910-r7 remains unchanged: it was captured at 2026-09-10T21:39:58Z, contains 9 serialized wrapper captures with projection matches, and retains schema digest 2f3bc99e53080fa11b39592b64fb0ab964a16f568719a2622d0b2caf766ab629. The refreshed consumer-conformance record reports component_serialized_conformance / source_to_consumer: pass for the exact producer, gateway, MCP, and current harness identities above. No producer recapture was needed.

unverified Protocol PR #36 pins current harness main at d23b490 / 8dd448e2; its dependency-only sha2 0.10.9 to 0.11.0 digest API migration leaves the coop-native wire and serialization semantics unchanged. The capture uses a synthetic CapturePort and records native_session_executed: false. No live two-peer action, vote convergence, shared effect, native checksum settlement, or disconnect/rejoin recovery is recorded; live_status remains unverified. The v0.4.1 source-only release and current observability, runtime, provider, Workshop, and platform-support limits remain unchanged.

Latest native artifact successor — 2026-09-10, 21:53 UTC (protocol PR #35)

confirmed Protocol PR #35 merged at 2026-09-10T21:51:44Z. The current protocol artifact is d930110b / tree aef7ce55; CI 34534444584 and policy 34534444476 passed. This successor supersedes the 21:27 UTC artifact identity below while preserving the live-runtime boundary.

Artifact role	Reviewed source	Tree	Checks and boundary
Protocol artifact	d930110b	aef7ce55	CI/policy passed; schema and artifact source.
Producer sts2-game-mod	d23ca838	23336ca8	Fresh capture input; source-only producer.
Gateway consumer	c8be3a72	69b9dc22	Consumer component identity; live transport unverified.
MCP consumer	037d10de	53013a3f	Consumer component identity; live transport unverified.
Harness consumer snapshot	682c2b5b	173be647	Capture-bound consumer; live execution unverified.
Harness current main	d23b490	8dd448e2	CI / policy passed after dependency-only PR #44; artifact not refreshed.

confirmed The fresh producer capture coop-native-source-only-20260910-r7 was captured at 2026-09-10T21:39:58Z and contains 9 serialized wrapper captures, all with projection matches. The consumer-conformance record reports component_serialized_conformance / source_to_consumer: pass for the exact producer, gateway, MCP, and harness snapshot identities above. The schema digest remains 2f3bc99e53080fa11b39592b64fb0ab964a16f568719a2622d0b2caf766ab629. Harness main later advanced through dependency-only PR #44; the capture remains explicitly bound to 682c2b5b / 173be647 until refreshed.

unverified The capture uses a synthetic CapturePort and records native_session_executed: false. No live two-peer action, vote convergence, shared effect, native checksum settlement, or disconnect/rejoin recovery is recorded; live_status remains unverified. The v0.4.1 source-only release and current observability, runtime, provider, Workshop, and platform-support limits remain unchanged.

Latest observability successor — 2026-09-10, 20:44 UTC (post-PR #19 merge)

confirmed This read-only refresh follows observability PR #19 merging at 2026-09-10T20:42:45Z. It supersedes the earlier 20:02 UTC observability identity; all other source, component, release, Pages, host, provider, gameplay, and Workshop boundaries remain separate.

Repository	Current main	Tree	Checks and boundary
sts2-game-core	f9db577	8cb53ed	CI/policy passed; host-independent semantics.
sts2-game-mod	a70a5e5	0b16693	CI/policy/source-release passed; source-only prerelease.
sts2-gateway	de1fe72	cbf10ca	CI/policy passed; source/component conformance, live settlement unverified.
sts2-mcp-server	47d63f6	a6eb009	Main CI 34516747992 / policy 34516748169 passed; PR #39 CI 34515863120 / policy 34515863070 also passed; source/component conformance, live settlement unverified.
sts2-harness	0f71c18	6b8f26d	CI/policy passed; serialized consumer conformance, live execution unverified.
sts2-protocol	ed8626c	3681cf2	CI/policy passed; artifact checksum conformance, live support unverified.
ai-agent-observability	89539a6e	dd948bdb	CI passed after PR #19 merged; OTel bind/inode deployment repair is source/component evidence, while live ingestion/query/persistence remain unverified.
.github	f32a02c	350b53a	Governance records; no hosted check.
AI-Ascension.github.io	f8b1e8f	1218f1e	Validation/Pages deployment passed; static publication only.

unverified The source update does not change the observability runtime result: MLflow has one exact identity/trace match with 124 allowlisted spans and no terminal outcome; Laminar is credential-unavailable with no query rows or restart-persistence proof. Rootful Podman/image identity and the root-only Laminar query key remain inaccessible.

Latest acceptance successor — 2026-09-10, 19:15 UTC (post-19:05 native co-op consumer merges)

confirmed This read-only refresh follows gateway PR #38, MCP PR #39, harness PR #61, and protocol PR #34 merging between 17:51 and 19:05 UTC. It supersedes the 16:25 section below for current repository identity while preserving that section as history. The table records exact default-main commit and tree identities with the latest completed checks observed at capture. Source, serialized component, release, Pages, host, provider, gameplay, observability, and Workshop states remain separate.

Repository	Current main	Tree	Checks and boundary
sts2-game-core	f9db577	8cb53ed	CI and policy passed; host-independent semantics only.
sts2-game-mod	a70a5e5	0b16693	CI, policy, and source release passed; one source-only prerelease, with host loading and settled gameplay unverified.
sts2-gateway	de1fe72	cbf10ca	CI and policy passed; native route/forwarder and receipt validation are source/component conformance, with live host settlement unverified.
sts2-mcp-server	47d63f6	a6eb009	PR CI and PR policy passed; native conflict/recovery projection is source/component conformance, with live MCP-to-game settlement unverified.
sts2-harness	0f71c18	6b8f26d	CI and policy passed; native consumer conformance is serialized source/component evidence, with live provider, host, and gameplay execution unverified.
sts2-protocol	ed8626c	3681cf2	CI and policy passed; native consumer binding and checksum conformance pass at component level, with live support unverified.
ai-agent-observability	d7e79e1	179eab4	CI passed; live ingestion, query, persistence, and two-backend correlation remain unverified.
.github	9c795e6	8367f18	No hosted check recorded for this governance repository; governance and acceptance records only.
AI-Ascension.github.io	b0b04b8	45900bb	site validation and Pages deploy passed; static publication only.

• confirmed — Native co-op consumer conformance: Gateway PR #38 merged as de1fe72; MCP PR #39 merged as 47d63f6; harness PR #61 merged as 0f71c18; and protocol PR #34 merged as ed8626c. Their current-main checks passed. The accepted coop-native-v1 artifact reports schema digest 2f3bc99e53080fa11b39592b64fb0ab964a16f568719a2622d0b2caf766ab629 and serialized source-to-consumer pass for producer snapshot sts2-game-mod@ab702db / tree e3f0aa9d30fe25585fbb3c1fe8e3c1fcdfa43223, gateway de1fe723 / tree cbf10caa6775ca06adf7fe1e9d6cc98be6453a66, MCP 47d63f6 / tree a6eb009912a4f624c49398f6cfc25022da65b563, and harness H0 a2cb481 / tree 083e1dc3ca88c35eedc10a6187a63c91a9864c46. The producer snapshot and harness H0 identity are bounded artifact inputs; they are distinct from the current game-mod release/main and harness main rows above.
• unverified — Native co-op runtime gate: no live two-peer model-controlled action, vote convergence, shared effect, native checksum settlement, or disconnect/rejoin recovery trace is recorded. The next gate is an exact reviewed-artifact run on a disposable host with distinct peer identities and settled action, vote, checksum, and rejoin outcomes.
• unverified — Runtime and terminal evidence: no model-controlled Victory or replay of one is recorded. The named Windows and Linux records are bounded Defeat campaigns; forced Victory fixtures bypass ordinary play. Runtime-v4 source/component paths and the two-process native diagnostic do not establish general STS2 discovery/load compatibility, host ABI compatibility, provider execution, settled rest-site gameplay, or platform support.
• confirmed — Observability boundary: MLflow returned HTTP 200 for a failed run containing 124 spans but no terminal outcome. Laminar health returned HTTP 200, while its query returned HTTP 401 with zero rows/pages. No controlled-restart persistence result is recorded; rootful Podman/host access and a valid Laminar operator credential/path remain needed before terminal campaign queries before and after restart.
• confirmed — Release inventory: exactly one tag and one GitHub release exist, both sts2-game-mod-v0.4.0, published, non-draft, and marked prerelease, targeting a70a5e5 / tree 0b16693. Source-policy SHA-256 is f8fea839e28902843d1ea02db2589337ff36ec8214765d548c42177514fe3ba8; included-content digest is 54b56ad89e813b1d250bf8d3a318b377ccae26db7d7122f534b4adccfee2dbbe; Windows and Linux archive hashes are acdf792a359cdf4f7f078967371317a995aea7c8194415800a00efb40db10362 and 5670d7992d3e1276f4f8de1f3735f0d7e1595e7900990e7e9d7f1ef5ca5a77cf. The other eight repositories have zero tags and releases. This source-only release contains no compiled runtime or Workshop package and establishes no stable release or host compatibility.
• confirmed — Pages baseline: site main was b0b04b8 / tree 45900bb; validation 34502645662 and Pages deployment 34502645601 passed. Before this successor is deployed, cache-busted HTTPS requests returned HTTP 200 with r11 hashes: evidence.html 70e3ccee0726613a96094913c4d1170a84ac5e7c77705691ca49b09c0ffc50c6, repositories.html 4ae62d2bef237574d42e8650fab226f1a572380c6aa8c8e3aaf13d1222465612, and README.md 08c3976d4a62a1368055faac9ac1afb3c8a67003c5fbddae7f1bd4a44bc00fe7. This is static publication evidence only.

Latest acceptance successor — 2026-09-10, 16:25 UTC (post-16:20 merges)

confirmed This read-only refresh follows gateway PR #37 merging at 2026-09-10T16:20:43Z, harness PR #59 merging at 2026-09-10T16:21:05Z, and the game-mod source-only prerelease publishing at 2026-09-10T16:20:06Z. It supersedes the 16:13 r10 section below for current default-branch and release identity while preserving r10 as history. All nine default-main heads, their latest completed checks, and the release/tag inventory were rechecked. Source, component, and release records remain separate from native host legality, provider execution, settled gameplay, observability persistence, Workshop publication, and general release acceptance.

Repository	Current main	Checks and source/release boundary
sts2-game-core	f9db577	CI and policy passed; host-independent semantics only.
sts2-game-mod	a70a5e5	CI, policy, and source release passed; tag/release sts2-game-mod-v0.4.0 is source-only, with host loading and settled gameplay unverified.
sts2-gateway	5f3eadab	CI and policy passed; PR #37 test-only malformed-settled-receipt regression, with no live host execution.
sts2-mcp-server	8b6b738	CI and policy passed; transport/mapping source, with native game settlement unverified.
sts2-harness	5cc486a6	CI and policy passed; PR #59 conflicting-completion retry regression, with no live provider or game execution.
sts2-protocol	997de2a	CI and policy passed; schemas/conformance source, with native co-op consumer admission unverified.
ai-agent-observability	d7e79e1	CI passed; live ingestion, query, persistence, and two-backend correlation remain unverified.
.github	1c55e44	No hosted check recorded for this governance repository; governance and acceptance records only.
AI-Ascension.github.io	a161730	site validation and Pages deploy passed; static publication only.

• confirmed — Gateway PR #37: PR #37 merged at 5f3eadab from head 0524b67e on base 2cf9127. A malformed host SETTLED receipt missing its ticket/witness becomes explicit receipt_missing UNKNOWN with HTTP 503; an identical retry replays the retained outcome without redispatch or catalog consultation. CI and policy passed; this is a test-only source/component regression with no live host execution.
• confirmed — Harness PR #59: PR #59 merged at 5cc486a6 from head fcd1f681 on base 780f2d5. It binds idempotent provider completion retries to result-reference and digest metadata, rejects conflicting retries instead of returning a false duplicate success, and extends payload-integrity regression coverage. CI and policy passed; no live provider or game execution is claimed.
• confirmed — Game-mod source-only prerelease: tag/release sts2-game-mod-v0.4.0 targets a70a5e5, is published and non-draft, and is marked prerelease. The source-release workflow 34501301708 passed. The bundles contain no compiled mod, runtime payload, proprietary assemblies/assets, saves, profiles, credentials, machine-specific files, Workshop package, Steam item update, installer operation, or game launch; they do not establish discovery/load compatibility, host ABI compatibility, live gameplay, rest-site settlement, provider operation, Workshop publication, or platform support.
• unverified — Acceptance blockers: no model-controlled Victory or replay; no native two-peer action/effect/checksum settlement or disconnect/rejoin recovery; Laminar credential/path and rootful Podman/host acceptance are still needed; one source-only prerelease and tag exist in game-mod while the other eight repositories have zero tags and releases; and no verified Workshop upload, Steam legal agreement, entitlement, item/content visibility, subscription, discovery, loading, update, or rollback.
• confirmed — Pages publication baseline: at this capture site main was a161730; validation 34501507191 and Pages deployment 34501507182 passed, deployment 6376193182 succeeded, and the live r10 page returned HTTP 200. The r11 successor is not deployed until its site PR merges.

Latest publication successor — 2026-09-10, 19:26 UTC

confirmed The preceding 19:15 UTC successor is now published. Site main is 64de240 with tree 530c3f7819b92699bb266add9ef703477fde73d5; validation 34520369933 and Pages deployment 34520369905 passed, and deployment 6379445687 reached success.

confirmed Cache-busted HTTPS requests returned HTTP 200 and matched the merged tree exactly: README.md 9c4a5589bc35e41b71bb1ef26154b1c35e67f57d1f36e5f0e7b399ac51150dc3, evidence.html a2851de73896a6a2d19e91692043b9eaae028984baca273eeefc6b823e97fd8e, and repositories.html 46ac34bd073bc1db8294dee97a649685fa958c4ff027ce3054298af4776a4ecc. This confirms static publication only; it does not establish game runtime, provider settlement, native two-peer gameplay, observability persistence, release compatibility, or Workshop lifecycle acceptance.

Latest acceptance successor — 2026-09-10, 16:13 UTC (post-16:03 merge)

confirmed This read-only refresh follows harness PR #51 merging at 2026-09-10T16:03:56Z. It supersedes the 15:54+ section below for current default-branch identity while preserving that earlier snapshot as history. All nine default-main heads and their latest completed checks were rechecked. Source and check records remain separate from native host legality, provider execution, settled gameplay, observability persistence, Workshop publication, and release acceptance.

Repository	Current main	Checks and source boundary
sts2-game-core	f9db577	CI and policy passed; host-independent semantics only.
sts2-game-mod	a70a5e5	CI and policy passed; PR #71 source-policy and copied REST artifact parity merge, with host loading and settled gameplay still unverified.
sts2-gateway	2cf9127	CI and policy passed; bounded control-plane source, with host settlement and deployment still unverified.
sts2-mcp-server	8b6b738	CI and policy passed; transport/mapping source, with native game settlement still unverified.
sts2-harness	780f2d5	PR #51 CI and policy, then main CI and policy, passed; context-capture source/component wiring only, with native provider receipt, worker execution, host behavior, and gameplay settlement unverified.
sts2-protocol	997de2a	CI and policy passed; schemas/conformance source, with native co-op consumer admission still unverified.
ai-agent-observability	d7e79e1	CI passed; live ingestion, query, persistence, and two-backend correlation remain unverified.
.github	c2b1771	No hosted check recorded for this governance repository in this refresh; governance and acceptance records only.
AI-Ascension.github.io	457f002	site validation and Pages deploy passed; static publication only.

• confirmed — Harness PR #51 source/component boundary: PR #51 merged at 780f2d5 from head 280fd39 on base 4342789. It adds bounded CapturePort modes and identities, ordered component manifests, lifecycle capture, queue/private-vault gates, and parity/failure-fidelity tests, wiring capture through direct ExoSession::decide, the generic ProviderPort route, Astra's final CLI handoff, and Ollama's final serialized HTTP write. Successful body writes are recorded as completion; response, malformed, timeout, and partial-write failures remain indeterminate and are not receipts. The PR body records final validation at f95e8bc, production capture source 316c8bd, and fidelity artifact SHA-256 2b6b8dd5509801fe0e9d104cb97f669d59c6f0ac302ac5b19da116334fcbbcd6.
• source-derived — Harness PR #51 limits: no real provider, game, or external service was called. Synthetic differential fake-downstream comparisons do not establish a provider receipt, game action, browser run, native platform behavior, or an integrated producer/store demonstration. The native preflight reached root → lead only; coordinator/specialist ancestry remains unverified because the child had no collaboration tools.
• unverified — Acceptance blockers: no model-controlled Victory or replay; no native two-peer action/effect/checksum settlement or disconnect/rejoin recovery; Laminar credential/path and rootful Podman/host acceptance are still needed; zero tags and zero GitHub releases across the nine repositories; and no verified Workshop upload, Steam legal agreement, entitlement, item/content visibility, subscription, discovery, loading, update, or rollback.
• confirmed — Pages publication baseline: at this capture site main was 457f002; validation 34499991425 and Pages deployment 34499991509 passed. Deployment 6375923984 succeeded, and the live evidence page returned HTTP 200 with SHA-256 e67ec29a894e37194e6d93fe298107013ecdac797f261975f325566452dfbf3a. This confirms static publication only; the r10 successor is not deployed until its site PR merges.

Latest acceptance successor — 2026-09-10, 15:54+ UTC

confirmed This read-only refresh supersedes the 15:34–15:38 UTC table below for current default-branch identity while preserving that earlier snapshot as history. It rechecked all nine default-main heads, their latest completed hosted checks, release/tag counts, and the current Pages publication result. Source and check records remain separate from native host legality, provider execution, settled gameplay, observability persistence, Workshop publication, and release acceptance.

Repository	Current main	Checks and source boundary
sts2-game-core	f9db577	CI and policy passed; host-independent semantics only.
sts2-game-mod	a70a5e5	CI and policy passed; PR #71 source-policy and copied REST artifact parity merge, with host loading and settled gameplay still unverified.
sts2-gateway	2cf9127	CI and policy passed; bounded control-plane source, with host settlement and deployment still unverified.
sts2-mcp-server	8b6b738	CI and policy passed; transport/mapping source, with native game settlement still unverified.
sts2-harness	4342789	CI and policy passed; PR #58 worker handoff/runtime/store graph and watchdog-worker-v1 fixtures are wired at source/component level, while native worker execution and gameplay settlement remain unverified.
sts2-protocol	997de2a	CI and policy passed; schemas/conformance source, with native co-op consumer admission still unverified.
ai-agent-observability	d7e79e1	CI passed; live ingestion, query, persistence, and two-backend correlation remain unverified.
.github	309df81	No hosted check recorded for this governance repository in this refresh; governance and acceptance records only.
AI-Ascension.github.io	a451a70	site validation and Pages deploy passed; static publication only.

• confirmed — Merged source/component updates: game-mod PR #71 merged at a70a5e5 from head 2e70efee, closing the current-main source-distribution policy gap and restoring copied REST artifact parity with sts2-protocol@997de2a. Harness PR #58 merged at 4342789 from head ed033f26; the crate root wires the worker graph and the merge adds its schema, fixtures, command mapping, and restart/recovery regressions. These are source/component and CI records.
• unverified — Model-played terminal evidence: no model-controlled Victory or replay of a model-controlled Victory is recorded. The named Windows and Linux replays are bounded Defeat campaigns; forced Victory fixtures bypass ordinary play.
• unverified — Native co-op settlement and recovery: no live two-peer model-controlled action, vote convergence, shared effect, checksum settlement, or disconnect/rejoin recovery trace is recorded.
• confirmed — Observability query boundary: MLflow returned HTTP 200 for a failed run containing 124 spans but no terminal outcome. Laminar health returned HTTP 200, while its query returned HTTP 401 with zero rows/pages. No controlled-restart persistence result is recorded. unverified acceptance still needs rootful Podman/host access and a valid Laminar operator credential/path.
• confirmed — Release inventory: the read-only refresh found zero tags and zero GitHub releases across all nine repositories at capture. No public release is established.
• unverified — Workshop lifecycle: package validators and staging sources do not establish an uploaded Workshop item. Steam legal agreement acceptance, entitlement, item/content visibility, subscription/discovery/loading, update, and rollback remain unverified.
• confirmed — Pages publication: site main is a451a70; validation run 34498420048 and Pages deployment 34498419971 succeeded. The successor documentation in this draft is not deployed until its PR is merged.

Latest acceptance snapshot — 2026-09-10, 15:34–15:38 UTC

confirmed A read-only refresh recorded the nine exact default-main heads below and the separate Pages result. These source and check records do not establish native host legality, provider execution, settled gameplay, observability persistence, Workshop publication, or release acceptance.

Repository	Current main	Checks and source boundary
sts2-game-core	f9db577	CI and policy passed; host-independent semantics only.
sts2-game-mod	e532f4d	CI and policy passed; adapter source/probes, live settlement remains unverified.
sts2-gateway	2cf9127	CI and policy passed; bounded control-plane source, host settlement remains unverified.
sts2-mcp-server	8b6b738	CI and policy passed; transport/mapping source, native game settlement remains unverified.
sts2-harness	e5029f1	CI and policy passed; provider, worker, native restart, and gameplay acceptance remain unverified.
sts2-protocol	997de2a	CI and policy passed; schemas/conformance source, native co-op admission remains unverified.
ai-agent-observability	d7e79e1	CI passed; live ingestion, query, persistence, and two-backend correlation remain unverified.
.github	fec27b9	Governance and acceptance records only; no metadata, deployment, or release change is implied.
AI-Ascension.github.io	3935679	validation and Pages passed; static publication only.

• unverified — Model-played terminal evidence: no model-controlled Victory or replay of a model-controlled Victory is recorded. The named Windows and Linux replays are bounded Defeat campaigns; forced Victory fixtures bypass ordinary play.
• unverified — Native co-op settlement and recovery: no live two-peer model-controlled action, vote convergence, shared effect, checksum settlement, or disconnect/rejoin recovery trace is recorded. Game-mod PR #69 added source contracts and probes; current gateway, MCP, and harness records do not establish an admitted native co-op consumer path.
• confirmed — Observability query boundary: MLflow returned HTTP 200 for a failed run containing 124 spans but no terminal outcome. Laminar health returned HTTP 200, while its query returned HTTP 401 with zero rows/pages. No controlled-restart persistence result is recorded. unverified acceptance still needs rootful Podman/host access and a valid Laminar operator credential/path. Issue #8 is closed; that closure does not prove query access.
• confirmed — Release inventory: the read-only inventory found zero tags and zero GitHub releases across all nine repositories at capture.
• unverified — Workshop lifecycle: package validators and staging sources do not establish an uploaded Workshop item. Steam legal agreement acceptance, entitlement, item/content visibility, subscription/discovery/loading, update, and rollback remain unverified.
• unverified — Harness worker modules: at sts2-harness@e5029f1, crates/harness/src/lib.rs declares neither worker_command nor worker_runtime; the worker sources reference missing support, handoff/store, completion, execution, and control-test modules.
• confirmed — Pages publication: site main is 3935679; validation run 34495457608 and Pages deployment 34495457785 succeeded, and a live request returned HTTP 200. The deployed page still displayed the older 08:32 snapshot, so this is static-site evidence only.

Latest current default-main source records — 2026-09-10, 08:32 UTC

A fresh read-only GitHub refresh after game-mod PR #69 merged recorded nine default-main heads and 29 open pull requests. The records are source/component and pull-request evidence, and do not establish native host loading, settled effects, provider execution, deployment, release, Workshop lifecycle, or general compatibility. The status supplement retains the exact capture (`CURRENT-REMOTE-REFRESH-20260910-r7.json`, SHA-256 ed2c01dbd939d0f51d8939b30864a05f83edbf30b5fd7e4a40cf5e0b7acb3bda) and individual pull-request states.

Repository	Current main	Source/component boundary
sts2-game-core	07b51c88ebe9	Host-independent semantics and tests.
sts2-game-mod	b9754b803cbf	Merged PR69 native co-op host contract and source probes; exact-host loader build, live runtime, and model-controlled action settlement remain unverified.
sts2-gateway	6b6c7f2fac67	Seeded-run gateway source and bounded routes; host settlement and deployment remain unverified.
sts2-mcp-server	73e777b96700	Seeded-run transport and gateway mapping source; native MCP-to-game settlement remains unverified.
sts2-harness	33437ddb18f6	Merged durable recovery and raw action identity plus seeded-run transport/coordinator source; provider execution, native host restart, and gameplay settlement remain unverified.
sts2-protocol	e5e545c2ff71	Seeded-run protocol contract source, schemas, artifacts, validators, and conformance cases.
ai-agent-observability	28a48590afb7	Source topology and deployment tooling; current-main gameplay ingestion, persistence, and two-backend correlation remain unverified.
.github	c0049783d665	Governance and acceptance status records; no metadata, deployment, or release change is implied.
AI-Ascension.github.io	d0d8087e80c9	Merged PR19 static evidence and repository pages; Pages deployment succeeded and runtime/release evidence remain unverified.

• Game-mod PR69: merged at b9754b8 from head ab702db, with Rust foundation, policy, and managed source-only checks successful. The native co-op contracts and probes remain source/component evidence; no live two-peer host/client run, model-controlled action settlement, vote convergence, checksum settlement, or disconnect/rejoin trace is claimed.
• Storage cleanup: the fresh identity-bound cleanup remains storage evidence only; it does not establish a current native install, host load, provider settlement, or model-played gameplay.
• Remaining acceptance gates: native final artifact installation and loading, model-provider settlement, model-played Victory, native multiplayer actions and disconnect/rejoin recovery, Workshop agreement/item state/content/update/rollback lifecycle, deployment, public release, and gameplay ingestion/persistence/correlation in both observability backends remain unverified. The operator query-access prerequisite remains open in observability issue #8.

Latest current default-main source records — 2026-09-10, 08:09 UTC

A fresh read-only GitHub refresh after harness PR #50 merged recorded nine default-main heads and 27 open pull requests. The records are source/component and pull-request evidence, and do not establish native host loading, settled effects, provider execution, deployment, release, Workshop lifecycle, or general compatibility. The status supplement retains the exact capture and individual pull-request states.

Repository	Current main	Source/component boundary
sts2-game-core	07b51c88ebe9	Host-independent semantics and tests.
sts2-game-mod	903b645bf4dc	Seeded-run adapter source and managed boundary; native expert gameplay, installation, and settlement remain unverified.
sts2-gateway	6b6c7f2fac67	Seeded-run gateway source and bounded routes; host settlement and deployment remain unverified.
sts2-mcp-server	73e777b96700	Seeded-run transport and gateway mapping source; native MCP-to-game settlement remains unverified.
sts2-harness	33437ddb18f6	Merged PR #50 durable recovery and raw action identity source; provider execution, native host restart, and gameplay settlement remain unverified.
sts2-protocol	e5e545c2ff71	Seeded-run protocol contract source, schemas, artifacts, validators, and conformance cases.
ai-agent-observability	28a48590afb7	Source topology and deployment tooling; current-main gameplay ingestion, persistence, and two-backend correlation remain unverified.
.github	e11bc10775e	Governance and acceptance status records; no metadata, deployment, or release change is implied.
AI-Ascension.github.io	d5a11452334a	Merged PR18 static evidence and repository pages; Pages deployment is separately reported and runtime evidence remains unverified.

• Harness source boundary: harness PR #50 merged at 33437ddb with durable recovery and raw action identity source. This is a component boundary and does not establish provider execution, native host loading, or gameplay settlement.
• Storage cleanup: a fresh identity-bound precheck removed the previously reviewed stale Windows candidate exactly once, then verified the retained profile save and canonical source by unchanged hashes. Free space increased by 2,407,784,448 bytes. This is storage evidence only; it does not establish a current native install, host load, provider settlement, or model-played gameplay.
• Remaining acceptance gates: native final artifact installation and loading, model-provider settlement, model-played Victory, native multiplayer actions and disconnect/rejoin recovery, Workshop agreement/item state/content/update/rollback lifecycle, deployment, public release, and gameplay ingestion/persistence/correlation in both observability backends remain unverified. The operator query-access prerequisite remains open in observability issue #8.

Current owner evidence

• Native campaigns and fresh replays: a visible Windows Astra campaign reached Defeat with 333 settled actions, and a fresh process replay completed all 333. The Linux campaign reached Defeat with 431 settled actions after one controller restart following a catalog-read failure; its separate fresh native process replay began at Setup and completed all 431 without continuation, with an independent audit. Read the Windows record and Linux record.
• Terminal observation: forced Windows and Linux native fixtures observed a living-player Victory surface with disabled input and an empty legal catalog. They bypass ordinary play and do not establish a model-played campaign Victory. Read the native Victory record.
• Native co-op admission diagnostic: a separate two-process diagnostic reached the same later native run and exposed distinct native peer identities; both processes reported two peers with loading and recovery false, and the owned processes were cleaned up. After the client was stopped, the host kept reporting two connected peers for 164.257112 seconds while logging Peer not connected send errors. No model participation, action, vote, shared effect, settled outcome, disconnect event, rejoin, or recovery was observed, and the capture was obscured by a Windows Firewall prompt.
• Read-only co-op synchronization: the consumed coop-synchronization-v1 profile produced and read coordinator reports through the gateway and MCP executables. The check covered convergence, disagreement, disconnect/recovery, stale leases, and rejected reports with zero downstream game connections. It has no native peer identity, action, vote, shared-effect, or multiplayer game authority. Read the executable evidence.
• Still unverified: model-played Victory, all characters/seeds/branches, broad restart and host-version coverage, native multiplayer gameplay and recovery, clean-install/update/rollback and Workshop publication, and current-main evidence of real gameplay telemetry reaching both observability backends. The operator query-access prerequisite remains open in observability issue #8. See the current status supplement for reviewed source heads.

Earlier current default-main source records — 2026-09-10, 02:22 UTC

The following nine exact default-main records come from a fresh GitHub REST refresh. They are source/component evidence. They do not establish a host run, provider settlement, deployment, or release. The linked status supplement retains the 36 open PR heads, draft/ready states, mergeability, and check conclusions from the same refresh.

Repository	Current main	Bounded record
sts2-game-core	87e0f3d9355c	Host-independent semantics and tests.
sts2-game-mod	c21ddf38bd2b	Runtime-v4 expert bridge and bounded synthetic checks; native expert gameplay and settlement remain unverified.
sts2-gateway	776327aca63c	Runtime-v4 routes and map consumer path; host settlement and deployment remain unverified.
sts2-mcp-server	4787efa1251b	Runtime-v4 mapping and REST selector recovery; native MCP-to-game settlement remains unverified.
sts2-harness	f8b5858d0997	Documentation merge on top of merged PR41 functional source; provider, native, host-restart, and gameplay settlement remain unverified.
sts2-protocol	7fa0d8e82fbc	Runtime-v4 schemas, artifacts, validators, and conformance cases.
ai-agent-observability	28a48590afb7	Source topology and deployment tooling; current-main gameplay ingestion, persistence, and two-backend correlation remain unverified.
.github	217c9c10d82f	Governance and acceptance status records.
AI-Ascension.github.io	832068b69a44	Static evidence and repository pages; deployment remains unverified.

• Harness PR41 review: the merged source head 03fdc626 was independently checked at its exact head: 179 changed files, formatting, policy, Clippy, and a serial workspace result of 285 passed and 5 ignored. A default-parallel process-start race was retained as a validation limitation; the serial rerun passed. The bounded map, replay, REST recovery, and receipt-query source does not establish native gameplay or provider settlement.
• Remaining gates: native final artifact identity and installation, model-played Victory, native co-op actions and disconnect/rejoin recovery, Workshop lifecycle, provider settlement, deployment, and live gameplay telemetry ingestion/correlation in both observability backends remain unverified.

Latest post-merge default-main source records — 2026-09-10, 02:36 UTC

A second read-only GitHub refresh after the documentation merges updated the repository heads. These exact records are source/component evidence; they do not establish a host run, provider settlement, deployment, or release. The status supplement records the 31 open PRs from this same refresh.

Repository	Current main	Bounded record
sts2-game-core	87e0f3d9355c	Host-independent semantics and tests.
sts2-game-mod	caae865986d2	Merged seeded-run adapter and Runtime-v4 source/component paths; native expert gameplay and settlement remain unverified.
sts2-gateway	2b44bf347f79	Merged seeded-run boundary and Runtime-v4 routes; host settlement and deployment remain unverified.
sts2-mcp-server	b5a9262f1c76	Merged seeded-run profile and Runtime-v4 mapping; native MCP-to-game settlement remains unverified.
sts2-harness	3926e5a30ab5	Merged seeded-run transport and PR41 source; provider, native, host-restart, and gameplay settlement remain unverified.
sts2-protocol	d3ab5fca7d9d	Merged seeded-run selection context and Runtime-v4 schemas, artifacts, validators, and conformance cases.
ai-agent-observability	28a48590afb7	Source topology and deployment tooling; current-main gameplay ingestion, persistence, and two-backend correlation remain unverified.
.github	8336899bb0a1	Governance and acceptance status records.
AI-Ascension.github.io	2ae456c6395c	Static evidence and repository pages; deployment remains unverified.

• Post-merge identity: the organization main is 8336899bb0a and the site main is 2ae456c6395c. The site PR16 hosted static-and-proof check completed successfully.
• Remaining gates: native host loading, model-provider settlement, terminal gameplay, native co-op actions and recovery, observability persistence/correlation, Workshop lifecycle, deployment, and release remain unverified.

Historical source snapshots

The bullets below preserve the 2026-09-05 source and CI review. They remain historical and are not a current runtime claim.

• Source-derived: default-branch documents record a bounded runtime-v1 host probe on 2026-09-02 through harness → MCP → gateway → managed/native mod → Godot. The reported action was show_runtime_probe, with an overlay witness, generation advance, stale-generation rejection, and lease release. Read the mod report and cross-repository report.
• Evidence limit: these are author-reported host observations, not independently repeated by this site review. They name STS2 v0.107.1, Windows x86-64, an exact host-assembly digest, and pre-rename package hashes. Their source states include uncommitted changes; the reports are not a reproducible all-committed release matrix. The cited operator capture is not retained in the repository.
• Unverified: reliable autonomous gameplay, gameplay-rule mutation from that probe, provider-backed full runs, restart recovery, multi-instance concurrency, current-package host parity, other platforms, and release support. Merging Runtime-v3 source does not establish any of these.
• Source-derived: on 2026-09-05 the Exo semantic-catalog runtime-v3-gameplay lane merged into the default branches of protocol, game-core, game-mod, gateway, MCP, and harness; the competing bounded play_card lane was closed as superseded with its branches preserved. Each repository's declared gates passed at the merged head. That is confirmed only for those commands at those commits, and is not evidence of gameplay, settlement, autonomous runs, or host execution: no game was launched, no mod loaded, and no provider called. The managed bridge still has no concrete IRuntimeV3HostSource, an unverified integration limitation. The reviewed source heads are in the 2026-09-05 snapshot. Two co-op proposals remain open and are credited to no default branch.
• Source-derived: after that stack, function-budget follow-ups merged on 2026-09-05: game-mod PR #27 at bc46e443 and harness PR #19 at 3b9a70f. Their checks cover source and repository policy at those commits; this remains source/CI evidence and does not establish gameplay, settlement, autonomous runs, or host execution. The managed bridge still has no concrete IRuntimeV3HostSource, an unverified integration limitation. The reviewed source heads and evidence limits remain in the dated status snapshot.
• Source-derived correction: subsequent game-mod PR #28 merged at 8dca9890 to cover the frozen Runtime-v2 checksum inventory in CI, and PR #29 merged at f9b81f47 to clarify native safety and historical evidence. The PRs record source, CI, and documentation corrections; they do not establish gameplay, settlement, autonomous runs, host execution, provider calls, or deployment. The historical pins and explicit unverified limits above remain in force. Reviewed source heads remain in the dated status snapshot.
• Source-derived correction: protocol PR #12 merged on 2026-09-05 at 3470bd6291d87d4d3259ebe075ce3417d26812cf. It splits the Runtime-v3 action/transition/recovery and artifact-metadata/request-context definitions into dedicated modules and removes the two policy size exemptions; the PR records unchanged public reexports, schemas, frozen artifacts, and digests. This is source and repository-policy evidence only; consumer behavior, gameplay, settlement, autonomous runs, host execution, and provider calls remain unverified. The historical pins and explicit limits above remain in force.
• Source-derived: the organization now includes ai-agent-observability. Its self-hosted configuration and checks are separate from the gameplay path; source and CI are not proof of an operated deployment.

Rust remains central to the product crates, but the organization also contains managed C#, shell launchers, this static HTML/CSS/JavaScript site, and observability configuration/Python tooling. Follow each repository’s scoped policy exceptions.

The five labels

confirmed

Reproduced by a deterministic test or command at a pinned commit, observed by the project on a named date.

source-derived

Read directly from repository source or documentation at a pinned commit, but not executed.

proposed

A design direction or planned path. Nothing about it is claimed to work.

inferred

A reasonable conclusion from confirmed or source-derived facts that has not itself been tested.

unverified

Not established for the specified component, version, environment, or behavior. A bounded host observation must not be generalized to autonomous gameplay or another package.

Stamps are always paired with the word; the colour alone never carries meaning.

Historical foundation claim ledger — 2026-09-02

Rows below preserve the early pinned-source scope, not current capability ceilings. Read the later evidence update first. Historical claims of local or browser verification are author-reported unless separately reproduced.

Description synchronization

A historical description map was used on 2026-09-02 for: the organization profile, the descriptions and homepages of all eight repositories, the public-entry block at the top of each README, the metadata and Open Graph tags of this site, the social and proof cards, and the launch drafts. Each sentence was reviewed by cold readers who had not seen the repositories, revised twice, and approved on 2026-09-02. Later implementations can legitimately change those descriptions. Reconcile differences against dated source evidence rather than treating this historical map or its image cards as current capability ceilings.

Historical workflow observations — not current CI

Local validation on the same day: every workspace's tests pass and the policy tool reports zero errors, with --locked --offline on Rust 1.97.1.

What is unknown

• Traction: unknown. Stars and forks observed as 0 on 2026-09-02 are counts, not activation.
• Users: unknown. No analytics exist by policy.
• Referrals: unknown. The only measurement is an optional, consented "how did you find this" field on the issue forms.
• Retention: unknown.
• Whether a custom domain is intended: unknown; the site uses the default Pages URL.

Unknown is not zero, and it is never presented as either success or failure.

How to dispute a claim

Open an evidence issue: github.com/AI-Ascension/.github/issues/new?template=evidence.yml. Name the row number or the exact sentence, the surface where you read it, what you observed instead, and the command or file that shows it. A claim that cannot be backed is relabelled or removed; the ledger records the change.

Post-artifact source-head refresh

confirmed Two bounded source changes merged after the 22:27 UTC native artifact snapshot. Gateway PR #34 is 8ba5521c / tree afb63ec0; CI 34543637424 and policy 34543637382 passed. It preserves historical persisted host-install rows until a fresh in-memory grant and adds restart coverage.

confirmed Harness PR #66 is a0ace671 / tree ece08dbf; CI 34542788897 and policy 34542788865 passed. It adds an authenticated native worker endpoint and durable admission/recovery checks.

unverified The accepted protocol artifact remains bound to gateway c8be3a72 and harness 63dc5636; these later source heads were not silently substituted into the captured conformance record. No live host install, two-peer native action, shared settlement, disconnect/rejoin recovery, or model-played victory is established by these source checks.

Latest default-branch source refresh

confirmed A fresh read-only GitHub refresh at 2026-09-11T02:02:14Z records the current heads after the 23:48 UTC snapshot. Protocol 0bc689ea / tree 6d91bcf4 follows README-only PR #20; its current CI 34547243872 and policy 34547243877 passed. The accepted artifact files and digest remain unchanged from f22dd721.

confirmed Gateway f5582995 / tree 9f5f25f0 follows README-only PR #21; CI 34547237851 and policy 34547237849 passed. Game-mod bd8e9054 / tree 54ffc38e follows README-only PR #55; CI 34547520887, policy 34547520864, and its managed source-only boundary passed.

confirmed Harness 787c5dce / tree 2d0fd1f9 follows PR #67, which preserves provisional Unknown evidence during repeated recovery. Current CI 34552750699 and policy 34552750723 passed; the intervening PR #60 bounded context-memory policy and PR #65 added user-selected Ollama models. PR #67 CI 34552479720 and policy 34552479649 passed.

unverified The accepted native artifact remains protocol f22dd721 / tree 0e053e68, with conformance bound to producer capture input d23ca838, gateway c8be3a72, MCP 037d10de, and harness 63dc5636. The current heads above were not substituted into that source_to_consumer: pass record. The r7 capture remains the synthetic CapturePort record with 9 wrappers, projection_match: true, schema digest 2f3bc99e53080fa11b39592b64fb0ab964a16f568719a2622d0b2caf766ab629, and native_session_executed: false. No live host install, provider execution, model-played Victory, two-peer native action, shared settlement, native checksum settlement, or disconnect/rejoin recovery is established.