|
3 | 3 | "scenes": [ |
4 | 4 | { |
5 | 5 | "id": "s01_hook", |
6 | | - "vo": "An AI agent is about to build on Postgres — a decision this team reversed months ago. But first, it checks Settled. Superseded, Settled says — it's Aurora now, here's the proof. The agent fixes itself, before it ships the mistake. That's Settled: the decision layer your people, and your agents, check before they act." |
| 6 | + "vo": "An AI agent is about to build on Postgres. Problem is, this team moved off Postgres months ago. So before it writes a line, it asks Settled, and hears back: that's superseded, you're on Aurora now, here's where it was decided. It rewrites its own code before the mistake ships. That's Settled. The thing your team and your agents check before acting on a decision." |
7 | 7 | }, |
8 | 8 | { |
9 | 9 | "id": "s02_problem", |
10 | | - "vo": "It starts simple. A team picks Postgres, then Mongo, then settles on Aurora. The thread scrolls away — and now the latest decision is buried." |
| 10 | + "vo": "This is how it usually goes. A team picks Postgres, switches to Mongo, then lands on Aurora. A few weeks later the thread's buried, and nobody can say for sure which call still stands." |
11 | 11 | }, |
12 | 12 | { |
13 | 13 | "id": "s03_split", |
14 | | - "vo": "Same conversation, two teams. Without Settled, an engineer rebuilds on Postgres weeks later: a decision that was already reversed, and nobody can find. Three days, lost. With Settled, the agent checks what's binding first, and ships it right the first time." |
| 14 | + "vo": "Same thread, two teams. One engineer rebuilds on Postgres a month later, on a decision that was already reversed and that nobody can find. Three days gone. The other team's agent checks what's binding first, and gets it right the first time." |
15 | 15 | }, |
16 | 16 | { |
17 | 17 | "id": "s04_capture", |
18 | | - "vo": "Here's the real product. Settled watches every channel. When a decision lands, it catches it — with a confidence score — and asks a human to confirm." |
| 18 | + "vo": "So here's how it works. Settled reads every channel, and when a real decision lands, it flags it with a confidence score and asks a human to confirm." |
19 | 19 | }, |
20 | 20 | { |
21 | 21 | "id": "s05_ratify", |
22 | | - "vo": "One check mark settles it. The human stays in the loop — that's the feature, not a workaround." |
| 22 | + "vo": "One check mark and it's settled. A person always signs off. That's the whole point." |
23 | 23 | }, |
24 | 24 | { |
25 | 25 | "id": "s06_contested", |
26 | | - "vo": "And when it's still contested — Okta versus Auth0 — Settled says so. Nothing is binding until a human ratifies it." |
| 26 | + "vo": "And when it's still up in the air, Okta or Auth0, Settled says so. Nothing's binding until a human ratifies it." |
27 | 27 | }, |
28 | 28 | { |
29 | 29 | "id": "s07_lifecycle", |
30 | | - "vo": "Every decision carries a status. Proposed, contested, settled, superseded. Each anchored to the exact words and a permalink." |
| 30 | + "vo": "Every decision has a status: proposed, contested, settled, superseded. Each one pinned to the exact words that were said, and a link straight to them." |
31 | 31 | }, |
32 | 32 | { |
33 | 33 | "id": "s08_assistant", |
34 | | - "vo": "Anyone can just ask. Settled answers from the ledger — only what was actually decided, with the source attached." |
| 34 | + "vo": "You can just ask. Settled answers from the ledger, only what the team actually decided, and it shows its source." |
35 | 35 | }, |
36 | 36 | { |
37 | 37 | "id": "s09_query", |
38 | | - "vo": "Or run slash settled on any topic. The current binding decision, and its full history, right inside Slack." |
| 38 | + "vo": "Or run slash settled on anything. You get the current call and the full history behind it, right there in Slack." |
39 | 39 | }, |
40 | 40 | { |
41 | 41 | "id": "s10_apphome", |
42 | | - "vo": "The home tab is the whole ledger at a glance. Settled, contested, and what's still waiting on a human." |
| 42 | + "vo": "The home tab puts the whole ledger in one place. What's settled, what's still being argued, what's waiting on a human." |
43 | 43 | }, |
44 | 44 | { |
45 | 45 | "id": "s11_difference", |
46 | | - "vo": "So here's what makes Settled different. Every other tool logs a decision for a person to read later. Settled is the one an agent can ask — before it acts — is this still binding?" |
| 46 | + "vo": "This is the part other tools miss. They log a decision for a person to read later. Settled is the one an agent can ask, before it acts, whether it still stands." |
47 | 47 | }, |
48 | 48 | { |
49 | 49 | "id": "s12_mcp", |
50 | | - "vo": "Through its own MCP server, any agent — Claude, an I D E bot, your C I — checks Settled first. The one about to build on an old decision is stopped, and handed the one that still holds." |
| 50 | + "vo": "It runs its own MCP server, so any agent, Claude, an I D E bot, your C I, can check first. The one about to build on a stale decision gets stopped and handed the one that still holds." |
51 | 51 | }, |
52 | 52 | { |
53 | 53 | "id": "s13_close", |
54 | | - "vo": "Other tools remember what was said. Settled makes sure what was decided still holds — for the people, and the agents, working in Slack." |
| 54 | + "vo": "Other tools remember what was said. Settled keeps track of what was decided, and whether it still holds, for everyone working in Slack, people and agents alike." |
55 | 55 | } |
56 | 56 | ] |
57 | 57 | } |
0 commit comments