Evidence
Every claim, and the line that backs it.
This ledger lists each public claim used on this site and in the repository READMEs, its label, and the file, test, or command that supports it at a pinned commit. If a row is wrong, dispute it.
Labels
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. Applies to every runtime, host, game, and compatibility claim today.
Stamps are always paired with the word; the colour alone never carries meaning.
Claim ledger
Claim ledger
| # | Claim | Label | Evidence (file@commit · test · command) |
|---|---|---|---|
| 1 | A forward request carrying a stale lease epoch is denied as Fence(StaleEpoch) before any transport call (transport calls: 0). | confirmed | control_plane.rs@e7bce21 · stale_epoch_and_wrong_instance_are_denied_before_transport · cargo test --workspace --all-targets --all-features --locked |
| 2 | A proof naming a different instance is denied as Fence(WrongInstance) before the transport. | confirmed | same test as row 1; replay step 4 in fixture.json |
| 3 | A 9-byte body against an 8-byte limit is rejected as BodyTooLarge { limit: 8, actual: 9 } without a transport call; a valid forward makes exactly one transport call and returns 200. | confirmed | control_plane.rs@e7bce21 · fixed_transport_is_bounded_and_fail_closed |
| 4 | The gateway fails closed on readiness and process-crash faults. | confirmed | control_plane.rs@e7bce21 · readiness_and_crash_fail_closed |
| 5 | Shutdown closes admission and reports a stop failure rather than hiding it. | confirmed | control_plane.rs@e7bce21 · shutdown_reports_stop_failure_and_closes_admission |
| 6 | A fresh lease epoch is 1; allocation reconciles through the readiness port; release leaves the instance Stopped with one graceful stop. | confirmed | control_plane.rs@e7bce21 · allocation_reconciles_through_readiness, release_then_cleanup_removes_instance; control.rs |
| 7 | One MCP tool call maps to exactly one gateway request (GET /v1/instances/{id}/state) with x-mcp-request-id/x-mcp-session-id headers. | confirmed | seam.rs@5faed97 · valid_call_maps_to_one_owned_gateway_request, correlation_preserves_mcp_request_and_session_namespaces |
| 8 | The MCP adapter rejects malformed JSON (-32700), invalid params (-32602), and unsupported capabilities (-32601) before any gateway access; gateway Unauthorized maps to -32001. | confirmed | seam.rs@5faed97 · malformed_json_is_rejected_before_gateway_access, malformed_tool_arguments_are_invalid_params, unsupported_capability_is_rejected_without_forwarding, gateway_authorization_error_maps_to_stable_rpc_error |
| 9 | Core validate is pure: it accepts a valid action without mutating the snapshot and rejects stale generations and actor mismatches deterministically. | confirmed | domain_validation.rs@6c46a55 · accepts_valid_action_without_mutating_snapshot, rejects_stale_generation_before_action_rules, rejects_actor_mismatch_before_other_request_checks |
| 10 | Core golden vectors are reproducible across repeated evaluation (×64). | confirmed | same file · golden_vectors_are_reproducible_across_repeated_evaluation |
| 11 | Protocol metadata round-trips to the exact golden bytes; malformed digests fail closed; schemas are implementation-neutral. | confirmed | protocol_conformance.rs@f3ef7ca · neutral_metadata_round_trips_to_the_exact_golden_bytes, malformed_digest_and_safe_message_fail_closed, schema_and_case_are_implementation_neutral |
| 12 | Harness model retry reuses correlation and idempotency keys; records are idempotent and replayable; artifacts are lineage-bound; close unbinds every port once. | confirmed | foundation.rs@b485150 · model_retry_reuses_correlation_and_idempotency, records_are_idempotent_and_replayable, artifact_metadata_is_lineage_bound, close_unbinds_and_closes_every_port_once |
| 13 | Game-mod HTTP admission reaches the (fake) host only after the bounded main-thread queue is pumped; body limit and ABI gate fail closed; close rejects new admission without dropping existing work. | confirmed | composition.rs@aa465f3 · http_admission_reaches_fake_host_only_after_main_thread_pump, body_limit_and_abi_gate_fail_closed, close_rejects_http_admission_without_dropping_existing_work; queue capacity in crates/host/src/queue.rs (Full { capacity }) |
| 14 | All six product trees are Rust-only; non-Rust source is prohibited by the policy tool, which reports zero errors locally. | confirmed | each repository's tools/repo-policy · cargo run -p repo-policy -- --strict (0 warnings, 0 errors, 2026-09-02) |
| 15 | The browser replay and the cargo recipe print the same trace. | confirmed | fixture.json sha256 1115b6f6…695d; the proof page embeds the file byte for byte; three headless runs by the site builder and three by an independent verifier produced trace hash 80095d8c; six recipe runs (three warm, three from a fresh cargo home) hashed 1115b6f6…695d; recorded in VERIFICATION.md |
| 19 | A four-model live race on separate streams, described at aiascension.tech, is the intended use of this path. | proposed | event-site copy fetched 2026-09-02 (no stream links present); nothing in any repository runs a game or a model |
| 16 | A live Slay the Spire 2 path through mod, gateway, MCP adapter, and harness. | proposed | each repository's docs/ARCHITECTURE.md; no runtime exists |
| 17 | Runtime, host, and game compatibility. Planning host target STS2 v0.107.1 (Windows x86-64). | unverified | each repository's docs/COMPATIBILITY.md; planning target only |
| 18 | Isolation under real concurrency; authentication at an external boundary. | unverified | not claimed; only record-level isolation exists (sts2-gateway README) |
Descriptions
Description synchronization
One approved description map drives every public surface: 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. If a description on any surface differs from the one shown on the repositories page, that is drift, and it is a defect.
CI resultsobserved 2026-09-02
Workflow results on main
| Repository | Continuous integration | Repository policy | Cause |
|---|---|---|---|
| sts2-game-core | success | failure | DOC002: README link target outside the repository |
| sts2-game-mod | failure | failure | escaped \${{ … }} in both workflow files; no jobs ran |
| sts2-gateway | success | failure | DOC002: README link target outside the repository |
| sts2-harness | success | success | |
| sts2-mcp-server | success | success | |
| sts2-protocol | success | success |
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.
Unknown
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.
Dispute
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.