Inventory + Users / Devices
To close: Commit the c21 folder in bob-wire (it is untracked there). · Write its Outcome in bob-wire. · Remove the cross-repo pointer from design's CYCLES.md.
last activity Sep 1
Our new security advisor said inventory comes first, but our one inventory page mixed agents, machines and people. The call settled on two views: the technology, and the people.
Three polished mocks on the design site: technology by company, people with sensor coverage and spend, and one person's detail. The product's inventory and people pages grew from them.
Documents
With file names, on their own page →What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
Inventory shows the technology, rolled up by company; Users / Devices shows the people. Each uses the other only as a filter.
Two views instead of one · came from Mark Peterson and Tyler Flint
- 2
The people view grew into the product's Teams, Users & Devices page.
Where the people view went · came from Mark Peterson and Mark Parson
- Inventory shows whether each tool runs on a company or a personal account, with a ghost "block personal accounts" button. In words
- The people view counts who has the sensor against the company's identity list, and names the gaps to look into. In words
- Rough wireframes were skipped; three polished mocks were built on the design site, where the product's look lives. 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.
“I need, I guess, a definitive source of truth of all of my, like, my workstation inventory or my endpoint inventory, and then you'd be able to say, like, who who has the sensor installed, right, and who doesn't, and that should be actionable. Right? I should I should be like, oh, crap. Alexis Yes. Investigate that.”
market-analyst /calls/38075ead… (local)“would you guys be able to block, like, certain accounts and not others? Right? Because then that's that that's right there in a control enforcement... None of our none of our IP is ever gonna be going to, like, a personal chat GPT account”
market-analyst /calls/38075ead… (local)bob-wire-c21-D1 Split the dashboard: Inventory for agents and technology, Users / Devices for people and machines. Users are a filter in Inventory, not a dimension of it. — Tyler Flint
Inventory shows the technology, rolled up by company; Users / Devices shows the people. Each uses the other only as a filter.
“I need, I guess, a definitive source of truth of all of my, like, my workstation inventory or my endpoint inventory, and then you'd be able to say, like, who who has the sensor installed, right, and who doesn't, and that should be actionable. Right? I should I should be like, oh, crap. Alexis Yes. Investigate that.”
market-analyst /calls/38075ead… (local)“would you guys be able to block, like, certain accounts and not others? Right? Because then that's that that's right there in a control enforcement... None of our none of our IP is ever gonna be going to, like, a personal chat GPT account”
market-analyst /calls/38075ead… (local)No ruling needed: the work itself is the change.
The people view grew into the product's Teams, Users & Devices page.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Put inventory first, and split technology from people
Cited: the record names his 2026-08-31 call as the cycle's source. He asked that each technology roll up under its company, that sensor gaps be something you can act on ("oh, crap. Alexis... investigate that"), that device lists come from the company's identity and device systems, and he backed blocking personal AI accounts.
“I need, I guess, a definitive source of truth of all of my, like, my workstation inventory or my endpoint inventory, and then you'd be able to say, like, who who has the sensor installed, right, and who doesn't, and that should be actionable. Right? I should I should be like, oh, crap. Alexis Yes. Investigate that.” first-hand
Called the split, and asked for plain summaries
Cited: the design brief records the split as Tyler's, agreed by all on the call (about 56 minutes in). Matched: his wish for a plain-language summary of each person's AI use became the roster's summaries.
Wrote the notes and went straight to polished mocks
Cited: his notes open the initial prompt, and the record says he chose to skip the wireframe pass and build the three mocks on the design site.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 0 decisions · 3 key-change entries · 661 words · 0 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 c21 →