Don't connect the user to the permission.
A role-based access control model: who may do what, to which things, and why. Ten entities covering the full NIST shape — users, roles, permissions, operations, resources, sessions and separation-of-duty rules — plus the two things every real deployment has that the standard leaves out: groups, and an application that scopes everything.
10 nodes · 14 relationships · 64 properties · 21 KB
Two things, and the second is the one people miss.
A model for answering the question that corporate registries were rebuilt to answer: who actually owns this company? Eleven entities covering ownership chains, control that does not come from ownership, the trusts and nominee arrangements that interrupt both, and the filings that are the only evidence any of it is true.
11 nodes · 19 relationships · 94 properties · 30 KB
The quantity does not belong to the part.
A manufacturing bill of materials: the structure that says what a product is made of, all the way down from a saleable SKU to a material and a supplier's price. Ten entities covering the three things a real BOM has to hold at once — the structure, the sourcing, and the change history that explains why the structure is the shape it is.
10 nodes · 13 relationships · 72 properties · 21 KB
A flight is not a relationship between two airports.
A working model of airline scheduling and reservations, from the airport a flight leaves to the boarding pass that finally puts one passenger in one seat. Fourteen entities covering the two halves of the business that people usually conflate: the operation an airline flies, and the contract a passenger buys. It is small enough to read on one screen and large enough that the interesting decisions have to be made rather than avoided.
14 nodes · 19 relationships · 84 properties · 27 KB
A dependency is not on a version. It is on a name plus a range.
A model of how software packages depend on one another: what a publisher declares, what a resolver actually chose, who is allowed to change it tomorrow, and which known flaws are present. Eleven entities covering the manifest, the lockfile, the registry, the maintainers and the advisory chain.
11 nodes · 15 relationships · 77 properties · 26 KB
Current state that matters historically is not a property.
A complete subscription billing system: the catalogue that defines what is sold, the subscriptions that agree to buy it, the periods and prorations that decide what is owed, the invoices that demand it, the payments that settle it, and the events that tell everyone else. Thirty-four entities and one hundred and eighty-six documented fields.
34 nodes · 46 relationships · 186 properties · 69 KB
Opening a model puts it in this browser only — no account, nothing uploaded. Downloading gives you the same JSON to import into the single-file edition, which never touches the network at all.