See it work
The working system, running on this page.
A guardianship, start to finish, the way the office actually works it. Step through it yourself, watch every step seal itself into the record, then check the whole chain. Nothing to fill in first.
Runs right here · no form, no call · then talk to us if you want to
The walkthrough
Run it right here. No form, no call.
This is a guardianship, start to finish, the way the office actually works it. Step through it yourself, or press play and watch it run. Every step seals a record, and at the end you can check the whole chain.
An illustrative matter, with an invented docket number and an invented ordinance section. In your walkthrough the rules come from your own published code.
Your connection just dropped, and this page is still running. That is the whole idea.
Step 01 of 07 · Summons
The matter opens on a person, not a file.
- Person
- Found by name and date of birth
- Matter
- 26-GU-007
- Already linked
- Enrollment · 2 other matters · Fees current
You do You answer plain questions: who this is about, and who must appear.
It does The person is found once, by name and date of birth, and the matter attaches to the record they already have. Their enrollment, their other matters, and their balances are already linked.
Sealed to the record: Matter opened
No blank form. You answer what you know, in order.
One member, one record, across every department.
One record model. No nightly sync holding four databases in uneasy agreement.
Step 02 of 07 · Notice
The deadline comes from your ordinance, and says so.
- Rule
- Ch. 12.304
- Window
- 10 days from service
- Source
- Your published code
You do You say who must be told. That is the whole of your job here.
It does The notice window is computed from your own published code, and the exact section rides along with it. Nothing is carried in from another jurisdiction's template.
Sealed to the record: Notice issued
When the bench asks why the date is the date, the answer is on the screen.
The software conforms to the nation. Amend the code, the rule follows.
Rules are data read from your ordinances, not a template shipped in a vendor release.
Step 03 of 07 · Change of notice
Service fails. Every dependent date recomputes.
- Was
- Served 03 Feb · hearing 20 Feb
- Now
- Served 11 Feb · hearing 28 Feb
- Recomputed
- 4 dependent dates
You do You record what actually happened: service failed, the address changed.
It does Every date that hung off the original service is worked out again from the new one. Nothing is left pointing at a day that no longer means anything, and the change itself goes on the record.
Sealed to the record: Service updated
This is the step that silently ruins a case. Here it is arithmetic.
A missed date is how a tribe loses a matter it should have won.
Dates are computed from the record, so there is no stale value to go hunting for.
Step 04 of 07 · Calendar
The docket is computed, not remembered.
- Hearing
- 28 Feb · 09:00
- Temp order expires
- Day 45 · 17 Mar
- Annual account
- Scheduled · next year
You do You look at what is due. You do not maintain it.
It does The hearing and every deadline that follows from it land on the docket, worked out from the record and from your code, so nothing depends on somebody recalling a date from six months ago.
Sealed to the record: Hearing set
The obligation three years out is already on the calendar.
A lapsed guardianship leaves a child with no legal footing. This is that risk, closed.
Deadlines are derived state. There is no separate reminder system to keep in step.
Step 05 of 07 · Build
The AI drafts. A person decides.
- Drafted by
- The system, on your machine
- External calls
- 0
- Approved by
- The clerk · required
You do You review a draft instead of starting from a blank page.
It does The draft is assembled from the record, on your own hardware, and it stops and waits. Nothing becomes part of the official record until a person approves it, and the approval is recorded as theirs.
Sealed to the record: Draft approved by the clerk
It carries the slow half of the job. You keep the judgment.
The AI does the legwork. A person authorizes. The tribe keeps every decision.
Denied outbound by default. The model is on your disk. Nothing left the building.
Step 06 of 07 · File
Filed, attributed, and sealed as it happens.
- By
- The clerk
- When
- 2026-02-11 · 09:31
- Prior version
- Kept and readable
You do You file. The record does the remembering.
It does The filing is stamped with who did it and when, and locked to the record before it. The previous version is kept. Nothing is quietly altered and nothing quietly disappears.
Sealed to the record: Filed
Your work stays attributed to you, and cannot be rewritten after you leave.
An office with no trail is an office where an error leaves no mark. This closes it.
Append-only. A change leaves a mark; a removal shows as a gap at a named point.
Step 07 of 07 · The document
The order is generated from the record, and signed.
- Generated from
- The record
- Signature
- Sealed and checkable
- Reproducible
- Identical bytes, years later
You do What you see is what prints and files.
It does The order is produced from the matter itself, so the document and the record cannot quietly disagree. It is signed, and it can be reproduced identically years from now, byte for byte, from the sealed record.
Sealed to the record: Order sealed
No template wrangling, and no copying last year's file and missing a name.
An order the tribe can reproduce and prove is an order that holds up elsewhere.
Regenerate it in five years and the bytes and the signature match. Nothing to archive.
The record, sealing as you go 1 / 7
- 041 Matter opened 9f2a…c71
- 042 Notice issued 4d81…a02
- 043 Service updated 71bd…e40
- 044 Hearing set c3e9…18b
- 045 Draft approved by the clerk a07f…5d2
- 046 Filed 6b14…9ac
- 047 Order sealed e52d…3f0
Each record carries the fingerprint of the one before it. Remove one and the chain breaks at a named point. You can check it yourself, offline, with a tool that is not ours.
A deadline you can trust
Every rule shows the section it comes from.
The deadline you just watched be computed came from a published ordinance, and the system showed which one. In your walkthrough that is your code, and your sections.
- Rule
- Ch. 12.304
- Source
- your published code
- Enforced
- computed on the case
The system tracks the deadline and shows the exact section it comes from. When your practice differs from the written rule, it flags it instead of guessing.
What the live one adds
The same system, with your code in it.
What you just ran is an illustrative matter. In the live walkthrough it is your own ordinances, your own workflow, and your own staff asking the questions. It takes about fifteen minutes, at no cost and no commitment, and you will speak with the person who builds it.
- Your code, cited. The deadlines come from your published ordinances, and every rule shows its section.
- Your workflow. We walk a matter the way your office actually does it, including the places your practice differs from the written rule.
- Your questions. Bring your IT, your council, and the clerk. Each one gets to push on it.
- The unplug test, for real. Pull the connection and watch it keep working, on the machine in front of you.