Skip to contentThe claims register is public. 27 verified, 7 struck.

Three layers around one moment.

Everything in the platform serves the instant before an action executes. A kernel that decides. A knowledge layer the decision can draw on. A workforce that works inside both. Each layer has its own page; this one shows how they fit.

Composition

The three layers. One decision passes through all of them.

Something decides, something it can consult, and something doing the work. A proposed action meets all three before it runs.

The kernel

The deciding layer. It takes a proposed action and answers allow, hold or refuse. Deterministic mathematical governance: if its own checks cannot be discharged at start-up, it does not serve.

A governance layer that cannot vouch for itself has no business vouching for anything else.

What it decides
The Brain

The knowledge layer. Assertions are designed to carry their origin and a trust grade, and agents recall prior governed context on every run.

The page separates what runs today from what is design intent, and says which is which.

What is live
The governed workforce

The working layer. Agents run under quotas and spend caps, with human approval gates on the actions that matter.

A workforce you can hold to limits is a workforce you can let work.

How agents are held

Configuration

One platform, configured by pack. The engines stay the same; the pack is what changes.

The packs in detail

An industry is a configuration file, not a codebase. The pack states how the industry talks, where its limits sit, which document types govern the work, and who answers for what.

Because a pack is a file, it can be read before it governs anything, and diffed after it changes. Compliance reviews the rules; engineering reviews the diff; neither takes the other's word for it.

accountingadmissible labsbankingdefenceenergyhealthcareinsurancelegal

8 packs, read from the repository at build time, commit 9865101c.

packs/insuranceread at deploy
  1. authority.tomllimits
  2. retention.tomlrules
  3. outcomes.tomlverdicts
  4. documents.tomltypes
  5. sanctions.tomlscreens
  6. 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
            
        
Change the pack, not the kernel.8 packs ยท commit 9865101c

Evidence

What it all leaves behind. A decision that leaves no record is an anecdote.

Every governed action is sealed in a signed, tamper-evident record. The record is as much the product as the action is: it is what a reviewer reads when the question is no longer what should happen, but what did.

The evidence layer describes what a record carries, what a period of work adds up to, and how a third party checks either.

Start here

Start with one action

Bring the workflow you would least like to explain to an auditor. We will show you the layer it meets, the verdict it gets, and the record it leaves.