Phase‑Map‑and‑Gates

Phase Map and Gates

The Genesis Code Protocol is organised into a sequence of phases, each with its own checkpoint. Between phases the run arrives at a gate, where you must decide whether to proceed, branch to another phase, return to a previous checkpoint or terminate. The exact numbering and names vary between editions, but the overarching structure remains the same.

Typical phases

Below is a high‑level overview of common phases. Later editions may add or rename phases; consult the edition page (e.g. GCP‑V50) for specifics.

• Spark Generation / Worth‑It – evaluate the initial idea or automatically generate sparks to pursue. Confirm that the idea meets basic worth‑it criteria before proceeding.
• Opportunity & Mode – define the opportunity space, choose Full Run or Auto mode and set the risk tier (R1–R3).
• Context & Influence – gather background information, constraints, stakeholder impacts and market forces.
• Futures & Morph Space – explore future scenarios and morphological possibilities; generate divergent designs to broaden the search.
• Envelope & Hypotheses – set boundaries for the solution space and formulate hypotheses to test.
• Adversarial & Red‑Team – stress‑test assumptions through adversarial analysis, red‑teaming and counter‑examples.
• Concept Development – design solutions, propose architectures and produce prototypes or models.
• Simulation & War‑Game – run numerical models, simulations and war‑games to evaluate performance under various conditions.
• Refinement & Validation – optimise concepts, run experiments, cross‑validate results and compute metrics.
• Simplification & Optimisation – simplify solutions, optimise resources, and refine architectures for feasibility.
• Productisation & Documentation – prepare for deployment, generate user documentation, API references and integration guides.
• Readiness & Continuous Assurance – address readiness criteria, risk‑tiered rigour and continuous assurance (compliance, security, safety). This phase may include special gates for data rights and regulatory mappings.
• Closeout & Exit Wizard – finalise artifacts, archive intermediate work and run the Exit Wizard to export the Invention Package.

The phase map is linear by default but supports branching and loops when necessary. Each phase ends with a gate that prompts a decision in Auto mode or awaits your instruction in Full Run mode.