Phase 1 Pages
To close: Write the Outcome (17/17, cloud run, v2 pass) · Note the pages moved into qdash via c90 and c92 · Move to HISTORY.md
last activity Sep 8
Phase 1 called for 17 dashboard pages about people, teams and their AI tools, and the product had only an early prototype.
All 17 pages exist as mocks on one made-up company, each opening with a one-line verdict and a calm all-clear version. Four got a second pass after an advisor walkthrough.
Documents
With file names, on their own page →Start here
Documents
Threads
- Accounts (PRO-27) — prompt
- Accounts (PRO-27) — plan
- Agent detail (PRO-26) — prompt
- Agent detail (PRO-26) — plan
- — cloud kickoff prompt
- Device detail — prompt (PRO-23)
- Device detail — plan (PRO-23)
- Device detail v2 — plan
- Endpoints (PRO-34) — prompt
- Endpoints (PRO-34) — plan
- Execution Plan — the 17 Phase-1 pages
- Files — prompt (verbatim)
- Files (PRO-35) — plan and record
- Fleet Overview — prompt (PRO-19)
- Fleet Overview — plan and record (PRO-19)
- MCP servers (PRO-29) — prompt
- MCP servers (PRO-29) — plan
- Models (PRO-28) — prompt
- Models (PRO-28) — plan
- Plugins (PRO-32) — prompt
- Plugins (PRO-32) — plan
- Providers (PRO-25) — prompt
- Providers (PRO-25) — plan and record
- Stage 5 — reconcile: one world, one truth
- Repos (PRO-33) — prompt
- Repos (PRO-33) — plan
- Session detail (PRO-22) — prompt
- Session detail (PRO-22) — plan
- Session detail v2 — plan
- Skills (PRO-30) — prompt
- Skills (PRO-30) — plan and record
- Stage 1 — prompt (verbatim)
- Stage 1 — plan and record
- Teams & Users — prompt (verbatim)
- Teams & Users — plan and record (PRO-20)
- Teams & Users v2 — plan
- Tools (PRO-31) — prompt
- Tools (PRO-31) — plan
- User detail (PRO-21) — prompt (verbatim)
- User detail (PRO-21) — plan and record
- User detail v2 — plan
Pages
- /pages/phase1/accounts2 states
- /pages/phase1/agent-instance2 states
- /pages/phase1/device-detail2 states
- /pages/phase1/endpoints2 states
- /pages/phase1/files2 states
- /pages/phase1/fleet-overview2 states
- /pages/phase1/inventory2 states
- /pages/phase1/mcp2 states
- /pages/phase1/models2 states
- /pages/phase1/plugins2 states
- /pages/phase1/providers2 states
- /pages/phase1/repos2 states
- /pages/phase1/session-detail2 states
- /pages/phase1/skills2 states
- /pages/phase1/teams2 states
- /pages/phase1/tools2 states
- /pages/phase1/user-detail2 states
What changed
The three changes that matter most, in plain words. Open any one to see it.
- 1
Agent Inventory now opens with one sentence: how many installs we can see, and which ones we can't.
Inventory opens with a verdict · came from Mark Peterson and Mark Parsonopen →
- 2
All 17 Phase 1 pages exist, and every number on them comes from the same made-up company, so they agree.
Seventeen pages, one company · came from Mark Parsonopen →
- 3
After walking four pages with our security advisor, we drew them again; Session detail drops Chapters and says plainly how transcripts are protected.
Four pages drawn again after the walkthrough · came from Mark Peterson, Tyler Flint and othersopen →
- Every page also has an all-clear version: the same people on a day when nothing is wrong. New in this cycle
- These mocks and their made-up company became the starting point for the product's own pages in the weeks after. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
“Yeah. The, yeah, the journey starts at the at the inventory and and discovery, observability.”
market-analyst /calls/38075ead… (local)c81-D1 For operators, inventory and visibility first; governance appears only as quiet links. — Mark Parson
c81-D2 One linked made-up company for every page, and one page shape: verdict line, summary band, table of all, expand row, detail. — Mark Parson
Agent Inventory now opens with one sentence: how many installs we can see, and which ones we can't.
From the record: no recorded conversation behind this one.
c81-D2 One linked made-up company for every page, and one page shape: verdict line, summary band, table of all, expand row, detail. — Mark Parson
All 17 Phase 1 pages exist, and every number on them comes from the same made-up company, so they agree.
“This would make me nervous if I saw this in a demo to a certain degree because of all those questions... I just wanna make sure we have thought through that that problem a bit before we're too far down the road on this.”
market-analyst /calls/09ecfede… (local)“Making this only available if you've, you know essentially, bring your own key... that way, they know that they're... they hold the key. Right? Qpoint is never accessing this data... the bucket has to be immutable... WORM enabled. Write once, read many.”
market-analyst /calls/09ecfede… (local)c81-D4 Drop the Intensity labels; sort people by tokens instead. — Tyler Flint
c81-D5 Session detail drops Chapters, minimizes dialogue by default, and states its encryption plainly: local data unencrypted, anything stored or shared encrypted with the customer's own key. — Mark Parson
c81-D6 Promote each person's plain-language AI-use summary into the Teams & Users expand row. — Mark Parson
After walking four pages with our security advisor, we drew them again; Session detail drops Chapters and says plainly how transcripts are protected.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked who can read a transcript
On the Sept 3 walkthrough he said full session transcripts would make him nervous in a demo and proposed customer-held keys; the second Session detail now states how transcripts are protected. He also asked whether the sensor sees browser AI, and called a personal account the headline for a user.
“This would make me nervous if I saw this in a demo to a certain degree because of all those questions... I just wanna make sure we have thought through that that problem a bit before we're too far down the road on this.” first-hand
A plain summary of how each person uses AI
Proposed a human-readable summary per person and dropping the subjective Intensity labels for a sort by tokens; both are in the second Teams & Users.
“A summary. Like, to summarize how this person is using AI, would would just a human readable summary, would be would be great, and we can do that later.” internal
Spotted the browser-AI blind spot
Pointed out that browser AI can tell a person which commands to paste, making the person the one who runs them, and suggested flagging stretches with no signal; both are stated on the second pass.
“The models can cause bad behavior because they go through the web interface and say, what do I do with this and that, and it just tells them what commands to run, and now it actually is the user running maybe malicious commands.” internal
Set the shape, then took the notes
Ruled inventory first, one made-up company and one page shape for all 17 pages, and wrote the walkthrough notes the second pass was built from.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 34
The full record 0 decisions · 7 key-change entries · 1,143 words · 34 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c81 →