# Airfieldpath: Business Requirements (one epic, E1)

day. Scope of this draft: the general airport and FAA parts only. Everything that comes from Sanford's RFP is held in
section 7.12 as named placeholders, **awaiting RFP**, and no requirement here claims to be the Authority's.
Airfieldpath is the internal and vendor name. The product is white-label to the airport that runs it (discovery
principle 8). Repository `sanford-twin`; the twin it runs on is the Airport Twin.

Sources read for this document: docs/discovery-echo.md (sections 1 to 17 and principles 1 to 10), the domain registry
docs/domain-registry.json (217 terms, APT-001 to APT-217: 212 verified, 5 inferred, 0 fabricated; cited here as
APT-NNN), poc/screens.json (stellarview-poc/1, 27 screens and 122 must-do items, each carrying the ids that serve it),
docs/rfp/AWAITING.md (30 placeholders) and brand/final (the mark). Anything the registry did not verify is a gap in
section 23, never a requirement.

How the ids work: one sequence per category; each requirement is declared on its own line starting with its id and
its phase tag, for example (P3), which section 25 repeats and which is the authority for placement. Each line ends
with its acceptance (what a test or a person checks) and its evidence (what a reviewer opens). The requirements say
what, and how it is shown to be done. They do not say how to build it.

## 1. Executive Summary

An airport keeps its truth in many systems: maintenance, GIS, pavement, lighting control, finance, drawings, security.
Each is authoritative for its part, and nothing shows the airfield, its assets, their condition and the work on them
at once. Airfieldpath is the twin that joins them without replacing any of them, the line the Sanford RFP itself
draws (discovery section 2). It turns what those systems hold into one picture a person reads at a glance and into
the records the FAA, the state and the grant programs ask for: the Part 139 self-inspection, condition reports and
NOTAMs, the SMS, the pavement management program, the capital plan and its applications.

Drones are a lead strength, carried from Municipath and SprayPath: inspection missions planned from a twin asset,
gated on the airport's own airspace and rules, with their findings returned as evidence.

E1 builds it in 11 phases and 177 requirements, from the design system and the FAA pack in P1 to the platform in the
cloud, tested on the deployed app, in P11.

## 2. Business Overview

A white-label airport operations platform, licensed per airport with implementation and support services (to
confirm, GAP-E1-08). Florida first, with the FAA and Florida rules as one versioned pack; a second state is a new pack.
A sister of Municipath, Field Twin and SprayPath (discovery section 17).

## 3. Market Analysis

FAA certificated airports under Part 139 (APT-001, APT-002). One buyer is asking now (the Sanford RFP); North
Charleston has listed an operational twin; ACRP Project 03-66 prepared a guidebook for airport twin programs
(APT-186). The platforms on the market are filled by hand. None is known to make the FAA records an airport already
owes its working surface (discovery section 6, to verify per vendor).

## 4. Target Users

Airport operations (duty managers, inspectors), maintenance and facilities, planning and engineering, the capital
program and grants, the SMS manager, ARFF and police, IT and GIS, drone crews, auditors and records officers. The
RFP's own roles and user counts are AW-08.

## 5. Problem Statement

Data held in separate systems never joined; the airfield's state read from several screens; Part 139 records kept by
hand; pavement and lighting plans that go stale between consultants' reports; grant evidence copied by hand; GIS and
the ALP stale between surveys (discovery section 7).

## 6. Solution Overview

The ten founding principles of the discovery govern every requirement: complement, never replace; a source is
probed, licensed and approved before it is active; see it and immediately know; evidence, not words; the FAA's
language inside; open and standards-based; sensitive handled as sensitive; the app is the organization; the money is
part of the operation; a foundation built in steps.

## 7. Core Features

Each line: id, phase, the requirement, its acceptance, its evidence.

### 7.1 Design system, shell, the organization as tenant, the FAA and Florida pack (P1)

REQ-FUNC-001 (P1) The shell: the organization's mark and name, the screen rail grouped by the work (Drones, Operate, Assets, Fund, Prove, Set up), the context line with the airport's identifier, reference point and elevation from NASR (APT-154, APT-155), the clock in UTC and local time, and the signed-in person and role, on every screen. Acceptance: every screen opens in the shell with the five parts present. Evidence: captures of three screens.
REQ-FUNC-002 (P1) Every screen opens on one state word in a bordered box, one sentence saying where and since when, and chips for what a person acts on. Acceptance: each built screen shows exactly one state word and its sentence. Evidence: the design review captures.
REQ-FUNC-003 (P1) Every view state (screen, selection, layers, scheme, light or dark) has an address that reopens it in the same state, permissions permitting. Acceptance: a copied address reopens the same view for another permitted user. Evidence: the shell spec.
REQ-FUNC-004 (P1) The organization is the tenant: its name, mark, colours and typefaces present the whole app as that airport; the vendor's name appears nowhere a tenant's users see. Acceptance: a search of the built UI and exports finds no vendor name. Evidence: the search output.
REQ-FUNC-005 (P1) A tenant's look comes from brand discovery: each value recorded with where it was read and confirmed by a named person before it is applied; no airport's or agency's mark is used without that record. Acceptance: a brand without a source or a confirmation cannot be applied. Evidence: the brand record.
REQ-FUNC-006 (P1) The FAA and Florida rules are one tagged, versioned pack (Field Twin's pack pattern): its registry terms, record formats, retention periods and data sources, each with its source and date; a version is immutable and a tenant moves to a new one on purpose, by a named person, on the record. Acceptance: a pack release leaves the tenant on its version until moved. Evidence: the pack record and the move record.
REQ-FUNC-007 (P1) Every value on every screen carries the system of record that owns it, its time and its age; a value with no owner is shown as unowned, never as fact. Acceptance: a sample of 50 values each names its owner and age. Evidence: the sample check.
REQ-FUNC-008 (P1) An in-app notifications tray with an unread count, to which every later phase publishes (findings, outages, NOTAM drafts, held launches, deadlines). Acceptance: a published event reaches the tray of the people it concerns. Evidence: the tray spec.
REQ-FUNC-009 (P1) Global search over places (runway, taxiway, apron, gate, building) and, as phases ship, assets, work orders, NOTAMs, inspections and applications. Acceptance: a taxiway letter finds its segments on the map. Evidence: the search spec.
REQ-FUNC-010 (P1) Roles decide what each person sees and does (duty manager, inspector, maintenance, planner, grants, SMS, ARFF, drone crew, IT, viewer); a role's limits are shown with the reason, never hidden as an error. Acceptance: a viewer sees operate screens read-only with the reason. Evidence: the roles spec.

### 7.2 Systems of record: the source registry and Intake (P2)

REQ-FUNC-011 (P2) Every system of record and public source is a registry source with a lifecycle of proposed, approved, active, paused, blocked and retired (Field Twin's lifecycle), its state and the age of its last reading shown. Acceptance: one source walked through every state. Evidence: the lifecycle record.
REQ-FUNC-012 (P2) A source becomes active only with a probe that proves its key, a confirmed licence or data agreement, a freshness target and an approver who is not the activator. Acceptance: activation without any one of the four does not happen and says which is missing. Evidence: the activation guard spec.
REQ-FUNC-013 (P2) Each probe is kept append-only: when, by whom or by which runner, the outcome, the key check method and the evidence hash. Acceptance: a probe record cannot be edited. Evidence: the probe table check.
REQ-FUNC-014 (P2) Each source declares the values it owns; the twin holds no value of its own for a function a system of record covers, and two sources cannot own the same value. Acceptance: a second claim on an owned value is reported as a conflict. Evidence: the ownership map.
REQ-FUNC-015 (P2) A source that goes quiet past its freshness target shows stale, then failing, with the reason; its values show their age and are never filled in. Acceptance: a stopped feed turns stale within its target. Evidence: the honest-state spec.
REQ-FUNC-016 (P2) Writing back to a system of record happens only through that system's own interface, only on a path the tenant has approved, and each write is recorded with who and when. Acceptance: a write on an unapproved path does not reach the system. Evidence: the write-back log.
REQ-FUNC-017 (P2) The RFP's selected airport systems are created as proposed sources marked awaiting RFP until the document names each one (AW-04, AW-05). Acceptance: each placeholder source shows its AW id. Evidence: the registry capture.
REQ-FUNC-018 (P2) Intake: documents and data (the ALP set, surveys, as-builts, drawings, asset lists, PCI reports) are loaded; the AI drafts each record, matches duplicates and checks each value against the data standard (APT-046). Acceptance: a loaded ALP set yields drafted records with their checks. Evidence: the Intake capture.
REQ-FUNC-019 (P2) Each Intake item is accepted, fixed, rejected or merged by a person, kept with who verified it and when; only verified items count anywhere. Acceptance: an unverified item appears in no screen total. Evidence: the totals check.
REQ-FUNC-020 (P2) A document marked as Sensitive Security Information (APT-124) is detected at Intake and restricted to people with a need to know (APT-125). Acceptance: a marked test document is restricted on arrival. Evidence: the restriction record.

### 7.3 Airfield Now: the airfield model, conditions and NOTAMs (P3)

REQ-FUNC-021 (P3) The airfield model: runways, taxiways, aprons and buildings from the airport's GIS to AC 150/5300-18B (APT-044, APT-046), with public map data shown only as a labelled stand-in until the GIS is joined. Acceptance: every runway and taxiway drawn with its source named. Evidence: the model capture.
REQ-FUNC-022 (P3) Runway facts (designation, length, width, surface, lighting, declared distances, pavement rating) from the FAA airport master record (APT-048), refreshed each 28-day cycle, with the cycle shown. Acceptance: a new cycle's change appears with its cycle date. Evidence: the cycle diff.
REQ-FUNC-023 (P3) Airfield Now shows every runway in its state (open, caution, closed, construction, unavailable), always with a word, from the records that set it. Acceptance: each runway shows a state from a record. Evidence: the Airfield Now capture.
REQ-FUNC-024 (P3) What needs a person now: each item with its place on the airfield, its state, how long it has held and its owning system, newest first. Acceptance: a new finding appears in the list within the tray's latency. Evidence: the list capture.
REQ-FUNC-025 (P3) Conditions and NOTAMs in force, each with its time and its source, read from the FAA NOTAM system once that source is active (APT-062, APT-063). Acceptance: a NOTAM in the FAA system appears with its number and time. Evidence: the read record.
REQ-FUNC-026 (P3) A NOTAM is drafted from a closure or condition on the map in the NOTAM manual's format (APT-062), for a person to file in NOTAM Manager (APT-064); the twin never files one itself. Acceptance: a draft opens with its text; no filing path exists in the API. Evidence: the draft and the API listing.
REQ-FUNC-027 (P3) A condition ends in the twin when its NOTAM is cancelled in the FAA system, and the twin shows both. Acceptance: a cancelled test NOTAM ends its condition. Evidence: the condition record.
REQ-FUNC-028 (P3) Runway condition codes and field condition reports are shown when reported, with the matrix they came from (APT-065 to APT-067). Acceptance: a reported code shows with its matrix row. Evidence: the capture.
REQ-FUNC-029 (P3) Hot spots from the FAA airport diagram (APT-060, APT-176) are drawn on the model and named on every item inside them. Acceptance: an item inside a hot spot names it. Evidence: the capture.
REQ-FUNC-030 (P3) Each operational screen carries its thread: which FAA record, state record or grant its data feeds. Acceptance: each operational screen shows its thread from the records. Evidence: captures.

### 7.4 Part 139 operations: self-inspection, lighting, wildlife and FOD, construction safety (P4)

REQ-FUNC-031 (P4) The self-inspection (APT-018) runs as a checklist in the Part 139 Subpart D categories (APT-006, APT-009, APT-011, APT-015, APT-016, APT-021 to APT-025, APT-029, APT-040), each item placed on the airfield. Acceptance: a full round completed on a tablet. Evidence: the inspection record.
REQ-FUNC-032 (P4) Each discrepancy is recorded with its place, its photo, the rule it breaks and its severity, then routed as a work order to the maintenance system of record. Acceptance: a discrepancy reaches the maintenance system as a work order. Evidence: the routing record.
REQ-FUNC-033 (P4) A discrepancy that needs an airport condition report or a NOTAM (APT-028) says so and opens the draft. Acceptance: a pavement finding in a movement area opens a draft. Evidence: the draft.
REQ-FUNC-034 (P4) Inspections due, done and overdue are shown; each record is kept for the period the rule sets (APT-007); periodic and special inspections are kept the same way (APT-019, APT-020). Acceptance: a missed round shows overdue. Evidence: the schedule capture.
REQ-FUNC-035 (P4) Each entry names its inspector, with their training record's state (APT-008). Acceptance: an inspector with lapsed training is shown so on their entries. Evidence: the training check.
REQ-FUNC-036 (P4) Every lighting circuit and visual aid (APT-068 to APT-073) on the map with its state from the lighting control system (APT-076), once that source is active. Acceptance: a circuit's state change appears with its age. Evidence: the capture.
REQ-FUNC-037 (P4) Lighting outages with their place, the rule they are measured against and how long they have held; each outage routed as a work order, with a NOTAM draft where one is needed. Acceptance: an outage raises a work order and a draft. Evidence: the routing record.
REQ-FUNC-038 (P4) The preventive maintenance schedule for visual aids (APT-077) with its record. Acceptance: a missed check shows overdue. Evidence: the schedule capture.
REQ-FUNC-039 (P4) Wildlife sightings, dispersals and strikes on the map with species and time; the wildlife hazard management plan's actions with their state (APT-026, APT-027). Acceptance: a sighting appears on the map and in the plan's log. Evidence: the log.
REQ-FUNC-040 (P4) A strike report is drafted in the FAA's form for a person to submit to the FAA database (APT-136, APT-137). Acceptance: a draft carries every field the form needs. Evidence: the draft.
REQ-FUNC-041 (P4) FOD finds with their place, their kind and the walk or sweep that found them (APT-040, APT-138). Acceptance: a find appears on the map with its source. Evidence: the FOD log.
REQ-FUNC-042 (P4) Land uses near the airport that attract wildlife, drawn against the advisory circular's separation distances (APT-041). Acceptance: the distance rings drawn from the airport's operations area. Evidence: the capture.
REQ-FUNC-043 (P4) Every construction area with its phase, its closures and its safety plan (APT-043); the marking, lighting and barricades each area needs and whether the inspection found them (APT-029). Acceptance: a phase change updates its closures. Evidence: the plan record.
REQ-FUNC-044 (P4) The NOTAMs each construction phase needs, their state, and the haul routes, staging areas and escorts. Acceptance: a phase without its NOTAM shows due. Evidence: the capture.

### 7.5 ARFF, the emergency plan and the storm plan (P5)

REQ-FUNC-045 (P5) The ARFF index from the FAA record (APT-012, APT-160) and the vehicles and agents it requires (APT-013), each with its state. Acceptance: a vehicle out of service shows its effect on the index. Evidence: the capture.
REQ-FUNC-046 (P5) Each response drill's times against the rule's limits of 3 and 4 minutes (APT-014), with its record. Acceptance: a drill over the limit shows failed. Evidence: the drill record.
REQ-FUNC-047 (P5) The airport emergency plan (APT-017) on the twin: its grid map, access points and staging areas. Acceptance: the grid drawn on the model. Evidence: the capture.
REQ-FUNC-048 (P5) The training records the ARFF rule requires, each with its due date (APT-008, APT-013). Acceptance: a due item shows on the screen and in the tray. Evidence: the capture.
REQ-FUNC-049 (P5) The storm plan plays as phases (watch, warning, closure, recovery) under the emergency plan's natural disaster procedures (APT-017), against a modelled storm always labelled modelled. Acceptance: an exercise walks the four phases. Evidence: the exercise record.
REQ-FUNC-050 (P5) The aircraft relocation plan: which aircraft leave and which are secured, with the place and the deadline for each. Acceptance: the list exports for tenants. Evidence: the export.
REQ-FUNC-051 (P5) Closures and the NOTAMs each storm phase needs, drafted for a person to file. Acceptance: the closure phase opens its drafts. Evidence: the drafts.
REQ-FUNC-052 (P5) The recovery inspection: every runway, taxiway, light and sign checked before reopening, kept as a special inspection (APT-020). Acceptance: a runway cannot show open before its recovery check. Evidence: the inspection record.
REQ-FUNC-053 (P5) The damage assessment: each item with its photo, place, time and estimate, kept as evidence for disaster funding. Acceptance: the list exports with its photos. Evidence: the export.

### 7.6 Assets, maintenance and pavement (P6)

REQ-FUNC-054 (P6) The asset registry: every asset with its class, place, condition and the system of record that owns it (APT-149). Acceptance: every asset names its owner. Evidence: the registry capture.
REQ-FUNC-055 (P6) Each asset's history: work orders, inspections, condition readings and documents, from the systems that hold them. Acceptance: an asset's history lists items from two systems. Evidence: the capture.
REQ-FUNC-056 (P6) An asset with no owning system or a stale one says so plainly. Acceptance: a stale owner shows on its assets. Evidence: the capture.
REQ-FUNC-057 (P6) Assets by condition and by age against their planned life. Acceptance: the view sorts by remaining life. Evidence: the capture.
REQ-FUNC-058 (P6) Open work orders read from the maintenance system of record, each placed on the airfield, with what raised it (inspection, outage, find, schedule). Acceptance: a work order raised by an inspection links back to it. Evidence: the link.
REQ-FUNC-059 (P6) Preventive maintenance due and overdue against the schedule the maintenance system holds. Acceptance: an overdue item shows overdue. Evidence: the capture.
REQ-FUNC-060 (P6) A work order is closed only in the maintenance system; the twin shows the close on its next reading. Acceptance: no close action exists in the twin. Evidence: the API listing.
REQ-FUNC-061 (P6) Every pavement section on the map coloured by its PCI (APT-083) from the pavement management program (APT-082), with the program's own colour bands. Acceptance: each section shows its PCI and survey date. Evidence: the capture.
REQ-FUNC-062 (P6) Each section's last survey to ASTM D5340 (APT-084), its distresses (APT-086) and its recommended maintenance (APT-085). Acceptance: a section opens its survey and distresses. Evidence: the capture.
REQ-FUNC-063 (P6) The program's inspection schedule and whether it is met (APT-087, APT-088). Acceptance: a section past its schedule shows overdue. Evidence: the schedule check.
REQ-FUNC-064 (P6) The sections whose condition puts them in the capital plan, with their cost range. Acceptance: a section under its trigger appears in the capital plan. Evidence: the link.
REQ-FUNC-065 (P6) Published pavement ratings: each runway's PCR from the FAA record (APT-090) and its PCI as FDOT's statewide program published it (APT-201), kept as the state baseline. Acceptance: both shown with their source and date. Evidence: the capture.

### 7.7 The 3D twin, the flythrough, ground access and open standards (P7)

REQ-FUNC-066 (P7) The airport in three dimensions from the same geometry, with layers for assets, pavement, lighting, construction and wildlife. Acceptance: each layer toggles without reloading. Evidence: captures with each layer.
REQ-FUNC-067 (P7) Selecting a building or pavement area opens its asset record and names its owning system. Acceptance: a click opens the record. Evidence: the capture.
REQ-FUNC-068 (P7) Each information container of the model shows its state (work in progress, shared, published, archived) as ISO 19650 sets them (APT-139). Acceptance: a container moved to published shows so. Evidence: the container record.
REQ-FUNC-069 (P7) Every value the geometry does not carry (heights, interiors) uses test data (carefully crafted and curated test data for common use cases) until a drawing or model supplies it. Acceptance: no unlabelled height. Evidence: the capture.
REQ-FUNC-070 (P7) The flythrough: a camera path over the real footprints, labelled, that pauses at any place to open what the twin knows there. Acceptance: a pause opens the place's records. Evidence: the capture.
REQ-FUNC-071 (P7) Ground access on the same model: I-4, SR 417 (APT-206), the local roads and the SunRail Sanford station (APT-187), from public map data with its credit (APT-188). Acceptance: each line shows its source. Evidence: the capture.
REQ-FUNC-072 (P7) Landside assets (roads, parking, curb) on the same model as the airfield when landside is in scope (AW-29). Acceptance: a landside asset opens its record. Evidence: the capture.
REQ-FUNC-073 (P7) The standards the twin reads and writes listed with body, edition and source: ISO 19650, IFC, CityGML, 3D Tiles, OGC API Features, IndoorGML, GeoPackage, AIXM, AMDB, COBie, AC 150/5300-18B, ISO/IEC 30173 (APT-139 to APT-151, APT-046). Acceptance: each listed with its registry id. Evidence: the capture.
REQ-FUNC-074 (P7) Everything the tenant holds exports in an open format on request (GeoPackage, IFC, CSV). Acceptance: a layer exports and reopens in a standard tool. Evidence: the export.
REQ-FUNC-075 (P7) The standards the RFP names (AW-09) are marked awaiting RFP until the document is read. Acceptance: the list shows the placeholder. Evidence: the capture.

### 7.8 Drones: operations, inspection missions and the cockpit (P8)

REQ-FUNC-076 (P8) Every drone mission over the airfield, each serving a named Part 139 duty (pavement, lighting, FOD, wildlife), with SprayPath's states from draft through checked, selected, released and flown to under review. Acceptance: a mission walked through each state. Evidence: the mission record.
REQ-FUNC-077 (P8) The airport's airspace class and tower hours from the FAA record (APT-161) and the authorization each flight needs (APT-128, APT-129, APT-130, APT-207). Acceptance: the screen shows the class in force at the current time. Evidence: the capture.
REQ-FUNC-078 (P8) Each aircraft's eligibility: maker domicile (APT-191), Florida security tier (APT-192), FCC Covered List status (APT-193), Remote ID (APT-131) and the state's approved list (APT-215). Acceptance: an ineligible aircraft cannot be assigned to a mission. Evidence: the eligibility record.
REQ-FUNC-079 (P8) The response to an unauthorized drone as the emergency plan sets it (APT-134), detection coordinated with the FAA (APT-132), mitigation left to the federal agencies (APT-133). Acceptance: the plan's steps open from an alert. Evidence: the capture.
REQ-FUNC-080 (P8) A mission is planned from a twin asset (a pavement section, a lighting circuit, an apron), its path drawn over the asset. Acceptance: a mission created from a section carries its id. Evidence: the mission record.
REQ-FUNC-081 (P8) The release gate: airspace authorization, tower coordination, NOTAM, weather, crew credentials, Remote ID, runway separation and prohibited equipment (APT-180); each family passes, fails or cannot be evaluated, and the worst result decides (SprayPath's rule). Acceptance: one failing family holds the launch. Evidence: the gate run.
REQ-FUNC-082 (P8) A held launch shows its reasons and what would clear it; a gate run expires after its validity period. Acceptance: an expired run cannot release. Evidence: the gate record.
REQ-FUNC-083 (P8) Release is by a person after a go; one release flies once. Acceptance: a second flight on one release does not start. Evidence: the release record.
REQ-FUNC-084 (P8) Findings return to the asset as evidence, unverified until a person confirms each one; a finding never changes a value a system of record owns (the PCI stays the pavement program's). Acceptance: a confirmed finding updates the distress record only. Evidence: the finding record.
REQ-FUNC-085 (P8) Drone imagery may be attached to a self-inspection record, and the self-inspection is never complete on drone data alone (APT-210). Acceptance: a round with only drone data cannot be closed. Evidence: the inspection record.
REQ-FUNC-086 (P8) The cockpit: one mission large with the others in view, never more aircraft per remote pilot than the waiver the tenant holds, one without a waiver (APT-189, APT-190). Acceptance: a second simultaneous flight without a waiver does not start. Evidence: the cockpit record.
REQ-FUNC-087 (P8) Eye and top-down views over the real geometry, with altitude, speed, battery and Remote ID state on the view. Acceptance: both views render the airfield. Evidence: captures.
REQ-FUNC-088 (P8) First-person detections marked unverified until a person confirms, rejects or acts on them. Acceptance: an unconfirmed detection appears in no total. Evidence: the totals check.
REQ-FUNC-089 (P8) The drone layer is labelled envisioned until the RFP puts drones in scope (AW-29); Florida's drone law bounds what is flown (APT-213, APT-214). Acceptance: the label shows on each drone screen. Evidence: captures.

### 7.9 The funding loop: radar, builder, pipeline and Florida (P9)

REQ-FUNC-090 (P9) Funding Radar: the programs an airport sponsor can draw on, each with its rule, share and source: AIP entitlement and discretionary (APT-093, APT-105, APT-106), the infrastructure law programs (APT-108 to APT-110), passenger facility charges (APT-107), FDOT aviation grants (APT-196, APT-197). Acceptance: each program shows its registry id. Evidence: the capture.
REQ-FUNC-091 (P9) Each capital project is scored against each program from the twin's evidence: strong, weak or missing. Acceptance: a project's score names the evidence behind it. Evidence: the score record.
REQ-FUNC-092 (P9) The capital improvement plan's projects (APT-104) with the condition evidence behind each one. Acceptance: each project links its evidence. Evidence: the capture.
REQ-FUNC-093 (P9) Florida's comprehensive airport infrastructure program (APT-116): the inventory and schedule, the preventive maintenance, the prioritized repair plan and the progress report, kept from the twin's records for the annual certification, records kept 5 years. Acceptance: the year's certification package exports. Evidence: the package.
REQ-FUNC-094 (P9) Real awards appear only as a public record states them, marked as reported (APT-174, APT-175). Acceptance: every award row names its source. Evidence: the capture.
REQ-FUNC-095 (P9) Application Builder: an application's sections built from the twin's records (pavement condition, asset age, outages, findings), each figure with its source and date. Acceptance: every figure in a built section opens its source. Evidence: the section record.
REQ-FUNC-096 (P9) Each section's readiness and the evidence still missing. Acceptance: a missing estimate lowers readiness and is named. Evidence: the capture.
REQ-FUNC-097 (P9) The crosswalk from the project to the ALP (APT-049, APT-101), the capital plan and the environmental process (APT-115). Acceptance: a project not on the ALP is flagged. Evidence: the crosswalk.
REQ-FUNC-098 (P9) The pack version and the source states each application was built from are recorded with it. Acceptance: an application shows its pack and source cycle. Evidence: the application record.
REQ-FUNC-099 (P9) The package exports in the program's format for a person to submit. Acceptance: an export opens in the program's format. Evidence: the export.
REQ-FUNC-100 (P9) Grant Pipeline: every grant from drafting through submitted, awarded, delivering and reporting to closeout, with owners and dates. Acceptance: a grant moved through each stage. Evidence: the pipeline record.
REQ-FUNC-101 (P9) The sponsor assurances an award carries (APT-096, APT-088, APT-098, APT-100, APT-101) and how each is met from the record. Acceptance: each assurance names its evidence. Evidence: the capture.
REQ-FUNC-102 (P9) Required reports are filled from measured results, and each result becomes evidence for the next application. Acceptance: a report section fills from the record. Evidence: the report.
REQ-FUNC-103 (P9) Each award's records are kept for the retention period (APT-181), shown on the award. Acceptance: the retention date shows. Evidence: the award record.

### 7.10 Safety management, accountability and the shift briefing (P10)

REQ-FUNC-104 (P10) The safety reporting system (APT-037): hazards (APT-039) with their risk, place and state. Acceptance: a report creates a hazard on the map. Evidence: the hazard record.
REQ-FUNC-105 (P10) Safety risk management (APT-034): severity and likelihood on the tenant's own matrix, the mitigation recorded, kept for the period 139.301 sets (APT-007). Acceptance: an assessment records its mitigation. Evidence: the SRM record.
REQ-FUNC-106 (P10) Safety assurance (APT-035): the measures, audits and their trend. Acceptance: a measure shows its trend from the records. Evidence: the capture.
REQ-FUNC-107 (P10) Safety promotion (APT-036): training and communication records. Acceptance: training coverage shows from the records. Evidence: the capture.
REQ-FUNC-108 (P10) The SMS implementation plan's deadlines from the rule for the airport's class (APT-038), and the accountable executive (APT-032) named. Acceptance: the deadline shows for the tenant's test. Evidence: the capture.
REQ-FUNC-109 (P10) Each record the rules require, its retention period and how the twin keeps it. Acceptance: each record type names its rule and period. Evidence: the records table.
REQ-FUNC-110 (P10) Sensitive security information (APT-124) and Florida's exempt records (APT-183, APT-184) are marked and kept out of every public view and export. Acceptance: a public export contains none. Evidence: the export check.
REQ-FUNC-111 (P10) A public records request (APT-182) is answered with what can be released and what is exempt, with the reason. Acceptance: a test request yields both lists. Evidence: the response package.
REQ-FUNC-112 (P10) The shift briefing (Municipath's Corridor Anchor, retold): scene by scene, it drives the twin's own screens as it speaks. Acceptance: each scene opens its screen. Evidence: the briefing capture.
REQ-FUNC-113 (P10) The briefing says only figures the screens already show, each with its source and age. Acceptance: every spoken figure matches its screen. Evidence: the figure check.
REQ-FUNC-114 (P10) The briefing proposes each action (a NOTAM draft, a work order, an inspection) and a person confirms it; it never acts on its own. Acceptance: no action runs without a confirmation record. Evidence: the confirmation log.

### 7.11 The platform family, the cloud and the RFP trace (P11)

REQ-FUNC-115 (P11) The platform family: Municipath, Field Twin and SprayPath described by what each repository holds, built or POC only; nothing claimed that a sister does not hold. Acceptance: each claim links its repository file. Evidence: the family record.
REQ-FUNC-116 (P11) What exists toward the hosted service and what is a target, stated plainly on the screen. Acceptance: each item carries built or target. Evidence: the capture.
REQ-FUNC-117 (P11) The Florida state systems the airport sits inside, each with its source (APT-196 to APT-206). Acceptance: each row shows its registry id. Evidence: the capture.
REQ-FUNC-118 (P11) The RFP trace: every placeholder the RFP must fill, where it waits in the kit, and what the listing says, marked unconfirmed (docs/rfp/AWAITING.md). Acceptance: the screen lists all 30 placeholders. Evidence: the capture.
REQ-FUNC-119 (P11) Each requirement traced to its rule and its screen, from this document and poc/screens.json. Acceptance: the trace check passes. Evidence: the check output.

### 7.12 Sanford-specific requirements (awaiting RFP)

None are written. One public fact bears on them: the Board's agenda of 2026-10-06 lists approval of a grant named
Digital Twin (APT-216), and a PTGA for vehicle movement area transponders (APT-217), a likely source. When the RFP arrives, this section takes one requirement per scope item of Attachment C, each with
its RFP page, traced to the general requirements above where one already serves it, as a new id where none does. The
placeholders it waits on: AW-04 (selected systems), AW-05 (their interfaces), AW-06 (deliverables and phases), AW-07
(functional scope), AW-08 (users and roles), AW-09 (standards), AW-11 (hosting and data), AW-12 (support), AW-23 (data
the Authority provides), AW-25 (cybersecurity and SSI), AW-26 (acceptance), AW-29 (drones, simulation, terminal,
landside) and AW-30 (measures of success).

## 8. User Stories

The POC's scenarios are the stories, each across several roles: the morning self-inspection that finds an edge
spall inside hot spot HS 1 and ends in a work order and a NOTAM draft; a lighting outage on the north side of Runway
9L/27R; wading birds at a pond and a strike to report; a construction phase with its closures; a modelled tropical
storm from watch to recovery; a drone pavement survey held by its gate; the Taxiway C application built from
evidence. Each phase's walkthrough plays the stories its phase makes possible.

## 9. Technical Architecture

Web app, API, workers and infrastructure in one repository; the Airport Twin reached through its own interface, as
SprayPath reaches Field Twin.

REQ-ARCH-001 (P1) Monorepo for the web app, the API, the workers and the infrastructure, with a local stack that boots every service in containers from one command. Acceptance: a fresh machine boots the stack and the first screen from the prerequisites script. Evidence: the boot log.
REQ-ARCH-002 (P2) Each source runs through one ingestion path (fetch, validate, map, keep), its runs recorded with counts and errors, retried by policy. Acceptance: a failing run shows its error and its retry. Evidence: the run log.
REQ-ARCH-003 (P7) Every action is the same on the screen, through the API and in the terminal; the API is described in OpenAPI and versioned. Acceptance: the three paths produce the same record for the same action. Evidence: the parity spec.
REQ-ARCH-004 (P11) The platform runs in the cloud across availability zones, multi-tenant, with the serving region shown (a target today, discovery section 17). Acceptance: a zone failure drill keeps the airfield picture live. Evidence: the drill report.
REQ-ARCH-005 (P11) Every account value is a templated variable with a prerequisites script; staging and production deploy from the same templates. Acceptance: a fresh account deploys from the script. Evidence: the deploy log.
REQ-ARCH-006 (P8) Drone data (images, logs, detections) is stored in the United States only (APT-195). Acceptance: the storage location check shows US regions only. Evidence: the configuration export.

## 10. Data Model

Tenants, packs and their versions, sources and probes, features of the airfield, assets, inspections, findings,
NOTAM drafts, work order links, pavement sections and surveys, missions and flights, hazards, programs, applications,
awards, artefacts, the trail. Every table tenant-scoped, every record versioned.

REQ-DATA-001 (P1) Every table carries the tenant and is isolated by row-level security; the app connects as a role that cannot bypass it (SprayPath's pattern). Acceptance: a cross-tenant read fails in the integration spec. Evidence: the RLS spec.
REQ-DATA-002 (P1) Records are append-only and versioned; nothing operational is updated in place or deleted inside its retention period (APT-007, APT-181). Acceptance: an update writes a new version and keeps the old. Evidence: the versioning spec.
REQ-DATA-003 (P3) Airfield features keep their source (GIS, NASR, OSM stand-in), their survey date and their accuracy class (APT-045). Acceptance: every feature shows its source and date. Evidence: the feature table check.
REQ-DATA-004 (P6) Assets are keyed to their owning system's identifier; the twin's own id never replaces it. Acceptance: every asset carries its owner's key. Evidence: the key check.
REQ-DATA-005 (P10) An append-only trail of every action with who and when, kept for the retention period. Acceptance: no action without its trail entry. Evidence: the trail check.
REQ-DATA-006 (P2) Data the Authority provides for the implementation (AW-23) loads through Intake and is verified before it counts. Acceptance: the first delivered set loads with its checks. Evidence: the Intake record.

## 11. Integration Requirements

Each system of record and public source speaks its own interface through the registry (P2).

REQ-INT-001 (P2) The FAA airport master record (NASR) is read each 28-day cycle (APT-048). Acceptance: the cycle loads and its diff shows. Evidence: the run log.
REQ-INT-002 (P3) NOTAMs are read from the FAA NOTAM system under its access terms (APT-063); drafts go to a person for NOTAM Manager (APT-064). Acceptance: a read returns the airport's NOTAMs. Evidence: the read record.
REQ-INT-003 (P3) The airport GIS is read to AC 150/5300-18B (APT-046) and kept in step with the ALP (APT-049, APT-050). Acceptance: a GIS layer loads with its metadata. Evidence: the run log.
REQ-INT-004 (P6) The maintenance system of record: work orders and preventive maintenance read, and new work orders written through its own interface on an approved path (AW-05). Acceptance: a round trip of one work order. Evidence: the round-trip record.
REQ-INT-005 (P6) The pavement management program's sections and surveys are read (APT-082); FDOT's published runway PCI is read as the state baseline (APT-201). Acceptance: both load with their dates. Evidence: the run log.
REQ-INT-006 (P4) The lighting control and monitoring system's circuit states are read (APT-076). Acceptance: a state change appears within its freshness target. Evidence: the run log.
REQ-INT-007 (P4) Strike reports are drafted in the FAA form for the national database (APT-137). Acceptance: a draft validates against the form. Evidence: the draft.
REQ-INT-008 (P7) Models and drawings are read and written in IFC (APT-140) and site data in CityGML (APT-141) and 3D Tiles (APT-142), as the RFP names them (AW-09). Acceptance: a model round-trips. Evidence: the export and import.
REQ-INT-009 (P9) The FDOT aviation side: projects in JACIP (APT-199) and the Florida Aviation Database (APT-200) are read where FDOT gives access; grant agreements are PTGAs (APT-196). Acceptance: a project's FDOT record links to its twin project. Evidence: the link.

## 12. Security Requirements

REQ-SEC-001 (P1) Sign-in through the tenant's identity provider (OIDC) with roles per tenant; no shared accounts. Acceptance: a user of one tenant cannot open another's screens. Evidence: the auth spec.
REQ-SEC-002 (P2) Each source's credentials are held in the platform's secret store by reference, never in a source record; a missing secret blocks activation. Acceptance: a source with an unresolved secret stays inactive. Evidence: the activation check.
REQ-SEC-003 (P2) SSI handling (APT-123 to APT-126): marked, need to know, safeguarded, and the security systems source stays blocked until the tenant and TSA rules for it are settled. Acceptance: an SSI record is unreadable to a user without need to know. Evidence: the access log.
REQ-SEC-004 (P10) Florida's exempt records (APT-183, APT-184) are restricted; the twin's integration map is cybersecurity information seen by administrators only. Acceptance: a non-administrator cannot open the map. Evidence: the access log.
REQ-SEC-005 (P11) Built to the NIST Cybersecurity Framework (APT-185) and the digital twin security guidance (APT-153); the tenant's own rules are AW-25. Acceptance: the control mapping complete for the deployed stack. Evidence: the control map.
REQ-SEC-006 (P11) Backups are encrypted and restored in a drill; keys are per environment. Acceptance: a restore drill passes. Evidence: the drill report.

## 13. Performance Requirements

REQ-PERF-001 (P3) Airfield Now opens in under 2.5 s on a mid-range laptop and updates states every 10 s without a reload. Acceptance: measured in the phase's perf run. Evidence: the perf report.
REQ-PERF-002 (P7) The 3D view opens the whole airport in under 4 s and holds 30 frames a second on a mid-range laptop. Acceptance: measured in the phase's perf run. Evidence: the perf report.
REQ-PERF-003 (P7) The API answers reads at p95 under 150 ms. Acceptance: measured in the phase's perf run. Evidence: the perf report.
REQ-PERF-004 (P11) Availability of 99.9% or better for the airfield picture over 30 days, measured and shown (the RFP's service levels are AW-12). Acceptance: the measure shown on the family screen. Evidence: the availability report.

## 14. Scalability Requirements

Scale is an airport, then several airports in one state, then another state: tenants and packs are added without
code. A Part 139 Class I airport of SFB's size (four runways, APT-156 to APT-159) is the design case.

## 15. User Interface Requirements

The house UI directive (Cockpit for operations, Instrument for records, Companion for the inspector's tablet), Tower
Night dark by default.

REQ-UI-001 (P1) The design system: every colour, size, radius and duration is a token; three house schemes (Tower Night, Apron, Federal Blue), each in light and dark. Acceptance: the token check finds no literal; every screen captured in 3 schemes and 2 modes. Evidence: the token check output and captures.
REQ-UI-002 (P1) The status language is fixed whatever the look: open green, caution yellow, closed red, construction orange, unavailable grey, modelled purple, always with a word, never colour alone. Acceptance: every status carries its word. Evidence: the design review.
REQ-UI-003 (P1) Airfield signs drawn on the model follow the sign standard's colours (APT-079). Acceptance: a mandatory sign drawn red with white text. Evidence: the capture.
REQ-UI-004 (P1) A tenant palette that fails WCAG 2.1 AA contrast is not applied to text and a compliant shade is derived (APT-179). Acceptance: a 2.9:1 accent is replaced for text and its derived shade passes. Evidence: the contrast check output.
REQ-UI-005 (P1) Every screen shows its state honestly: loading, empty, stale with its age, unavailable with the reason, offline, error with what to do; never demo data, never a blank. Acceptance: each state provoked on the first screens. Evidence: captures of each state.
REQ-UI-006 (P1) Lamps pulse only while the thing they stand for is live; every animation stops under reduced motion. Acceptance: with reduced motion on, nothing moves. Evidence: the motion spec.
REQ-UI-007 (P1) Anything modelled, illustrative or envisioned says so on the screen where it appears. Acceptance: a search of the screens finds no unlabelled modelled value. Evidence: the label check.

## 16. Mobile Requirements

REQ-UI-008 (P4) The self-inspection runs on a tablet in the field, offline, and syncs when back in coverage, each entry with its time and place. Acceptance: a round recorded offline syncs in order. Evidence: the sync test.
REQ-UI-009 (P8) The drone crew's checklist and the gate result open on a tablet at the launch point. Acceptance: the gate shows on the tablet. Evidence: the capture.

## 17. API Requirements

Every action is available on the screen, through the API and in the terminal (section 9, P7); the API is described in
OpenAPI and versioned; no API exists to file a NOTAM, close a work order or command a drone (see
requirements REQ-FUNC-026, REQ-FUNC-060 and REQ-FUNC-083).

## 18. Compliance Requirements

Each rule cites its registry term; the Accountability and Records screen (P10) shows how each is met.

REQ-COMP-001 (P2) No covered telecommunications or video surveillance equipment is accepted as a source (APT-180); each device class is checked when connected. Acceptance: a covered make does not connect and the rule is shown. Evidence: the check record.
REQ-COMP-002 (P4) Part 139 terms and categories are used as the rule writes them, so the screens read the way an FAA inspector reads (APT-001 to APT-030). Acceptance: an airport certification specialist's review of the operate screens finds no unfamiliar term. Evidence: the review notes.
REQ-COMP-003 (P9) Grant records follow the uniform guidance as FAA applies it (APT-114), Buy American (APT-111) and DBE reporting (APT-112) where the award carries them; the RFP's own funding clauses are AW-21. Acceptance: an award's compliance list complete at its deadline. Evidence: the award record.
REQ-COMP-004 (P8) Drone use follows Part 107 (APT-127, APT-128, APT-189, APT-207, APT-208) and Florida's drone law (APT-191, APT-192, APT-213 to APT-215); a mission outside them is not released. Acceptance: a mission in Class C without its authorization record holds. Evidence: the gate run.
REQ-COMP-005 (P10) Accessibility to WCAG 2.1 AA for every screen (APT-179). Acceptance: an automated and a manual audit pass. Evidence: the audit report.
REQ-COMP-006 (P10) Information shown or released carries its source, time, method and age; modelled values said as modelled. Acceptance: a sample of 50 values each carries all four. Evidence: the sample check.

## 19. Testing Strategy

Every phase ends with a walkthrough on real public data (NASR, FDOT's published PCI, public map data) and records made
in the run; the last phase runs them all on the deployed app. The RFP's acceptance criteria are AW-26.

REQ-TEST-001 (P1) Each phase ends with a walkthrough of its screens, captured in the default scheme and in light, judged against the UI directive; a phase whose screens fail is not done. Acceptance: the phase's design review passes. Evidence: the captures and the review record.
REQ-TEST-002 (P1) The POC (poc/index.html, stellarview-poc/1) is the screen brief: every must-do item is traced to a requirement id of this document. Acceptance: staging/e1-airfieldpath/check.py passes. Evidence: the check output.
REQ-TEST-003 (P2) A walkthrough: NASR and one other source registered, probed, licensed, approved and activated by two people; a source cut off and shown stale. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-004 (P3) A walkthrough of Airfield Now on real NASR data: the runways, a condition, a NOTAM drafted and its cancellation. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-005 (P4) A walkthrough: a self-inspection round with a finding routed to a work order and a NOTAM draft; an outage; a strike drafted. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-006 (P5) A walkthrough: a drill timed against the rule; a storm exercise through its four phases, labelled modelled. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-007 (P6) A walkthrough: an asset's history from two systems; pavement sections with their surveys beside FDOT's runway PCI. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-008 (P7) A walkthrough: the 3D view, the flythrough paused on a place, a layer exported to GeoPackage and reopened. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-009 (P8) A walkthrough: a mission planned from a section, held by its gate, cleared, released, flown in a simulator, its findings confirmed. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-010 (P9) A walkthrough: a project scored on the radar, an application built from evidence to export, an award tracked and a report filled. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-011 (P10) A walkthrough: a hazard assessed, a records request answered with its exemptions, a shift briefing confirmed scene by scene. Acceptance: runs without a stub. Evidence: the walkthrough capture.
REQ-TEST-012 (P11) The first flight: the whole platform deployed and every phase's walkthrough run against the deployed app. Acceptance: all walkthroughs pass on the deployed app. Evidence: the walkthrough reports.

## 20. Deployment Strategy

Local containers, then a staging cloud deployment, then production (P11). Every account value is a templated variable
with a prerequisites script. The hosting model the RFP sets is AW-11.

## 21. Maintenance & Support

Packs are versioned and released; tenants move on purpose. Each source's state is watched on Systems of Record; a
quiet one is shown, never filled. Support hours, service levels, training, documentation and the contract term are
AW-12, AW-20 and AW-24.

## 22. Success Metrics

Every runway, taxiway and apron with a state from its owning system; one self-inspection with its discrepancies
routed and closed in the maintenance system; every pavement section with its PCI and next action; one capital plan
line and one application section generated from the records (discovery section 8). The Authority's own measures are
AW-30.

## 23. Risk Assessment

| Gap | Class | What is open | Holds |
|-|-|-|-|
| GAP-E1-02 | client | The RFP document itself: all 30 placeholders of docs/rfp/AWAITING.md | section 7.12 |
| GAP-E1-03 | platform | No sister platform is live in a cloud; the hosted service is a target (discovery section 17) | P11 |
| GAP-E1-04 | research | FAA NOTAM system access terms for a read-only consumer (APT-063) | REQ-INT-002 |
| GAP-E1-05 | research | FAA 5010 operations and based aircraft counts: removed from NASR in 2024; the ADIP API needs an authorization | the operations tiles |
| GAP-E1-06 | domain | Whether the Authority is a "special district government" under 28 CFR 35.104, setting its ADA date at April 26, 2028 (APT-179) | REQ-COMP-005 dates |
| GAP-E1-07 | domain | Whether Rule 60GG-2.0075 and Fla. Stat. 934.50(7) reach the Authority as a governmental agency (APT-192, APT-215) | REQ-FUNC-078 |
| GAP-E1-08 | client | Business model and pricing (licence per airport with services) | section 2 |
| GAP-E1-09 | research | SFB's SIS designation: read from a handbook map, to confirm on FDOT's SIS map (APT-203) | the family screen |
| GAP-E1-10 | domain | Drones: one-to-many waivers and proposed Part 108 (APT-190, APT-194); no FAA design standard for a small-drone dock | REQ-FUNC-086, the drone station |
| GAP-E1-11 | research | FY2026 AIP grant to SFB: reported by an aggregator and the press, not reconciled with an FAA record (seed note) | the awards table |
| GAP-E1-12 | domain | Expert review of the registry by an airport certification specialist, an airport engineer and Florida counsel (expertReviewStatus required) | production use of the registry |
| GAP-E1-13 | client | Trademark clearance of the mark | the mark on public material |

## 24. Implementation Timeline

Sized as Municipath E1 was, from SprayPath E1's measured rates: 41.5 minutes of wall clock a unit likely, 27.6 low,
57.0 high. Each phase: its ids divided by 1.35 ids a unit, rounded up, plus one capture unit. The RFP's schedule is
AW-01, AW-06 and AW-22.

| Phase | ids | units |
|-|-|-|
| P1 | 23 | 19 |
| P2 | 17 | 14 |
| P3 | 15 | 13 |
| P4 | 19 | 16 |
| P5 | 10 | 9 |
| P6 | 16 | 13 |
| P7 | 15 | 13 |
| P8 | 18 | 15 |
| P9 | 17 | 14 |
| P10 | 16 | 13 |
| P11 | 11 | 10 |
| total | 177 | 149 |

| | per unit (wall) | 149 units |
|-|-|-|
| low: phases 7 to 12 rate | 27.6 min | 68.5 h |
| likely: late-phase rate | 41.5 min | 103.1 h |
| high: late-phase 75th percentile | 57.0 min | 141.6 h |

The figures rest on one engagement's measures and do not count stops for account limits.

## 25. Big Bang Epic Spec

### 25.1 The epic

One epic: **Airfieldpath E1**, repository `sanford-twin`. Not a constellation: the Airport Twin is reached through its
interface. 11 phases, under the cap of 16.

### 25.2 The phases

**P1. Design system, shell, the organization as tenant, the FAA and Florida pack.** Needs nothing earlier; the OIDC provider. Screens: the shell on every screen.
Delivers: REQ-FUNC-001, REQ-FUNC-002, REQ-FUNC-003, REQ-FUNC-004, REQ-FUNC-005, REQ-FUNC-006, REQ-FUNC-007, REQ-FUNC-008, REQ-FUNC-009, REQ-FUNC-010, REQ-UI-001, REQ-UI-002, REQ-UI-003, REQ-UI-004, REQ-UI-005, REQ-UI-006, REQ-UI-007, REQ-ARCH-001, REQ-DATA-001, REQ-DATA-002, REQ-SEC-001, REQ-TEST-001, REQ-TEST-002.
Acceptance: a tenant signs in and sees the app as itself in three schemes, light and dark; the pack's first version with its sources.

**P2. Systems of record: the source registry and Intake.** Needs P1. Screens: Systems of Record; Intake.
Delivers: REQ-FUNC-011, REQ-FUNC-012, REQ-FUNC-013, REQ-FUNC-014, REQ-FUNC-015, REQ-FUNC-016, REQ-FUNC-017, REQ-FUNC-018, REQ-FUNC-019, REQ-FUNC-020, REQ-ARCH-002, REQ-DATA-006, REQ-INT-001, REQ-SEC-002, REQ-SEC-003, REQ-COMP-001, REQ-TEST-003.
Acceptance: NASR active through probe, licence and two people; a source cut off and shown stale; an SSI document restricted on arrival.

**P3. Airfield Now: the airfield model, conditions and NOTAMs.** Needs P2. Screens: Airfield Now; Condition and NOTAMs.
Delivers: REQ-FUNC-021, REQ-FUNC-022, REQ-FUNC-023, REQ-FUNC-024, REQ-FUNC-025, REQ-FUNC-026, REQ-FUNC-027, REQ-FUNC-028, REQ-FUNC-029, REQ-FUNC-030, REQ-DATA-003, REQ-INT-002, REQ-INT-003, REQ-PERF-001, REQ-TEST-004.
Acceptance: the airfield live from NASR with its states; a NOTAM drafted, filed by a person and its cancellation closing the condition.

**P4. Part 139 operations: self-inspection, lighting, wildlife and FOD, construction safety.** Needs P3; the maintenance system's interface (AW-05). Screens: Self-Inspection; Airfield Lighting; Wildlife and FOD; Construction Safety.
Delivers: REQ-FUNC-031, REQ-FUNC-032, REQ-FUNC-033, REQ-FUNC-034, REQ-FUNC-035, REQ-FUNC-036, REQ-FUNC-037, REQ-FUNC-038, REQ-FUNC-039, REQ-FUNC-040, REQ-FUNC-041, REQ-FUNC-042, REQ-FUNC-043, REQ-FUNC-044, REQ-INT-006, REQ-INT-007, REQ-UI-008, REQ-COMP-002, REQ-TEST-005.
Acceptance: a round on a tablet with a finding routed to a work order and a draft; an outage routed; a strike drafted.

**P5. ARFF, the emergency plan and the storm plan.** Needs P3, P4. Screens: ARFF and the Emergency Plan; Storm Plan.
Delivers: REQ-FUNC-045, REQ-FUNC-046, REQ-FUNC-047, REQ-FUNC-048, REQ-FUNC-049, REQ-FUNC-050, REQ-FUNC-051, REQ-FUNC-052, REQ-FUNC-053, REQ-TEST-006.
Acceptance: a drill timed against 3 and 4 minutes; a storm exercise through its four phases, labelled modelled.

**P6. Assets, maintenance and pavement.** Needs P2, P4; the pavement program's data (AW-05). Screens: Asset Registry; Maintenance and Work Orders; Pavement.
Delivers: REQ-FUNC-054, REQ-FUNC-055, REQ-FUNC-056, REQ-FUNC-057, REQ-FUNC-058, REQ-FUNC-059, REQ-FUNC-060, REQ-FUNC-061, REQ-FUNC-062, REQ-FUNC-063, REQ-FUNC-064, REQ-FUNC-065, REQ-DATA-004, REQ-INT-004, REQ-INT-005, REQ-TEST-007.
Acceptance: an asset's history from two systems; a work order round trip; pavement sections beside FDOT's runway PCI.

**P7. The 3D twin, the flythrough, ground access and open standards.** Needs P3, P6. Screens: The Airport in 3D; Flythrough and Ground Access; Open Standards.
Delivers: REQ-FUNC-066, REQ-FUNC-067, REQ-FUNC-068, REQ-FUNC-069, REQ-FUNC-070, REQ-FUNC-071, REQ-FUNC-072, REQ-FUNC-073, REQ-FUNC-074, REQ-FUNC-075, REQ-ARCH-003, REQ-INT-008, REQ-PERF-002, REQ-PERF-003, REQ-TEST-008.
Acceptance: the 3D view and flythrough on the real footprints; a layer exported and reopened; the same action on screen, API and terminal.

**P8. Drones: operations, inspection missions and the cockpit.** Needs P3, P6; an aircraft that meets the eligibility rules; a simulator. Screens: Drone Operations; Inspection Mission; Drone Cockpit.
Delivers: REQ-FUNC-076, REQ-FUNC-077, REQ-FUNC-078, REQ-FUNC-079, REQ-FUNC-080, REQ-FUNC-081, REQ-FUNC-082, REQ-FUNC-083, REQ-FUNC-084, REQ-FUNC-085, REQ-FUNC-086, REQ-FUNC-087, REQ-FUNC-088, REQ-FUNC-089, REQ-ARCH-006, REQ-UI-009, REQ-COMP-004, REQ-TEST-009.
Acceptance: a mission from a section held by its gate, cleared, released once, flown in a simulator, its findings confirmed onto the section.

**P9. The funding loop: radar, builder, pipeline and Florida.** Needs P6 (evidence). Screens: Funding Radar; Application Builder; Grant Pipeline.
Delivers: REQ-FUNC-090, REQ-FUNC-091, REQ-FUNC-092, REQ-FUNC-093, REQ-FUNC-094, REQ-FUNC-095, REQ-FUNC-096, REQ-FUNC-097, REQ-FUNC-098, REQ-FUNC-099, REQ-FUNC-100, REQ-FUNC-101, REQ-FUNC-102, REQ-FUNC-103, REQ-INT-009, REQ-COMP-003, REQ-TEST-010.
Acceptance: the Taxiway C application built from evidence to export; an award tracked and a report filled; the Florida certification package exported.

**P10. Safety management, accountability and the shift briefing.** Needs P4, P6. Screens: Safety Management; Accountability and Records; Operations Briefing.
Delivers: REQ-FUNC-104, REQ-FUNC-105, REQ-FUNC-106, REQ-FUNC-107, REQ-FUNC-108, REQ-FUNC-109, REQ-FUNC-110, REQ-FUNC-111, REQ-FUNC-112, REQ-FUNC-113, REQ-FUNC-114, REQ-DATA-005, REQ-SEC-004, REQ-COMP-005, REQ-COMP-006, REQ-TEST-011.
Acceptance: a hazard assessed; a records request answered with its exemptions; a briefing confirmed scene by scene.

**P11. The platform family, the cloud and the RFP trace, tested on the deployed app.** Needs every earlier phase. Screens: Platform Family; RFP Trace.
Delivers: REQ-FUNC-115, REQ-FUNC-116, REQ-FUNC-117, REQ-FUNC-118, REQ-FUNC-119, REQ-ARCH-004, REQ-ARCH-005, REQ-SEC-005, REQ-SEC-006, REQ-PERF-004, REQ-TEST-012.
Acceptance: the platform deployed; a failover and a restore drill passed; every walkthrough run against the deployed app.

### 25.3 Coverage

| Source | Phase | Left for E2, and why |
|-|-|-|
| Discovery principles 1 to 10 | all | none |
| POC, 27 screens, 122 must-do items (each carries its ids in poc/screens.json) | P1 to P11 | none |
| Sanford's RFP scope (Attachment C) | section 7.12 | every item, awaiting RFP |
| A drone station on the airfield (Municipath's Hive, NSB's drone airport) | none | E2: no FAA design standard; a design proposal first |
| One pilot flying several drones | P8 holds to one | E2: needs a 107.35 waiver the Authority holds |
| The terminal interior (IndoorGML) | P7 lists the standard | E2: awaiting RFP (AW-29) |

### 25.4 Seed data

No demo data, by policy. Each walkthrough runs on real public data (NASR, FDOT's published runway PCI, public map data,
the FAA's grant records) and on records made through the app during the run. Anything modelled is labelled modelled;
anything illustrative appears only in the POC, which says so on every screen and keeps it in poc/seed/illustrative.json.
