Factory docs, home
Page navigation

Pre-release documentation. Proposed designs are labelled in the page; acceptance evidence is maintained in the build review. Local paths appear as placeholders. Current state: Build review.

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.

LevelShowsWhere
1. At a glanceThe Factory, its Workflows and the Module groups, with status words and countsAt a glance
2. The whole pictureWhat every Workflow and Module can do, and which Modules each Workflow shares or uses aloneThe whole picture
3. Uses and sub-partsWhich Workflow uses which Module, and each Module's significant sub-partsUsage grid and the tables
4. Each Module explainedOne page per Module in plain words, with its portrait and limitsHow the parts fit together and the module guides
5. ContractsEach Module's exact API, bounds and evidenceModule references

At a glance

The Factory at the top composes every Workflow, each shown with its status word and how many Modules it uses; below them, every Module group with its Module count and status words.

Open the at-a-glance diagram at full size.

The whole picture

Factory at the top composes every Workflow; each Workflow box lists its capabilities and the Modules it shares with other Workflows or uses alone, with planned use marked as planned; below them, the Module groups list every Module with its status and capabilities.

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

A grid with one row per Module, grouped as in the diagram above, and one column per Workflow plus Factory. Filled circles mark documented use, open circles planned use, and a count shows how many Workflows share each Module.

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

LayerStatusWhat it addsFactory-level ModulesComposes
FactoryIn progressRuns 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 factsLocal 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 workflowResearch, 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

WorkflowStatusWhat it doesShared ModulesOnly in this WorkflowStill to build
ResearchIn progressReads 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 semanticsFull root and exact-main CI qualification
Planning and prioritisationPlannedRanks 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
ImplementationIn progressTakes 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 workflowFull root and exact-main CI qualification, A qualified live model provider
VerificationIn progressRuns 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 / AssuranceRepository collector, Confined executor, Repository Assurance, External verification workflowFull root and exact-main CI qualification
Release and recoveryPlannedIntegrates 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 deliveryIn progressBinds 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
MarketingIn progressWrites 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 validationPlannedMeasures 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)NoneMeasurement contracts, Experiment evaluator
RepairPlannedReads 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)NoneSource adapters and detectors, Case and episode state, Production evaluator, Action gateway
Simplification and retirementPlannedFinds 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)NoneCapability records, Retirement obligation checks
Service access operationsPlannedKnows which services each Product uses · Brokers credentials without revealing their values · Renews and revokes access within Authority.Service access (planned)NoneAccess runbooks, Credential vault, Credential broker
Knowledge capture and retrievalIn progressDocuments architecture and practice decisions · Records decisions with their reasons and sources · Retrieves relevant prior decisions for new work.Architecture and practice guidance (planned)KnowledgeFull root and exact-main CI qualification

Modules and their capabilities

GroupModuleStatusCapabilitiesUsed by
Records and runsCommand journalAccepted locallyRecords each Command once, with result and Events · Replays the recorded answer on retry · Refuses stale or conflicting commandsResearch, Marketing
Records and runsExecutionAccepted locallyOwns each Run and Attempt · Holds a fixed Budget and durable cancellation · Starts nothing on its ownImplementation
Records and runsEvidence / AssuranceAccepted locallyKeeps content-addressed, attributable Evidence · Folds Evidence into a three-valued Verdict · Missing Evidence never passesResearch, Implementation, Verification, Outcome validation (planned)
Isolation and executionAttempt fence / workspaceAccepted locallyOne ownership gate per Attempt · A fresh private workspace · Stale owners cannot resumeImplementation, Verification
Isolation and executionLocal fixture workerAccepted locallyRuns built-in fixtures as bounded processes · Records process Evidence · Leaves judgement to AssuranceFactory
Isolation and executionConfined executorAccepted locallyRuns one program against read-only snapshots · A macOS sandbox with no network or writes · Observes and reports; never judgesVerification
AssuranceGuarded verification / recoveryAccepted locallyVerifies a fixture under exclusive ownership · Settles orphaned Attempts within Budget · Separates a past Verdict from current validityFactory
AssuranceRepository collectorAccepted locallyRuns a Candidate's frozen checks in the sandbox · Stores one Evidence record per run · Refuses mismatched pins before anything runsVerification
AssuranceRepository AssuranceAccepted locallyJudges a sealed Candidate from stored Evidence · Authenticates its manifest and base · Never relabels fixture proofVerification
AssuranceExternal verification workflowIn progressPreflights an independently sealed caller Candidate · Finds original witnesses without uncertain recollectionVerification
Repository and deliveryRepository sealing / export and integrationAccepted locallySeals bounded edits as an immutable Candidate · Exports the exact bytes · Moves a branch at most once; no blind retryImplementation, Verification, Release and recovery (planned), Simplification and retirement (planned)
Repository and deliveryProduct gate and delivery recordsAccepted locallyHolds per-Product grants, revocation and stop · Freezes Slices with allowances · Admits integration only on a current VerdictImplementation, Verification, Release and recovery (planned), Outcome validation (planned), Repair (planned)
Repository and deliveryProducersAccepted locallyAsks a model once for proposed edits · Returns an untrusted Proposal for sealing · Never applies, integrates or judgesImplementation
Repository and deliveryDelivery composition (D4)In progressBinds a Product store and freezes authored work · Seals Candidates and re-derives repository Verdicts · Source composition with acceptance still pendingEnd-to-end delivery
Repository and deliveryCheckout Git (R7)In progressReads one bounded committed blob by inspected commit · Preserves checkout files and configuration · No model, repository mutation or independent package entryNo Workflow yet
Repository and deliveryImplementation worker workflowIn progressDispatches a real worker under a native Product hold · Retains original Attempt, Budget and restart identityImplementation
Repository and deliveryFactory concert workflowIn progressComposes prepared native stages through public contracts · Recovers original integration and stable completed replayFactory
Architecture and knowledgeArchitecture and practice guidanceProposedRecommends 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 modePlanning and prioritisation (planned), Implementation (planned), End-to-end delivery (planned), Repair (planned), Simplification and retirement (planned), Knowledge capture and retrieval (planned)
Architecture and knowledgeKnowledgeIn progressRetains reviewed lessons and current permissions · Offers bounded advice and authenticated planning draftsKnowledge capture and retrieval
Planning and guidanceProject guidanceAccepted locallyUp to eight core values per Product · Immutable revisions and pins · Names exactly which guidance appliedPlanning and prioritisation (planned), Implementation (planned), Factory
Planning and guidanceTemporal PlanningAccepted locallyKeeps attributed date claims and precision · Checks dependencies and notice windows · Retains disagreements and unknownsResearch (planned), Planning and prioritisation (planned), Marketing (planned)
Planning and guidanceCapacity planningAccepted locallyConditional capacity scenarios · Shows deficits, reserves and unknowns · Reserves no quota and admits nothingPlanning and prioritisation (planned)
Planning and guidanceMaterial TimingAccepted locallyChecks material slots against calendar rules · Readiness, embargo, notice and DST checks · Publishes nothing; reserves no channelMarketing (planned)
Planning and guidanceProposal ownershipAccepted locallyKeeps immutable typed proposals · First offer fixes ownership permanently · Starts no deliveryPlanning and prioritisation (planned), Repair (planned)
Planning and guidanceGuidance acceptanceAccepted locallyApplies one offered Guidance command · Reconciles it against recorded history · Replay returns the original revisionFactory
Planning and guidanceMilestone research handoffIn progressPrepares an attributed first-plan draft · Prepares the original unassessed M01 request · No Research launch or new work authorityNo Workflow yet
Planning and guidanceMilestone work briefIn progressCopies one selected implementation generation · Keeps captured dates, counts and unknowns · Produces an unadmitted work briefNo Workflow yet
Planning and guidanceCalendarIn progressShared Gregorian civil-date and ISO-week arithmetic · Canonical host-zone conversion with fixed fold and gap rules · No storage, scheduling, clock read or authorityNo Workflow yet
Operations and signalsBranch healthAccepted locallyReads branch checks and workflow history · Red, green or unknown per Product · Keeps failure episodes; mirrors blockersRelease and recovery (planned), Factory
Operations and signalsOperational SignalsAccepted locallyAccepts redacted, authenticated observations · Commits Signals and coverage together · A gap is never shown as healthyOutcome validation (planned), Repair
Operations and signalsPrevention registerIn progressSays whether each guardrail is in place · Records results and owner exemptions · Never a default passFactory
Operations and signalsLifecycle scheduleIn progressKeeps the timetable of named checks · Admits, defers and settles each occurrence once · Runs nothing by itself yetResearch (planned), Marketing (planned), Factory
Portfolio and owner viewPortfolioAccepted locallyRegisters each Product with one checkout · Shows sourced facts and usage · Unknown is never shown as zeroPlanning and prioritisation (planned), Factory
Portfolio and owner viewDashboardAccepted locallyA local browser view of progress and usage · Actions, values and the digest in one place · Guarded Portfolio and configured milestone commandsFactory
Portfolio and owner viewRequired actions and blockersAccepted locallyOne list of reported actions and blockers · Names an owner before saying it needs you · Guides blocker resolutionFactory
Portfolio and owner viewOwner digestAccepted locallyCited exception batches · A short weekly digest · Green only when the evidence agreesFactory
Portfolio and owner viewOwner policyAccepted locallyRecords asks, answers and minutes · Keeps rules you confirm, on test data (draft) · Weekly counts with honest unknownsFactory
Portfolio and owner viewWork itemsIn progressKeeps per-Product work ownership · Refuses undeclared duplicate work · Reports read Git lanes without deleting themNo Workflow yet
Portfolio and owner viewMilestone objectivesIn progressRetains objectives and their immutable revisions · Selects one next priority or none · No automatic Research, tickets or resource ETANo Workflow yet
Provider eventsProvider eventsAccepted locallyProjects one scoped notification · Checks caller permission and pins · Quiet when nothing changedFactory
Provider eventsProvider subscriptionsAccepted locallyBounded subscription lifecycle · Rechecks permission before contact · Signed verification only; no deliveryFactory
Provider eventsProvider event requestsAccepted locallyRoutes list, subscribe and unsubscribe · A lost reply stays unknown · Starts no server and sends no eventsFactory
Provider eventsProvider Guidance toolsAccepted locallyInspects one offered Guidance proposal · Applies it through its existing receiver · No new authority or automatic retryFactory
Provider eventsProvider diagnosticsIn progressProjects bounded historical provider observations · Keeps the original result unchanged · No inferred causes, retry permission or provider callsNo Workflow yet
Provider eventsProvider event deliveryIn progressDelivers one retained notification within fixed bounds · Reconciles original attempts and unknown contact · A receipt does not prove processing or domain workNo Workflow yet
Models, research and accessIntelligenceAccepted locallySays which modules may use a model and why · Owner-approved model lists per task · Refuses rather than substitutesResearch, Implementation (planned), Marketing (planned), Simplification and retirement (planned)
Models, research and accessDiscovery sourcesAccepted locallyReads commissioned public Sources · Keeps short, re-verifiable citations · Refuses oversize input; never truncatesResearch, Marketing (planned)
Models, research and accessService accessAccepted locallyMaps each Product's outside services · Knows where credentials live, by name only · Lists vault items without values (draft) · Never reads or records a secret valueRelease and recovery (planned), Marketing (planned), Repair (planned), Service access operations (planned)
Models, research and accessResearch jobsIn progressCollects once under an existing source commission · Keeps untriaged coverage and short citations · Never renews an original allowanceNo Workflow yet
Models, research and accessResearch semanticsIn progressSynthesises commissioned native Research evidence · Retains shared allowance and uncertain collection exposureResearch

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.

ModuleStatusSub-partWhat it does
Evidence / AssuranceAccepted locallyEvidence storeStores each process observation once, content-addressed
Evidence / AssuranceAccepted locallyAssurance judgeJudges gathered Evidence into a local-fixture Verdict
Attempt fence / workspaceAccepted locallyAttempt fenceGates Attempt ownership with a kernel-released lock
Attempt fence / workspaceAccepted locallyAttempt workspaceProvisions and disposes a private directory per Attempt
Local fixture workerAccepted locallyFixture workerRuns one fixture as a bounded child and stores Evidence
Local fixture workerAccepted locallyFixture programsProvides the pass, fail, hang and noisy child programs
Local fixture workerAccepted locallyFence gate preloadMakes the child hold the Attempt fence before code runs
Local fixture workerAccepted locallyExecution manifestHashes the guarded fixture sources into one digest
Guarded verification / recoveryAccepted locallyVerification policyVerifies, recovers, cancels and inspects guarded Runs
Guarded verification / recoveryAccepted locallyAttempt ledgerRecords Attempt preparations, reports and fence proofs
Guarded verification / recoveryAccepted locallyFixture command lineRuns verify, inspect, cancel and recover from the shell
Repository collectorAccepted locallyCheck collectorRuns each process check once and stores its Evidence
Repository collectorAccepted locallySnapshot storeKeeps frozen Slice fixture inputs, written once
Repository AssuranceAccepted locallyFrozen Slice recordsParses and digests acceptance, recipe and environment
Repository AssuranceAccepted locallyObservation formatEncodes and decodes repository observation records
Repository AssuranceAccepted locallyRepository judgeJudges Candidate Evidence into a repository Verdict
Repository sealing / export and integrationAccepted locallyCandidate sealingSeals proposals as Candidates and exports their bytes
Repository sealing / export and integrationAccepted locallyGuarded integrationMoves the target ref once per prepared Action
Repository sealing / export and integrationAccepted locallyShared wire grammarParses identities and intents and encodes Git objects
Product gate and delivery recordsAccepted locallyProduct gateAdmits production, checks and integration per Product
Product gate and delivery recordsAccepted locallyPre-effect checkAnswers whether an admitted dispatch may act now
Product gate and delivery recordsAccepted locallyDelivery recordsKeeps create-once delivery inputs and results
Product gate and delivery recordsAccepted locallyAssessment derivationDerives a Slice Assessment from a reproduced Verdict
ProducersAccepted locallyProducer contractDefines the provider-neutral request, result and gate
ProducersAccepted locallyClaude producerProposes edits through the pinned Claude Code CLI
ProducersAccepted locallyOpenAI producerProposes edits through the OpenAI Responses API
ProducersAccepted locallyQualification scriptRuns a bounded live qualification and writes Receipts
Delivery composition (D4)In progressPlan source recordsRetains bounded canonical fixture roots after freeze
Delivery composition (D4)In progressAuthored compositionJoins authored work to existing gate checks
Architecture and practice guidanceProposedDelivery mode advisorExplains each mode and proposes a mode review
Architecture and practice guidanceProposedCode analysisReads a pinned snapshot read-only under a cap
Architecture and practice guidanceProposedPractice catalogueHolds reviewed styles, patterns, practices and idioms
Architecture and practice guidanceProposedADR drafter and validatorDrafts a proposed ADR and rejects incomplete ones
Project guidanceAccepted locallyGuidance coreRecords Product values as pinned, digest-bound revisions
Project guidanceAccepted locallyValues editorLets the owner view and edit values in the browser
Capacity planningAccepted locallyCapacity forecastForecasts headroom and a completion range
Capacity planningAccepted locallyOutcome comparisonCompares a recorded forecast with the actual outcome
Proposal ownershipAccepted locallyProposal ownershipFixes one owner per proposal generation at first offer
Proposal ownershipAccepted locallyNotification ownershipOwns one notification occurrence on the same record
Branch healthAccepted locallyHealth and episode coreDerives Product health and failure episodes per poll
Branch healthAccepted locallyGitHub readerReads branch checks and workflow runs, read-only
Branch healthAccepted locallyPortfolio mirrorMirrors each episode as a Portfolio blocker fact
Prevention registerIn progressGuardrail templatesHolds three frozen, digest-pinned guardrail rules
Prevention registerIn progressPresence evaluationTurns supplied reads into one presence fact per rule
Prevention registerIn progressWrite-once recordsRecords results and owner exemptions once
Prevention registerIn progressVisibility readReads repository visibility with one GitHub request
Lifecycle scheduleIn progressOccurrence timetableNames, admits, defers and settles each occurrence
Lifecycle scheduleIn progressProvider call ledgerAdmits each provider call within the weekly ceiling
Lifecycle scheduleIn progressLaunchAgent rendererReturns LaunchAgent text without writing or loading it
PortfolioAccepted locallyProduct registryRegisters Products, each bound to one Git checkout
PortfolioAccepted locallyFact and usage streamsRecords sourced facts and usage Receipts per Product
PortfolioAccepted locallySourced viewsBuilds Product, Portfolio, condition and blocker views
PortfolioAccepted locallyRead-only collectorsInspects checkouts and maps model results to Receipts
DashboardAccepted locallyJSON contractDefines the versioned records the browser reads
DashboardAccepted locallyView projectionProjects Portfolio, attention and guidance reads
DashboardAccepted locallyHTTP serverServes loopback routes and configured guarded commands
DashboardAccepted locallyBrowser appFormats and lays out pages without computing counts
Required actions and blockersAccepted locallyAttention listProjects sourced conditions into actions and notices
Required actions and blockersAccepted locallyBlocker detailShows a blocker report, standing and retained history
Required actions and blockersAccepted locallyActions and blocker pagesLists items and blocker detail in the browser
Owner digestAccepted locallyException batchesForms up to three daily batches of new episodes
Owner digestAccepted locallyWeekly digestRenders a cited Monday digest of at most 150 words
Owner digestAccepted locallyOwner notesRecords delight and frustration notes per week
Owner digestAccepted locallyFactory readerReads Branch health, Portfolio and Attention
Owner policyAccepted locallyAsk ledgerRecords and counts owner asks per ISO week
Owner policyDraftOwner rulesKeeps owner-confirmed rules and answers whether to ask
Provider Guidance toolsAccepted locallyInspect offer toolReads one offered Guidance generation, read-only
Provider Guidance toolsAccepted locallyApply offer toolRequests only the original commissioned Guidance command
IntelligenceAccepted locallyIntelligence registryDeclares where each Module may use a model, and why
IntelligenceAccepted locallyModel selectorPicks the first eligible approved model for a task
IntelligenceAccepted locallyDeclaration tablesRenders the README and reference Intelligence tables
Discovery sourcesAccepted locallySource collectorFetches commissioned public Sources into Captures
Discovery sourcesAccepted locallyCitations and driftMakes, verifies and re-checks quoted Citations
Discovery sourcesAccepted locallyCapture cacheHolds Capture text on disk, re-hashed on every read
Discovery sourcesAccepted locallyText operationsExtracts items, normalises text and checks quotes
Service accessAccepted locallyService catalogueDefines frozen Service kinds, slots and signatures
Service accessAccepted locallyService discoveryScans trees and listings for names into a Service map
Service accessAccepted locallyAccess recordsRecords bindings and pins and answers readiness
Service accessDraftVault listerLists 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

Research Workflow: Discovery sources, Intelligence, Evidence / Assurance, Lifecycle schedule, Command journal, hanging together from one line.

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

Planning and prioritisation ensemble

Planning and prioritisation Workflow: Project guidance, Portfolio, hanging together from one line.

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

Implementation ensemble

Implementation Workflow: Product gate and delivery records, Producers, Attempt fence / workspace, Execution, Repository sealing / export and integration, hanging together from one line.

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

Verification ensemble

Verification Workflow: Repository collector, Confined executor, Repository Assurance, Evidence / Assurance, Attempt fence / workspace, hanging together from one line.

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

Release and recovery ensemble

Release and recovery Workflow: Repository sealing / export and integration, Product gate and delivery records, Service access, hanging together from one line.

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

Marketing ensemble

Marketing Workflow: Service access, Lifecycle schedule, Intelligence, Command journal, hanging together from one line.

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

Outcome validation ensemble

Outcome validation Workflow: Product gate and delivery records, Evidence / Assurance, hanging together from one line.

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

Repair ensemble

Repair Workflow: Service access, Producers, Repository sealing / export and integration, Repository Assurance, Product gate and delivery records, hanging together from one line.

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

Simplification and retirement ensemble

Simplification and retirement Workflow: Intelligence, Repository sealing / export and integration, hanging together from one line.

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

Factory ensemble

Factory: Portfolio, Dashboard, Required actions and blockers, Project guidance, Lifecycle schedule, hanging together from one line.

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.

Source: docs/explanation/composition.md