capx-ai/casa/casa-pulse

casa-pulse

The recap craft. A recurring, read-only snapshot of the company over a window, saved so the entries form a timeline. It never changes state; it reports.

Steps

1. If company-brain/profile.json does not exist, tell the founder to run /casa-start

first and stop.

1. Set the window. Default 7d unless the user names one (24h, 30d). Read

company-brain/NOW.md, build-map.json, state.json, finance/receipts.jsonl, experiments.jsonl, and the latest decisions/. Pull live numbers from any connected analytics or billing source (read-only; integrate, do not vendor).

1. Read the company side. Over the window: progress (playbooks completed, level

change), settled spend recorded in finance/receipts.jsonl, the key product and customer metrics, and any experiment that closed. Use the actionable metric, not the cumulative total.

1. Read the on-chain side if the company has one. If the company has a token or on-chain

layer, include its signals (trading volume, fees, holders) alongside the company metrics, so both are visible in one read. Skip this entirely for companies without one.

1. Flag what needs attention. Anomalies, stalls (a node ready but untouched for the

window), loops overdue, and any guardrail metric moving the wrong way.

1. Save the entry. Write a dated pulse to company-brain/pulse/<date>.md so the

entries build a timeline. Do not edit any other state. End with the one thing to do next (and hand to casa-priority if the founder wants the full re-evaluation).

Rules

• Read-only. The pulse reports; it never completes a node, marks a loop, or changes a

decision.

• Actionable metrics over vanity. Every rate names its window.
• If the company has an on-chain layer, show its signals alongside the company metrics.
• No em-dashes, no emojis.