-
Notifications
You must be signed in to change notification settings - Fork 29
Expand file tree
/
Copy pathindex.html
More file actions
391 lines (354 loc) · 14.4 KB
/
index.html
File metadata and controls
391 lines (354 loc) · 14.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>CortexPilot | First proven workflow and public proof pack</title>
<meta
name="description"
content="CortexPilot's first proven workflow: the news_digest public baseline, its proof pack, and the shortest proof-first loop before deeper adoption."
/>
<link rel="canonical" href="https://xiaojiou176-open.github.io/CortexPilot-public/use-cases/" />
<meta property="og:title" content="CortexPilot | First proven workflow and public proof pack" />
<meta
property="og:description"
content="The first proven workflow, proof pack, benchmark summary, and Workflow Case recap for CortexPilot."
/>
<meta property="og:url" content="https://xiaojiou176-open.github.io/CortexPilot-public/use-cases/" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:title" content="CortexPilot | First proven workflow and public proof pack" />
<meta
name="twitter:description"
content="The first proven workflow, proof pack, benchmark summary, and Workflow Case recap for CortexPilot."
/>
<style>
:root {
--bg: #f4efe7;
--paper: rgba(255, 251, 244, 0.92);
--ink: #17232c;
--muted: #536673;
--accent: #9f4c26;
--accent-dark: #244157;
--line: #d8ccbb;
--success: #215f48;
--warn: #8d5319;
}
* { box-sizing: border-box; }
body {
margin: 0;
font: 16px/1.65 "Trebuchet MS", Verdana, sans-serif;
color: var(--ink);
background:
radial-gradient(circle at 12% 12%, rgba(203, 115, 73, 0.16), transparent 22%),
radial-gradient(circle at 88% 8%, rgba(36, 65, 87, 0.14), transparent 18%),
linear-gradient(180deg, #f7f2ea 0%, #efe6d8 100%);
}
main {
max-width: 1040px;
margin: 0 auto;
padding: 48px 20px 88px;
}
a {
color: var(--accent-dark);
text-underline-offset: 2px;
}
.mini-nav {
display: flex;
flex-wrap: wrap;
gap: 12px;
margin-bottom: 18px;
}
.eyebrow {
display: inline-block;
margin-bottom: 14px;
padding: 8px 14px;
border-radius: 999px;
background: rgba(36, 65, 87, 0.08);
color: var(--accent-dark);
font-size: 14px;
font-weight: 700;
}
.hero,
.panel,
.callout {
background: var(--paper);
border: 1px solid var(--line);
border-radius: 24px;
}
.hero {
padding: 28px;
}
.panel,
.callout {
padding: 22px;
margin-top: 24px;
}
h1,
h2 {
font-family: Georgia, "Times New Roman", serif;
line-height: 1.1;
}
h1 {
margin: 0 0 16px;
font-size: clamp(38px, 6vw, 60px);
}
h2 {
margin: 40px 0 14px;
font-size: 30px;
}
.lede {
color: var(--muted);
font-size: clamp(19px, 2.2vw, 24px);
margin: 0 0 14px;
}
.caption {
color: var(--muted);
margin: 10px 0 0;
}
.grid {
display: grid;
gap: 16px;
grid-template-columns: repeat(auto-fit, minmax(220px, 1fr));
}
.card {
background: var(--paper);
border: 1px solid var(--line);
border-radius: 22px;
padding: 18px;
}
.card h3 {
margin-top: 0;
margin-bottom: 10px;
font-size: 19px;
}
.badge {
display: inline-block;
margin-bottom: 10px;
padding: 5px 10px;
border-radius: 999px;
font-size: 12px;
font-weight: 700;
letter-spacing: 0.02em;
}
.badge.success {
background: rgba(33, 95, 72, 0.12);
color: var(--success);
}
.badge.warn {
background: rgba(141, 83, 25, 0.12);
color: var(--warn);
}
table {
width: 100%;
border-collapse: collapse;
margin-top: 14px;
background: rgba(255, 255, 255, 0.55);
border-radius: 18px;
overflow: hidden;
}
th,
td {
text-align: left;
padding: 10px;
border-bottom: 1px solid #ece4d9;
vertical-align: top;
}
th {
background: rgba(36, 65, 87, 0.06);
}
tr:last-child td {
border-bottom: none;
}
code {
background: rgba(36, 65, 87, 0.08);
border-radius: 6px;
padding: 2px 6px;
font-family: "SFMono-Regular", Menlo, monospace;
}
ul,
ol {
padding-left: 22px;
}
</style>
</head>
<body>
<main>
<nav class="mini-nav" aria-label="Top navigation">
<a href="../">Back to the public landing page</a>
· <a href="../compatibility/">Compatibility matrix</a>
· <a href="../ai-surfaces/">AI + MCP + API surfaces</a>
· <a href="../ecosystem/">Ecosystem map</a>
· <a href="../builders/">Builder quickstart</a>
</nav>
<section class="hero">
<span class="eyebrow">The public proof-first entrypoint</span>
<h1>First proven workflow and public proof pack</h1>
<p class="lede">
Start here if you want the shortest honest CortexPilot story.
<strong>What can I run, inspect, and trust today before I dive into
the deeper protocol and builder surfaces?</strong>
</p>
<p class="caption">
The answer is still: start with <strong>news_digest</strong>. It is the
only official release-proven public baseline. <code>topic_brief</code> and
<code>page_brief</code> stay useful, but they remain showcase expansions
until they each have their own healthy proof and benchmark bundles.
</p>
</section>
<h2>The 10-minute proof-first loop</h2>
<ol>
<li>Start one `news_digest` run from the PM surface.</li>
<li>Watch it show up in Command Tower and confirm the Workflow Case exists.</li>
<li>Open Proof & Replay and inspect the result before trusting it.</li>
<li>Reuse the Workflow Case recap as the share-ready proof asset.</li>
</ol>
<p>
If you arrived here from the
<a href="../agent-starters/">agent starter kits</a>,
this page is the post-install proof target. In plain English: do not
assume the starter file already proved a real integration. Come back
here and make sure the same proof pack still holds.
</p>
<h2>What success should look like</h2>
<div class="grid">
<article class="card">
<span class="badge success">Visible run</span>
<h3>It shows up in the product</h3>
<p>One task exists in PM and one Workflow Case exists for that run. You are not relying on a shell success line alone.</p>
</article>
<article class="card">
<span class="badge success">Reviewable proof</span>
<h3>You can inspect what happened</h3>
<p>You can open proof, replay, and recap artifacts without guessing where they went or whether the run is real.</p>
</article>
<article class="card">
<span class="badge success">Honest boundary</span>
<h3>You know what is proven</h3>
<p>You can clearly explain why <strong>news_digest</strong> is proven today and why the other two paths are not yet equivalent.</p>
</article>
</div>
<h2>Proof status by public case</h2>
<table>
<thead>
<tr>
<th>Case</th>
<th>Current proof state</th>
<th>What to inspect today</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>news_digest</strong></td>
<td>Official release-proven first public baseline</td>
<td>
<a href="../releases/assets/news-digest-healthy-proof-2026-03-27.md">healthy proof summary</a>
·
<a href="../releases/assets/news-digest-benchmark-summary-2026-03-27.md">single-run benchmark summary</a>
</td>
</tr>
<tr>
<td><strong>topic_brief</strong></td>
<td>Public showcase only; not yet equally release-proven</td>
<td>Treat as discovery/story surface until a dedicated healthy proof and benchmark bundle exists.</td>
</tr>
<tr>
<td><strong>page_brief</strong></td>
<td>Public showcase only; browser-backed path, not yet equally release-proven</td>
<td>Treat as discovery/story surface until a dedicated healthy proof and benchmark bundle exists.</td>
</tr>
</tbody>
</table>
<h2>The proof pack for <code>news_digest</code></h2>
<div class="callout">
This is the smallest reusable trust bundle on the public surface today:
one healthy proof summary, one single-run benchmark, one Workflow Case
recap, and one storefront status ledger that says what is still missing.
</div>
<table>
<thead>
<tr>
<th>Artifact</th>
<th>Why it matters</th>
<th>Open now</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Healthy proof summary</strong></td>
<td>Shows the tracked healthy result path for the official public baseline.</td>
<td><a href="../releases/assets/news-digest-healthy-proof-2026-03-27.md">Open proof summary</a></td>
</tr>
<tr>
<td><strong>Single-run benchmark summary</strong></td>
<td>Shows the current public performance baseline without pretending it is a broad benchmark campaign.</td>
<td><a href="../releases/assets/news-digest-benchmark-summary-2026-03-27.md">Open benchmark summary</a></td>
</tr>
<tr>
<td><strong>Workflow Case recap</strong></td>
<td>Shows the strongest share-ready artifact for why Workflow Cases matter outside the operator UI.</td>
<td><a href="../releases/assets/news-digest-workflow-case-recap-2026-03-27.md">Open recap asset</a></td>
</tr>
<tr>
<td><strong>Proof-pack manifest</strong></td>
<td>Shows the machine-readable directory of what is in the public trust bundle today and what is still missing.</td>
<td><a href="../releases/assets/news-digest-proof-pack-2026-03-27.json">Open proof-pack manifest</a></td>
</tr>
<tr>
<td><strong>Global proof-pack index</strong></td>
<td>Shows the storefront-wide index of proven bundles, showcase bundles, and current public proof gaps.</td>
<td><a href="../assets/storefront/proof-pack-index.json">Open proof-pack index</a></td>
</tr>
<tr>
<td><strong>Demo-status ledger</strong></td>
<td>Shows which storefront captures are healthy, degraded, missing, or still only explanation assets.</td>
<td><a href="../assets/storefront/demo-status.md">Open demo-status ledger</a></td>
</tr>
</tbody>
</table>
<h2>Why this helps discovery</h2>
<p>
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.
</p>
<h2>Why share-ready Workflow Cases matter</h2>
<p>
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.
</p>
<h2>Proof files you can inspect today</h2>
<ul>
<li><a href="../releases/assets/news-digest-healthy-proof-2026-03-27.md">Tracked healthy proof summary for <code>news_digest</code></a></li>
<li><a href="../releases/assets/news-digest-benchmark-summary-2026-03-27.md">Tracked single-run benchmark baseline for <code>news_digest</code></a></li>
<li><a href="../releases/assets/news-digest-workflow-case-recap-2026-03-27.md">Tracked Workflow Case recap asset for <code>news_digest</code></a></li>
<li><a href="../releases/assets/news-digest-proof-pack-2026-03-27.json">Machine-readable proof-pack manifest for <code>news_digest</code></a></li>
<li><a href="../assets/storefront/proof-pack-index.json">Global proof-pack index across public proven and showcase bundles</a></li>
<li><a href="../assets/storefront/live-capture-requirements.json">Machine-readable live-capture contract for the tracked healthy GIF and English-first public capture set</a></li>
<li><a href="../assets/storefront/demo-status.md">Demo-status ledger for healthy, degraded, and missing storefront assets</a></li>
<li><a href="../assets/storefront/benchmark-methodology.md">Benchmark methodology and wording boundary</a></li>
</ul>
<h2>Current gaps that still matter</h2>
<ul>
<li>The public healthy path is strongest for <strong>news_digest</strong>; the other two cases still need their own healthy proof and benchmark bundles.</li>
<li>The current benchmark story is a tracked single-run baseline, not a broad release average.</li>
<li>The current recap story now has one tracked <strong>news_digest</strong> Workflow Case asset, tracked healthy local captures and proof assets, and one remaining broader benchmark gap.</li>
</ul>
<h2>What we still do not claim</h2>
<ul>
<li>We do not claim that <strong>topic_brief</strong> or <strong>page_brief</strong> are equally release-proven yet.</li>
<li>We do not claim that a storyboard or degraded local capture counts as healthy end-to-end proof.</li>
<li>We do not claim that the current benchmark file is a broad multi-run release average.</li>
</ul>
<p>
Need the surrounding operator and builder story? Visit the
<a href="../compatibility/">compatibility matrix</a>, the
<a href="../ai-surfaces/">AI + MCP + API surface guide</a>, the
<a href="../builders/">builder quickstart</a>, or the
<a href="../ecosystem/">ecosystem map</a>.
</p>
</main>
</body>
</html>