Overview

The Operations Manifest is the framework that coordinates work which has shipped and now keeps producing. It is the home for going concerns — publications, business cycles, personal routines, maintenance loops, monitoring systems — work whose value lives in continuing, not in completing. It sits as the fourth and final classification in Ora’s matrix system, alongside Project (finite-deliverable work), Passion (ongoing exploration without required deliverables), and Incubator (unclassified ideas in holding).

Most planning systems handle Projects well — finite goals, milestones, shipping dates. Most systems also recognize ongoing exploration, even if loosely. But the work that shipped and now keeps producing typically has no coordination home. A Project Matrix wants a terminal milestone; the work doesn’t have one. A Passion Matrix wants no required deliverable; the work has many. The Operations Manifest fills the gap.

The framework specifies what an Operation Matrix contains. A Service Statement — the cycle-shape parallel to a Project’s Resolution Statement — names what the Operation is committed to producing on each cycle. A Cadence rule defines what counts as a cycle (daily by 9am ET, weekly on Monday, on-event when a corpus updates). Coordinated Corpora are the bodies of information the Operation reads on its cycle; Coordinated Outputs are the rendered things it produces. Recurring Active Milestones replace a Project’s terminal milestones — they are the per-cycle commitments. Aspirational Maturity Gates fire after extended operation (100 cycles shipped without missing cadence; quarterly external review passed for a year) and signal mature operation. A Performance Log accumulates cycle-by-cycle outcomes. An Incident Log accumulates deviations. A Devolution Gate gives the Operation three clean exits — Sunset, Revert to Passion, or Recast as Project — when it’s time to stop.

The framework answers questions like: I run a weekly podcast — how do I track it without burying it in process? My business has accounting, customer ops, and product release cycles all on different rhythms — how do I coordinate them? My book just shipped and there’s a continuing audience now — what changes? My morning practice is starting to drift and I want to notice when it does — how do I set that up? The common shape is: there is something running that should keep running well, and the user wants a coordination home that supports rather than burdens it.

Two design principles run through the framework. The Friction Principle says the cost of populating an Operation Matrix must not exceed its coordination value. At the lower end of the operational complexity spectrum (a personal weekly routine), the matrix is three to five questions and fits on one screen. At the upper end (a publication with a 12-stage editorial workflow), the matrix legitimately becomes denser; the gradient is continuous and paced by the user. The Substrate Boundary says the framework coordinates the cognitive scaffolding around an Operation, not the embodied substrate the Operation operates in — the matrix tracks training plans and post-mortems for a personal training regimen, but the user still has to do the workout. The framework optimizes the direction of embodied work without claiming to embody it.

Systemic context

Operations Manifest does not iterate matrices on its own. The Problem Evolution Framework (PEF), which is matrix-type aware, reads project_type: operation and dispatches to OM specifications by reference — drift signals, MOM auto-invocation triggers, supervision drift checks, Promotion Protocol behavior, Iteration Entry recording. OM provides the Operation-side semantics PEF iterates against. Strategic-layer content is populated by the Mission, Objectives, Milestones Clarification Framework (MOM) running in M-Supervised mode with its Operation classification branch — Service Statement Objectivity Protocol replaces Resolution Statement Objectivity Protocol; recurring milestones and maturity gates replace terminal milestones. Coordinated Corpora are independent CFF (Corpus Formalization) entities; the Operation declares consumption rather than ownership. Coordinated Outputs are independent OFF (Output Formalization) entities; the Operation declares which it produces. Process Coherence supervises load-bearing fields across all matrix types and watches for cycle-shape drift signals. The five-framework picture — OM coordinated with PEF, MOM, CFF, OFF, and Process Coherence — is captured in [[Paper — Matrix Lifecycle System]].

Ora’s output

Example question: I publish a weekly podcast. I want a way to keep it running cleanly without slowly letting it drift into something different from what I started. What should I track, and what should I leave alone?

Ora’s response (running Operations Manifest in O-FromExisting mode, minimal invocation):

The work you’ve described is an Operation, not a Project — the value lives in continued production, not in shipping a single deliverable. Since you’re already running it informally, I’ll back-fill an Operation Matrix from observed practice rather than designing top-down. The Friction Principle says: at the personal-routine end of the complexity spectrum, the matrix should be small, the elicitation should be light, and supervision should match. Here is what the matrix gets, what it deliberately omits, and why.

Service Statement (descriptive of current practice, Lock-protected):

The podcast publishes one episode per week, on Monday morning, focused on conversations with builders working alone or in small teams.

That sentence does three things. It names the cadence (one episode per week, Monday morning). It names the deliverable (an episode of conversational interview content). It names the editorial frame (builders working alone or in small teams). The frame is the part most likely to drift if no one is watching, which is why it sits inside the Service Statement instead of in some looser editorial-vision document.

Excluded Outcomes (the cycle-shape near-miss patterns):

  • Cadence met but quality degraded — episode shipped Monday morning but the conversation was rushed or thin and you’d rather not have published it.
  • Cadence met but frame drifted — episode shipped Monday morning but the guest is no longer a builder working alone or in small teams; you’ve slid into general business interviews.
  • Output produced but not consumed — episodes are shipping but listeners have stopped engaging; the Operation is succeeding mechanically without producing value.

These are the patterns to watch for. They are the runtime guards against silent drift.

Cadence and Deliverables:

Weekly episode — one per week, published Monday by 9am — produced via your existing recording-and-editing workflow — Cycle Close Verification at publication.

Coordinated Corpora: None required at the personal-routine scale. If you accumulate a guest pipeline document, episode notes, or a research log, those become Coordinated Corpora later — but they don’t have to exist now. The matrix supports adding them when you want them; it does not require them up front.

Coordinated Outputs: Just the podcast feed itself.

Recurring Active Milestone: “Weekly episode published Monday by 9am.” Verification: Cycle Close Verification (was the episode published on time, was the conversation a Tier-1 conversation by your own standards, was the guest within the editorial frame). The Performance Log records the answer each week — success, degraded, or failed.

Aspirational Maturity Gate: “50 consecutive episodes shipped on cadence.” This is the gate that, if you cross it, signals the Operation is mature. PEF Layer 5’s Promotion Protocol fires when the gate is met and asks whether to promote a new gate (e.g., “100 consecutive on cadence with no quality degradations”), or whether the Operation is fully mature and the gate need not be replaced.

Devolution Gate: Three options if the Operation should stop — Sunset (the work is done, retire the matrix cleanly); Revert to Passion (you keep doing podcast-like work but not on a required cadence); Recast as Project (turn the catalog into a book and finish that). The gate is real and recorded; picking any of the three options is healthier than indefinite drift.

Performance Log: Initialized empty. Each Monday after publication, append one line — date, episode reference, success / degraded / failed, optional note. That is the Operation’s empirical record. After 20 entries, you can see whether you’re shipping clean, whether you’re shipping but degrading, or whether you’re missing.

Incident Log: Initialized empty. When a release is delayed or pulled, log it with what happened and what the resolution was. The pattern across incidents is what tells you whether the workflow needs adjustment.

What is deliberately omitted: No editorial board, no contributor onboarding template, no cross-cutting sponsor coordination corpus, no rendering pipeline specification. None of that exists in your current practice and adding it pre-emptively would burden the matrix into uselessness. If the podcast scales to a team, those sections come in then — not now.

What this gets you: A small artifact, fitting on roughly one screen, that names what you’re committed to producing, on what rhythm, what would count as drift, and how you’d notice. The Performance Log and Incident Log are the empirical record across cycles. When PEF iterate runs (you can fire it monthly, or when something feels off), it reads the matrix, checks for drift signals, surfaces near-miss patterns if it sees them, and recommends small adjustments. Process Coherence watches the Service Statement for silent edits and surfaces them if they happen.

That is the Operation’s coordination home. It is small because the work is small. As the work grows, the matrix grows with it.

Commercial AI comparison

Comparison content auto-populates when the comparison-refresh framework runs against this question. Drafters do not author this section.

Brief comparison commentary

Auto-populates with the comparison content above.

How to use this framework

You can run the Operations Manifest pattern with any AI of your choice using a single composed prompt. Paste the framework’s specification, then your description of the operation you want a coordination home for. The AI will produce the Operation Matrix.

The composition pattern in three pieces:

  1. The framework instructions. The full text of Framework — Operations Manifest.md (downloadable below). Paste it as the first part of your prompt.
  2. Your operation description. A natural-language description of what you’re already running (or want to run), the cadence, what corpora and outputs are involved (if any), and which entry mode applies — O-FromProject (a finished project that should keep running), O-FromScratch (top-down vision), O-FromExisting (informal practice you want to formalize), or O-FromCorpus (a body of information that has surfaced an underlying operation).
  3. Your invocation choice. Tell the AI which mode you want: minimal (three-to-five-question quick draft), or full (every layer elicited).

A complete prompt looks like:

[Paste the full Framework — Operations Manifest specification]

Run OM-Init in O-FromExisting mode, minimal invocation.

Operation description: I publish a weekly podcast on Monday mornings, focused on conversations with builders working alone or in small teams. I record on Wednesday or Thursday, edit on Friday, and ship Monday. I have no formal coordination apparatus. I want a coordination home that helps me notice if I drift, without burdening me with process.

The AI will return an Operation Matrix back. You can save it to a vault, a Notion page, a markdown file — wherever you keep your work. The format is markdown, plain text, and self-contained.

If you don’t have a vault system, you can keep the matrix as a single document and refer to it monthly to check whether your practice still matches what the matrix says. The Performance Log can live as a running list of entries; the Incident Log as another. The matrix is the thing; everything else is the empirical record around it.

The framework is deliberately tool-agnostic. It runs the same against Claude, GPT, Gemini, or any other capable model. The substance — Service Statement, Cadence, Excluded Outcomes, the Friction Principle, the Substrate Boundary — does not depend on Ora’s runtime. The runtime is Ora’s coordination apparatus; the framework is a thinking tool any reader can pick up.

Other examples

  • A small accounting practice. Monthly client deliverables, quarterly tax cycles, annual audits. The Operation Matrix coordinates three different cadences (monthly, quarterly, annual) and several Coordinated Corpora (client documents, tax-code reference, prior-year working papers). The Service Statement names the practice’s commitment (“monthly close by the 15th, quarterly filings on schedule, annual audit complete by April 30 for affected clients”); Cycle Close Verification on each cadence catches degradation early. Demonstrates multi-cadence Operations and dense Coordinated Corpora.

  • A personal training regimen. Three workouts per week with embodied substrate. The Service Statement names the practice (“strength training three times per week, progressive overload, alternating push-pull-legs split”). Coordinated Corpora are light — a training plan document, a video reference library. Performance Log records what was done and how it felt; Incident Log records form breakdowns or injuries. Demonstrates the Substrate Boundary directly: the matrix coordinates direction; the workout itself happens off-vault and the user logs it.

  • A book that’s just shipped. The Project closes; a continuing audience exists. The user runs PEF Layer 5’s Promotion Protocol, the Project closure conversion gate fires, and the user converts the Project Matrix into an Operation Matrix in place. Service Statement reformulates from “first edition shipped” to “ongoing reader engagement maintained, errata addressed, supplementary material released as warranted.” Demonstrates O-FromProject conversion — the canonical shape of “Project shipped and now keeps producing.”

Citations

The Operations Manifest sits at the intersection of several traditions. Operations management — W. Edwards Deming’s plan-do-check-act cycle, Eliyahu Goldratt’s theory of constraints — is the proximate ancestor of cadence-based work specification. The Lamrim tradition in Tibetan Buddhism is the canonical example of a framework that scaffolds the cognitive direction of practice without claiming to embody the practice itself; the Substrate Boundary in this framework is named for it. ITIL and similar IT service management frameworks supply the modern vocabulary for “service” as a cycle-shape commitment. The Friction Principle as a design heuristic owes to Don Norman’s work on the design of everyday things — at low complexity, a system’s value depends on whether the user adopts it, which depends on whether the setup cost is dominated by the coordination value. The matrix-type-aware iterate pattern is internal to Ora and is documented in [[Paper — Problem Evolution Framework]].

The framework is single-author and originated 2026-05-08. The worked examples (the Main Street Independent publication as a Project → Operation conversion; the Inception and Incubation Operation as a self-referential research instance) are documented in Appendices C and D of the canonical specification.

Downloads

  • Framework specification (PDF) — link to ora-ai.org canonical artifact when published
  • Framework specification (plain text) — link to ora-ai.org canonical artifact when published
  • Full white paper (PDF) — link when published