Stars

Philosophy

Acceptance, failure and pauses should correspond to consistent states; report-structure defects should not hide the actual cause.

Architecture & control flow

1. 01

   Hold the current phase when scope or literature responses are unresolved.

2. 02

   Select actions by node type: question, lens contract, mechanism, experiment, attack and candidate.

3. 03

   Align statistics across report outcomes and collect residual blind spots from reviews.

4. 04

   Provide test cases for phase gates, report schemas and repair nodes.

Architecture outline derived from this version’s control flow.

What this version changes

Compared with Ocean, repairs scope and literature gates and adds type-driven scheduling and complete report fields. This snapshot’s policy also returns to local seed construction, so it should not be described as fully retaining Ocean’s content-generation capability.

Implementation & evidence scope

The archive retains an older V4-pro README; Stars changelog and source establish the snapshot’s identity. Its reported golden tests concern simulated flow and structure, while the candidate-generation path still needs the later Jupiter repairs.

Code & bundled material

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