Skip to content

HANDOFF.md

Latest commit

 

History

History
99 lines (69 loc) · 4.89 KB

HANDOFF.md

File metadata and controls

99 lines (69 loc) · 4.89 KB
Raw

HANDOFF — what was built + how it works

Customer-facing build manifest. Customized for {CUSTOMER_NAME} on {BUILD_DATE}. This is your "what is this thing" reference.

Summary

  • Customer: {CUSTOMER_NAME}
  • Tier: {TIER} (Starter / Pro / Studio)
  • Archetype pack: {ARCHETYPE} (creator / founder / consultant / writer / generic)
  • Build start: {BUILD_START_DATE}
  • Build complete: {BUILD_COMPLETE_DATE}
  • Operator: {OPERATOR}
  • Engagement letter: signed {ENGAGEMENT_DATE}

What got built

Universal core (every Personal OS gets these)

  • Vault structure with pillars: identity / finances / content / network / journal / inbox / drafts / _archive / templates
  • Top-level files: home.md / todos.md / inbox.md / plan.md / north-star.md / principles.md / bets.md / network.md
  • Identity layer: adn.md (drafted from intake) / memory.md / relationships.md / wins.md / personal.md (gitignored)
  • Finance layer: revenue.md / burn.md / net-worth.md / payment-rails.md (templates filled with intake data where provided)
  • Content layer: voice.md / source-material.md / pipeline.md / posts/ / lead-magnets.md
  • Templates folder: daily / weekly / monthly / project / note scaffolds

Skill pack installed

  • .claude/commands/ — slash commands for daily/weekly/monthly rituals + capture + drafting + scaffolding + graph maintenance (full list in .claude/commands/_README.md)
  • .claude/agents/ — subagents for synthesis (os-synth), finances, network, body, content, graph (full list in .claude/agents/_README.md)
  • .claude/settings.json — permissions + autonomous-mode hooks

Conventions

  • .personal-os/architecture.md — 3-layer model (commands / pillar agents / synthesis agent)
  • .personal-os/linking-conventions.md — wikilink + canonical-anchor rules for vault graph
  • .personal-os/metadata-conventions.md — frontmatter schema per file type
  • .personal-os/graph-state.md — graph baseline (orphans, hubs, density)
  • .personal-os/growth-doctrine.md — your version of the 7 universal rules
  • .personal-os/log.md — append-only session memory

Archetype pack: {ARCHETYPE}

  • archetype-packs/{ARCHETYPE}/ — pillar bundle specific to your role
  • Archetype-specific slash commands (see archetype-packs/{ARCHETYPE}/pack-readme.md)
  • Archetype-specific agents (see archetype-packs/{ARCHETYPE}/pack-readme.md)
  • Pre-filled archetype pillars per intake answers

Customizations applied (from your intake)

{Operator fills this list per customer build — name, north-star draft, primary pillars, body-floor signals, principles starter set, archetype-specific tuning, etc.}

  • {fill}
  • {fill}

What was NOT built (out of scope per engagement letter)

  • Platform-specific algorithm coaching (Reels / YouTube SEO / TikTok / Instagram-specific growth)
  • Therapy / personal life coaching
  • Tax / legal / financial advisory
  • Ghostwriting on your behalf
  • Custom code beyond Claude Code subagents
  • Replacement of your actual creative output

Your perpetual license

You retain perpetual access to this vault — even if the orchestration retainer ends. Templates, agents, and slash commands stay yours to use. {OPERATOR} retains rights to the underlying architecture, agent prompts, and template patterns for use in future client engagements (per engagement letter §IP).

Next steps

  1. SETUP.md — install Obsidian + Claude Code + Git, fill [fill] markers (30 min, do this first)
  2. USAGE.md — daily / weekly / monthly mechanics
  3. PERSONAL-FIRST-WEEK.md — your 7-day onboarding plan
  4. docs/growth-doctrine.md — the 7 rules (re-read at every /sunday)
  5. Run /morning-journal first thing tomorrow — start the streak
  6. Schedule your Day 7 first /sunday call with your operator
  7. After 30 days of clean rituals: CUSTOMIZE.md — extend the system your way

Support cadence (per your tier)

  • Starter: monthly 30-min check-in / email-only async / 48hr response
  • Pro: bi-weekly 30-min sync / monthly content review / 24hr async response
  • Studio: weekly 30-min sync / custom builds on request / 4hr async response

Full SLAs in docs/support-slas.md. Refund terms in docs/refund-policy.md. Crisis triage available regardless of tier — message your operator if drift, breakdown, or pivot moment.

When something breaks

  • Claude Code not finding commands → confirm you're inside this directory; check .claude/settings.json permissions
  • Slash command behaves wrong → message your operator; commands iterate based on customer feedback
  • Agent advice feels off → flag in next sync; agents tune over time
  • Vault graph getting tangled → run /link-sweep weekly; if persistent, run /graph-review

Who built this

The Personal OS architecture was built and proven on a real operator before productisation. You're {CUSTOMER_NUMBER} in the Personal OS customer roster.

Built {BUILD_COMPLETE_DATE}. Last updated {BUILD_COMPLETE_DATE}.