A demo that is maintained by hand drifts from the product. This one is built by a test suite from an empty database, and the suite fails when the product grows a capability the demo does not show.
Built, not kept
- Three stages Compile the model, run 27 catalogues in dependency order, verify wholeness.
- A taxonomy of 158 capabilities across fourteen domains, with 635 menu-reachable objects. The ledger moved from 50 covered and 108 pending to 133 covered, four deferred, three not applicable and 18 pending.
- Extracted from the client The client's configurable surface was read mechanically: 835 interfaces, 275 enumerations, 5,537 members across 1,614 files. The hand-written coverage document had described about four percent of it. A new key that appears unclassified fails the build.
What it contains
- Four applications Hospital admissions with nineteen objects and a 58-bed floor plan, an order, a work order and a support queue.
- Real spatial data Thirty-one examples over 4,610 World Bank observations and 258 of 261 country boundaries.
- 1,333 help pages written into the information sidebar, schema-proved and journalled, with a switch that writes one node's pages instead of all of them.
It is the corpus the authoring rules are harvested from and the examples agents are shown. A demo that doubles as a specification.