domain masterplan and workflow

the masterplan: system architecture (g-002)

the system is composed of four core domains, each with a distinct architectural metaphor, function, and governing role. their relationship is mapped in the g-002 masterplan, the site plan of the organization.

Name	Role	Function	Core Activities	Workflow	Sheets Examples	SHEETS INDEX
O-100 SHEETS	operational studio, mktg & workshop: To Create & Deliver Value → Communication, Impact, Revenue, CEO/COO role: `Generation = What you do for clients + How you sell it`;	any entry with `domain: o-series` is a operational interface & dashboard.	client delivery, meetings, communication, project-based work, product development, marketing/sales campaign	this is where most `active` work happens. these entities are the primary drivers of the business.	O-300: Domain Overview O-301: Dashboard Interface	O-series o-301: dashboard interface (the value creation workflow for a client project).O-301: Generation O-302 a client.a product development sprint.a marketing campaign.website launch
F-100 SHEETS	resource management: to direct resources (financial energy) to sustain and grow the business., CFO role: `Management = How you handle money + How you organize work`; MEP/utilities, control room system	any entry with `domain: f-series` is a resource control system.	your budget tracker, the "energy flow" sankey diagram model, a specific invoice.	workflow: an `o-series` project is completed. this triggers the creation of a new `f-series` invoice entity, which is then linked back to the project.	F-100: Domain Overview F-201: Sankey Diagram F-202: Financial Controls	f-201: process workflow (energy flow) (the sankey diagram model).f-202: financial controls (the cash runway tracker).a specific invoice.the quarterly budget.F-201: Maintenance
L-100 SHEETS	the Self-Society: `Containment = Legal Framework + Civic Obligations;` base building; site & zoning, structural	To Define & Defend Boundaries → Trust & Security (Risk is contained)	LLC operating agreement, a client contract, an NDA template.	when you start a new `o-series` client project, you connect it to its corresponding `a-series` contract.	L-100: Domain Overview L-200: Process Workflow	the llc operating agreement.L-200: process workflow (the executable legal review process).L-100: domain overview.A-101: Foundation L200: process workflow
G-100 SHEETS	"context map" & observer dashboard; command center	any entry with `domain: g-series` is a principle or a map of the system itself.	a strategic principle, a system diagram, the `g-003 architect's dashboard` itself.	these are the high-level controls and views that allow you to operate the machine.	G-001: Legend & Key Plan G-002: Masterplan G-003:	a strategic principle.G-500: legend & key plan (a document defining the system's terms).G-200: titleblock dashboard.G-100: master

the domains of operation

‣

O-000 SERIES: value generation, workshop interface (CEO/COO role)

‣

F-000 SERIES: financials/CFO role, energy maintenance, resource management (control room)

‣

A-100 SERIES: containment, structural integrity, foundational blueprint

‣

G-series: governance & system-level views, alignment & orientation

define the workflows and domain events.

example workflow: new client engagement

o-series executes a finalize_client_agreement command on a client project aggregate.
upon success, it publishes a client_agreement_finalized event containing the core details (client id, project scope, value).
a-series subscribes to this event. its legal context consumes the event and initiates an internal create_legal_entity_file command.
the next crucial step is to map the cross-context workflows. ask: what business event in one domain triggers a process in another? f-series also subscribes to this event. its financial context consumes the event and initiates an internal generate_initial_invoice command.

this event-driven flow ensures that the o-series does not need to know anything about the internal workings of the legal or financial domains. they are autonomous yet coordinated.

the core mechanic: executable process workflows

the "how" of the system is a standardized workflow applied across all domains. each x-01 process workflow sheet uses a double-diamond model visualized as an exploded axonometric diagram. this is not just a drawing; it is a visual algorithm that makes the contract of each role executable, ensuring a predictable rhythm for all operations, from legal review to product delivery.

‣