Home / Cases
Cases: one person's deployments, each an ABP
Every shape on this site is a vendor's product in a configuration. A case is one level up and across from that: one person, the assistants they actually run, the connectors they actually switched on, and a mandate for each elicited in their own words. The same four objects, one level up, with the person's single mandate on one side and the union of every grant they hold on the other.
The cases
One person, two assistants, six deployments, one shared account
An early beta user: a business user whose day runs in a mail, calendar and files suite, with two chat assistants connected to different parts of it and a third, out of scope here, handling text messages.
The session that built this site's last twelve releases, as a ledger
An agent in a managed container with this repository attached, over three days and nine turns, with a deployer giving instructions in prose and a harness with standing rules.
One person, three surfaces of one product, one account holding every past conversation
A deployer who runs the same assistant in the browser, as a coding agent and as a desktop work product, and who knows the past conversations contain secrets.
What a case holds
| Object | In a shape | In a case |
|---|---|---|
| The mandate | a starting point the site authored, to be argued with | elicited from the person, every line marked said, inferred or unstated |
| The grant | measured or read from the vendor's pages on a date | usually not yet measured; the nearest published shape stands in, labelled. One case is the shape this site is maintained from, which was measured |
| The delta | derived, stored, recomputed on every build | provisional against the nearest shape wherever the grant is not measured, and it says so |
| The barrier | recorded per row from the vendor's words | unknown on most rows, because consent screens were not captured |
| The ledger | not a thing a shape has | what one session actually spent, counted from the repository where it could be and marked estimated or cannot see where it could not |
The honest summary is that a case starts with the mandate side full and the grant side empty, which is the opposite of a shape. The walkthroughs at your mailbox and the cost ABP are how the other side gets filled: the person runs the discovery prompts in each assistant and the answers become the measured rows.
The cases as JSON · The four objects · The estate universe