Back to the public landing page · Compatibility matrix · AI + MCP + API surfaces · Ecosystem map · Builder quickstart
Public use cases and share-ready assets
CortexPilot already has three public first-run cases. The goal here is to make them easier to discover, explain, and reuse as proof-first assets.
Release-proven first run
- news_digest: the official proof-oriented first public baseline
- topic_brief: a bounded topic brief with search-backed evidence, currently a public showcase path
- page_brief: a browser-backed brief over one URL, currently a public showcase path
Proof status by public case
| Case | Current proof state | What to inspect today |
|---|---|---|
| news_digest | Official release-proven first public baseline | healthy proof summary · single-run benchmark summary |
| topic_brief | Public showcase only; not yet equally release-proven | Treat as discovery/story surface until a dedicated healthy proof and benchmark bundle exists. |
| page_brief | Public showcase only; browser-backed path, not yet equally release-proven | Treat as discovery/story surface until a dedicated healthy proof and benchmark bundle exists. |
First run to proof to share
- Start one public pack
- Confirm it in Command Tower, Workflow Cases, and Proof & Replay
- Reuse the Workflow Case as a share-ready recap asset
Why this helps discovery
These use cases are not just examples for people who already know the product. They are also the easiest way to explain what CortexPilot does with AI workflow cases, read-only proof surfaces, and share-ready recap assets without jumping straight into the full operator UI.
Why share-ready Workflow Cases matter
The point is not just to export JSON. The point is to make a case easier to review, easier to circulate, and easier to compare without sending everyone back through the full operator UI.
Proof files you can inspect today
- Tracked healthy proof summary for
news_digest - Tracked single-run benchmark baseline for
news_digest - Demo-status ledger for healthy, degraded, and missing storefront assets
- Benchmark methodology and wording boundary
Current gaps that still matter
- The public healthy path is strongest for news_digest; the other two cases still need their own healthy proof and benchmark bundles.
- The current benchmark story is a tracked single-run baseline, not a broad release average.
- The next Wave 4 upgrades should add stronger share-ready recap assets without pretending the repo is already a hosted service.
Need the surrounding operator and builder story? Visit the compatibility matrix, the AI + MCP + API surface guide, the builder quickstart, or the ecosystem map.