Mission Control Intake Lifecycle ¶

Mission Control uses Jira labels to make AIOE intake status visible and actionable. Every AIOE intake request must include REQ_SOPT_AIOE, then one lifecycle label that describes the current Intake state.

Intake Lifecycle Flow ¶

flowchart TD

    A[INTAKE_BACKLOG]
    A --> B[INTAKE_PO_REVIEW]

    %% PO Review
    B -->|Business review passed| C[INTAKE_ARCH_REVIEW]

    %% Architecture Review
    C -->|Technical review passed| D[INTAKE_SCRUM_READY]

    %% Scrum Ready
    D -->|Implementation work planned| F[INTAKE_SCRUM_DELIVERY]

    %% Done
    F -->|Work delivered and
    accepted by PO and customer| G[INTAKE_DONE]

    %% Styling
    classDef normal fill:#e6f0ff,stroke:#3366cc;
    classDef done fill:#d5f5d5,stroke:#2e8b57;

    class A,B,C,D,F normal;
    class G done;

flowchart TD

    %% Special states — reachable from any active stage
    subgraph SP [Special states — reachable from any active stage]
        direction TB
        CA[INTAKE_CUSTOMER_ACT_REQ]
        EA[INTAKE_EXTERNAL_ACT_REQ]
        R[INTAKE_REJECTED]
    end

    %% Styling
    classDef action fill:#fff2cc,stroke:#cc9900;
    classDef rejected fill:#ffe6e6,stroke:#cc0000;

    class CA,EA action;
    class R rejected;

Lifecycle Labels ¶

Label	Meaning
`INTAKE_BACKLOG`	Default state for newly submitted Intakes. Product Owners typically handle two to three Intakes concurrently and pick up new ones from the backlog according to their current workload.
`INTAKE_PO_REVIEW`	Waiting for Product Owner review to validate the business problem, value, scope, and priority, or because the requirements are not yet clear and require further refinement.
`INTAKE_ARCH_REVIEW`	Ready for architecture review and technical feasibility assessment.
`INTAKE_SCRUM_READY`	Approved by Architecture and ready for implementation by the Scrum team.
`INTAKE_SCRUM_DELIVERY`	Implementation work has been planned and is underway.
`INTAKE_DONE`	All linked implementation work has been completed and accepted by the Product Owner and customer.
`INTAKE_CUSTOMER_ACT_REQ`	Reachable from any active stage. Paused pending customer input, clarification, or a decision before work can continue.
`INTAKE_EXTERNAL_ACT_REQ`	Reachable from any active stage. Paused pending action from an external party or dependency before work can continue.
`INTAKE_REJECTED`	Reachable from any active stage. Rejected because the request is not aligned with AIOE priorities, lacks sufficient business value, is technically infeasible, or the external dependency cannot be resolved.

Three Roles in Intake Lifecycle ¶

Roles	Primary Responsibility
Product Owner	Prioritize intakes based on business value, customer impact, and urgency. Validate that the delivered solution meets the original request.
Architecture Office	Assess technical feasibility, review solution design, identify risks, evaluate team resources and provide architectural guidance.
Scrum Team	Implementation

Please refer to Home for an overview of how these three roles collaborate throughout the Mission Control intake and delivery process.