---
name: business-os-handoff
description: Maintain a lightweight business operating repository by reconciling current priorities, active work, evidence, next actions, and an optional data-driven dashboard. Use when Codex is asked to update a business handoff, align strategy documents after work ships, reconcile a dashboard with canonical state, or prepare the next operator or agent to continue without re-auditing the business.
---

# Business OS Handoff

Keep the canonical handoff and its glanceable dashboard aligned with evidence from the current session.

## Workflow

1. Read repository instructions completely. Treat the file they name as canonical as the source of truth.
2. Inspect the working tree before editing. Preserve unrelated and uncommitted changes.
3. Read the current handoff, dashboard data, active venture documents, recent decisions, and operating constraints that affect the request.
4. Separate facts into:
   - current focus;
   - operating products or commitments;
   - work in flight;
   - waiting or externally blocked work;
   - next actions;
   - completed work worth preserving as evidence.
5. Reconcile contradictions in favor of the newest verified evidence. Do not turn an unmeasured value into zero or an idea into an approved commitment.
6. Update the canonical handoff concisely. Preserve historical facts that still constrain current decisions.
7. If the repository has a generated or data-driven dashboard, edit only the content or state block allowed by its instructions. Keep its focus, queue, waiting items, shipped work, rules, and links consistent with the handoff.
8. Run the repository's smallest relevant validation, including a diff whitespace check. Review the final diff for accidental changes.
9. Report what changed, what remains uncommitted, and any external artifact that must be refreshed separately.

## Guardrails

- Keep strategy and operating context separate from application code.
- Prefer the smallest revenue-first next action over speculative product work.
- Preserve explicit approval gates for pricing, publishing, customer communication, production access, and destructive changes.
- Never claim that an email, deployment, sale, or measurement exists without direct evidence.
- Do not rewrite the full history when a focused state update is enough.
- Do not commit a dirty repository unless the user explicitly asks and the intended scope is clear.

## Completion check

The handoff should let a new operator answer, without another audit: What matters now? What is live? What is in flight? What is waiting? What happens next? What must not be done?