← Blueprint for solo SE consultants
Operational scenarios, nominal + off-nominal, generated.
The ConOps is where the mission becomes concrete — Design Reference Mission scenarios that walk the system through its operational envelope. Blueprint generates these from your brief: nominal paths first, off-nominal contingencies after, with every actor, environment assumption, and success criterion traced to the source.
What a Blueprint scenario carries.
Per the NASA SE Handbook §4.1.2.2, a ConOps scenario documents the system in operation against a specific mission profile. Blueprint emits the canonical structure:
- Scenario name + classification (nominal vs off-nominal)
- Operational environment — physical, regulatory, organizational
- Stakeholders involved + their roles in the scenario
- Step-by-step operational sequence with timing + decision points
- Performance expectations traced to MOEs / MOPs
- Source citations per claim — the brief chunk that justified each step
ARCHIPELAGO (1,500-word coastal-swarm brief) yields 4 nominal + 3 off-nominal scenarios — coastline survey, obstacle-encounter, communication-blackout fallback, swarm- recovery on partial loss, etc. Each is independently citable + addressable as DRM-N or DRM-N-off.
The math.
The canonical ConOps section. Blueprint output cites the section directly + traces to it.
Nominal + off-nominal pair per major mission mode. Scales with brief detail.
Each scenario step links to the MOE / MOP that scores its success — the V&V trace lives in the ConOps.
Full Phase 1.4 run. ConOps is one of 35 artifacts; the rest land at the same time.
Why generated ConOps holds up.
ConOps is the artifact most prone to “LLM hallucination adjacent to operational details” — a generic prompt produces plausible-sounding mission steps that the reviewer recognises as fiction. Blueprint avoids this for two structural reasons.
The Stakeholder Worker runs before the ConOps emitter. By the time scenarios are generated, the stakeholder register + NGO tree + constraints register are already grounded in citations. The scenario builder doesn’t invent actors; it composes the ones the brief already named.
The Citation Verifier judges every operational claim. Each scenario step that asserts a behavior or assumption gets a citation pointing at the source. The independent LLM judge passes or fails the link; failures are surfaced in the run telemetry as “ICC precision” — measured at 80% on ARCHIPELAGO.
Questions about ConOps generation.
How many scenarios does Blueprint generate per mission?
Scales with brief detail. A 1,500-word coastal-swarm brief yields ~4 nominal + ~3 off-nominal. A 3,000-word multi-phase mission yields proportionally more. The Handbook doesn't prescribe a count — Blueprint follows the brief's natural decomposition.
Can I add a scenario after generation?
Yes. Output is markdown — add a scenario section in your editor following Blueprint's structure. The citation chain breaks for hand-added steps unless you cite back to the brief manually; that's the trade-off.
Does Blueprint generate sequence diagrams or just text?
Text-first. The operational sequence is a numbered step list with actors + timing. Mermaid sequence diagrams are roadmapped for the bundle export; today, generate a diagram from the text in your tool of choice.
Related.
- AI requirements writer →
Shall-statements with rationale + verification + citation.
- AI shall-statement writer (deep dive) →
How a Blueprint shall-statement is structured + how to read its citation.
- ← Back to: Blueprint for solo SE consultants