An AiOS has 8 layers.

Tier 1 — Foundation rules

One file at the root of my machine that loads at the start of every session.

~/.claude/CLAUDE.md · loads first, every time.

• Global operating manual

  The root rules file. Loads at the start of every session and pulls in the knowledge files via @file imports.

Tier 2 — Persistent memory

A short rules cache that survives across sessions, so corrections never get lost between conversations.

Re-injected on every session start.

• Memory index

  Auto-loaded memory index. Persists across sessions.

• Lessons cache

  Short-rule extract for runtime. Re-injected on every session start so corrections never get lost.

Tier 3 — Home router

The entry point at my Desktop home folder — it routes the work into the right venture.

Reads the request, picks the lane.

• Home root router

  Entry point at the home directory. Routes work to the right venture folder.

Tier 4 — Knowledge files

The knowledge files holding my priorities, profile, people, lessons, frameworks — auto-loaded into every session.

One operator brain, always loaded.

• Architecture references

  Synthesis of community architecture references. Planning ground truth.

• Voice scaffolding

  Multi-surface voice scaffolding. Read before any external content draft.

• Live priority cache

  Daily priority cache. Updated at end-of-day. Holds what's hot today, never stale.

• Data classification + PII scan

  Data classification + PII scan rules. Required read before any external service call.

• Debug playbook

  Enumerated failure modes plus an escalation tier and incidents log.

• Frameworks

  Mental models, decision patterns, and hard-won frameworks. Read on-trigger when one applies to the current decision.

• Topic index

  Topic to file map. Hand-rolled retrieval layer until vector search lands.

• Corrections log

  Full corrections log. Every correction the operator gives gets logged here, then collapsed into the lessons cache.

• Lessons archive

  Deprecated rules. Kept for history, never deleted.

• Relationship map

  Relationship map with collision rules and firewall flags. Read on-trigger when a request involves a named person.

• Operator profile

  Condensed identity file: voice, frameworks, current focus. Loaded every session.

• Agent roster

  Single source of truth for the agent inventory. Never hardcoded elsewhere.

Tier 5 — Project context files

One file inside each business folder — JFly.Ai, Real Estate, Finances — that adds the rules for that venture.

Loads when work moves into the folder.

• Events business context

  Events business context file.

• Finance context

  Finance context file. Defaults to a propose-only autonomy tier — the agent never moves money on its own.

• Brand + product layer

  Customer-facing brand and product context. Routes to brand, consulting, and live-site sub-folders.

• Real estate context

  Real estate context file. Property portfolio operating notes.

• Tax context

  Entity tax document context.

Tier 6 — Agents

One Chief of Staff today. Agents earn their spot — more spin up when the work genuinely splits.

Earned, not assumed.

• Finance Director

  Spins up when finance questions exceed what the Chief of Staff can carry.

  planned

• Content Director

  Spins up the first time the Chief of Staff produces flat content three times in a row.

  planned

• Chief of Staff

  The Day-1 agent. Plays every director role directly until real pain triggers a spin-up.

• Events / Ops / BD Directors

  Spin up on real pain — per the agent roster.

  planned

• Real Estate Director

  Spins up during an active transaction or when tenant issues stack up.

  planned

• Research Director

  Spins up when research routinely exceeds 30 minutes through the Chief of Staff.

  planned

Tier 7 — Hooks, output styles, skills

The hooks that fire on session events, plus the skills and styles the agent uses to actually do the work.

The agent's tool palette and triggers.

• Session-start hook

  Fires on startup, resume, clear, and compact. Re-injects key state so context never silently drops.

• Skills library

  Installed skills library — the agent's tool palette for routine work.

• Executive brief style

  Default response style. Short. Headlines first. Plain English.

• Research style

  Research output style. Lead with the answer. Cite or flag the gap.

Tier 8 — External memory

NotebookLM notebooks holding the long-term context — the brain that doesn't fit inside any one chat.

Where the system remembers across years.

• Context brain

  External long-term context store. Full operator context.

• System guide

  External notebook covering the system architecture reference.

• Domain notebooks

  Additional domain-specific notebooks in the external memory layer.

• Tool stack

  External notebook for the tool stack and system map.

• Vector retrieval

  Vector retrieval. Replaces the hand-rolled topic index as primary retrieval.

  planned

Schematic complete

This is eleven phases of my own work, in front of you.

The faster path is me at your desk for an afternoon — same machine you actually use, same files you actually work on.