# Output + Integration — the doc, the one-pager, and feeding the OS

Two deliverables, always. The **markdown doc** is the full holistic record (and the human-readable one-pager). The **living dashboard** is the working surface the alignment meetings read. Build both.

---

## Deliverable 1 — The Vision Document (`.md`)

Write to `/mnt/user-data/outputs/Vision-Document-YYYY.md` and `present_files` it. Lead with a distilled **one-pager** (the part meant for fast consumption + sharing with a team), then the **full doc** below it. Mirror the standard structure. Use the person's chosen format (bullets vs Vivid Vision) for the level content.

```markdown
# Vision Document — [Name] — [Year]

> **[Purpose Statement — the one line everything ladders up to]**

---

## ◇ The One-Pager   _(distilled — for fast reference + team)_

**Purpose:** [one line]

**Polaris cascade**
- 🌐 10-Year: [1–2 line distillation]
- 🌐 3-Year: [1–2 line distillation]
- 🔥 12-Month: [the 2–3 headline goals]

**This Quarter**
- KPIs: [the 3–4 headline numbers + targets]
- Projects: [the 3–6 project names]

**This Month:** [the month's headline goals]

---

## 🌱 Seed of Life — the life vision
_(one line per area — the broad agenda)_
- **Health:** …
- **Social:** …
- **Family:** …
- **Finance:** …
- **Career:** …
- **Intellect:** …
- **Intimacy:** …
- _(Spiritual: …)_

## 🌞 10-Year Master Plan — [date set]
- …

## 🌐 3-Year Vision — [date set]
- …

## 🔥 12-Month Goals — [year]
### Personal
- [ ] …
### Business
- [ ] …

## 📅 Monthly Goals — [month]
- [ ] …  _(each ladders to a 12-month goal)_

## 📊 Quarterly Business KPIs — [Q# year]
| KPI | Target | Current |
|---|---|---|
| … | … | … |

## Quarterly Projects — [Q# year]
### [Project name] — [status]
- **Ladders to:** [goal/KPI]
- **Done =** [observable outcome]
- **Owner:** … · **Metric:** …

### Quarterly Personal Projects
- [ ] …

---
*Set: [date] · This is a living document — reviewed weekly, updated monthly/quarterly, rebuilt yearly.*
```

If they chose **Vivid Vision** for a level, write that level as flowing present-tense prose (where they are, what the day feels like, who's there, what the work looks like) instead of bullets — keep the lower execution levels (12-month, monthly, KPIs, projects) as bullets/tables regardless, because those have to be checkable.

---

## Deliverable 2 — The living Vision Document dashboard

This is what makes the vision *operational* — the alignment skills read it. Copy `assets/vision-doc-dashboard.html` to `/mnt/user-data/outputs/` and `present_files` it.

**Then seed it with THEIR content — this is the key step.** The dashboard template ships with empty seeds. Fill them with what you just extracted, or the alignment meetings will read placeholders instead of the real vision.

The dashboard persists three things under storage key **`sfb:vision:v1`**:
- **cascade** — `{hundred, twentyfive, three, twelve}`, each `{txt, status}`. Map the person's ladder onto whichever levels they reached (10-Year sits naturally in the `twentyfive`/long slot or relabel in the doc; use `three` for the 3-Year and `twelve` for the 12-Month headline). Status is `on` / `reset` / `off`.
- **goals** — array of `{id, text, target, current, unit}`. Put the 12-month goals here (both personal + business), with a number + unit wherever one fits, so the pace bars work.
- `rocks` — array of `{id, name, why, dod, owner, metric, status}`. Put the quarterly projects here.

**How to seed it:** the dashboard clears its template seed the moment its data is edited. The clean way is to tell the user to do a one-time wipe-and-fill, OR — more reliably — instruct them in one line that the dashboard is pre-filled with a template and to edit each level/goal/project to their own via the on-card edit buttons. If you want to pre-load their content programmatically, the storage key and JSON shape above are the contract; keep the key identical so it stays the *same* living doc the alignment skills use. Do **not** change the dashboard's schema or key — that's what keeps the whole OS in sync.

> Note: the dashboard intentionally holds only cascade + 12-month goals + projects (it's the alignment working surface). The **Purpose Statement, the Seed-of-Life personal lines, the Monthly Goals, and the Quarterly KPIs live in the markdown doc.** That split mirrors the real workflow: the deep doc is the full vision, the dashboard is the live execution surface.

---

## How it feeds the alignment Operating System

Once seeded, the vision is the shared source of truth at the top of the OS. Same dashboard, same `sfb:vision:v1` key, read by every cadence:

- **Weekly Alignment → Mission Review:** opens this dashboard, orients on the cascade ("still pointing the right way?"), updates current numbers on the goals, and asks "does this week's work ladder up to the projects?" The weekly doesn't *set* vision — it checks alignment to it.
- **Monthly Alignment:** sets new monthly goals against the 12-month goals; tracks quarter-to-date pace.
- **Quarterly Alignment:** the deep rebuild — grades the projects, edits the Polaris cascade, commits new projects, resets goals. This is where the vision doc gets its quarterly overhaul.

So the work compounds: the vision set here is the vision the weekly references and the quarterly rebuilds — never a disconnected copy.

---

## Auto-file the snapshot (optional)

Offer once at the end: *"Want me to file this to your Drive Operations folder so your meetings can pull it?"* On yes, use the Google Drive MCP (`tool_search` → `Google Drive:create_file`) to write the `.md` straight into the Operations folder, and confirm in one line with the link. Future alignment meetings retrieve it via Drive search.

Project knowledge is the one thing that can't be automated (UI-only). Mention it only if they specifically want the vision in-context for the AI; otherwise Drive auto-save + the living dashboard cover compounding. If they're not using Drive, skip that step — the markdown download + the dashboard are the deliverables.

---

## Future build (don't build unless asked)
The living-documents roadmap already lists a **Seed of Life dashboard** (`sfb:sol:v1`) as the next asset to build. A natural enhancement for this skill later: a Purpose banner + Monthly Goals section on the vision dashboard, and wiring the SOL dashboard so the *personal* side of the vision is as live as the business side. Out of scope for the build itself — note it as a one-liner.
