An industry, written down.
The engines carry no industry-specific code, and what changes between industries is the pack. It states how the industry talks, where its limits sit, what governs the work, and who answers for what.
- pack
- insurance
- vocabulary
- the industry's terms, defined once
- boundaries
- where an action must stop
- documents
- the instrument types that govern the work
- outcomes
- what done, and gone wrong, mean here
- accountability
- who answers for which action
- rule digest
- recomputed at every boot
- on mismatch
- REFUSE TO SERVE
Contents
What a pack carries. Described at capability level.
A pack's rule contents belong to the organisation whose rules they are. This page describes the shape.
The vocabulary
What the industry calls things, defined in one place, so a proposal, a check and a record can mean the same thing by the same word.
Boundaries and ceilings
Where an action must stop. The pack states the bounds a proposed action has to sit inside, and the ceilings it must never cross.
Governing document types
The kinds of instrument the industry runs on, declared by type, so a record can say which kind of document an action was governed under.
Outcome definitions
What done means here, and what gone wrong means. The pack defines the outcomes the industry counts, in terms a record can carry.
The accountability scheme
Who answers for what. The pack sets out which roles hold which authority, and where an action requires a person.
In the repository today
8 packs, read at build time, commit 9865101c. A count, not a quality claim.
Binding
The pack is load-bearing. A governance rule that can drift is not a rule.
Configuration has a poor reputation, and it has earned it. In most systems a configuration file is advisory: the code consults it when convenient, and drifts away from it over time. This one is checked at every boot, and the kernel refuses to serve if it has moved.
packs/insuranceread at deploy- authority.tomllimits
- retention.tomlrules
- outcomes.tomlverdicts
- documents.tomltypes
- sanctions.tomlscreens
- pack.tomlmanifest
1
# packs/insurance/authority.toml
2
3
[limits.settle_claim]
4
value_max
=
500_000
5
requires_human
=
false
6
7
[limits.issue_refund]
8
value_max
=
250_000
9
requires_human
=
true
10
11
[rules.retention]
12
minimum_years
=
6
The industry pack is load-bearing: at boot, the governance layer recomputes the pack’s rule digest and refuses to serve if it does not match.
For a reviewer, that closes the gap between the pack that was approved and the pack that is running.
If its own checks cannot be discharged at start-up, it does not serve at all.
The same standard the pack is held to, applied to the thing that reads it.
Because the pack is a file, it can be read before it governs anything. Compliance can review it. Engineering can diff it.
Neither has to take the other’s word for what changed.
First vertical
Insurance is the first. A pack in the repository is a starting point, not a finished vertical.
Insurance OS covers underwriting, claims, reinsurance, bordereaux and regulatory reporting workflows. The other packs in the repository are shapes waiting for an organisation’s rules.
Start here
Your industry is a file we have not written yet
Bring the rules you already answer to. We will show you what they look like as a pack, and the record an action leaves under them.