Name | Role | Sheets Examples | SHEETS INDEX | Function | Core Activities | Workflow |
|---|---|---|---|---|---|---|
"context map" & observer dashboard; command center | G-001: Legend & Key Plan G-002: Masterplan G-003: | any entry with | a strategic principle, a system diagram, the | these are the high-level controls and views that allow you to operate the machine. | ||
the Self-Society: | L-100: Domain Overview L-200: Process Workflow | To Define & Defend Boundaries → Trust & Security (Risk is contained) | LLC operating agreement, a client contract, an NDA template. | when you start a new | ||
resource management: to direct resources (financial energy) to sustain and grow the business., CFO role: | F-100: Domain Overview F-201: Sankey Diagram F-202: Financial Controls | any entry with | your budget tracker, the "energy flow" sankey diagram model, a specific invoice. | workflow: an | ||
operational studio, mktg & workshop: To Create & Deliver Value → Communication, Impact, Revenue, CEO/COO role: | O-300: Domain Overview O-301: Dashboard Interface | any entry with | client delivery, meetings, communication, project-based work, product development, marketing/sales campaign | this is where most |
Entity Name | Type | Purpose (Tied to Drivers) | Title/Description | Titleblock: General Notes (Set-Wide; Tied to Core Purpose) | Titleblock: Key Plan (Entity Grid Overview; Axes & Coordinates) | Titleblock: Legend (Lines/Symbols; View-Specific) | Titleblock: Sheet Notes (Sheet-Specific; Numbered/Annotated; Cross-Refs) | View (Entity-Generated; Series-Based Info Types) |
|---|---|---|---|---|---|---|---|---|
the quarterly budget. | ||||||||
a specific invoice. | ||||||||
f-202: financial controls (the cash runway tracker). | ||||||||
f-201: process workflow (energy flow) (the sankey diagram model). | ||||||||
F-201: Maintenance | Management: Map “metabolism” kinetic energy (active cash flow) and potential energy (capital management); direct flows for equilibrium. | role of CFO. Energy Flow Diagram: Revenue & Expenses | As G-002: Directs energy; sovereignty via allocation. | As G-002: Vertical (Production: South/Past—flows; North/Future—projections); Horizontal (Cognition: Left/Internal—reserves; Right/External—streams). | Ref G-002: Scope: ······; Kinetic: – – – –; Potential: ———; In/Out: →; Transfers: ↔. | 1. Accounts (annotate scope). 2. Draws (cross-ref O-301). 3. Buffers (ref L-103). | Sankey Diagram: Dashed kinetic (South-North); solid potential reservoirs. Scope: ······ (market reach). Vertical timeline: Past flows (South) → Projections (North). Info types: Finance, management, creation. |
Entity Name | Type | Purpose (Tied to Drivers) | Title/Description | Titleblock: General Notes (Set-Wide; Tied to Core Purpose) | Titleblock: Key Plan (Entity Grid Overview; Axes & Coordinates) | Titleblock: Legend (Lines/Symbols; View-Specific) | Titleblock: Sheet Notes (Sheet-Specific; Numbered/Annotated; Cross-Refs) | View (Entity-Generated; Series-Based Info Types) |
|---|---|---|---|---|---|---|---|---|
a strategic principle. | ||||||||
G-200: titleblock dashboard. | ||||||||
G-500: legend & key plan (a document defining the system's terms). | ||||||||
G-100: master | Establish entity framework; tie drivers to trust-building. | General Notes, Legend & Key Plan | As G-002: Energy system; trust via separation/rules. Axes as above. | Ref G-002: Scope: ······; Axis-Production: | 1. Use G-002 linetypes for consistency. 2. Cross-refs: Ops feeds finance; legal contains both. 3. Quarterly diagnostics. |
Entity Name | Type | Purpose (Tied to Drivers) | Title/Description | Titleblock: General Notes (Set-Wide; Tied to Core Purpose) | Titleblock: Key Plan (Entity Grid Overview; Axes & Coordinates) | Titleblock: Legend (Lines/Symbols; View-Specific) | Titleblock: Sheet Notes (Sheet-Specific; Numbered/Annotated; Cross-Refs) | View (Entity-Generated; Series-Based Info Types) |
|---|---|---|---|---|---|---|---|---|
L-100: domain overview. | ||||||||
L-200: process workflow (the executable legal review process). | ||||||||
the llc operating agreement. | ||||||||
A-101:
Foundation | Containment: Define boundaries/identity; build trust. | Site Plan: Brand & Structure | As G-002: Containment prevents leaks; trust via separation. | As G-002: Vertical (Production: South/Past—registration; North/Future—brand growth); Horizontal (Cognition: Left/Internal—LLC; Right/External—brand). | Ref G-002: Scope: ······ (property lines); Containment: □; External flow: →; Internal: ———. | 1. Brand trademarks (annotate scope angle). 2. Structure (cross-ref L-102). 3. Check laws (ref F-202). | Diagram: Brand (right, scope ······); LLC shield (left). Vertical timeline: Registration (South) → Scaling (North). Info types: Legal, brand, creation. | |
L200: process workflow | Containment: Anchor legal existence. | Foundation Plan: Formation Documents | As G-002: Vessel for energy; trust via proof. | As G-002: Vertical (Production: South/Past—filing; North/Future—renewals); Horizontal (Cognition: Left/Internal—governance; Right/External—deed/EIN). | Ref G-002: Scope: ······; Containment: □; Official: ———; Application: – – – –. | 1. Articles timeline (South). 2. Operating Agreement (cross-ref L-103). 3. EIN (ref F-201). | Layout: Deed/EIN (right); Articles/Agreement (left). Vertical timeline: Filing (South) → Renewals (North). Info types: Formation, management, timeline. |
Entity Name | Type | Purpose (Tied to Drivers) | Title/Description | Titleblock: General Notes (Set-Wide; Tied to Core Purpose) | Titleblock: Key Plan (Entity Grid Overview; Axes & Coordinates) | Titleblock: Legend (Lines/Symbols; View-Specific) | Titleblock: Sheet Notes (Sheet-Specific; Numbered/Annotated; Cross-Refs) | View (Entity-Generated; Series-Based Info Types) |
|---|---|---|---|---|---|---|---|---|
website launch | milestone | |||||||
a marketing campaign. | ||||||||
a product development sprint. | ||||||||
a client. | ||||||||
o-301: dashboard interface (the value creation workflow for a client project). | ||||||||
O-series | ||||||||
O-301:
Generation | Generation: Convert inputs to value. | role of CEO. Core Process Plan: SOPs & Workflow | As G-002: Transforms potential to kinetic; trust via outputs. | As G-002: Vertical (Production: South/Past—jobs; North/Future—projects); Horizontal (Cognition: Left/Internal—SOPs; Right/External—client paths). | Ref G-002: Scope: ······; Generation: →; Process: – – – –; Rooms: □. | 1. SOPs (annotate scope). 2. Workflows (cross-ref L-103). 3. Self-mgmt (ref F-201). | Plan: SOPs (left); Workflows (right). Scope: ······ (service reach). Vertical timeline: Jobs (South) → Projects (North). Info types: Operations, generation, management. | |
O-302 | Generation: Equip for efficiency; scale creation. | Tools & Equipment layout Plan: Tech Stack | As G-002: Boosts value gen; trust via tools. | As G-002: Vertical (Production: South/Past—tools; North/Future—upgrades); Horizontal (Cognition: Left/Internal—tools; Right/External—client-facing). | Ref G-002: Scope: ······; Equipment: ———; Tools: – – – –; Integration: ↔. | 1. Stack APIs (annotate scope). 2. Hardware/software (cross-ref O-301). 3. Updates (ref F-202). | Layout: Software (right); Hardware (left). Scope: ······ (tech reach). Vertical timeline: Current stack (South) → Upgrades (North). Info types: Tech, operations, maintenance. |