Eureka

Philosophy

Generation quality must be traceable to what was validated. A package must not simultaneously claim acceptance and rejection; this release centers on evidence and status consistency.

Architecture & control flow

1. 01

   Reuses the discovery_v52 contract, tension, equation, object, conjecture and bridge layers.

2. 02

   aurora_bridge translates physics abstractions, equation genomes, conjectures and counterexample fields into Aurora inputs.

3. 03

   reconcile_final_verdict treats Aurora as authoritative, recomputes summary counts and propagates status to each idea.

4. 04

   Bridge transitions gain explicit provenance; version enums and test-discovery wrappers are aligned.

Architecture outline derived from this version’s control flow.

Inputs & outputs

Inputs

Eureka direction/mode plus equation, physical-abstraction, conjecture and counterexample records.

Outputs

A discovery package with canonical final_verdict, consistent summary counts and per-idea verification_status, plus gate summaries.

Implemented components

• Concrete Aurora adapters, terminal reconciliation, explicit bridge transitions and standard test-runner wrappers.

Implementation & evidence scope

Surrogate simulation and function-style CoMath stubs remain; full integration, agent coordination and claim provenance are deferred. The 5.4 audit found the CLI still rebuilt a seed genome rather than always indexing the harvested payload, with unresolved abstract-unit and UNKNOWN-residual issues. Seeded prior fields support structural checks but do not constitute a real literature backend.

Code & bundled material

The introduction draws on bundled notes, changelogs and central code. Software tests, synthetic diagnostics and scientific effectiveness use different evidence standards.