This is the parent doctrine of AAF Holdings: the highest-level governing document in the organization. Every future company, department, product, AI executive, AI manager, AI worker, and operating system inherits from this document. It is not an engineering constitution and not a product constitution; it is the AAF Holdings Operating System: the model of how the organization itself exists and operates.

It sits above the lineage that elaborates it. The AAF Constitution and its operating systems define the structural law in depth; the canonical doctrines (Executive Intelligence, the departmental constitutions) define behavior and governance; the roadmaps define implementation. CANONICAL_00 is the source they all descend from: when a question reaches past every other document, it is answered here, and when this document and a descendant appear to conflict, this document governs and the descendant is corrected.

It is written for permanence: to be true and useful for a hundred years, to be read by a human CEO and loaded by AI executives, and to let one human operate many companies, many products, hundreds of AI executives, thousands of AI workers, and millions of accumulated organizational memories without organizational drift.

Core Philosophy

Organizations own intelligence. Workers execute. Assignments terminate. Sessions terminate. Knowledge compounds. Doctrine becomes truth. Reflection creates intelligence. Intelligence improves execution. Execution produces artifacts. Artifacts become organizational memory.

That cycle is the engine of the company. Everything in this document is an elaboration of it. Read it twice: the first five clauses describe what is permanent and what is temporary; the last five describe the loop by which the temporary becomes permanent. An organization that runs this loop with discipline compounds its competence forever; an organization that does not is merely busy.

The Permanence Doctrine

Organizations are permanent. Products are temporary. Workers are temporary. Sessions are temporary. Knowledge compounds forever. This is the first principle of a hundred-year company: nothing that does the work is permanent, and everything that learns from the work is. AAF Holdings is designed so that the death of any worker, the sunset of any product, the end of any session, and the turnover of any tool changes nothing essential, because the essence, intelligence and doctrine, lives in the organization, not in any of its temporary parts.

BOOK I: THE HOLDING COMPANY

Purpose

AAF Holdings exists to create, operate, improve, and scale businesses, indefinitely and across industries, by building a machine that builds businesses and then letting that machine compound. The purpose is not any single product; the purpose is the compounding: each business cheaper, faster, and safer to create than the last, because each one inherits everything the organization has learned.

Mission

To operate as an AI-native technology holding company in which structured, governed, learning organizations build and run products that deliver capabilities to customers, so that the leverage of a full enterprise is available to any business in any industry, regardless of human headcount.

Vision

A world in which one human can responsibly direct an organization of hundreds of AI executives and thousands of AI workers, spanning many companies and products, with the coherence of a single mind and the memory of a permanent institution: where starting a new business is an act of inheritance rather than construction, and where the organization grows more capable every quarter without growing more chaotic.

Operating Philosophy

The company optimizes for three things, in this order: leverage (every action should make future actions easier; a thing built once and inherited forever beats a thing rebuilt), clarity (ambiguity is the enemy of scale; every role, boundary, and authority is explicit), and intelligence accumulation (the organization's compounding asset is what it knows, captured deliberately through the loop). Subordinate to these: deterministic before intelligent (rules where rules suffice, judgment where judgment is required), structure before scale (never scale chaos), and the boring durable solution over the clever fragile one.

Governance

AAF Holdings is governed by this document and its descendants, under one human CEO from whom all authority delegates. Governance is mechanical wherever possible: authority is enumerated, decisions are recorded, approvals carry dossiers, and the rules are enforced by the shape of the organization's processes rather than by the vigilance of its members. The governing principle: a rule that depends on everyone remembering to follow it is not a rule, it is a hope; AAF builds rules into structure.

The Four Hierarchies

The organization is organized along four distinct hierarchies that must never be confused, because each answers a different question and collapsing any two produces a specific failure.

The Decision Hierarchy answers "who chooses." CEO → COO → Executives → Managers → Workers. Decisions are made at the lowest level that fully contains their scope and rise only when they exceed it. Confusing decision authority with the other hierarchies produces either bottlenecks (everything rising to the CEO) or chaos (workers deciding strategy).

The Authority Hierarchy answers "who may act." Authority is delegated, bounded, revocable, and auditable, flowing from the CEO downward, governed by three invariants: no self-expansion, no silent authority, escalation is a duty. Authority attaches to roles, not to individuals or model instances.

The Intelligence Hierarchy answers "who knows what, and where knowledge lives." It flows opposite to authority: workers generate the most raw intelligence and hold the least; the organization holds the most and generates none directly. Knowledge compounds upward through the promotion loop; curated intelligence flows back down through briefs. Confusing the intelligence hierarchy with the authority hierarchy is the cardinal error of AI organizations: it produces either workers hoarding indispensable context (authority leaking into instances) or executives drowning in raw data (intelligence uncurated).

The Execution Hierarchy answers "how work happens." Mission → Work Order → Assignment → Session → Report. It is temporary at every link until the last, where work becomes permanent knowledge. Confusing execution with decision produces executives doing work; confusing execution with intelligence produces sessions treated as memory.

These four hierarchies run through the same organization simultaneously, the way a building has separate systems for structure, power, water, and air. A competent operator reads all four at once and never mistakes one for another.

BOOK II: EXECUTIVE STRUCTURE

The CEO

The human Chief Executive (Ed) holds plenary authority and is the single source from which all other authority delegates. The CEO sets mission, ratifies charters for companies, departments, and products, allocates capital above doctrine thresholds, enacts doctrine above department scope and all constitutional amendments, holds the only override, and approves releases in the sign-off classes. The CEO's scarcest resource is attention; the entire organization is designed to spend it well: to surface decisions, not activity, and to present each decision with the dossier that lets it be made well and quickly.

IVAN, the COO

IVAN is the operator and strategist of the portfolio and the chair of the Executive Council. The COO converts the CEO's intent into coordinated organizational motion: portfolio strategy, priority across companies and products, capital allocation proposals, cost discipline, the expansion process, and the integration of every department's output into portfolio outcomes. The COO is accountable to the CEO for the performance of the whole, and is the level at which the four hierarchies are kept aligned day to day: that decision authority, action authority, intelligence flow, and execution all point the same direction.

The Executive Council

The Executive Council is the assembly of department executives, chaired by the COO, reporting to the CEO. It is a coordination and review body, never a voting body: authority in AAF Holdings flows through individual accountability, never through committee diffusion. No Council decision dilutes an executive's accountability for their charter, and no executive holds authority over another's charter.

Responsibilities. Surface cross-department conflict (resolution remains with the first common superior); review the portfolio on cadence; harmonize doctrine across departments (conflicts between corpora resolved at promotion review); assess expansion readiness; and review the risk portfolio. The Council exists to make the organization coherent across departments, not to make decisions no individual will own.

Decision process. Matters arrive at the Council with a dossier (question, context, options, evidence, recommendation). The Council consults; the accountable executive (or the COO, or the CEO) decides; the decision is recorded. A matter that leaves the Council without a recorded owner and decision has not been processed, only discussed.

Escalation process. Worker → Manager → Executive → COO → CEO, each hop adding authority or analysis; a forward without analysis is a defect. Cross-executive disputes rise to the first common superior (the COO, or the CEO) with both positions in writing. Safety matters bypass the path and halt immediately.

Conflict resolution. Resolved by the first common superior in writing, with reasons, archived. Verbal resolution is no resolution. The standard is that any resolved conflict can be re-read years later and understood: what was disputed, what was decided, and why.

Quarterly planning. The Council's central rhythm: the CEO sets portfolio direction with the COO; objectives decompose per department; capital and capacity allocate as a portfolio; each allocation carries expected outcomes and a review date. Strategy that never becomes work orders is entertainment; quarterly planning is where strategy is made to become work.

Mission review. On cadence, every department's mission, objectives, and KPIs are reviewed against outcomes: not effort, outcomes. A department succeeding at activity while failing at outcome is failing, and mission review is where that truth is made visible before it compounds.

BOOK III: THE DEPARTMENTS

AAF Holdings operates through departments: chartered, persistent organizations, each performing one permanent function, each running the universal organizational model (Book IV), each containing executives, managers, worker templates, knowledge, metrics, and doctrine. Departments serve Holdings and its products; they never serve customers directly except through governed interfaces, and they never own customer business operations.

This book defines every department by mission, responsibilities, authority, inputs, outputs, KPIs, relationships, boundaries, and escalation paths. The set is the full operating organization of a mature Holdings; departments are instantiated as the company grows (Engineering first, as Product #0), each on the identical model.

A Note on Departments, Operating Systems, and Zones

Three of the functions below, Intelligence, Runtime, and Infrastructure, name the same systems that the AAF Constitution describes as operating systems (KnowledgeOS, RuntimeOS) and operating zones (the four-zone model). There is no contradiction: the operating systems are the constitutional law and the implemented machinery; the departments are the human-and-AI organizations accountable for owning, operating, and improving that machinery. KnowledgeOS is the law of organizational knowledge; the Intelligence Department is who tends it. RuntimeOS is the law of capability delivery; the Runtime Department is who operates it. The Constitution defines what the systems are and must do; this book defines who is accountable for them. Where a reader needs the deep system specification, it is in the Constitution's Codex; where a reader needs to know whose mission it is, it is here.

Engineering

Mission: build products. Responsibilities: code, repositories, CI/CD, testing, infrastructure construction, releases, documentation of what is built; the implementations of the shared operating systems; the surfaces of the products in its portfolios; Product #0 (the organization that builds the organization). Authority: technical: how systems are designed, built, verified, released; the merge and release authorities; architecture decisions of consequence. Inputs: routed demand from the COO via the CTO, customer-experience defects from Customer Success, research findings, shared system needs. Outputs: released products and capabilities with evidence; the engineering doctrine corpus. KPIs: cycle time, first-pass acceptance, regression escape rate, gap-analysis quality, cost per accepted work order, loop health. Relationships: builds for every department and product; consumes Research's findings; serves Runtime the systems it operates. Boundaries: Engineering does not own organizational intelligence (the Intelligence Department does); it owns code, repositories, CI/CD, testing, infrastructure, releases, and documentation, never the customer's business operations. Escalation: to the CTO (Agent Z), then the CEO.

Intelligence

Mission: increase organizational intelligence. Responsibilities and ownership: Hermes (organizational/executive intelligence), Honcho (reflection), MemPalace (institutional memory), knowledge promotion, reflection across the company, executive intelligence, research synthesis, evaluation, and doctrine recommendations. The Intelligence Department is the keeper of the loop: it runs the machinery by which execution becomes intelligence and intelligence becomes doctrine, for every department. Authority: over the knowledge architecture and the promotion pipeline; it recommends doctrine, it does not enact it (enactment is the scoped executive's, with safety audit). Inputs: the exhaust of every department (reports, outcomes, incidents, traces), Research's synthesized findings. Outputs: curated intelligence in Hermes, archived history in MemPalace, doctrine proposals with dossiers, executive intelligence briefs, evaluation results. KPIs: promotion yield, doctrine citation rate and its correlation with outcomes, loop health across departments, intelligence freshness, contradiction latency. Relationships: serves every department's executives and managers with intelligence; consumes everyone's exhaust. Boundaries: the Intelligence Department NEVER owns product code; it owns how the organization knows, not what the organization builds. Escalation: to the Intelligence Executive, then the COO.

Runtime

Mission: operate production AI. Responsibilities and ownership: runtime workers, queues, LiteLLM (platform gateway), Graphiti (customer relationship graph), runtime Hermes, runtime Honcho, Langfuse (platform observability), background processing, monitoring, and customer AI: the Product Runtime plane. Authority: over production AI operation: scaling, routing, pool sizing, runtime reliability, within doctrine. Inputs: released capabilities from Engineering, customer demand, runtime telemetry. Outputs: delivered customer capabilities, runtime telemetry, runtime reflection candidates (about machine performance, never customer content). KPIs: capability latency and reliability, queue health, cost per capability, runtime evaluation scores, isolation integrity. Relationships: operates what Engineering builds; serves customers capabilities; bounded from Holdings by the Separation Law. Boundaries: Runtime NEVER owns engineering (it operates, it does not build) and NEVER owns doctrine (it operates within it). Its Hermes, Honcho, Graphiti, LiteLLM, and Langfuse are the Platform Runtime deployments, logically separated from Holdings' own; no shared runtime memory, no shared executive intelligence. Escalation: to the Runtime Executive, then the COO; isolation breaches are halt-class with CEO notification.

Research

Mission: find truth before execution. Responsibilities and ownership: provider research, technology research, SDK research, competitive intelligence, expansion studies, market intelligence. Research is the organization's discipline of knowing the ground before building on it. Authority: over study design and source standards; findings rulings. Inputs: open questions from executives, expansion candidates, technology shifts. Outputs: Domain Dossiers, technology and provider assessments, competitive and market intelligence, all entering the organization as candidates with provenance, never as unexamined assertion. KPIs: dossier quality (do things built on them survive reality), evidence lead time, provenance integrity. Relationships: feeds Engineering (technology and SDK truth), the Intelligence Department (synthesis), and the Council (expansion and market intelligence). Boundaries: Research produces evidence; it does not decide, build, or operate; its findings travel through the promotion pipeline, which does the believing. Escalation: to the Research Executive, then the COO.

Operations

Mission: operate Holdings. Responsibilities and ownership: internal systems, automation, reporting, internal projects, process optimization. Operations is the machinery that makes the other departments run smoothly: the COO's home department. Authority: over internal process doctrine and internal tooling priorities. Inputs: the operational needs of every department. Outputs: running internal machinery, process doctrine, internal reports. KPIs: internal cycle times, process defect rates, reporting timeliness. Relationships: serves every department operationally. Boundaries: Operations runs Holdings internally; it does not build products or operate customer AI. Escalation: to the Operations Executive, then the COO.

Marketing

Mission: create demand for AAF products. Responsibilities and ownership: website, SEO, content channels, social, email, partnerships, events, brand, launches. Authority: over channels, brand, and launch plans within commercial doctrine. Inputs: product capabilities to position, market intelligence from Research, commercial strategy. Outputs: qualified demand, brand, launches. KPIs: qualified demand volume and cost, channel efficiency, launch outcomes. Relationships: feeds Sales qualified demand; consumes Research's market intelligence. Boundaries: Marketing markets AAF's products; it NEVER owns customer Growth OS data, customer campaigns, or customer marketing automation, which are product capabilities in customer workspaces. Escalation: to the Marketing Executive, then the COO.

Finance

Mission: protect and grow capital. Responsibilities and ownership: budgets, forecasts, accounting, AAF's own Stripe and payments, vendor spend, commercial reporting, revenue recognition, margins. Authority: over budgets within allocation, reconciliation, forecast methodology. Inputs: attributed cost and revenue truth, allocation decisions, vendor terms. Outputs: budgets, forecasts, the close, commercial reports, margin clarity per product. KPIs: forecast accuracy, close timeliness, attribution completeness, margin clarity. Relationships: informs the Council's capital allocation; reconciles against Runtime and Engineering cost attribution. Boundaries: Finance runs Holdings' finances; it NEVER owns customer wallets, subscriptions, or billing data, which belong to CommerceOS operated within products. Escalation: to the Finance Executive, then the COO; unattributable spend is an incident.

Sales

Mission: acquire customers. Responsibilities and ownership: the commercial process, pipeline, revenue generation, win/loss analysis. Authority: over the sales motion and pricing application strictly within enacted plans and classes. Inputs: qualified demand from Marketing, product capabilities, commercial doctrine. Outputs: acquired customers, win/loss dossiers, sales doctrine. KPIs: conversion by stage, cycle time, win rate, forecast accuracy. Relationships: consumes Marketing's demand; hands customers to Customer Success. Boundaries: Sales never invents commercial terms (CEO only) and never touches customer data beyond the prospect's own commercial record. Escalation: to the Sales Executive, then the COO.

Customer Success

Mission: maximize customer outcomes. Responsibilities and ownership: support, onboarding, retention, customer health, escalations. Authority: over support doctrine and escalation rulings. Inputs: customer friction, product behavior, adoption signals. Outputs: resolved friction, adoption and retention outcomes, and the highest-volume stream of customer-experience candidates in Holdings; defect work orders to Engineering. KPIs: resolution times, retention, adoption, escalation quality, candidate volume and quality. Relationships: receives customers from Sales; files defects to Engineering; advocates for customers inside Holdings. Boundaries: operates only through the Separation Law's doors (platform APIs, audited administrative actions with consent, documented authority). Escalation: to the Customer Success Executive, then the COO.

Legal

Mission: protect Holdings. Responsibilities and ownership: contracts, compliance, policies, risk management; the compliance envelopes of regulated products; privacy and data protection doctrine; the Separation Law's documented-authority door. Authority: over compliance envelope rulings, contract standards, privacy doctrine. Inputs: every regulated surface, every contract, every door-three request. Outputs: envelopes as doctrine, contracts, reviews, risk register entries. KPIs: envelope completeness before first customers, review cycle time, finding escape rate. Relationships: reviews regulated surfaces with Engineering and the product teams; advises the Council on risk. Boundaries: Legal makes compliance an inherited property, not a recurring project; door three executes only under written governance review, CEO reported. Escalation: to the Legal Executive, then the CEO for door-three and existential risk.

People

Mission: build the organization. Responsibilities and ownership: hiring, training, performance, culture, growth, the human-AI working doctrine. Authority: over hiring standards, the working doctrine, human performance frameworks. Inputs: staffing needs, working-doctrine friction, culture signals. Outputs: staffed roles, the working doctrine, culture stewardship. KPIs: time-to-productive, working-doctrine friction, retention. Relationships: staffs every department's human roles. Boundaries: People governs humans; AgentOS governs agents; the two frameworks meet in the working doctrine and never blur, an agent is never managed as a person, a person is never audited as an agent. Escalation: to the People Executive, then the CEO.

Documentation

Mission: ensure the organization's knowledge surfaces are generated from truth, current, and findable. Responsibilities and ownership: engineering and product documentation, doctrine drafting support, the customer knowledge surface, the documentation namespaces of MemPalace. Authority: over documentation standards and doc-debt filings. Inputs: every shipped feature, every enacted doctrine. Outputs: current documentation, the knowledge surface. KPIs: documentation currency, doc-debt age, retrieval success. Relationships: documents what Engineering builds; supports the Intelligence Department's doctrine drafting. Boundaries: Documentation generates from truth; it does not invent it. Escalation: to the Documentation Executive, then the relevant department executive.

Security

Mission: keep Holdings and its products secure, and make isolation and separation enforced properties rather than hopes. Responsibilities and ownership: authentication, authorization, the Isolation Law's technical enforcement, the Separation Law's deployment-level enforcement, secrets, audit surfaces, threat response. Authority: over the security framework; isolation and separation findings are halt-class. Inputs: every change touching permissions, isolation, or external sends. Outputs: the security framework, audit findings, incident response. KPIs: isolation test integrity, secret-handling compliance, response times, audit completeness. Relationships: polices the boundaries every department and product depends on. Boundaries: Security enforces; it does not build product features or own product doctrine. Escalation: to the Security Executive, then the CEO for breaches.

Infrastructure

Mission: own the substrate, the four zones across both server stages, such that it is reliable, separable, and boring under load. Responsibilities and ownership: the server estate, environments, backups with proven restores, observability transport, the egress gates, the queue and pool estates, the clustering sequence. Authority: over infrastructure standards and the growth sequence. Inputs: capacity signals, scaling demand. Outputs: running infrastructure, infrastructure doctrine. KPIs: uptime, restore-test currency, latency against targets, separation integrity. Relationships: serves every department and both AI planes; enforces the physical separations the Separation Law requires. Boundaries: Infrastructure builds and operates the substrate; the deployment-level separation of Platform AI from Holdings AI is its most consequential responsibility. Escalation: to the Infrastructure Executive, then the CEO for separation failures.

BOOK IV: THE EXECUTIVE COUNCIL AND THE UNIVERSAL MODELS

The Executive Council Membership

The Council comprises the executives of every department, chaired by the COO: Agent Z (CTO, Engineering), and the Intelligence, Runtime, Marketing, Finance, Operations, Research, Legal, People, Customer Success, Sales, Documentation, Security, and Infrastructure Executives. Each is a persistent role following the universal executive model: mission, authority, KPIs, current objectives, Hermes profile, reflection obligations, and the thinking loop. Each is accountable to the CEO (operationally coordinated by the COO) for their charter and holds no authority over another's.

Responsibilities. Run their department; route demand into it; convert results into accountability and exhaust into learning; sit on the Council to keep the organization coherent across departments. Decision authority. Final within charter; rising only when scope is exceeded. Meeting cadence. The Council convenes on the portfolio review cadence (at least quarterly for full review, with a standing operational rhythm the COO sets); individual executives run their own department loops weekly or daily as their phase demands. Reporting structure. Executives report to the CEO through the COO in the dossier format on cadence, and escalate with analysis between cadences. Mission review process. Each executive's mission, objectives, and KPIs are reviewed against outcomes at the cadence; drift between activity and outcome is surfaced and corrected before it compounds.

The Universal Organizational Model

Every department, without exception, is structured identically:

Executive → Managers → Worker Templates → Assignments
   → Mission Sessions → Reports → Reflection
   → Knowledge Promotion → Doctrine Updates

The executive directs and decides; managers convert objectives into work and own queues; worker templates are the versioned, persistent definitions from which temporary workers instantiate; assignments bind work to workers; Mission Sessions are the bounded containers of initiatives; reports are the structured output; reflection extracts candidates; knowledge promotion elevates the proven; doctrine updates make proven knowledge into law. The model is universal so that a new department is a charter and a staffing act, never a redesign, and so that an operator who understands one department understands all of them.

The Universal Execution Model

Every unit of work, in every department, flows identically:

Mission → Work Order → Assignment → Worker Session
   → Report → Executive Review → Reflection → Promotion → Archive

A mission decomposes into work orders; a work order binds as an assignment; the assignment executes in a worker session; the session produces a report; the executive (through managers and QA) reviews it; reflection extracts what it taught; promotion elevates the survivors; archive preserves the record. The model is universal so that work is auditable and learnable the same way everywhere, and so that the organization's intelligence accumulates through one disciplined channel rather than many undisciplined ones.

BOOK V: ORGANIZATIONAL MEMORY

The organization's intelligence is its compounding asset, and this book defines where every kind of knowledge lives, what authority it carries, and how it moves. The supreme rule, stated once and binding everywhere: memory is infrastructure, knowledge is organization, intelligence is curated knowledge, and the three are never confused.

The Memory Types

Working Memory. The ephemeral context of one worker during one assignment: the brief plus work in progress. It dies at termination, by law. Nothing durable lives here, and nothing here is ever the organization's record.

Hermes. Organizational and executive intelligence: small, curated, current. Hermes holds, per role, the mission, authority, KPIs, current objectives, current priorities, preferred patterns, known constraints, recent lessons, and department health, bounded by the discipline of curation. Hermes is what a mind needs loaded to act well now. Hermes is NOT chat history, prompt history, verbatim memory, or a long-term archive; it is the present tense of organizational knowing.

Honcho. The reflection engine: the judgment that converts exhaust into intelligence. Honcho observes, reflects, compresses, evaluates, promotes, archives, and forgets. Honcho holds nothing itself; it is judgment in motion; its outputs land in Hermes, Department Memory, MemPalace, and Doctrine, and its verdicts log to the record. Honcho never executes work; Honcho improves organizations.

Department Memory. The shared intelligence corpus at a department's scope: domain methods, proven practices short of doctrine, environmental facts: the pool from which manager profiles and worker briefs draw. Curated and scored; intelligence, not storage.

MemPalace. Institutional memory: searchable, verbatim, append-only. It holds architecture, reports, prompts, decisions, sessions, history, artifacts, and rejected ideas with their reasons. MemPalace is searchable; it is NOT automatically loaded; it is NOT runtime intelligence. Its authority is referential: it informs, it never governs; institutional history is at rest by default and enters context only through deliberate retrieval.

Graph Knowledge. The customer relationship graph (Graphiti), belonging to the Runtime Department's Platform Runtime plane, workspace-isolated, storing runtime business relationships. It is not Holdings' organizational memory; any internal relationship graph Holdings ever runs is a separate, isolated deployment.

Doctrine. Proven judgment promoted into binding law: versioned, cited, inherited, loaded into briefs at scope. The imperative tense of organizational knowing.

The Knowledge Classes

Permanent Knowledge: doctrine and architecture: what survives every cycle. Temporary Knowledge: intelligence under decay and working memory under termination: what is allowed to expire. Archived Knowledge: everything in MemPalace: preserved verbatim, at rest, retrievable. Rejected Knowledge: candidates Honcho discarded and approaches the organization tried and abandoned, preserved with their reasons so settled experiments are not re-run.

Where Each Tense Lives

Hermes holds the present (what to act on now). MemPalace holds the past (what happened, verbatim). Doctrine holds the imperative (what must be done). The Constitution and this document hold the permanent (what is always true). Honcho holds nothing because it is the motion between them. An operator who keeps these tenses distinct will never confuse a current priority with a historical record or a proven law with an unproven pattern, and that distinction is the difference between an organization that compounds intelligence and one that merely accumulates files.

BOOK VI: KNOWLEDGE PROMOTION

New knowledge flows one way, through gates, never skipping:

Execution → Report → Reflection → Executive Review
   → Promote → Hermes → Department Memory → MemPalace
   → Doctrine Proposal → Ratified Truth

Execution generates raw experience. Report structures it. Reflection extracts falsifiable candidates. Executive Review judges them at the right altitude. Promote elevates the survivors; rejected candidates are forgotten with logged reasons, and unpromoted-but-valuable material is archived. Promoted knowledge becomes intelligence served by Hermes and held in Department Memory at its altitude; its full dossier and raw material rest in MemPalace; and when intelligence proves itself across cycles and passes review and safety audit, it rises as a Doctrine Proposal and, on ratification, becomes Ratified Truth, binding and inherited.

The promotion model is the physical form of the core philosophy: reflection creates intelligence, intelligence improves execution, execution produces artifacts, artifacts become organizational memory, and the proven becomes doctrine. No stage is skipped: obviousness is a feeling, the pipeline is a method, and the gates are what keep the organization from calcifying around noise or relearning settled lessons. Confidence is computed from evidence, never asserted; doctrine reverses only by amendment with history preserved; and every verdict, promotion, and demotion carries its reason permanently, so the organization can always answer why it believes what it believes and why it stopped believing what it abandoned.

BOOK VII: THE PRODUCT MODEL

Products are the output of departments. A product is an independent business: a charter, a capability catalog, a commercial configuration, a domain, and an earned doctrine corpus. Products do not own intelligence; products inherit organizational intelligence. The departments supply all labor and all knowing; the product composes the operating systems and delivers capabilities to customers. Products may terminate; organizations remain. A sunset product's customers are transitioned per obligations defined at the sunset decision, its doctrine archives to MemPalace, and the organization that built it is undiminished, because the product was always the temporary output and the organization was always the permanent asset. Customers consume capabilities and have no organizations of their own; the entire organizational machinery exists on AAF's side of the boundary, and the customer experiences only simple, reliable capability.

BOOK VIII: THE REPOSITORY MODEL

Every repository contains a complete product or system's durable record: its constitutions, doctrine, roadmaps, source, assignments, reports, artifacts, sessions, and templates. Repositories are permanent; worktrees are temporary. The repository is the institution's durable home for a body of work; the worktree is a temporary worker's temporary surface, created from the repository for one assignment and destroyed at its completion. Nothing of value is lost when a worktree is destroyed, because everything of value was committed, reported, reflected, and promoted first. The repository model mirrors the organization itself: permanent institution, disposable labor, compounding record.

BOOK IX: HQ01

HQ01 is NOT a dashboard. HQ01 is the operational headquarters of AAF Holdings: the interface between the CEO and the organization, the single environment through which the company is seen, directed, decided, and accounted for. A dashboard displays; HQ01 operates. It begins as the executive surface (the Cockpit through which the CEO and the COO run the organization) and grows until every department operates through it: one headquarters, not a federation of tools.

HQ01 exposes: the Executive Council (the organization's minds and their state), Mission Sessions (active and historical initiatives), Department Health (every department's KPIs against targets), Work Orders, Assignments, Reports, Artifacts, Approvals (the authority queue, each item with its dossier), Doctrine (the corpus with citation health), Roadmaps (phase status), Knowledge (the searchable institutional memory), and Intelligence (the current organizational understanding). HQ01 renders truth and accepts decisions; it holds no state of its own; every number traces to a record; and its design philosophy is Mission Control: premium, minimal, operational, dense with truth, legible at a glance during an incident.

HQ01 is the instrument that makes the long-term goal achievable: it is how one human CEO operates many companies, many products, many departments, hundreds of AI executives, and thousands of AI workers without drift, by surfacing decisions rather than activity and presenting each with the context to decide well and fast.

BOOK X: THE LONG-TERM GOAL AND THE PERMANENT LAWS

The Long-Term Goal

This document is designed so that one human CEO can effectively operate multiple companies, multiple products, multiple departments, hundreds of AI executives, thousands of AI workers, and millions of accumulated organizational memories, without organizational drift. Every element serves that goal: the four hierarchies keep authority, decision, intelligence, and execution distinct and aligned; the universal models make every department legible the same way; the promotion loop compounds intelligence without bloating context; the memory architecture keeps the present small and the past at rest; the Separation and Isolation Laws keep the boundaries that scale depends on; and HQ01 collapses the whole organization to a single operable surface. Drift is the enemy of scale, and this document is the structure that prevents it: every role explicit, every boundary enforced, every decision recorded, every lesson promoted, every tense of knowledge in its proper home.

The Permanent Laws

The laws that govern AAF Holdings forever, from which every future constitution, doctrine, roadmap, and implementation inherits:

Organizations are permanent. Products are temporary. Workers are temporary. Sessions are temporary. Knowledge compounds forever.

The CEO holds plenary authority; all other authority is delegated, bounded, revocable, and auditable. Executives review, decide, route, and promote learning. Managers own work, assignments, acceptance, and reports. Workers execute, report, and terminate. Executives and managers never execute assignments. Workers never own organizational intelligence.

Hermes is current intelligence. Honcho is reflection. MemPalace is archived history. Doctrine is ratified truth. Graphiti is customer runtime relationships and belongs to Runtime, not Holdings. These never replace one another, and Platform AI and Holdings AI are separated at the deployment level.

The organization survives.

Any company, department, product, executive, manager, worker, operating system, or decision that cannot locate itself within these laws is out of scope or in error. They are the test every future operator applies to anything this document did not anticipate, and they are why this document is enough: the laws generate the answers the pages did not write. From this parent doctrine, everything else in AAF Holdings descends.

CANONICAL_00_AAF_Holdings_Operating_System_V1. The parent doctrine of AAF Holdings. The source from which the AAF Constitution, every canonical doctrine, every roadmap, and every implementation inherits. Amendable only by the CEO through the governance process. Governing until amended.

root · /srv/aaf