One Rust search-matrix config reproduces depth, strata, and leaf comparisons locally and on EC2
One immutable Rust search-matrix configuration can evaluate the same ordered public roots across multiple completed depths, chance-strata counts, and named leaf-weight files on a workstation or a large x86 EC2 instance, retaining per-column values, selected actions, work, scheduling, memory, and machine analytics sufficient for exact cross-depth comparison.
On this page
- Created
- Updated
No explanation has been written for this record yet.
Technical recordThe registered claim, mechanism and falsification criteria
- Claim
- One immutable Rust search-matrix configuration can evaluate the same ordered public roots across multiple completed depths, chance-strata counts, and named leaf-weight files on a workstation or a large x86 EC2 instance, retaining per-column values, selected actions, work, scheduling, memory, and machine analytics sufficient for exact cross-depth comparison.
- Mechanism
- A Rust analytics binary reads a frozen root corpus and a Cartesian matrix of depths, strata, and leaf definitions, then invokes the deterministic central-frontier scheduler for every cell and writes canonical JSONL rows. A launcher packages an exact source snapshot, resolves the regional Amazon Linux x86_64 AMI through AWS's public SSM parameter, optionally creates a time-limited targeted Capacity Reservation, launches an IMDSv2-only instance with no inbound SSH requirement, enforces a wall timer and instance-initiated termination, uploads artifacts, and records the AWS and machine identifiers. The same matrix command is used locally and remotely.
- Falsification criteria
- The frozen-weight Rust leaf differs bit-for-bit from the existing Rust fair leaf on any checked state, or the matrix binary changes an action/value when only output order or worker count changes.
- The analytics output omits any requested root/depth/strata/leaf cell, legal sibling value, task/work/cache count, timing segment, worker utilization row, source/config hash, or machine profile reference.
- The EC2 launcher can silently exceed its declared wall/memory/cost envelope, leaves an unlimited Capacity Reservation, uses a hard-coded regional AMI, requires public SSH ingress, or changes the matrix configuration between local and remote execution.
- Information class
- infrastructure
- Lifecycle
- assessed
- Assessment
- supported-as-tested
- Evidence tier
- mechanics-only
- Dependencies
- Evidence references
Agent contextHow to extend this record
To add a reader-facing explanation, write web/content/research/TH-20260825-rust-search-matrix-ec2-6fc9f806.mdx; it renders above this record on the next request. The registered record itself is in the technical record above.
Record file: research/theories/TH-20260825-rust-search-matrix-ec2-6fc9f806.json, validated against research/schemas/theory-v1.schema.json.
Registered by Codex / unknown (root).