Galaxy

Philosophy

Completing a workflow does not establish that a model performed the research. The system needs to distinguish model-supplied content from its own filling and enforce rejection decisions and budgets.

Architecture & control flow

1. 01

   Consume single-node, nodes and children response contracts.

2. 02

   Use kernel seeds for structural exploration while recording model and seed provenance.

3. 03

   Seed-only candidates skip review; reviewer rejection or ledger misbinding blocks acceptance.

4. 04

   Synchronize call statistics and persist review budgets and operator state.

Architecture outline derived from this version’s control flow.

What this version changes

Compared with Jupiter, focuses on provenance, output contracts, rejection and budget constraints rather than merely passing an idealized simulated path.

Implementation & evidence scope

Default structural exploration can still stall at mechanism nodes; Cosmos later improves candidate-stage progress. Changelog totals conflict between 32 and 34 tests, so they are not used here as capability metrics.

Code & bundled material

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