Lattice, the library
Start from what already works.
Lattice is the structure a build begins with. It holds the workflows, roles, permissions, data models, integrations, rules and tests that a working system needs, so a new mission starts with operational memory instead of a blank prompt.
A template remembers screens. A library remembers behavior.
Most reuse in software is cosmetic. You get the shape of a page and none of the decisions underneath it: who is allowed to approve this, what happens when the integration times out, which states this record can legally move between, what has to be recorded when it does.
Lattice keeps that deeper layer. It is the part that took a team six months and a production incident to learn, held in a form the next build can inherit.
What the library carries
- Actors, roles, identities and permission boundaries.
- State models, workflows, approvals and exception paths.
- Data models, validation rules and evidence requirements.
- Integration contracts, dependencies, retries and fallback behavior.
- Interface patterns tied to operational meaning rather than layout.
- Tests, simulations, observability hooks and deployment assumptions.
Reuse the structure. Preserve the difference.
The failure mode of reuse is pretending two businesses are the same. Lattice separates the stable operational pattern from the policy that is genuinely specific to one customer, so the first can compound while the second stays honest.
| Reused structure | Adapted per mission |
|---|---|
| Identity and role primitives | Named roles, access policy, organizational boundaries |
| Workflow and state patterns | Escalation paths, service levels, local rules |
| Integration adapters and contracts | Credentials, field mappings, environment constraints |
| Evidence and test structures | Risk thresholds, required approvals, acceptance criteria |
| Interface components | Brand, content, hierarchy, task-specific interaction |
Why this compounds
Every mission that survives contact with the world teaches something a prompt cannot recover on its own. When that lesson goes back into Lattice, the next mission starts further along, and Verity checks the inherited structure against the new mission rather than taking it on trust. The library gets more valuable the more it has been used, which is the opposite of how a template gallery behaves.
Do not ask a model to rediscover production from scratch.