AA19
[ Architecture · 10 Systems ]

ARCHITECTURE.

How the operating system is built. Layers, tiers, learning loops, verification, governance, and progressive autonomy. Tuning in from ten channels.

MODEL AA19-01WALNUT / 1968
● CH 01System OverviewREC

Organizational Operating System

AA19 continuously observes organizational state, measures operational health, records decisions, creates work, verifies outcomes, and improves future behavior through accumulated organizational intelligence.

System Responsibilities
  • ›Continuous observation
  • ›Execution coordination
  • ›Organizational learning
  • ›Governance and verification
Operating Principles
  • ›State is continuously observed
  • ›Decisions are preserved
  • ›Behavior improves through use
Inputs
  • ›Founder intent
  • ›Operational signals
  • ›Decision outcomes
  • ›External information
Outputs
  • ›Verified work product
  • ›Organizational intelligence
  • ›Progressive autonomy
Verification Method
Outcomes are recorded against intent, then re-evaluated as evidence accumulates.
Source of Truth
Organizational State Ledger
        ┌───────────────────────────────────────────┐
        │              ORGANIZATIONAL OS            │
        └───────────────────────────────────────────┘
               │            │            │
          OBSERVE       EXECUTE      GOVERN
               │            │            │
               ▼            ▼            ▼
            STATE  ───► DECISIONS ───► LEARNING
                              │
                              ▼
                         AUTONOMY
AA19
MODEL AA19-02BEIGE / 1979
● CH 02Architecture ModelREC

Four-Layer Architecture

Responsibility is separated into four layers. Information moves upward, governance moves downward. Each layer has a distinct concern and cannot bypass the layer above or below.

System Responsibilities
  • ›Execution carries out work
  • ›Observation measures state
  • ›Learning preserves outcomes
  • ›Governance defines authority
Operating Principles
  • ›Separation of concerns
  • ›Upward signal, downward authority
  • ›No layer bypass
Inputs
  • ›Work requests
  • ›Operational telemetry
  • ›Decision history
  • ›Policy and identity
Outputs
  • ›Actions
  • ›Health metrics
  • ›Guidance
  • ›Authority decisions
Verification Method
Each layer publishes its own state. Cross-layer transitions are logged and reconciled.
Source of Truth
Layer Manifest
↓ governance flows down↑ information flows up
L4
GOVERNANCE
Brain · QA · Strategy · Founder Dependency · Brand Intelligence
L3
LEARNING
Memory · Guidance · Coach · Decision History
L2
OBSERVATION
Analytics · Revenue Flow · Department Health · Workforce Mgmt
L1
EXECUTION
Research · Outbound · Content · Partnerships
AA19
MODEL AA19-03NAVY / 1982
● CH 03Resolution OrderREC

Four-Tier Execution Model

Every situation resolves through a fixed order of tiers. Earlier tiers are exhausted before later tiers are invoked. External reasoning is the last resort, not the default.

System Responsibilities
  • ›Tier 1 enforces rules
  • ›Tier 2 recalls memory
  • ›Tier 3 applies organizational intelligence
  • ›Tier 4 invokes external reasoning
Operating Principles
  • ›No action bypasses earlier tiers
  • ›Cheapest sufficient tier wins
  • ›Provenance is preserved per decision
Inputs
  • ›Situation context
  • ›Governance rules
  • ›Historical outcomes
  • ›Organizational state
Outputs
  • ›Resolved action with provenance
Verification Method
Each decision records the tier that resolved it. Tier distribution is monitored over time.
Source of Truth
Decision Provenance Log
SITUATION
   │
   ▼
[ TIER 1 ] RULES                ─── governance ───┐
   │ unresolved?                                   │
   ▼                                               │
[ TIER 2 ] MEMORY               ─── experience ───┤
   │ unresolved?                                   │
   ▼                                               │
[ TIER 3 ] ORG INTELLIGENCE     ─── state    ─────┤
   │ unresolved?                                   │
   ▼                                               │
[ TIER 4 ] EXTERNAL REASONING   ─── synthesis ────┘
   │
   ▼
RESOLVED ACTION  (tier + provenance preserved)
AA19
MODEL AA19-04RUST / 1971
● CH 04Compounding BehaviorREC

Organizational Learning Loop

The organization learns through operation. Founder decisions, QA findings, and outcomes are converted into organizational intelligence that changes future behavior.

System Responsibilities
  • ›Capture decisions
  • ›Record outcomes
  • ›Update guidance
  • ›Adjust future behavior
Operating Principles
  • ›Learning is evidence-based
  • ›Behavior change is observable
  • ›Loops are continuous
Inputs
  • ›Founder approvals, edits, rejections
  • ›QA findings
  • ›Measured outcomes
Outputs
  • ›Updated memory
  • ›Updated guidance
  • ›Behavior deltas
Verification Method
Behavior deltas are measured against historical baselines after guidance updates.
Source of Truth
Learning Ledger
  DECISION ──► MEMORY ──► GUIDANCE ──► BEHAVIOR
      ▲                                      │
      │                                      ▼
   LEARNING ◄──── OUTCOME ◄────────── (operation)
AA19
MODEL AA19-05OLIVE / 1976
● CH 05System LayerREC

Verification Architecture

Verification is a system layer, not a feature. A capability is not considered complete until evidence exists that the system performed as designed.

System Responsibilities
  • ›Define expected behavior per subsystem
  • ›Collect evidence continuously
  • ›Report coverage
  • ›Flag drift
Operating Principles
  • ›No capability without evidence
  • ›Coverage is observable
  • ›Stale verification is treated as risk
Inputs
  • ›Subsystem state
  • ›Expected behavior contracts
  • ›Operational telemetry
Outputs
  • ›Verification status
  • ›Coverage percentage
  • ›Drift alerts
Verification Method
Every subsystem publishes status, coverage, last verification time, and source of truth.
Source of Truth
Verification Registry
SubsystemStatusCoverageLast VerificationSource of Truth
Revenue FlowVerified94%2h agoLedger
Department HealthVerified91%4h agoMetrics Store
GoalsVerified88%1h agoGoal Registry
Action ItemsVerified96%12m agoAction Log
MemoryVerified93%8m agoMemory Ledger
GuidanceVerified89%26m agoGuidance Store
AnalyticsVerified92%3h agoEvent Stream
WorkforceVerified90%47m agoWorkforce State
Founder DependencyVerified87%1h agoDecision Log
Decision HistoryVerified95%5m agoDecision Log
Brand IntelligenceVerified86%6h agoIdentity Store
BrainVerified92%1m agoBrain State
AA19
MODEL AA19-06OAK / 1973
● CH 06Org StructureREC

Department Model

The organization is modeled as a set of departments. Each department has measurable health, owned goals, action items, ownership, and historical learning.

System Responsibilities
  • ›Maintain department health
  • ›Track goals and action items
  • ›Record ownership
  • ›Preserve historical learning
Operating Principles
  • ›Health is measured, not asserted
  • ›Ownership is explicit
  • ›History informs creation of new actions
Inputs
  • ›Operational signals
  • ›Goal definitions
  • ›Action outcomes
Outputs
  • ›Department health score
  • ›Action items
  • ›Historical learning records
Verification Method
Department health is reconciled against source-of-truth metrics on a defined cadence.
Source of Truth
Department Registry
Revenue
92
Marketing
84
Operations
88
Customer Success
91
Product
79
Intelligence
94
Leadership
86
AA19
MODEL AA19-07OBSIDIAN / 1985
● CH 07Operating MetricREC

Founder Dependency Model

Founder dependency is treated as a measurable operating metric. It can be measured, reduced, and tracked over time.

System Responsibilities
  • ›Measure approvals, edits, rejections, overrides, corrections, and decision ownership
  • ›Aggregate dependency over time
  • ›Surface dependency trends
Operating Principles
  • ›Dependency is observable
  • ›Reduction is intentional
  • ›Trust precedes autonomy
Inputs
  • ›Founder interactions
  • ›Decision history
Outputs
  • ›Dependency score
  • ›Dependency trend
  • ›Trust signal
Verification Method
Dependency components are recomputed from raw interaction logs. Trends are reconciled against decision outcomes.
Source of Truth
Founder Interaction Log
DEPENDENCY  ──►  TRUST  ──►  AUTONOMY  ──►  FOUNDER FREEDOM
   (measured)     (earned)     (granted)         (resulting)
AA19
MODEL AA19-08BRICK / 1970
● CH 08Decision PipelineREC

Decision Architecture

Every significant decision moves through a fixed pipeline. Context, outcome, and learning are preserved so that decision quality compounds.

System Responsibilities
  • ›Observe
  • ›Diagnose
  • ›Decide
  • ›Act
  • ›Verify
  • ›Learn
Operating Principles
  • ›Every decision has context
  • ›Every decision has an outcome
  • ›Outcomes feed future decisions
Inputs
  • ›Situation context
  • ›Relevant memory
  • ›Applicable guidance
Outputs
  • ›Decision record
  • ›Action
  • ›Outcome record
  • ›Learning delta
Verification Method
Decision records are sampled and re-evaluated against actual outcomes.
Source of Truth
Decision Log
OBSERVE ──► DIAGNOSE ──► DECIDE ──► ACT ──► VERIFY ──► LEARN
   ▲                                                       │
   └───────────────────────────────────────────────────────┘
AA19
MODEL AA19-09BRASS / 1969
● CH 09Identity LayerREC

Organizational Identity

Organizational Identity is loaded before execution. It defines voice, positioning, ICP, principles, offers, messaging, and standards, and it influences every output.

System Responsibilities
  • ›Maintain identity components
  • ›Distribute identity to executing agents
  • ›Enforce identity in outputs
Operating Principles
  • ›Identity is loaded, not inferred
  • ›Identity is consistent across agents
  • ›Identity is reusable
Inputs
  • ›Founder-defined identity
  • ›Approved examples
  • ›Refinements over time
Outputs
  • ›Consistent outputs across agents
  • ›Reusable organizational asset
Verification Method
Outputs are sampled and scored for identity adherence against the active identity revision.
Source of Truth
Identity Store
Voice
Positioning
ICP
Principles
Offers
Messaging
Standards
AA19
MODEL AA19-10PLUM / 1981
● CH 10Authority ModelREC

Progressive Autonomy

Authority is granted deliberately. Autonomy is earned through evidence. The objective is not automation. The objective is trusted operation.

System Responsibilities
  • ›Track approval history
  • ›Maintain guidance maturity
  • ›Monitor QA performance
  • ›Evaluate operational consistency
Operating Principles
  • ›Autonomy is earned
  • ›Evidence is required
  • ›Authority can be revoked
Inputs
  • ›Verified outcomes
  • ›Guidance maturity
  • ›Approval history
  • ›QA performance
  • ›Operational consistency
  • ›Organizational trust
Outputs
  • ›Autonomy level per capability
  • ›Authority grants
  • ›Revocations when evidence regresses
Verification Method
Autonomy grants are tied to evidence thresholds. Regression triggers downgrade.
Source of Truth
Authority Ledger
[ APPROVAL ]  ──►  [ HYBRID ]  ──►  [ AUTONOMOUS ]
  every action       routine auto         independent
  reviewed           critical to founder  operation
                     │
                     └── evidence: outcomes · guidance · QA · consistency · trust
AA19

See the process behind it.

The five steps clients walk from approval, to hybrid, to autonomous operations.

Open Process →