Source: frameworks/advisory-os-file-architecture.md

Advisory OS File Architecture

Location: ~/advisory-os/ Lives at: ~/advisory-os/advisory-os-file-architecture.md

Full Directory Tree

~/advisory-os/
├── advisory-os-file-architecture.md
│
├── clients/
│   ├── _templates/
│   │   ├── reference-data/
│   │   ├── master-plan/
│   │   ├── constraints/
│   │   ├── projects/
│   │   ├── transcripts/
│   │   └── session-notes/
│   │
│   ├── ruben-crulliance/
│   │   ├── reference-data/
│   │   ├── master-plan/
│   │   ├── constraints/
│   │   ├── projects/
│   │   │   └── accounting-manager-os/
│   │   │       ├── project-plan/
│   │   │       ├── blueprint/
│   │   │       ├── builds/
│   │   │       └── deployment/
│   │   ├── transcripts/
│   │   └── session-notes/
│   │
│   └── rob-foncannon/
│       └── [same structure]
│
├── business/
│   ├── finance/
│   │   ├── invoicing/
│   │   ├── expenses/
│   │   ├── pricing/
│   │   ├── tax/
│   │   └── revenue-tracking/
│   │
│   ├── hr-people/
│   │   ├── contractors/
│   │   └── collaboration-agreements/
│   │
│   ├── marketing/
│   │   ├── campaigns/
│   │   ├── content-drafts/
│   │   ├── published/
│   │   └── evergreen/
│   │
│   ├── operations/
│   │   ├── internal-sops/
│   │   ├── legal/
│   │   ├── contracts/
│   │   ├── subscriptions/
│   │   └── vendors/
│   │
│   ├── product-innovation/
│   │   ├── advisory-os-methodology/
│   │   ├── service-lines/
│   │   └── offerings/
│   │
│   ├── sales/
│   │   ├── prospects/
│   │   ├── proposals/
│   │   ├── mini-sites/
│   │   ├── outreach/
│   │   └── pipeline-reports/
│   │
│   └── strategy/
│       ├── annual-plan/
│       ├── goals/
│       ├── positioning/
│       └── vision/
│
├── calls/
│   ├── tpc/
│   └── client-sessions/
│
├── tools/
│   ├── cadence/
│   ├── rapport/
│   ├── client-portal/
│   ├── interview-agent/
│   └── writing-partner/
│
└── frameworks/
    ├── 00-START-HERE.md
    │
    ├── maturity-model/
    │
    ├── constraint-priority-matrix/
    │   └── constraint-priority-matrix-instructions.md
    │
    ├── master-plan-system/
    │   ├── client-delivery-system-instructions.md
    │   ├── 01-context.md
    │   ├── 02-example-client-master-plan.html
    │   └── 03-quality.md
    │
    ├── project-plan-system/
    │   ├── build-design-agent-instructions.md
    │   ├── build-design-agent-upload-checklist.md
    │   ├── 01-example-project-plan.html
    │   └── 02-example-client-blueprint.html
    │
    ├── campaign-system/
    │   ├── campaign-system-instructions.md
    │   ├── 01-orientation.md
    │   ├── 02-context.md
    │   ├── 03-example-campaign-map.html
    │   ├── 03-example-distribution-map.html
    │   ├── 03-example-campaign-content.html
    │   ├── 03-example-briefing-flow.html
    │   └── 04-quality.md
    │
    └── deployment-cycle/
        └── qc-agent-instructions.md

Quick Reference

Area	Purpose
clients/	One folder per client. `_templates/` for new client setup. All clients regardless of engagement type.
business/	Seven business functions: finance, hr-people, marketing, operations, product-innovation, sales, strategy
calls/	Group calls (TPC) and one-to-one client sessions
tools/	App development — specs, build guides, code references
frameworks/	Advisory OS intellectual property — methodology docs, agent instructions, golden examples

Client Folder Structure

Every client gets the same base folders. Projects are added as initiatives are scoped.

Folder	What lives here
reference-data/	Canonical proper nouns, team roster, tools. Shared across all agents.
master-plan/	Client Master Plan (advisor-only) and Client Roadmap (client-facing)
constraints/	Constraint briefs (client input) and priority matrix outputs (advisor analysis)
projects/[initiative]/	One subfolder per initiative with: project-plan, blueprint, builds, deployment
transcripts/	Session recordings and transcripts
session-notes/	Extraction agent outputs, session summaries, prep notes

New Client Setup

cp -r ~/advisory-os/clients/_templates ~/advisory-os/clients/new-client-name

Template and instructions files live at _templates/ root level. They do not copy into client folders — only the empty subfolders copy.

Document Types

Per-Client Documents

Document	Scope	Who sees it	Where it lives
Client Master Plan	Whole client, forever	Advisor only	`clients/[name]/master-plan/`
Client Roadmap	Whole engagement arc	Client + Advisor	`clients/[name]/master-plan/`
Project Plan	One initiative, beginning to end	Advisor only	`clients/[name]/projects/[initiative]/project-plan/`
Client Blueprint	One initiative	Client + Advisor	`clients/[name]/projects/[initiative]/blueprint/`

Supporting Documents

Document	What it is	Where it lives
Client Reference Data	Canonical proper nouns, team roster, tools. Shared across all agents.	`clients/[name]/reference-data/`
Constraint Priority Matrix	Diagnostic output — constraints typed, tiered, patterned	`clients/[name]/constraints/`
Deployment Plan	Raw Build Design Agent output — feeds the Project Plan	`clients/[name]/projects/[initiative]/deployment/`
Build deliverables	SOPs, templates, checklists, snapshots — the actual things that get implemented	`clients/[name]/projects/[initiative]/builds/`

Where Files Go

What you're creating	Where it goes
Client reference data (proper nouns, team, tools)	`clients/[name]/reference-data/`
Client Master Plan (HTML card)	`clients/[name]/master-plan/`
Client Roadmap (engagement-level, client-facing)	`clients/[name]/master-plan/`
Constraint brief or matrix output	`clients/[name]/constraints/`
Deployment plan (Build Design Agent output)	`clients/[name]/projects/[initiative]/deployment/`
Project Plan (advisor-only execution card)	`clients/[name]/projects/[initiative]/project-plan/`
Client Blueprint (client-facing initiative view)	`clients/[name]/projects/[initiative]/blueprint/`
Build deliverable (SOP, template, checklist, snapshot)	`clients/[name]/projects/[initiative]/builds/`
Session transcript	`clients/[name]/transcripts/`
Session extraction or prep notes	`clients/[name]/session-notes/`
Prospect research or vetting	`business/sales/prospects/`
Proposal document	`business/sales/proposals/`
Marketing campaign assets	`business/marketing/campaigns/[campaign-name]/`
Finished evergreen content	`business/marketing/evergreen/`
Internal SOP for my own business	`business/operations/internal-sops/`
Advisory OS methodology docs	`business/product-innovation/advisory-os-methodology/`
Framework documentation (maturity model, matrix, etc.)	`frameworks/[framework-name]/`
Agent project instructions	`frameworks/[framework-name]/`
App build guides or specs	`tools/[tool-name]/`
Group call recaps	`calls/[call-type]/`

File Naming Convention

All files: lowercase, hyphens, no spaces, no version numbers.

Instruction Files

[system-name]-instructions.md

These get pasted into the Claude project instructions field. They never have numbers. If a file ends in -instructions.md, it goes in the project instructions field.

Upload/Context Files (numbered)

01-context.md
02-example-client-master-plan.html
03-quality.md

Numbers set the reading order. These are uploaded as project knowledge files.

Client Files

[client-name]-[document-type].md
[client-name]-[document-type]-[mon-yyyy].html    (deliverables)
[client-name]-[document-type]-[yyyy-mm-dd].md    (daily working files)

Client name always comes first. Canonical files (reference data, master plan) have no date — they're updated in place.

Examples:

ruben-reference-data.md (canonical, no date)
rob-foncannon-reference-data.md (canonical, no date)
ruben-constraint-priority-matrix-2026-02-10.md (daily working file)
ruben-master-plan-feb-2026.html (deliverable)