Factory is built in three layers. Modules are bounded building blocks. Workflows compose Modules, and sometimes other Workflows, into one complete job. Factory composes the Workflows across the product lifecycle and adds portfolio coordination and operating policy. The design owns these definitions; independent adoption says what each layer must prove before another system can use it on its own.
This map includes the architectural Workflow catalogue and its planned uses. The current local concert offers thirteen caller-prepared stage kinds through native contracts; it does not execute the catalogue's planned Release, Repair or operating services. Local acceptance, customer release and live outcome evidence have separate gates. Each status below is a word, and the build review owns acceptance evidence.
Levels of detail
Start at the top and stop at the level you need. The first three levels are drawn from one checked data file; the last two are each Module's own pages.
| Level | Shows | Where |
|---|---|---|
| 1. At a glance | The Factory, its Workflows and the Module groups, with status words and counts | At a glance |
| 2. The whole picture | What every Workflow and Module can do, and which Modules each Workflow shares or uses alone | The whole picture |
| 3. Uses and sub-parts | Which Workflow uses which Module, and each Module's significant sub-parts | Usage grid and the tables |
| 4. Each Module explained | One page per Module in plain words, with its portrait and limits | How the parts fit together and the module guides |
| 5. Contracts | Each Module's exact API, bounds and evidence | Module references |
At a glance
Open the at-a-glance diagram at full size.
The whole picture
Open the composition diagram at full size.
Read the diagram: Start at the bottom. Each Module box says what that part can do, in a few words, and whether it is shared by several Workflows or used by one. Each Workflow box lists the job it completes, the shared Modules it relies on, the Modules only it uses and what is still to build. The Factory box at the top lists what only the full composition adds.
Usage grid
Open the usage grid at full size.
Common and unique parts. A few Modules recur across jobs. In the documented designs, Evidence / Assurance keeps what Research, Implementation and Verification observed, and the Product gate and Repository carry a Slice into a sealed Candidate for both Implementation and Verification. More sharing is planned than documented: Service access, for example, is planned for four Workflows and documented in none, so it is drawn with open circles. Other Modules belong to one job only, such as Discovery sources in Research or the Repository collector in Verification. The Most shared Modules line below counts both kinds from the data. A shared Module keeps one owner and one contract however many Workflows use it.
Where the lists come from
The map is drawn from one data file, composition.json, and each Workflow links its owning document in the tables below. The two kinds of use have different authority:
- Documented use (filled circles, no marker) is a Module the owning document names: the Research, Implementation and Marketing packets, the Verification design and the Repair epic.
- Planned use (open circles, marked planned) is the map author's reading of where a Module is likely to fit, or a use the owner has asked for, such as Marketing checking competitors through Discovery sources. For catalogue-only Planning and prioritisation, Release and recovery, Outcome validation, Simplification and retirement and Service access operations, links remain planned pending their owning designs. Knowledge now has an installed native Module and bounded planning controls; its proposed Architecture use remains planned. The owner chose on 2 October 2026 to keep these links, and their ensemble plates, marked as planned. Treat them as questions, not design decisions.
Shared and unique are derived from those lists, never typed by hand. node scripts/render-composition.ts redraws the three diagrams and the tables below; with --check it fails when they differ from the data, and the docs tests fail when a new module guide is missing from the map.
One set of maps. The owner asked on 2 October 2026 for the maps to become one set at different levels of detail. This page holds levels 1 to 3. The hand-drawn module map in docs/guide/ predates several Modules and is no longer linked from any page; E41 retires it and generates the level 4 card list from the same data.
Two additions from the owner's interview. The Architecture and practice guidance Module appears as Proposed: it has no guide or code yet, and its design and owner decisions lead to E39 and E40. The original proposal to run Implementation, Verification and production Release in turn remains an unconfirmed production operating default. The current End-to-end delivery row describes commissioned local Delivery through Implementation, Verification, guarded integration and observational assessment. It makes no production Release claim.
The tables
The tables carry the same facts as the diagrams, as text.
The Factory layer
| Layer | Status | What it adds | Factory-level Modules | Composes |
|---|---|---|---|---|
| Factory | In progress | Runs thirteen prepared native stage kinds · Stops for missing input and retains original identities · Preserves native Authority and Budget · Recovers original uncertain integration before fresh work · Offers observational Marketing with current supported facts | Local fixture worker, Guarded verification / recovery, Portfolio, Dashboard, Required actions and blockers, Owner digest, Owner policy, Project guidance, Guidance acceptance, Branch health, Prevention register, Lifecycle schedule, Provider events, Provider subscriptions, Provider event requests, Provider Guidance tools, Factory concert workflow | Research, Planning and prioritisation, Implementation, Verification, Release and recovery, End-to-end delivery, Marketing, Outcome validation, Repair, Simplification and retirement, Service access operations, Knowledge capture and retrieval |
Most shared Modules: Evidence / Assurance (3 documented, 1 planned); Product gate and delivery records (2 documented, 3 planned); Repository sealing / export and integration (2 documented, 2 planned); Intelligence (1 documented, 3 planned); Architecture and practice guidance (0 documented, 6 planned); Service access (0 documented, 4 planned); Temporal Planning (0 documented, 3 planned).
Workflows at a glance
| Workflow | Status | What it does | Shared Modules | Only in this Workflow | Still to build |
|---|---|---|---|---|---|
| Research | In progress | Reads commissioned public Sources with checkable citations · Keeps findings attributed, with unknowns and expiry · Proposes work; selecting a Slice is a separate decision. | Discovery sources, Evidence / Assurance, Command journal, Intelligence, Lifecycle schedule (planned), Temporal Planning (planned) | Research semantics | Full root and exact-main CI qualification |
| Planning and prioritisation | Planned | Ranks needs by evidenced value and cost · Relates sourced dates, capacity and dependencies · Frames Slices with Outcome, scope and acceptance. | Project guidance (planned), Temporal Planning (planned), Proposal ownership (planned), Architecture and practice guidance (planned) | Portfolio (planned), Capacity planning (planned) | Opportunity gate, Owner decision bundle, Objective and Capability records |
| Implementation | In progress | Takes a ready Slice, snapshot, workspace and Budget · Proposes bounded edits; seals one immutable Candidate · Records execution Evidence; never judges its own work. | Attempt fence / workspace, Repository sealing / export and integration, Product gate and delivery records, Evidence / Assurance, Project guidance (planned), Intelligence (planned), Architecture and practice guidance (planned) | Execution, Producers, Implementation worker workflow | Full root and exact-main CI qualification, A qualified live model provider |
| Verification | In progress | Runs frozen checks on a sealed Candidate in a sandbox · Judges stored Evidence: Verified, Failed or Inconclusive · Keeps the verifier independent of the implementer. | Product gate and delivery records, Repository sealing / export and integration, Attempt fence / workspace, Evidence / Assurance | Repository collector, Confined executor, Repository Assurance, External verification workflow | Full root and exact-main CI qualification |
| Release and recovery | Planned | Integrates only on a current Verdict · Exposes changes progressively by risk · Restores service before diagnosing incidents. | Repository sealing / export and integration (planned), Product gate and delivery records (planned), Service access (planned) | Branch health (planned) | Action gateway, Release adapter, Independent recovery controller |
| End-to-end delivery | In progress | Binds and freezes a caller-authored Slice · Runs native Implementation and independent Verification · Integrates once and assesses retained evidence. Composes Implementation and Verification. | Architecture and practice guidance (planned) | Delivery composition (D4) | Full root and exact-main CI qualification, Customer release and live qualification |
| Marketing | In progress | Writes only from typed, current, supported facts · Checks competitors' public claims first · Runs as a resumable job with a pluggable drafter · Times and publishes only through authorised adapters. | Command journal, Intelligence (planned), Temporal Planning (planned), Lifecycle schedule (planned), Service access (planned), Discovery sources (planned) | Material Timing (planned) | A qualified drafting model, Publication adapter with Receipts, Release and benefit fact sources, Action gateway |
| Outcome validation | Planned | Measures against a predeclared rule and window · Concludes Supported, Rejected or Inconclusive · Never hides a Rejected result. | Product gate and delivery records (planned), Evidence / Assurance (planned), Operational Signals (planned) | None | Measurement contracts, Experiment evaluator |
| Repair | Planned | Reads redacted crash and performance Signals · Reproduces before repairing; verifies before and after · Closes the source only through an authorised Action. Composes Implementation and Verification. | Operational Signals, Proposal ownership (planned), Product gate and delivery records (planned), Service access (planned), Architecture and practice guidance (planned) | None | Source adapters and detectors, Case and episode state, Production evaluator, Action gateway |
| Simplification and retirement | Planned | Finds duplication and boundary friction weekly · Proposes refactors that keep every ability · Retires behaviour without stranding customers. | Intelligence (planned), Repository sealing / export and integration (planned), Architecture and practice guidance (planned) | None | Capability records, Retirement obligation checks |
| Service access operations | Planned | Knows which services each Product uses · Brokers credentials without revealing their values · Renews and revokes access within Authority. | Service access (planned) | None | Access runbooks, Credential vault, Credential broker |
| Knowledge capture and retrieval | In progress | Documents architecture and practice decisions · Records decisions with their reasons and sources · Retrieves relevant prior decisions for new work. | Architecture and practice guidance (planned) | Knowledge | Full root and exact-main CI qualification |
Modules and their capabilities
| Group | Module | Status | Capabilities | Used by |
|---|---|---|---|---|
| Records and runs | Command journal | Accepted locally | Records each Command once, with result and Events · Replays the recorded answer on retry · Refuses stale or conflicting commands | Research, Marketing |
| Records and runs | Execution | Accepted locally | Owns each Run and Attempt · Holds a fixed Budget and durable cancellation · Starts nothing on its own | Implementation |
| Records and runs | Evidence / Assurance | Accepted locally | Keeps content-addressed, attributable Evidence · Folds Evidence into a three-valued Verdict · Missing Evidence never passes | Research, Implementation, Verification, Outcome validation (planned) |
| Isolation and execution | Attempt fence / workspace | Accepted locally | One ownership gate per Attempt · A fresh private workspace · Stale owners cannot resume | Implementation, Verification |
| Isolation and execution | Local fixture worker | Accepted locally | Runs built-in fixtures as bounded processes · Records process Evidence · Leaves judgement to Assurance | Factory |
| Isolation and execution | Confined executor | Accepted locally | Runs one program against read-only snapshots · A macOS sandbox with no network or writes · Observes and reports; never judges | Verification |
| Assurance | Guarded verification / recovery | Accepted locally | Verifies a fixture under exclusive ownership · Settles orphaned Attempts within Budget · Separates a past Verdict from current validity | Factory |
| Assurance | Repository collector | Accepted locally | Runs a Candidate's frozen checks in the sandbox · Stores one Evidence record per run · Refuses mismatched pins before anything runs | Verification |
| Assurance | Repository Assurance | Accepted locally | Judges a sealed Candidate from stored Evidence · Authenticates its manifest and base · Never relabels fixture proof | Verification |
| Assurance | External verification workflow | In progress | Preflights an independently sealed caller Candidate · Finds original witnesses without uncertain recollection | Verification |
| Repository and delivery | Repository sealing / export and integration | Accepted locally | Seals bounded edits as an immutable Candidate · Exports the exact bytes · Moves a branch at most once; no blind retry | Implementation, Verification, Release and recovery (planned), Simplification and retirement (planned) |
| Repository and delivery | Product gate and delivery records | Accepted locally | Holds per-Product grants, revocation and stop · Freezes Slices with allowances · Admits integration only on a current Verdict | Implementation, Verification, Release and recovery (planned), Outcome validation (planned), Repair (planned) |
| Repository and delivery | Producers | Accepted locally | Asks a model once for proposed edits · Returns an untrusted Proposal for sealing · Never applies, integrates or judges | Implementation |
| Repository and delivery | Delivery composition (D4) | In progress | Binds a Product store and freezes authored work · Seals Candidates and re-derives repository Verdicts · Source composition with acceptance still pending | End-to-end delivery |
| Repository and delivery | Checkout Git (R7) | In progress | Reads one bounded committed blob by inspected commit · Preserves checkout files and configuration · No model, repository mutation or independent package entry | No Workflow yet |
| Repository and delivery | Implementation worker workflow | In progress | Dispatches a real worker under a native Product hold · Retains original Attempt, Budget and restart identity | Implementation |
| Repository and delivery | Factory concert workflow | In progress | Composes prepared native stages through public contracts · Recovers original integration and stable completed replay | Factory |
| Architecture and knowledge | Architecture and practice guidance | Proposed | Recommends architecture and practice per delivery mode · Explains what each delivery mode gains and costs · Drafts ADRs citing patterns, practice and idioms · Advises only; flags usage outgrowing the mode | Planning and prioritisation (planned), Implementation (planned), End-to-end delivery (planned), Repair (planned), Simplification and retirement (planned), Knowledge capture and retrieval (planned) |
| Architecture and knowledge | Knowledge | In progress | Retains reviewed lessons and current permissions · Offers bounded advice and authenticated planning drafts | Knowledge capture and retrieval |
| Planning and guidance | Project guidance | Accepted locally | Up to eight core values per Product · Immutable revisions and pins · Names exactly which guidance applied | Planning and prioritisation (planned), Implementation (planned), Factory |
| Planning and guidance | Temporal Planning | Accepted locally | Keeps attributed date claims and precision · Checks dependencies and notice windows · Retains disagreements and unknowns | Research (planned), Planning and prioritisation (planned), Marketing (planned) |
| Planning and guidance | Capacity planning | Accepted locally | Conditional capacity scenarios · Shows deficits, reserves and unknowns · Reserves no quota and admits nothing | Planning and prioritisation (planned) |
| Planning and guidance | Material Timing | Accepted locally | Checks material slots against calendar rules · Readiness, embargo, notice and DST checks · Publishes nothing; reserves no channel | Marketing (planned) |
| Planning and guidance | Proposal ownership | Accepted locally | Keeps immutable typed proposals · First offer fixes ownership permanently · Starts no delivery | Planning and prioritisation (planned), Repair (planned) |
| Planning and guidance | Guidance acceptance | Accepted locally | Applies one offered Guidance command · Reconciles it against recorded history · Replay returns the original revision | Factory |
| Planning and guidance | Milestone research handoff | In progress | Prepares an attributed first-plan draft · Prepares the original unassessed M01 request · No Research launch or new work authority | No Workflow yet |
| Planning and guidance | Milestone work brief | In progress | Copies one selected implementation generation · Keeps captured dates, counts and unknowns · Produces an unadmitted work brief | No Workflow yet |
| Planning and guidance | Calendar | In progress | Shared Gregorian civil-date and ISO-week arithmetic · Canonical host-zone conversion with fixed fold and gap rules · No storage, scheduling, clock read or authority | No Workflow yet |
| Operations and signals | Branch health | Accepted locally | Reads branch checks and workflow history · Red, green or unknown per Product · Keeps failure episodes; mirrors blockers | Release and recovery (planned), Factory |
| Operations and signals | Operational Signals | Accepted locally | Accepts redacted, authenticated observations · Commits Signals and coverage together · A gap is never shown as healthy | Outcome validation (planned), Repair |
| Operations and signals | Prevention register | In progress | Says whether each guardrail is in place · Records results and owner exemptions · Never a default pass | Factory |
| Operations and signals | Lifecycle schedule | In progress | Keeps the timetable of named checks · Admits, defers and settles each occurrence once · Runs nothing by itself yet | Research (planned), Marketing (planned), Factory |
| Portfolio and owner view | Portfolio | Accepted locally | Registers each Product with one checkout · Shows sourced facts and usage · Unknown is never shown as zero | Planning and prioritisation (planned), Factory |
| Portfolio and owner view | Dashboard | Accepted locally | A local browser view of progress and usage · Actions, values and the digest in one place · Guarded Portfolio and configured milestone commands | Factory |
| Portfolio and owner view | Required actions and blockers | Accepted locally | One list of reported actions and blockers · Names an owner before saying it needs you · Guides blocker resolution | Factory |
| Portfolio and owner view | Owner digest | Accepted locally | Cited exception batches · A short weekly digest · Green only when the evidence agrees | Factory |
| Portfolio and owner view | Owner policy | Accepted locally | Records asks, answers and minutes · Keeps rules you confirm, on test data (draft) · Weekly counts with honest unknowns | Factory |
| Portfolio and owner view | Work items | In progress | Keeps per-Product work ownership · Refuses undeclared duplicate work · Reports read Git lanes without deleting them | No Workflow yet |
| Portfolio and owner view | Milestone objectives | In progress | Retains objectives and their immutable revisions · Selects one next priority or none · No automatic Research, tickets or resource ETA | No Workflow yet |
| Provider events | Provider events | Accepted locally | Projects one scoped notification · Checks caller permission and pins · Quiet when nothing changed | Factory |
| Provider events | Provider subscriptions | Accepted locally | Bounded subscription lifecycle · Rechecks permission before contact · Signed verification only; no delivery | Factory |
| Provider events | Provider event requests | Accepted locally | Routes list, subscribe and unsubscribe · A lost reply stays unknown · Starts no server and sends no events | Factory |
| Provider events | Provider Guidance tools | Accepted locally | Inspects one offered Guidance proposal · Applies it through its existing receiver · No new authority or automatic retry | Factory |
| Provider events | Provider diagnostics | In progress | Projects bounded historical provider observations · Keeps the original result unchanged · No inferred causes, retry permission or provider calls | No Workflow yet |
| Provider events | Provider event delivery | In progress | Delivers one retained notification within fixed bounds · Reconciles original attempts and unknown contact · A receipt does not prove processing or domain work | No Workflow yet |
| Models, research and access | Intelligence | Accepted locally | Says which modules may use a model and why · Owner-approved model lists per task · Refuses rather than substitutes | Research, Implementation (planned), Marketing (planned), Simplification and retirement (planned) |
| Models, research and access | Discovery sources | Accepted locally | Reads commissioned public Sources · Keeps short, re-verifiable citations · Refuses oversize input; never truncates | Research, Marketing (planned) |
| Models, research and access | Service access | Accepted locally | Maps each Product's outside services · Knows where credentials live, by name only · Lists vault items without values (draft) · Never reads or records a secret value | Release and recovery (planned), Marketing (planned), Repair (planned), Service access operations (planned) |
| Models, research and access | Research jobs | In progress | Collects once under an existing source commission · Keeps untriaged coverage and short citations · Never renews an original allowance | No Workflow yet |
| Models, research and access | Research semantics | In progress | Synthesises commissioned native Research evidence · Retains shared allowance and uncertain collection exposure | Research |
Significant sub-parts
A sub-part is listed only when it has its own responsibility and entry point; a Module with one responsibility has none. A part without its own status inherits its Module's status; an explicit status refers to that part's own acceptance scope.
| Module | Status | Sub-part | What it does |
|---|---|---|---|
| Evidence / Assurance | Accepted locally | Evidence store | Stores each process observation once, content-addressed |
| Evidence / Assurance | Accepted locally | Assurance judge | Judges gathered Evidence into a local-fixture Verdict |
| Attempt fence / workspace | Accepted locally | Attempt fence | Gates Attempt ownership with a kernel-released lock |
| Attempt fence / workspace | Accepted locally | Attempt workspace | Provisions and disposes a private directory per Attempt |
| Local fixture worker | Accepted locally | Fixture worker | Runs one fixture as a bounded child and stores Evidence |
| Local fixture worker | Accepted locally | Fixture programs | Provides the pass, fail, hang and noisy child programs |
| Local fixture worker | Accepted locally | Fence gate preload | Makes the child hold the Attempt fence before code runs |
| Local fixture worker | Accepted locally | Execution manifest | Hashes the guarded fixture sources into one digest |
| Guarded verification / recovery | Accepted locally | Verification policy | Verifies, recovers, cancels and inspects guarded Runs |
| Guarded verification / recovery | Accepted locally | Attempt ledger | Records Attempt preparations, reports and fence proofs |
| Guarded verification / recovery | Accepted locally | Fixture command line | Runs verify, inspect, cancel and recover from the shell |
| Repository collector | Accepted locally | Check collector | Runs each process check once and stores its Evidence |
| Repository collector | Accepted locally | Snapshot store | Keeps frozen Slice fixture inputs, written once |
| Repository Assurance | Accepted locally | Frozen Slice records | Parses and digests acceptance, recipe and environment |
| Repository Assurance | Accepted locally | Observation format | Encodes and decodes repository observation records |
| Repository Assurance | Accepted locally | Repository judge | Judges Candidate Evidence into a repository Verdict |
| Repository sealing / export and integration | Accepted locally | Candidate sealing | Seals proposals as Candidates and exports their bytes |
| Repository sealing / export and integration | Accepted locally | Guarded integration | Moves the target ref once per prepared Action |
| Repository sealing / export and integration | Accepted locally | Shared wire grammar | Parses identities and intents and encodes Git objects |
| Product gate and delivery records | Accepted locally | Product gate | Admits production, checks and integration per Product |
| Product gate and delivery records | Accepted locally | Pre-effect check | Answers whether an admitted dispatch may act now |
| Product gate and delivery records | Accepted locally | Delivery records | Keeps create-once delivery inputs and results |
| Product gate and delivery records | Accepted locally | Assessment derivation | Derives a Slice Assessment from a reproduced Verdict |
| Producers | Accepted locally | Producer contract | Defines the provider-neutral request, result and gate |
| Producers | Accepted locally | Claude producer | Proposes edits through the pinned Claude Code CLI |
| Producers | Accepted locally | OpenAI producer | Proposes edits through the OpenAI Responses API |
| Producers | Accepted locally | Qualification script | Runs a bounded live qualification and writes Receipts |
| Delivery composition (D4) | In progress | Plan source records | Retains bounded canonical fixture roots after freeze |
| Delivery composition (D4) | In progress | Authored composition | Joins authored work to existing gate checks |
| Architecture and practice guidance | Proposed | Delivery mode advisor | Explains each mode and proposes a mode review |
| Architecture and practice guidance | Proposed | Code analysis | Reads a pinned snapshot read-only under a cap |
| Architecture and practice guidance | Proposed | Practice catalogue | Holds reviewed styles, patterns, practices and idioms |
| Architecture and practice guidance | Proposed | ADR drafter and validator | Drafts a proposed ADR and rejects incomplete ones |
| Project guidance | Accepted locally | Guidance core | Records Product values as pinned, digest-bound revisions |
| Project guidance | Accepted locally | Values editor | Lets the owner view and edit values in the browser |
| Capacity planning | Accepted locally | Capacity forecast | Forecasts headroom and a completion range |
| Capacity planning | Accepted locally | Outcome comparison | Compares a recorded forecast with the actual outcome |
| Proposal ownership | Accepted locally | Proposal ownership | Fixes one owner per proposal generation at first offer |
| Proposal ownership | Accepted locally | Notification ownership | Owns one notification occurrence on the same record |
| Branch health | Accepted locally | Health and episode core | Derives Product health and failure episodes per poll |
| Branch health | Accepted locally | GitHub reader | Reads branch checks and workflow runs, read-only |
| Branch health | Accepted locally | Portfolio mirror | Mirrors each episode as a Portfolio blocker fact |
| Prevention register | In progress | Guardrail templates | Holds three frozen, digest-pinned guardrail rules |
| Prevention register | In progress | Presence evaluation | Turns supplied reads into one presence fact per rule |
| Prevention register | In progress | Write-once records | Records results and owner exemptions once |
| Prevention register | In progress | Visibility read | Reads repository visibility with one GitHub request |
| Lifecycle schedule | In progress | Occurrence timetable | Names, admits, defers and settles each occurrence |
| Lifecycle schedule | In progress | Provider call ledger | Admits each provider call within the weekly ceiling |
| Lifecycle schedule | In progress | LaunchAgent renderer | Returns LaunchAgent text without writing or loading it |
| Portfolio | Accepted locally | Product registry | Registers Products, each bound to one Git checkout |
| Portfolio | Accepted locally | Fact and usage streams | Records sourced facts and usage Receipts per Product |
| Portfolio | Accepted locally | Sourced views | Builds Product, Portfolio, condition and blocker views |
| Portfolio | Accepted locally | Read-only collectors | Inspects checkouts and maps model results to Receipts |
| Dashboard | Accepted locally | JSON contract | Defines the versioned records the browser reads |
| Dashboard | Accepted locally | View projection | Projects Portfolio, attention and guidance reads |
| Dashboard | Accepted locally | HTTP server | Serves loopback routes and configured guarded commands |
| Dashboard | Accepted locally | Browser app | Formats and lays out pages without computing counts |
| Required actions and blockers | Accepted locally | Attention list | Projects sourced conditions into actions and notices |
| Required actions and blockers | Accepted locally | Blocker detail | Shows a blocker report, standing and retained history |
| Required actions and blockers | Accepted locally | Actions and blocker pages | Lists items and blocker detail in the browser |
| Owner digest | Accepted locally | Exception batches | Forms up to three daily batches of new episodes |
| Owner digest | Accepted locally | Weekly digest | Renders a cited Monday digest of at most 150 words |
| Owner digest | Accepted locally | Owner notes | Records delight and frustration notes per week |
| Owner digest | Accepted locally | Factory reader | Reads Branch health, Portfolio and Attention |
| Owner policy | Accepted locally | Ask ledger | Records and counts owner asks per ISO week |
| Owner policy | Draft | Owner rules | Keeps owner-confirmed rules and answers whether to ask |
| Provider Guidance tools | Accepted locally | Inspect offer tool | Reads one offered Guidance generation, read-only |
| Provider Guidance tools | Accepted locally | Apply offer tool | Requests only the original commissioned Guidance command |
| Intelligence | Accepted locally | Intelligence registry | Declares where each Module may use a model, and why |
| Intelligence | Accepted locally | Model selector | Picks the first eligible approved model for a task |
| Intelligence | Accepted locally | Declaration tables | Renders the README and reference Intelligence tables |
| Discovery sources | Accepted locally | Source collector | Fetches commissioned public Sources into Captures |
| Discovery sources | Accepted locally | Citations and drift | Makes, verifies and re-checks quoted Citations |
| Discovery sources | Accepted locally | Capture cache | Holds Capture text on disk, re-hashed on every read |
| Discovery sources | Accepted locally | Text operations | Extracts items, normalises text and checks quotes |
| Service access | Accepted locally | Service catalogue | Defines frozen Service kinds, slots and signatures |
| Service access | Accepted locally | Service discovery | Scans trees and listings for names into a Service map |
| Service access | Accepted locally | Access records | Records bindings and pins and answers readiness |
| Service access | Draft | Vault lister | Lists one 1Password vault by names, never values |
Workflow ensembles
Each plate hangs the portraits of a Workflow's Modules from one shared line: the Workflow is the line they work along. Portraits are whole and uncropped; a character says nothing about acceptance or completion. Plates exist only for Modules that already have a family portrait.
Research ensemble

Discovery sources, Intelligence, Evidence / Assurance, Lifecycle schedule (planned), Command journal. Full-size PNG.
Planning and prioritisation ensemble

Project guidance (planned), Portfolio (planned). Full-size PNG.
Implementation ensemble

Product gate and delivery records, Producers, Attempt fence / workspace, Execution, Repository sealing / export and integration. Full-size PNG.
Verification ensemble

Repository collector, Confined executor, Repository Assurance, Evidence / Assurance, Attempt fence / workspace. Full-size PNG.
Release and recovery ensemble

Repository sealing / export and integration (planned), Product gate and delivery records (planned), Service access (planned). Full-size PNG.
Marketing ensemble

Service access (planned), Lifecycle schedule (planned), Intelligence (planned), Command journal. Full-size PNG.
Outcome validation ensemble

Product gate and delivery records (planned), Evidence / Assurance (planned). Full-size PNG.
Repair ensemble

Service access (planned), Producers, Repository sealing / export and integration, Repository Assurance, Product gate and delivery records. Full-size PNG.
Simplification and retirement ensemble

Intelligence (planned), Repository sealing / export and integration (planned). Full-size PNG.
Factory ensemble

Portfolio, Dashboard, Required actions and blockers, Project guidance, Lifecycle schedule. Full-size PNG.
No plate yet for End-to-end delivery, Service access operations, Knowledge capture and retrieval: fewer than two of their Modules have a portrait, or their Modules are not yet known.
What this map does not establish
- A Workflow listed here is not an independently adoptable Workflow until its adoption gate has evidence.
- A Module's place in a Workflow is the documented design, not a proved composition. E35 owns that proof.
- The ensemble plates are mechanical composites of reviewed portraits. The commissioned ensemble scenes in the ensemble commission have not been generated.
