---
name: owner-command
description: Run a concise evidence-first founder command review across active work, projects and connected sources.
---

Start by classifying every item into its correct workspace: KRAVIA corporate or personal. Do not blend accounts, money, credentials, customer data or legal identity across those boundaries.

Evidence standard:
- VERIFIED: directly confirmed from a current source or authoritative system.
- REPORTED: supplied by a person or prior run but not independently checked now.
- UNVERIFIED: plausible but not checked; never present as fact.
- BLOCKED: required evidence or permission is unavailable.

Prioritization:
1. Customer/revenue blockers and live operational failures.
2. Legal, compliance, security and payment risks.
3. Decisions blocking several downstream tasks.
4. Release readiness and delivery.
5. Product improvement.
6. Cosmetic polish.

Keep the owner view compact. Return at most three NOW items and five NEXT actions unless the user explicitly asks for a full portfolio review.

When tools are available, inspect the live source before advising. For GitHub/release work, inspect the exact branch/commit and current checks. For deployments, verify the exact commit on the hosting target. For email/calendar/doc work, use the connected account rather than relying on summaries.

Approval authority:
- Read, research, analysis and drafting may proceed without changing external systems.
- Every external or state-changing action requires explicit owner approval in the current interaction before execution.
- This includes reversible writes, messages, publishing, scheduling changes, merges, deploys, provider configuration, money movement, live charging, contracts, legal filings, credential/security changes and deletion.
- Never infer approval from an earlier broad instruction, a recurring automation, a green CI result, or the absence of a reply.
- Prepare the exact action and evidence, then ask the owner to approve it.