Four separately-running production systems are composed here into one view. That unified console does not exist yet — it is a design. Every headline figure on this page was probed live out of the running system on 6 August 2026 and is carried from a single sourced file. Everything that is interface texture rather than a measured number — the incident rows, the sample question, the citation formatting, the pipeline stage names, the placement of points on the map — sits inside a block marked REPRESENTATIVE.
Nothing here is dressed up to look further along than it is. On this site that is a feature, not a disclaimer.
Live = a production system this figure was read out of. Design = composed for this view.
Corpus
Ingestion, retrieval, and the citation back to the page
Probed liveQuestion
"What did the United States commit to build as a condition of terminating the rancheria, and was it ever built?"
Answer
Roads and water systems. The Smith River Rancheria was named in the California Rancheria Termination Act of 1958 and terminated in 1960. Those systems were never built. In Tillie Hardwick v. United States the termination was held in 1983 never to have lawfully occurred for that reason, and boundaries were restored by court order in March 1987.
The rancheria is named in the schedule of terminations, with distribution of assets conditioned on the completion of specified improvements.
Termination is held never to have lawfully occurred, the United States having failed to construct the roads and water systems promised as its condition.
Restored exterior boundaries recorded by court order.
Citation formatting and chunk identifiers above are representative. What is verified: 289 fact-ledger entries under five-tier evidence grading, drawn from 28,190 retrieval chunks across 1,262 documents.
Check counts are verified. The wording of each check is representative.
Built by agent-driven retrieval from NARA, BLM General Land Office, GovInfo, BIA and the Del Norte County Recorder — then preserved and hash-manifested. Not a wired API integration. The rigour is the point: the repository’s own README states the records do not by themselves prove any present legal claim.
The public Lever page is not deployed — it lives on an unmerged branch. Shown here as a capability, not as a product you can visit.
Operations
One live operational picture from many public feeds
Probed liveEmergency dispatch, road closures, weather alerts, river gauges, air quality, wildfire, court filings and municipal notices — continuously ingested and cross-referenced. The same shape as a northern emergency operations picture.
Scanner-audio processing is built and deployed but has not processed clips in production — all observed incident volume is API and feed derived. Memberships are not taking payment.
Territory
The geospatial layer under the sovereign northern compute argument
Probed live278 records · 30,616 MW · 11 provinces and territories
Point placement and relative sizing above are representative and drawn by hand — this is a schematic, not a survey. The verified figures are the ones printed inside the frame and in the cells above: 278 Canadian data-centre records totalling 30,616 MW across 11 provinces and territories.
All twenty-two are live. The two set apart at the end are the fibre layers, and they cover Vancouver Island and nothing else. There is no proprietary national fibre dataset here and we do not claim one.
The precedent, already indexed: what a comparable programme actually paid out, in a form somebody can query rather than argue about.
Fibre coverage is 2 of 22 layers and is Vancouver Island only. There is no proprietary national fibre dataset. Several pages are marketing-only.
Pipeline
What a services firm looks like when the leave-behind is recurring
Design| # | Offer | Price | Delivery | First dollar | State |
|---|---|---|---|---|---|
| 01 | Chapter & VerseFinal Agreement implementation audit | $35,000 – $50,000 CAD, fixed | 2–3 weeks | 14–30 days | Sellable |
| 02 | Claim ReadySpecific claims research accelerator | $35,000 – $40,000 CAD per claim | 4–6 weeks | 30–60 days | Sellable |
| 03 | Season PassProposal and reporting operations, run for you | Annual, renewed on the funding year | Continuous | 45–90 days | Sellable |
| 04 | Plan AcceleratorChapter 11 regional land use planning | Phase 2 — requires reference customers first | Months, not years | Day 90+ | Phase 2 |
The last column is empty because it is true. No purchase order has been issued. Step two of the sequence below is the one that changes that.
Fix the cap table on paper.
Dana at 51%+ with documented control. Canadian entity owns or perpetually licenses the delivery IP. Indigenous Business Directory application started. Do not pitch Arrow before this is settled — their first diligence question is who owns what.
Run one live build for one named nation Dana can call this week.
Their own Final Agreement, their own document holdings, 48 hours, ending with a request for a $35–50K purchase order on the same call. This tests the only three things that matter: does the demo convert to a signature, can this buyer transact without a council resolution, and does the Canadian data gap actually block delivery when the corpus is band-held.
The Arrow meeting.
Ask for the full $200K, structured across four budgets, paid in milestones tied to transactions. Bring the purchase order from step two into the room. A distributor funds pipeline it can transact, not a cause it admires.
Sell Chapter & Verse into three more of the 27.
Off Dana’s direct relationships. Fixed price, named deliverable, no subscription, and the word "AI" nowhere in the title.
Stand up the recurring layer where it is legally possible.
Season Pass for Indian Act bands, priced on the funding year. Run one Claim Ready engagement as a margin experiment and measure honestly whether manual Canadian archival access destroys the unit economics.
The marquee work.
Chapter 11 plan acceleration and the northern compute leg. Both need reference customers and working capital that do not exist yet. This is what the October stage is for — not what October pays for.
This quadrant is a plan, not a book of business. There is no signed engagement in it. The prices, delivery windows and time-to-first-dollar figures are the ones written down for each offer — what is not yet true is that anyone has bought one.
Why this screen and not a slide
This is what we operate it looks like.
A report is finished the day it is delivered. A console is never finished — somebody has to feed it, watch it, and answer for it on a Tuesday morning. That is the whole commercial argument, drawn.
Stays. The leave-behind is the recurring revenue, because nobody else can operate it. The nation owns the corpus. We keep the thing that reads it running — and that is a line item that renews, not a deliverable that ends.
The four capabilities, and where each already runs
A terminated rancheria’s paper record, reassembled into something you can ask questions of.
Twenty-five public feeds, one live operational picture, running in production.
A live Canadian infrastructure map — and the dataset that makes the compute argument concrete.
Four offers, one sequence, and a price under signature authority.
Three of the four are running production systems today. The fourth is a plan. The console that joins them is the design on this page.
Somebody asks the question from the floor. By the time you step off, it is on this screen.
This site is the proof. It did not exist this morning. It was built from the recording of a single meeting, on the same day as the meeting.