← Flightdeck cockpit

Mission detail

Mission 4 — Standard Mission Template Research & Calibration

Discover, test, and calibrate the smallest standard Founder’s Flightdeck Mission template that can launch diverse Missions in planning mode, separating universal Mission avionics from goal-specific add-ons and skills.

activePersistentMission Wake armed

Owner

Pilot + Navigator

Mission updated

Sep 6, 2026, 12:18 a.m.

Flight log

2 events

Active assumptions

0

Evidence

0 records

Wake history

0

Mission operational scan

Planning mode — requirements gathering

In flightNo decision required

Navigator is doing

Gather the Mission 4 requirements by comparing Missions 1, 2, and 3: identify what every Mission requires, what is optional, what belongs in core Avionics, what belongs in add-ons or Skills, and what Planning Mode must learn before recommending additional capabilities.

Next Gate

Mission 4 produces a first candidate Standard Mission Template with explicit universal core fields/capabilities, optional add-on categories, Planning Mode requirement questions, Authority Envelope requirements, and evidence showing which elements are truly shared across materially different Missions.

Attention

Nothing needs the Pilot now.

Latest durable Flight Log change

Mission reality reconciled through mission_4_planning_started: Mission 4 entered planning mode to gather and test the requirements for a standardized Founder’s Flightdeck Mission template and modular add-on model. (1 operational, 0 evidence-bearing, 0 historical attention events observed; no active Pilot attention remains).

Open detail

What the Pilot needs to know now

Pilot attention

Nothing currently requires Pilot intervention. Historical evidence remains visible without reopening resolved attention.

Mission objective

Discover, test, and calibrate the smallest standard Founder’s Flightdeck Mission template that can launch diverse Missions in planning mode, separating universal Mission avionics from goal-specific add-ons and skills.

Latest durable Flight Log change

Mission reality reconciled through mission_4_planning_started: Mission 4 entered planning mode to gather and test the requirements for a standardized Founder’s Flightdeck Mission template and modular add-on model. (1 operational, 0 evidence-bearing, 0 historical attention events observed; no active Pilot attention remains).

Evidence that matters

0 evidence records · 0 active assumptions · 0 historical records currently meet Mission Wake materiality.

Pilot judgment

No Pilot decision is currently required.

Current state

Planning mode — requirements gathering

In flight

Navigator is doing

Gather the Mission 4 requirements by comparing Missions 1, 2, and 3: identify what every Mission requires, what is optional, what belongs in core Avionics, what belongs in add-ons or Skills, and what Planning Mode must learn before recommending additional capabilities.

Navigator owns this action. The Pilot does not need to execute it.

Next Gate

Mission 4 produces a first candidate Standard Mission Template with explicit universal core fields/capabilities, optional add-on categories, Planning Mode requirement questions, Authority Envelope requirements, and evidence showing which elements are truly shared across materially different Missions.

Mission Operating Loop · V0

Evidence → judgment → action → learning

Loop clear to continue

A single read-only view of the Mission chain. It does not infer a decision, clear a Signal, or advance authority.

1. Evidence

0 records

No current Wake materiality

2. Assumptions

0 active

No active assumptions recorded

3. Signal / blocker

Clear

No active blocker

4. Decision / action

Navigator authorized

Gather the Mission 4 requirements by comparing Missions 1, 2, and 3: identify what every Mission requires, what is optional, what belongs in core Avionics, what belongs in add-ons or Skills, and what Planning Mode must learn before recommending additional capabilities.

5. Outcome / learning

Recorded

Mission reality reconciled through mission_4_planning_started: Mission 4 entered planning mode to gather and test the requirements for a standardized Founder’s Flightdeck Mission template and modular add-on model. (1 operational, 0 evidence-bearing, 0 historical attention events observed; no active Pilot attention remains).

Return path: verified outcomes and Navigator checkpoints belong in the Flight Log, where new evidence can reopen assumptions and propagate forward.

Mission Navigator · V0

Ask Flightdeck what happens next

Navigator answers from the Mission’s durable state and current cockpit evidence, while distinguishing Pilot-owned judgment from Navigator-owned execution. It does not invent authority or clear Signals.

Avionics · bounded execution V0

Record a server-verified Navigator checkpoint

This control re-reads durable Mission state and active Signals on the server before writing. It can append one immutable checkpoint to the Flight Log, but it cannot clear Signals, change decisions, advance build state, or cross Pilot authority.

Available only while the Mission remains inside its authority envelope with no active attention-bearing Signal.

Pilot Channel · V0

Record something Flightdeck should remember

Use this only when you want an observation preserved in append-only Mission history. You do not need to submit observations merely to keep the build moving.

This records evidence; it does not clear Signals or transfer Pilot authority.

Operational state

Planning mode — requirements gathering

Within authority envelopeOpen

Completed

Mission charter established around the hypothesis that every Mission should launch from a common operating core and earn goal-specific complexity through add-ons only as requirements become clear.

Next authorized action

Gather the Mission 4 requirements by comparing Missions 1, 2, and 3: identify what every Mission requires, what is optional, what belongs in core Avionics, what belongs in add-ons or Skills, and what Planning Mode must learn before recommending additional capabilities.

Verification gate

Mission 4 produces a first candidate Standard Mission Template with explicit universal core fields/capabilities, optional add-on categories, Planning Mode requirement questions, Authority Envelope requirements, and evidence showing which elements are truly shared across materially different Missions.

State updated

Sep 6, 2026, 12:18 a.m.

Mission Wake

No wake-worthy evidence

Open

Supporting or neutral evidence stays quiet. Weakening evidence becomes Watch. Contradictory evidence becomes Wake. Historical evidence remains preserved after attention is resolved; only active reviewing Signals keep this section open.

Quiet

supports · neutral

Watch

weakens

Wake

contradicts

Mission Flight Log

2 verified events

Open history

Append-only verified events. This is history, not a confidence score.

Mission reality reconciled through mission_4_planning_started: Mission 4 entered planning mode to gather and test the requirements for a standardized Founder’s Flightdeck Mission template and modular add-on model. (1 operational, 0 evidence-bearing, 0 historical attention events observed; no active Pilot attention remains).

mission_reconciled

Aug 29, 2026, 8:44 p.m. · avionics

Mission 4 entered planning mode to gather and test the requirements for a standardized Founder’s Flightdeck Mission template and modular add-on model.

mission_4_planning_started

Aug 29, 2026, 12:11 a.m. · navigator

Assumption Registry

0 active · 0 evidence records

Open

Operating beliefs are explicit and question-able. Evidence is attached to the belief it tests; confidence remains uncalibrated until repeated observation earns it.

No assumptions have been recorded for this Mission yet.

Mission signals

0 signals in history

Open

Signals stay in history after review. Resolving a Watch acknowledges it; it does not erase the evidence that caused it.

No material signals have been recorded for this Mission yet.