Matrix Lifecycle System

Overview

The Matrix Lifecycle System is the part of Ora that gives work a shape in time. Every piece of work in the vault — a project under way, a routine being run, a question being explored, an idea being held in incubation — lives in a matrix. The matrix is not just a record; it is a typed structure with a lifecycle. The classification determines the lifecycle, and the lifecycle determines what the supervisory machinery (PEF, Process Coherence) does at each stage. The Matrix Lifecycle System is the four classifications, the lifecycle shape per classification, the inter-classification transitions, and the cross-pool cultivation that operates across all matrices simultaneously.

Four classifications, mutually exclusive at the core. Project — focused effort with a finite, tangible deliverable and a terminal endpoint at delivery. Operation — going concern producing recurring deliverables on a cadence with no terminal endpoint until sunset criteria are met. Passion — ongoing exploration with practices and directions of travel; no terminal claims to verify; no required deliverables. Incubator — pre-classification holding pattern; an idea with a Critical Unknown that will eventually resolve into one of the other three classifications. Domain types (book, knowledge, workflow, fiction) compose with the core; a matrix is one of the four core types and may carry a domain type alongside.

Each classification has a shape in time. Projects initialize with a Resolution Statement, populate Active milestones (P-Feasibility-verified) and Aspirational milestones (with Contingency notes), iterate as work proceeds (PEF iterate; Promotion Protocol promotes Aspirational to Active as Contingencies resolve), close at the terminal Active milestone, and optionally pass through the Project closure conversion gate that fires Project → Operation conversion when the deliverable continues producing value through ongoing use. Operations initialize via one of four entry modes (O-FromProject / O-FromScratch / O-FromExisting / O-FromCorpus), populate a Service Statement plus Cadence rule plus Coordinated Corpora plus Coordinated Outputs plus recurring Active milestones plus Aspirational maturity gates, run cycles (Cycle Close Verification per cycle), promote maturity gates as multi-cycle patterns hold, and optionally pass through a Devolution Gate offering three clean exits (Sunset / Revert to Passion / Recast as Project). Passions initialize with Mission Core Essence and Emotional Drivers, populate Practices and Directions of Travel, iterate with light supervision (practice continuity, direction-of-travel evolution), and may reclassify when a stable Resolution Statement candidate emerges (Project) or recurring deliverables emerge (Operation). Incubators initialize with a Critical Unknown plus exploration plan, accumulate evidence toward resolution, and reclassify as Project / Operation / Passion when the Critical Unknown resolves.

Two frameworks specify the system’s apparatus directly. The Operations Manifest specifies the Operation classification’s matrix structure and runtime — it is the matrix-shape framework for Operations alongside the implicit matrix-shape definitions for Projects (in Mission/Objectives/Milestones Clarification), Passions (also in MOM), and Incubators (also in MOM). The Inception and Incubation Framework is the only framework in the system whose scope is the entire matrix pool simultaneously — it operates across MindSpec, the vault matrix index, and the Incubator pool, finding intersections, surfacing dormant items, and responding to inspiration events. Together they provide the classification-specific specification (OM for Operations) and the cross-pool cultivation (IIF for the whole pool).

What the system does that no individual framework or classification does is provide a classification taxonomy with reclassification machinery. A matrix is born as one of the four types and may transform through several types in its lifetime — an Incubator’s Critical Unknown resolves and the matrix reclassifies as a Project; the Project ships and converts to an Operation; the Operation runs for years and devolves to a Passion. At each transition, the strategic-layer content reformulates per the new type’s shape, the supervisory machinery shifts to the new type’s behavior, and the matrix’s history is preserved in its Iteration History. The taxonomy is not just a labeling exercise; it is the runtime structure that determines what happens to the work over time.

Systemic context

The Matrix Lifecycle System is the substrate the supervisory apparatus operates on. The Strategic Supervision System (PEF + MOM + Lock + Promotion Protocols) reads project_type from the matrix’s frontmatter and dispatches type-specifically — but the type definitions, lifecycle shapes, and reclassification machinery are this system’s responsibility. The Coordination Layer (Process Coherence + Oversight Configuration + Meta-Layer Architecture) supervises matrix-level events at runtime — but again, the matrix-type-aware lock-loading depends on this system’s type definitions. The Information Lifecycle System (PFF, PIF, CFF, OFF, TMF, DCA) operates on corpora and outputs that matrices declare consumption of (Operations declare Coordinated Corpora; Operations declare Coordinated Outputs; Projects can spawn corpora as deliverables) — the consumption-declaration semantics are specified in Operations Manifest, but the broader information-flow apparatus is the Information Lifecycle System’s. The Knowledge Production System (MindSpec Interview + KAC + Creativity from Knowledge and Values) feeds into IIF’s value-alignment math (MindSpec is the values substrate that IIF reads) — IIF’s residue measurement is the empirical evidence for the Knowledge Production System’s central claim that recognition is irreducibly human.

Constituent frameworks and lifecycle definitions

Operations Manifest (OM v1.0) — the Operation classification specification. Per-framework treatment in Operations Manifest Framework. Specifies the Operation Matrix’s strategic-layer fields (Mission, Service Statement, Cadence rule, Coordinated Corpora, Coordinated Outputs, recurring Active milestones, Aspirational maturity gates, Performance Log, Incident Log, Spawned Activity Registry, Devolution Gate); the four entry modes (O-FromProject for Project → Operation conversion, O-FromScratch for top-down vision, O-FromExisting for formalizing informal practice, O-FromCorpus for corpus-need-driven Operations); Cycle Close Verification with the four cycle-shape near-miss patterns; Maturity Gate Specification; Devolution Gate’s three options. Reuses MOM, PEF, CFF, OFF, and Process Coherence rather than inventing parallel apparatus. Bound by the Friction Principle (low-complexity matrices stay small) and the Substrate Boundary (the framework coordinates cognitive scaffolding, not embodied substrate).

Inception and Incubation (IIF v1.0) — the cross-pool cultivation framework. Per-framework treatment in Inception and Incubation Framework. The only framework whose scope is the entire matrix pool simultaneously. Three modes — Mode 1 (Generation cadence — plant) runs value-alignment math across MindSpec and the vault matrix index, surfaces top intersections, generates candidates, pre-filters via the adversarial pipeline, presents the digest; Mode 2 (Review cadence — water + retire) surfaces existing Incubators by drift signal (dormant, newly relevant, decaying, adjacency-active); Mode 3 (Inspiration response — combine, event-driven) handles in-conversation inspiration events with adjacency search. The Recognition Lock binds the framework: recognition cannot be silently substituted by automation. The Spark Recognition Corpus accumulates the empirical record over many cycles; the residue (recognitions the value model cannot predict) is the central evidence for the white paper on creativity = recognition.

The Project lifecycle. Init → populate strategic layer (Mission, Resolution Statement, Excluded Outcomes, Constraints, Objectives, Active and Aspirational milestones) → iterate (PE-Iterate cycles with drift checks against Excluded Outcomes; Promotion Protocol promotes Aspirational to Active as Contingencies resolve) → close at terminal Active milestone (PEF Layer 4’s drift check verifies completion) → optional Project closure conversion gate (PEF Layer 5’s Promotion Protocol step b: “Does this deliverable continue producing value through ongoing use?” If yes, dispatch to OM-Convert mode with convert-in-place vs. spawn-new options). Spawned Projects can spawn under a parent matrix; the parent’s Spawned Activity Registry records the relation.

The Operation lifecycle. Init via one of four entry modes (specified in OM) → populate strategic layer (Mission, Service Statement, Cadence, Coordinated Corpora, Coordinated Outputs, recurring Active milestones, Aspirational maturity gates) → run cycles (Cycle Close Verification per cycle; Performance Log appends; Incident Log appends on deviation) → promote maturity gates as multi-cycle patterns hold (Promotion Protocol step c) → optional Devolution Gate (Sunset / Revert to Passion / Recast as Project) when the Operation should no longer continue. Operation-spawned Projects may build apparatus the Operation needs; sub-Operations may run under a parent Operation; Coordinated Corpora are independent CFF entities the Operation declares consumption of (with primary-curator markers).

The Passion lifecycle. Init with Mission Core Essence and Emotional Drivers → populate Practices and Directions of Travel → iterate with light supervision (PE-Iterate watches practice continuity and direction-of-travel evolution; no terminal claims to verify, no Lock on Resolution Statement because there isn’t one) → reclassification possible if a stable Resolution Statement candidate emerges (Project) or recurring deliverables emerge (Operation). Passion supervision is light per the Friction Principle; the matrix is the home for the work, the supervisory machinery does not produce false alarms on work that legitimately doesn’t have terminal claims.

The Incubator lifecycle. Init with a Critical Unknown plus exploration plan → accumulate evidence toward resolution (the Critical Unknown is the matrix’s endpoint analog; resolution is the lifecycle goal) → reclassify as Project / Operation / Passion when the Critical Unknown resolves (MOM Layer 1 reclassification; the matrix’s project_type updates; the strategic layer reformulates per the new type’s shape; Iteration History preserves the Incubator history). The Critical Unknown can resolve into any of the three other classifications — this was a deliberate generalization in 2026-05-08 to retire the prior implicit assumption that Incubators only became Projects.

The cross-pool layer. IIF is the only framework whose scope is the entire matrix pool simultaneously. Mode 1 generates candidates at high-value intersections of MindSpec values and existing matrices — sparks become new Incubators. Mode 2 surfaces existing Incubators by drift signal — dormant, newly relevant, decaying, adjacency-active — for review and decision. Mode 3 handles inspiration events — adjacency search across the pool, missing-piece combinations, direct promotion to Project / Operation / Passion when the spark is hot. The cross-pool layer is what gardens the matrix space: ideas plant (inception), water or retire (incubation), combine (inspiration response). PEF iterate and Process Coherence operate per matrix; IIF operates across the pool.

End-to-end worked example

Scenario. A user has been thinking about how independent builders find their first paying customers. They’re not sure if it’s an idea they’ll write about, a newsletter they’ll publish, or just a question they’ll keep noodling. They invoke IIF Mode 3 (inspiration response).

IIF Mode 3 / Inspiration response. The user brings the idea to a session: “I keep coming back to the question of how indie builders get their first ten customers.” IIF runs the adjacency math against the user’s Incubator pool. Top-3 adjacencies surfaced — two old Incubators (one about consultative-versus-product sales for technical founders; one about the asymmetry between launch announcements and ongoing customer support) plus one matrix from MindSpec values (a high alignment with “respect for craft as the route to commercial success”). The user reviews. They realize the new idea is a missing-piece combination with the consultative-sales Incubator — that one had been dormant because the user didn’t know what to do with it; the new framing gives it a home. The user picks: combine the new idea with the consultative-sales Incubator and update its Critical Unknown to “What is the actual playbook for indie builders moving from technical product to first ten paying customers, and how does it differ from the consultative-sales pattern that already exists?”

The Incubator matrix updates. Performance Log entry: Mode 3 success. The other two adjacencies are noted but no action taken. No new Incubator is created (the new idea integrated into the existing one).

Six weeks later / IIF Mode 2 review cycle. The monthly review cycle fires. Drift signal computation runs across the Incubator pool. The consultative-sales Incubator is flagged “newly relevant” (its alignment has continued to climb because of vault activity around indie-builder topics). The user reviews and decides: develop. The matrix passes through MOM Layer 1 reclassification.

MOM Layer 1 reclassification. MOM runs the four-test classification on the now-developed Incubator. The Project Test asks: “What is the primary, tangible deliverable?” The user names: “A weekly newsletter exploring the indie-builder customer-acquisition playbook for 12 consecutive weeks, then either continuing or wrapping with a synthesized e-book.” That’s a deliverable with a terminal endpoint at week 12. Project Test passes. Classification: Project. The Incubator’s project_type updates from incubator to project. The Critical Unknown reformulates as the candidate Resolution Statement; MOM Layer 3 runs the Resolution Statement Objectivity Protocol against it; Excluded Outcomes are surfaced; the matrix’s strategic layer is reformulated from Incubator-shape to Project-shape.

The Iteration History preserves the Incubator stage as the matrix’s pre-history; the Project lifecycle starts at iteration 1 of the Project type.

Twelve weeks of Project execution. Each week the user writes an essay. PE-Iterate runs at month-end on the matrix. Each iteration’s drift check confirms no Excluded Outcome firing positive (no slide into general business commentary, no slide into off-frame guests, no slide into pure aggregation). The Performance Log records each week’s success. The terminal Active milestone — “12th essay shipped, e-book draft synthesized” — is approached.

Project terminal milestone closure. Week 12 ships. The matrix’s terminal milestone is verified complete via PEF Layer 4’s drift check. PEF Layer 5’s Promotion Protocol fires the Project closure conversion gate:

“Your Project’s terminal milestone has closed. Does this deliverable continue producing value through ongoing use?”

The user pauses. The newsletter has built an audience; the synthesized e-book is one deliverable but the audience is going to keep wanting to hear from them. Yes — the deliverable continues producing value.

“Convert in place (flip project_type from project to operation in this matrix file; prior Project content moves into the founding Operation Iteration Entry) or spawn new (create a new Operation Matrix; preserve the Project Matrix as historical record)?”

The user picks convert in place. The matrix’s project_type updates to operation. PEF dispatches to Operations Manifest’s OM-Convert mode (specifically O-FromProject entry mode).

OM-Convert / O-FromProject. OM reformulates the strategic layer. The Resolution Statement (“12th essay shipped, e-book draft synthesized”) becomes a Service Statement candidate (“Continue publishing the indie-builder customer-acquisition newsletter on a weekly cadence, with quarterly synthesis essays and annual e-book editions”). The Service Statement Objectivity Protocol runs (cycle-shape adaptation). New Operation-shape Excluded Outcomes are surfaced — cadence met but quality degraded; coordinated corpora consumed but unchanged; output produced but not consumed; maturity gate gamed not earned. Cadence rule: weekly by Friday morning. Coordinated Corpora: the existing newsletter archive, an emerging research-notes corpus. Coordinated Outputs: the weekly essay; the quarterly synthesis; the annual e-book. Recurring Active milestone replaces the prior terminal milestone. Aspirational maturity gates added: “52 consecutive weekly essays shipped without missing cadence” and “annual e-book edition shipped two years running.” Devolution Gate documented (Sunset / Revert to Passion / Recast as Project as future options).

The Project’s content moves into the founding Operation Iteration Entry. The matrix is now Operation-shaped; Process Coherence will fire on cycle-close events going forward; the Performance Log starts fresh under the Operation classification but the Iteration History preserves the full Project → Operation arc.

Two years later / Devolution. The newsletter has run as an Operation for two years. Audience has shifted; the user’s interest has moved on; the work feels rote rather than alive. PEF Layer 4’s drift detection picks up a sustained pattern of degraded cycles. The Devolution Gate fires.

“The Operation has been showing sustained drift signals — degraded cycles, missed cadences, declining engagement. Three options: Sunset (close cleanly; matrix archived as historical record), Revert to Passion (you keep writing on indie-builder topics but not on a required cadence), Recast as Project (synthesize the entire run into a final e-book or book and finish that).”

The user picks Recast as Project. The matrix’s project_type updates from operation to project. The Service Statement reformulates back to a Resolution Statement: “Final synthesis book on the indie-builder customer-acquisition playbook is published and the newsletter is closed.” Active milestone: ship the synthesis book by Date X. Aspirational milestones underneath. The Operation stage is preserved in the Iteration History. The matrix lifecycle continues — but as a Project with a terminal endpoint.

That is one matrix’s journey across the lifecycle system: Incubator (with cross-pool inspiration) → Project (twelve-week newsletter run) → Operation (two-year ongoing publication via Project → Operation conversion) → Project (final synthesis book via Devolution Gate’s Recast option). Three classifications inhabited; two reclassifications fired; the Iteration History preserves the full arc. The matrix is the same file the entire time — the lifecycle is the shape work takes in time, and the matrix backbone supports the shape changing as the work itself changes.

How to compose this system

You can run the Matrix Lifecycle System pattern with any AI of your choice using the per-framework specifications and the classification taxonomy. The composition is heavier than single-framework composition because the system spans multiple frameworks and the cross-pool layer needs values + matrix index substrates.

The minimum useful composition is: the Operations Manifest framework specification, the Inception and Incubation framework specification, the four-test classification logic from MOM (you can paste MOM too if you want full classification dispatch), and your existing matrix file (if any).

For a single-matrix transition (e.g., your Project just shipped its terminal milestone and you want to consider Operation conversion), the prompt is:

[Paste the Operations Manifest specification and the MOM specification]

Run OM-Convert against this matrix.

[Paste your closing Project matrix]

The terminal milestone has been verified complete. Run the Project closure conversion gate. If I convert, dispatch to O-FromProject and reformulate the strategic layer.

The AI returns: the gate question with reasoning, the convert-in-place vs. spawn-new options with implications, and (after your choice) the reformulated Operation Matrix.

For cross-pool work (e.g., you want the system to surface Incubators that have become newly relevant), the prompt is:

[Paste the Inception and Incubation specification]

Run IIF Mode 2 (review cadence).

MindSpec: [Paste your values document.]

Incubator pool: [Paste your existing Incubators with brief summaries.]

Compute drift signals and surface by category.

The AI returns: the drift-signal classification per Incubator, grouped by signal, with evidence per item.

For the full lifecycle system (running across all four classifications and the cross-pool layer), the practical pattern is to invoke per-stage as needed rather than instantiating the whole system at once — the system runs across months and years; instantiation is per-event.

What this system enables

What this system does that the constituent frameworks alone do not is provide a classification taxonomy with reclassification machinery and a cross-pool cultivation layer. Three things become possible with the system that are not possible with the parts in isolation:

• Work has a shape in time, and the shape can change as the work changes. Without the system, a “project” is a labeling convenience — once the label is applied, the labeling stays even when the work no longer fits. With the system, an Incubator can resolve into any of three other classifications, a Project can convert to an Operation when the deliverable continues producing value, an Operation can devolve to a Passion when the cadence-pressure is no longer right. The matrix backbone supports the lifecycle shape changing without the matrix itself being recreated.
• Cross-pool cultivation operates over the whole matrix space, not one matrix at a time. Per-matrix supervision (PEF, Process Coherence) is necessary but insufficient — there are also patterns visible only across the entire pool of matrices. Newly-relevant Incubators that have become important because of recent vault activity. Inspiration events that retroactively activate dormant pieces in the pool. High-value intersections of MindSpec values and matrices that the user hadn’t named explicitly. IIF is the framework that operates at this scope; without it, the matrix space goes ungardened.
• The taxonomy is uniform across mutually-exclusive types with optional domain types composing. Before the four-classification system landed (2026-05-08), Project was the dominant classification, Operations had no home (they were forced into Project shape with awkward cycle workarounds), and Passion supervision was minimal. The unified four-classification taxonomy with mutually-exclusive core types and composable domain types lets every kind of work find a home with a lifecycle shape that fits — and the supervisory machinery treats them uniformly with type-appropriate weight.

Citations

The classification-with-lifecycle pattern draws on biology’s Linnaean taxonomy (mutually-exclusive types at each level with domain composition above and below), the project-management literature’s distinction between project and program (the proximate ancestor of the Project / Operation distinction), and lifecycle-management literature in software engineering (where artifacts pass through stages with explicit transitions). The reclassification machinery — matrices changing type without being recreated — is internal to Ora and emerged from the cumulative design sessions that produced the Operations Manifest in 2026-05-08.

The cross-pool cultivation pattern draws on combinatorial creativity research (Boden, Koestler, Kauffman) where novelty is recombination of existing elements, and on knowledge-management literature on the distinction between collection-level and item-level operations. IIF’s value-alignment math draws on Bayesian decision theory’s weighted-sum framing of preference aggregation. The Recognition Lock — recognition cannot be silently substituted by automation — is internal to Ora and grounds the white paper claim that recognition is irreducibly human; the empirical apparatus is the Spark Recognition Corpus, which accumulates the residue measurement over time.

The framework versions composed here are OM v1.0 and IIF v1.0, both canonical 2026-05-08; the four-classification system became canonical with the same date when the prior implicit Project-dominance was retired. Per-framework citations live in the per-framework papers (Operations Manifest Framework, Inception and Incubation Framework).

Open problems

• Every transition is a judgment call. The four-test sets the type; the reclassification triggers — a Critical Unknown “resolved,” a deliverable that “continues producing value,” “sustained drift” at the Devolution Gate — are all assessments, not measurements. A mis-judged transition gives the work the wrong lifecycle and the wrong supervision.
• The gates fire on heuristic thresholds. “26 consecutive cycles,” “sustained drift signals” — these are stated conditions, not learned ones. A gate can fire late (work stays rote past the point it should have devolved) or never fire at all.
• IIF’s value-alignment is a model of the user’s values, not the values. Mode 1 surfaces candidates by a weighted sum over MindSpec × the matrix index; high alignment is not high value, and the recognitions the math cannot predict — the Spark Recognition Corpus residue — are precisely the gap between the model and the thing modeled.
• Cross-pool cultivation only gardens what is already in the pool. IIF surfaces dormant matrices and high-value intersections among existing entries; value latent in ideas the user never captured as a matrix is invisible to it.