OPEN TRUST — Civic Verification Infrastructure

Why this fits your mandate

This maps to what you're already chartered to do.

Four direct lines between the Task Force's existing mandate and what OPEN TRUST ships — not a generic blockchain pitch, a fit to the specific paper you already hold.

Resolution R-455-21

A deliverable that ships before the feasibility study needs to touch custody

The Task Force's charter is to study whether the County should accept cryptocurrency for taxes and fees — a custody and banking question that moves on its own timeline. OPEN TRUST doesn't wait on that. It's a transparency layer, not a payment rail, so it ships in weeks and gives the Task Force a public win independent of the custody decision.

MDDC — blockchain & regulation pillar

A ready-made legislative artifact, not just a tool

One of the Digital Commission's three pillars is blockchain adoption and regulation advocacy. The Attestation Standard (A2) is written to be legislative-ready out of the gate — a model ordinance a policy body can actually introduce, not a product deck.

Florida's first state blockchain bill

A second first, at the county level

You already authored the state's first blockchain legislation. The Model Ordinance gives you the county-level companion: the first open-data attestation ordinance of its kind in Florida — same legislative track record, adjacent layer of government.

The debt-figure conversation

A neutral trust layer under a live public debate

Whatever the County ultimately decides about tokenizing debt or adopting a stable-value instrument, that debate runs on numbers. OPEN TRUST doesn't take a position in it — it makes sure the figures underneath it are sourced and independently checkable before anyone argues about what to do with them.

Three artifacts, three audiences

What actually gets delivered.

Each artifact stands alone and has zero county dependency — nothing here requires a signature, an API key, or a budget line to exist.

Lead deliverable

A2 — Attestation Standard

Audience: legislative track, other jurisdictions

The signed-claim format itself, plus model ordinance language ready for introduction. This is the artifact with your name on it — the thing other counties adopt, not just the thing this county runs.

Public-facing

A1 — Open Checkbook

Audience: public, press, vendors

Every public dollar traced to its primary instrument with a page-and-row locator. The dashboard a resident, a reporter, or a vendor can click through without calling anyone.

Audit-facing

A3 — Provenance Ledger

Audience: auditors, oversight, opposition research

The hash-chained receipts underneath the other two. This is also the exact audit trail a Resolution R-455-21 feasibility study needs to submit its findings.

Enforced in code, not by discipline

Four non-negotiables. Each has a test that proves it.

0

No county dependency

Tier 1 runs on public data only — no county signature, API key, budget line, or vendor number required. This is what lets it ship in weeks instead of quarters.

1

One-way wall

The edge never writes to origin. There is no public write path into county systems — nothing to hack, nothing to authorize, nothing for IT security to sign off on.

2

Summary law

A summary, index, briefing, or press release is never treated as a supporting instrument. The linter rejects kind IN (summary, index, generated) — only primary source documents count.

3

Verifiability without trust

Every attested number publishes with its signed payload attached. Nobody has to take the County's word, or ours — the proof travels with the claim.

What we build together

Concrete build-out, in order.

Seven things we can stand up specifically for the Task Force and the Digital Commission — each one shippable on its own, each one making the next one easier.

01

Pilot dataset — Task Force / MDDC public spend

First live slice of the Open Checkbook on a small, real dataset tied to the Task Force or Digital Commission's own public activity — every line sourced to a primary instrument. Proof of the model on something you already own, before asking the County for anything larger.

Depends on: public source access only · Ships in: weeks

02

Public verification kiosk

A simple public web tool: paste a published number, get back the primary instrument and the exact page-and-row locator it came from. The single demo that makes "unsourced numbers are mechanically impossible" tangible in thirty seconds, in a Task Force meeting or a press briefing.

Depends on: Pilot dataset live · Audience: press, public

03

Model ordinance, introduction-ready

A2's legislative language packaged for the Board of County Commissioners — your second landmark filing after R-455-21, this time defining how the County publishes and verifies its own numbers.

Depends on: G2 Perimeter sign-off · Owner: legislative track

04

Contradiction watch

A standing check that flags when two public sources publish conflicting figures for the same claim — the exact tool that keeps a fast-moving public number (like a debt-crisis figure) honest without OPEN TRUST ever taking a position on what should be done about it.

Depends on: ≥2 live sources (G5) · Value: fact-first positioning

05

CiviSync attestation training module

Plug the signed-attestation workflow into MDDC's existing county-employee training track. Staff learn to sign a verifiable claim the same way they'd file a report — turns the standard into a habit, not a one-time integration.

Depends on: A2 finalized · Owner: MDDC / CiviSync

06

Feasibility-study audit trail

Hand the R-455-21 feasibility study its own receipts: every data point the study cites, hash-chained and independently checkable, instead of a citations page nobody re-derives.

Depends on: A3 core-ledger merged (G3) · Owner: Task Force

07

Exportable template for the Wyoming-track collaboration

Package the model ordinance and standard as a drop-in template other jurisdictions can adopt without rebuilding it — the artifact for the interstate collaboration you're already building toward, ready to hand across state lines.

Depends on: Model ordinance filed locally · Reach: multi-jurisdiction

Delivery sequence

Never inverted.

Dashboard first and it's a website. Standard first and it's a legislative artifact — the actual currency of an advisory chairmanship, and the piece that outlasts any one dashboard.

Step 1

A2 — Attestation Standard

Legislative-ready language, delivered first. This is what gets your name on it.

→

Step 2

A3 — Provenance Ledger

The receipts layer, so every claim the standard makes is checkable from day one.

→

Step 3

A1 — Open Checkbook

The public dashboard, built on top of a standard and a ledger that already hold.

How we prove it, not just claim it

Gate board — no gate is passed by a mockup.

A design comp is not a build. Every gate below exits on working, tested criteria — the same discipline the standard demands of every published number, applied to the build itself.

Gate	Name	Exit criteria	Status
G0	Charter	Scope signed · Tier-3 exclusions accepted in writing · no fee either direction	OPEN
G1	Recon	Sources landed with URLs + fetch dates	pending G0
G2	Perimeter	Structural boundaries written · no seal adjacency	pending G0
G3	Foundation	Core ledger, attestation, receipts merged and tested	pending G0
G4	Quality	≥85% coverage · zero TODOs · named errors at every boundary	pending G0
G5	Data live	≥2 sources on schedule · one real contradiction caught in staging	pending G0
G6	Publication safe	Linter proven to block a deliberately unsourced value	pending G0
G7	Launch	Domain live · standard delivered · receipts verifiable by an outsider	pending G0

Structural boundaries

What this is not — by design, not by promise.

These aren't policy positions we're asking you to trust. They're structural: the system cannot do the things below, because the components that would let it do them were never built.

No tripwire in this build touches funds, custody, or a token. If a future phase ever approaches tokenizing debt, holding funds, routing citizen payments, or success-fee pricing tied to a public contract, that's a Tier 3 conversation for counsel — separate from, and outside the scope of, everything on this page.

×Token

×Custody

×Funds movement

×PII

×County signature to run

×Seal / partner-mark use

Next step: sign G0.

A free scope letter, Tier-3 exclusions accepted in writing, no fee in either direction. That single signature unlocks Recon and lets us put a live pilot dataset in front of the Task Force within weeks.

Review the gate board See the seven build items

Contact routing intentionally left for direct hand-off — no personal contact details published on this page.