Eight things that are true of this work, each with the place on this site where you can check it.
Each claim below is one line. Open it and the text goes down a level to the record it comes from, then to the data. Every number is read from the repository when the site is built. A status word is the one the requirements matrix or the screen uses.
The claims, each with its proof
1The airport is read from public records into a working twin, with no contract in place.
The geometry is OpenStreetMap. The runway facts are the FAA NASR record. Pavement condition is the FDOT inspection of 2022. The terrain is USGS 3DEP lidar. All 37 sources are in the register with a link, how each was read and when it was last validated. The proof of concept runs on 69 screens, on carefully crafted and curated test data for common use cases. Only the drone screens are simulated.
The register lists every source with its sha256 where one exists. Every part in the Exploder cites the sources it was read from and says if it is read or designed.
2The RFP is the app: each requirement is a row, and the row points to a screen.
The requirements matrix holds all 147 rows of RFP 2027-006 and its attachments. 123 of them name a screen that shows the requirement. The rest are procedural, or are marked target where the capability is designed and not shown. The status words are met, partly met, target and not offered, and the matrix defines each one.
Status counts: met 9, partly met 77, target 58, not offered 3.
3One platform and one method sit behind a family of twins.
The platform family screen names four: airports, roads and corridors, farm fields, and drone spraying. It says what each holds today and states which are built and which are a proof of concept only. 2 of the 4 are built; the others are proofs of concept.
Airports (Airfieldpath): started 2026-10-29. Roads and corridors (Municipath): 54 commits, 2026-10-24 to 2026-10-29. Farm fields (Field Twin): 116 commits, 2026-09-27 to 2026-09-29. Drone spraying (SprayPath): 465 commits, 2026-09-29 to 2026-10-22.
4The Interchange is ours, and Jira feeds it.
The Interchange sits between the platform and the owner's systems of record. Jira is off the shelf and sits on the platform side as one source feeding it. One work order leaves the twin for the owner's work order system and its status comes back. It is built and tested on fixtures: 81 tests, 81 pass. No real Jira and no real i3 has been called, but we will be ready. The Simplify i3 interface is to be confirmed with the Authority (Q-35).
The tests are listed by name on the tests page, with the count and the pass count read from a run when the site is built.
5Everything is built and documented with receipts.
The platform's interface standard is called the Stellar Standard: all seeing, all knowing, all receipts kept. On this site a receipt is a file you can open: a sha256 on each download, a last validated date on each source, an evidence line for each hop of the Interchange, and the repository commit the build came from, shown in the footer of every page. The proof of concept repository holds 445 commits from 2026-10-29 to 2026-11-16.
In the Exploder, 300 of 930 items carry a tag. Each tag says its source, its status and when it was last validated.
6The development tools are meant to run through the Interchange, so context, code and documents stay aware of each other.
Sheet A-04 draws a lane for the development and project tools: Git, Jira and Confluence, copying and linking through the Interchange. State: the Jira side is built and tested on fixtures. The repository holds adapters for Jira, Simplify i3, the alert channels and the ETL jobs. It holds no Git or Confluence adapter today, so those two are a design on the sheet and not built.
The Jira adapter's files are listed on its page, each tested on the fixture site.
7It was built quickly, and the dates are in the record.
The proof of concept repository's first commit is dated 2026-10-29 and its latest 2026-11-16: 445 commits. The Interchange repository's first commit is 2026-11-06 and its latest 2026-11-08: 15 commits. The plan runs 12 phases and 100 work units from the Authority's written authorization to go-live. The dates come from git, and the plan's dates move with the award date.
sanford-twin: started 2026-10-29; municipath: 54 commits, 2026-10-24 to 2026-10-29; sv-field-twin: 116 commits, 2026-09-27 to 2026-09-29; spraypath: 465 commits, 2026-09-29 to 2026-10-22
8The films, the documents and the plan are made with the platform itself.
The 7 films on this site were produced with the platform's own film tools. The twelve sheets are written by one build script from one data file and come with their PDFs. The plan is a data file of phases and work units that the page reads. Each of them is a component page here with its source file.
The lead film's chapters link to the screens it shows, and each screen links to the requirement rows that name it.
From a requirement to a screen to a component
147 rows, 69 screens. Choose a screen to see the rows that name it and the components that show it. Choose a row to see its screens. Statuses are the matrix's words.
Screens
Requirement rows
Components
The Interchange at the centre
The Interchange at the centre
Built and tested on fixtures. No real Jira and no real i3 has been called, but we will be ready. How it works.
The loop
The loop
Each step feeds the next, and the last returns to reporting. How it works.
The Exploder, with tagged assets
Every tag names one asset and says its source, its status and when it was last validated. In the data this build holds 930 items, 300 of them tagged. Each part of an exploded view is marked read, from a source, or designed, from the kit class model.
Picture: Exploder still of "Escalator, exploded" through the kit's film clock on the Light theme (exploder/?film=1, select and explode). Clip: Exploder clip: "Escalator, exploded" lifted apart and orbited, 4 seconds, through the kit's film clock on the Light theme. No sound.
Research: SFB facilities and assets (board minutes, OCR)
KONE 24/7 Connected Services
Data
read
Research: terminal elevators, escalators and baggage handling
Schindler Ahead
Data
read
Research: sensor catalogue for SFB
Asset tags on this class (6 tagged of 6 items)
Item
Tag
Status
Known
Source
Last validated
Escalator 1 (up, to the garage mezzanine)
SFB-ESCALATOR-001 proposed
record
inferred
Florida DBPR elevator extract (Bureau of Elevator Safety public records); SAA and OSI joint board agenda, 2023-03-24 (elevators and escalators, downtime charts); SAA minutes, 2023-09-18 (OSI default list)
2026-11-06
Escalator 2 (down, from the garage mezzanine)
SFB-ESCALATOR-002 proposed
record
inferred
Florida DBPR elevator extract (Bureau of Elevator Safety public records); SAA and OSI joint board agenda, 2023-03-24 (elevators and escalators, downtime charts); SAA minutes, 2023-09-18 (OSI default list)
2026-11-06
Escalator 3 (down, ticketing to checkpoint)
SFB-ESCALATOR-003 proposed
record
inferred
Florida DBPR elevator extract (Bureau of Elevator Safety public records); SAA and OSI joint board agenda, 2023-03-24 (elevators and escalators, downtime charts); SAA minutes, 2023-09-18 (OSI default list)
2026-11-06
Escalator 4 (up, ticketing to checkpoint)
SFB-ESCALATOR-004 proposed
record
inferred
Florida DBPR elevator extract (Bureau of Elevator Safety public records); SAA and OSI joint board agenda, 2023-03-24 (elevators and escalators, downtime charts); SAA minutes, 2023-09-18 (OSI default list)
the airport: its systems of record joined into one picture and the FAA records it owes
this kit: discovery, a registry of airport terms, the POC, the general requirements
sanford-twin, started 2026-10-29
Roads and corridors (Municipath)
Proof of concept only
roads and corridors: the I-4 corridor, its operations and its funding
a POC page of 33 screens, research and requirement drafts; its roadmap says nothing is built unless it says so; the same duty and rules approach serves many agencies on one road corridor
municipath, 54 commits, 2026-10-24 to 2026-10-29
Farm fields (Field Twin)
Built
a vendor-neutral digital twin of every farm field, with a source registry and state packs
NestJS API on PostGIS, React web, ingestion, change detection, scheduler, data health, Florida pack v1, AI-assisted source onboarding; 94 test files
sv-field-twin, 116 commits, 2026-09-27 to 2026-09-29
Drone spraying (SprayPath)
Built
planning, compliance and records for agricultural spray drones; the maker's own app flies
API, web command center, phone companion, workers; mission states and a release gate; 1,172 integration tests including tenant isolation