Public Methods, Replication, And Review Surface

This is where CCT's search grammar becomes executable. Formal constraints, prospective simulation questions, frozen comparisons, resource fronts, and physical exposure paths become objects another reader can inspect or rerun.

The selected release gives CCT a compact working memory. It records what was asked, which assumptions were active, what the comparator knew, how resources were counted, what outcome changed the route, and which question follows next. This lets formal work constrain experiments, simulation select higher-value exposures, and physical results return to a common language.

Download CCT Selected Public Replication Release V1.1

The archive is approximately 3.4 MB. Its SHA-256 is:

6edb487b9cd89d08bb38be0e3492a390946077bfef36d8c67043b17b8544473a

Inside the archive, README.md is the operator quickstart, CLAIMS_EVIDENCE_MAP.md connects each result to its artifact and next exposure, SOURCE_SET.json freezes the allowlist, and verify_release.py checks the package end to end.

What The Surface Makes Possible

Turn theory into active search constraints

CCT's theorem stack does more than sit beside the experimental program. It reveals which patterns are easy to manufacture, which conclusions are underdetermined, which resources must be counted, which causal paths must be conditioned, and which stronger claim requires a new proof object.

The package pairs bounded formal results with executable companions. The analytical proof establishes the result. The companion exercises its declared scope, assumptions, counterexamples, route priorities, and machine-readable certificate.

The compact proof spine contains five reader-facing theorem families:

  • scalar multiwell anti-uniqueness, OP0a;
  • regime-local measurement envelopes, OP1;
  • finite-state command attribution, OP3;
  • passive focusing and Born/Helmholtz routes, BT7b;
  • finite multi-resource programmability fronts, Vector OP4.

Explore Selected Formal Results and Open Questions

Test prospective regime discovery

Four simulation chains test increasingly substantial possibilities.

  • Structured space-time excitation improved a fixed-wave process frontier at equal incident energy, with destructive controls for phase, timing, and model alignment.
  • A frozen coordination-order grammar predicted useful handles and transferred to an external excitable-system model.
  • A common task-aligned intervention contrast prospectively separated positive, boundary, and adverse temporal-coordination regions across two standard-physics model families.
  • A structural representation changed prospective experiment selection under matched information, policy access, acquisition logic, and probe budgets, reducing regret-curve area against a tuned raw-schedule search.

The package carries the frozen configurations, source runners, result tables, reports, and artifact verifiers for all four chains.

A completed follow-on benchmark now extends the limited-probe chain across 36 new cases in three model systems. It treats the search representation and candidate menu as empirical parts of the method, locating a family-specific structural-search advantage and exposing transfer sensitivity across systems and menu construction. That paper-stage benchmark is summarized in When Structure Helps or Hurts Search; its manuscript and standalone replay package are candidates for a later selected replication release rather than contents of the current release.

Make architecture and resources first-class

Two narrower exhibits show how architecture can create useful handles:

  • a distributed schedule that writes retained geometry and fails under route-destroying controls;
  • frequency-position-mode co-design that exposes a controllable deformation mode absent from a lower-handle architecture.

Vector OP4 then makes the comparison front-valued. Energy remains central, while latency, calibration, synchronization, memory, reliability, setup, recovery, and support can change which strategy is genuinely preferable.

Carry results toward physical exposure

Three public-safe exposure cards translate the current search into physical questions:

  • measurement regime and observer mode;
  • field geometry and stable control basins;
  • route-state topology, retention, and reset.

They freeze the comparison class, measurements, branch outcomes, and next public artifact while leaving build-specific implementation in the controlled execution layer.

Translate physical primitives into Tau-X questions

The release includes one mission-ledger template and one synthetic translation example. These ask what an earned primitive would change in timing, sensing, coordination, correction, recovery, reliability, infrastructure, and the complete resource front.

This makes the mission horizon testable from both directions. Tau-X can send a hard requirement backward into theory, simulation, or CCT Labs; an earned primitive can travel forward into a more capable mission architecture.

Explore Tau-X

Choose A First Route

If you want to inspect... Start with... What it demonstrates
Formal constraints The five notes and companions in open-theorem-working-notes/ and cct-public-replication/ How bounded assumptions, counterexamples, and route consequences become executable.
Structured physical information Fixed-wave pilot and confirmation How phase, timing, and architecture affect a process frontier under equal incident energy.
Coordination order Coordination-order challenge and FHN transfer How an interaction-order grammar can predict and transfer a useful control sequence.
Cross-domain opportunity mapping Phase-0R map and Phase-1 discrimination How one prospective quantity separates positive, boundary, and adverse regions.
Limited-probe discovery Structural search and tuned raw-schedule GP How intervention structure can change which experiment is selected and reduce search burden.
Structural-search validity Prospective three-system benchmark summary How the usefulness of a search representation changes across system families and candidate menus.
Architecture leads Retained geometry and frequency-position-mode co-design How route structure and independent physical handles can change reachability.
Physical exposure exposure-cards/ How the selected evidence becomes a measurement, basin, or retained-state question.
Mission translation tau-x/ How an earned local primitive would enter a mission ledger.

Representative Reruns

After extracting the selected release:

python -m pip install -r requirements.txt
python verify_release.py

The runbook also provides individual commands for every formal capsule, simulation chain, and architecture exhibit. Campaign reruns begin by creating a fresh mutable workspace, preserving the frozen selected release and its hashes.

From Executable Object To Physical Exposure

The public surface helps a candidate move through a connected sequence:

  1. State the question. Define the observable, estimator, intervention, target, and comparison class.
  2. Apply formal constraints. Identify what can already be proved, ruled out, or narrowed.
  3. Map the candidate regime. Use simulation and synthetic cases to expose operating regions, confounders, and failure boundaries.
  4. Freeze the decision. Record what each workflow knows, what it selects, and what result changes the route.
  5. Expose it physically. Carry the selected question into CCT Labs or an appropriate external facility.
  6. Return the result. Update the theorem target, estimator, branch map, resource front, or mission architecture.

This is how public replication supports discovery rather than arriving only after it. The same objects that let another reader inspect a result also help decide which result is worth pursuing.

Public Reference And Controlled Execution

CCT uses two coupled execution layers.

The public reference layer exposes selected definitions, theorem companions, code, schemas, frozen comparisons, result tables, public-safe outputs, and reusable exposure structures. It gives outside readers and collaborators a shared interface for inspecting and extending the program.

The controlled execution layer carries build-specific materials, geometries, operating windows, calibration values, search maps, hardware constants, private notebooks, and partner-specific implementation choices. It preserves the continuity and experimental advantage needed to turn public questions into effective physical runs.

The layers meet through public-safe manifests, preregistrations, result summaries, and promotion records. That connection keeps the public method usable while allowing physical execution to remain cumulative.

Where Exact Status Lives

Different pages answer different questions:

  • What CCT Has Built and Opened presents selected capabilities, results, and next-stage possibilities.
  • Selected Formal Results and Open Questions presents the compact proof spine and active theorem frontier.
  • The selected release README.md provides the operator quickstart.
  • CLAIMS_EVIDENCE_MAP.md ties each public result to its source and next exposure.
  • SOURCE_SET.json and CHECKSUMS.sha256 record exact release contents and integrity.
  • Artifact-level READMEs and result files own the detailed interpretation of individual runs.

The selected release is the runnable front door. The Research Library preserves the wider conceptual and technical context.

See What CCT Has Built and Opened · Explore CCT Labs · Enter the Research Library