Understanding Campaign Results

The campaign result is one self-contained JSON artifact that includes the validated input as request_snapshot.

runs/campaign/<campaign-id>/campaign_plan_result.json

Read It In This Order

Section	Question
status and campaign_summary.status_class	Was the objective fully, partially, or unsuccessfully achieved?
summary	What strategy, duration, event count, assignment count, and propellant burden resulted?
campaign_summary.target_summary	Which positions were achieved, and what blocks the remainder?
campaign_summary.assignment_summary	Were all spacecraft assigned, and which assignments were overridden?
campaign_summary.event_summary	Was sequencing valid and how did the campaign unfold?
campaign_summary.mission_burden_summary	Which missions succeeded, were infeasible, or failed, and at what burden?
assignments, events, and missions	What detailed plan produced those summaries?
selection and diagnostics	Why was this strategy and refinement path chosen?

Begin with target closure. Fleet assignment is one input to closure; timing, sequencing, orbital residuals, and mission feasibility determine whether the target was fully achieved.

Outcome Classes

• Success means the requested completion criteria were met.
• Partial success means useful plan elements were produced but one or more target criteria remain unresolved.
• Unsuccessful or failed mission outcomes require their reason codes and diagnostics to distinguish physical infeasibility, campaign constraints, and execution failure.

For a partial campaign, the achieved positions, residual satellite count, blocking dimensions, and burden are the decision evidence.

Mission Side Bundles

Full artifact detail adds:

campaign_plan_result.missions/
|-- campaign_mission_bundles_manifest.json
`-- <satellite-id>/
    |-- mission_plan_request.json
    `-- mission_plan_result.json

These files support deeper mission review, while the campaign result remains the primary artifact.

Deterministic Review

astraeus review campaign --result <campaign_plan_result.json>

Add --output <review.md> to persist the review. The command is a deterministic reader of saved artifacts and leaves the campaign result unchanged.

When comparing campaign variants, compare the embedded request snapshots, outcome class, target summary, mission burden, and sequencing—not only total duration or propellant.

For field-level contracts, see the Campaign result reference.