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.
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 | not yet measured; the nearest published shape stands in, labelled |
| The delta | derived, stored, recomputed on every build | provisional, against the nearest shape, and it says so |
| The barrier | recorded per row from the vendor's words | unknown on most rows, because the consent screens were not captured |
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 walkthrough at your mailbox is how the grant 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