Skip to content
// PLATFORM · GOALS & MISSIONS

From business goals to executable software missions.

A four-level hierarchy that keeps strategy linked to execution. Every mission carries an owner, scope, risk, acceptance criteria, evidence, and approvals.

99.98%
Uptime
14.2ms
Latency
128/128
Nodes
platform · live fig_goals-an
// VOCABULARY

The four atoms.

Goal
A business or product outcome. Tied to a stakeholder, a measurable result, and a policy class.
Mission
A governed execution unit. Owns scope, risk, agents, evidence, and approvals.
Task
An implementation or validation work item produced by a mission and executed by an agent.
Evidence
Signed proof generated during mission execution — test packs, diffs, security findings, attestations.
// HIERARCHY

Goal-to-mission hierarchy.

  1. L0 // STRATEGIC OBJECTIVE

    Strategic objective

    Org-level outcome owned by an exec.

  2. L1 // PRODUCT GOAL

    Product goal

    A measurable product result laddering up to L0.

  3. L2 // MISSION GROUP

    Mission group

    A cohesive set of missions that together deliver the goal.

  4. L3 // MISSION

    Mission

    The governed execution unit with owner, scope, risk, acceptance.

  5. L4 // TASKS

    Tasks

    Agent-executable work items inside a mission.

  6. L5 // EVIDENCE

    Evidence

    Signed proof artifacts produced by the mission.

  7. L6 // OUTCOME

    Outcome

    The measured result rolled back to L1 / L0.

  8. CH · 08 · CONTINUE
// WORKED EXAMPLE

Launch subscription billing.

Goal
Launch subscription billing for the Pro tier by Q3 with < 0.5% involuntary churn.
Mission 1
Requirements + PRD with stripe-and-tax acceptance criteria.
Mission 2
Architecture brief: idempotent webhook handling, dunning state machine.
Mission 3
UI: checkout flow, plan picker, manage-billing portal entry.
Mission 4
API: subscription, invoice, dunning, webhook surface.
Mission 5
Test suite: 412 scenarios + tax-jurisdiction matrix.
Mission 6
Release readiness: PCI-DSS evidence pack and dunning runbook.
FIG · END OF FRAMEsig: hash-pinned · 08
// GOVERNANCE RULES

Every mission carries.

Owner

A named human, accountable in the audit ledger.

Scope

Files, repositories, tools, and data sources the mission may touch.

Risk class

Routing into the right approval and evidence policy.

Acceptance criteria

Machine-checkable conditions before evidence is signed.

Evidence

Test, security, and impact artifacts produced under the mission.

Approvals

The gates required — plan, merge, evidence, release.

FRAME · 07
FRAME · 08
// RELATED

Keep reading.

// INITIATE

Start a Software Factory pilot.

Connect one repository, one ticketing tool, and one mission. See evidence in days, not quarters.