01
Let phase pointers reflect real progress
Stars focuses on control flow and report contracts. A phase marked paused should not also advance the run pointer; missing literature should not count as a completed frontier. It repairs these inconsistencies so pauses, resumption and final reports agree more closely.
02
A hard gate at envelope resolution
Missing or low-confidence field resolution retains a paused state and phase_0. Draft fields can remain in the envelope without authorizing the literature stage. Scope resolution becomes a visible prerequisite: resumption must actually resolve framing instead of skipping it because artifacts exist.
03
Wait for the literature response
When literature-cartographer is unresolved, phase_1 remains in place and records the pending role rather than writing a placeholder frontier and searching onward. Only a response is saved as frontier_graph before advancement. Literature becomes a stage prerequisite with an explicit source point for later candidates and comparisons.
04
Route actions by node type
Routing reads a node-type schedule rather than merely rotating by depth, tracking tried operations, visits and exhaustion. Mechanisms, experiments and attacks can follow different progress paths. In this snapshot much of that tracking is still in memory; Jupiter and Galaxy later tighten persistence.
05
The local scaffold still needs content
Stars uses local node skeletons again, clearing placeholder strings and leaving fields for later fulfillment. This differs from Ocean’s role-driven expansion path: stricter phase gates do not mean every content capability was preserved. State control, node generation and final gates must be inspected separately rather than inferred from version numbering.
06
Align reports with validation
Report structure and validation are aligned around accepted candidates, repair-pending frontiers, honest failure and invalid runs. Tree, ledger, reviews and report remain separate for evidence tracing. Inputs depend on field and literature responses, and a paused state can be the output when the work is unfinished.
07
From content interfaces to phase consistency
Relative to Ocean, Stars repairs low-confidence advancement, unresolved literature fallback and phase gates, while adding node-type scheduling and report consistency. These are control-flow changes, not validation of scholarly outcomes. Jupiter then makes refutation affect candidate lifecycle, separating correct advancement from correct acceptance.
08
Where resumption actually continues
Resumption is best inspected through agreement among phase, status and pending role. A run still in the literature stage should expose the unfinished request instead of treating later nodes as prior-supported. Stars enforces this through phase gates, reducing contradictions between state and materials. Gates determine both the next operation and how a report can describe completed work.
Scheduling requires a similar check: type defines available operations, the tried list records unfinished ones, and exhaustion affects further selection. Fields and routing exist, but complete preservation of in-memory changes across resumption should not be assumed. Later event persistence addresses the need to retain post-creation revisions as well as the initial tree.
09
Retain non-monotonic changes in the history
Internal changelog and source identify Stars despite older V4-pro README headers. The snapshot retains local seeds or skeletons and incomplete operator-state persistence. This account does not convert engineering-gate success into novelty capability or conceal the change in generation path from Ocean to Stars.
Reading example · Explaining the workflow
Reading a paused literature stage
Suppose the field is resolved but literature cartography has not supplied a frontier.
- 01
Hold the literature stage and record the pending role.
- 02
Save the actual frontier after fulfillment before allowing expansion.
- 03
Inspect the next node-type action and whether the local skeleton has enough research content.
A run record separating waiting for literature from permission to search.
A conceptual reading example. No generation, retrieval, review or experiment was run, and no performance result is reported.
Changes in this version
Phase control
- Earlier approach
Some paused states advance or write a placeholder frontier.
- This version’s approach
Keep the phase on pause until necessary responses arrive.
Align resumption with the actual unfinished work.