Florida
This page renders the canonical Florida Atlas jurisdiction package. The canonical files remain the source of truth; this document is a structured rendering only.
1. Topology Metadata
Classification source. The metadata layer records that this metadata is derived from atlas.md and records Atlas corridor-topology placement only.
Interpretation boundary. The metadata layer records that this file is structural topology metadata only. It does not assign routing authority, Atlas surfaces, readiness, rank jurisdictions, modify evidence-layer interpretation, override evidence gaps, or infer deployment suitability.
2. Scope Boundary Statement
The evidence layer states that this file records only evidence-supported characteristics documented for Florida that are relevant to Atlas normalization. The evidence layer states that it does not assign trust posture, routing role, coordination tier, or Atlas surfaces.
This rendering mirrors the canonical package. It does not introduce analysis, rankings, readiness assessment, national role, leadership positioning, or deployment prescription beyond the canonical files. Surface assignment remains unset. No routing role is assigned.
3. Evidence Summary
The evidence layer documents the following for Florida.
Municipal Bitcoin experimentation and conference visibility
Sources cited by evidence.md: City of Miami public Bitcoin experimentation initiatives (2021–2023); recurring international Bitcoin conferences hosted in Miami.
Executive positioning and regulatory absence signals
Sources cited by evidence.md: public executive-branch positioning opposing federally issued retail CBDC deployment within Florida; comparative review of U.S. digital asset licensing regimes; comparative biometric regulation analysis across U.S. states; comparative state AI regulatory review.
Fintech corridor, migration, and international-connectivity structure
Sources cited by evidence.md: regional venture activity and institutional relocation patterns; post-2020 migration patterns across U.S. technology sectors; regional infrastructure and financial corridor mapping.
Municipal policy variability
Sources cited by evidence.md: comparative municipal infrastructure policy review within Florida.
4. Signals Summary
Derivation constraint. The signals layer records that signals derive strictly from evidence.md and that absence of signals reflects absence of normalized documentary coverage.
Method. The signals layer records that these signals are derived only from the evidence recorded in evidence.md.
5. Trust Dimensions Summary
Derivation constraint. The trust-dimensions layer records that dimensions derive strictly from signals.md and that absence of signals reflects absence of normalized signal-layer coverage.
Method. The trust-dimensions layer evaluates stability characteristics only, using only structures documented in evidence.md and signals.md. The trust-dimensions layer records that it does not assign routing role, coordination tier, Atlas surface, national significance, or leadership position.
6. Profile Summary
Derivation constraint. The profile layer records that profile content derives strictly from evidence.md, signals.md, and trust-dimensions.md.
7. Builder Mode Summary
Derivation constraint. The builder-mode layer records that builder-mode content derives strictly from normalized jurisdiction layers.
Scope. The builder-mode layer describes coverage limits, observed structural visibility, and known ecosystem signals. It does not describe deployment recommendations, operational guidance, or strategy.
Interpretive read
The builder-mode layer records that Florida reads as a municipally uneven jurisdiction where Miami-centered Bitcoin experimentation, executive positioning, and South Florida fintech corridor growth appear together, while statewide coverage remains incomplete.
Municipal experimentation pattern — observed structural visibility
The builder-mode layer records that the strongest documented experimentation pattern is metropolitan rather than statewide. The builder-mode layer records that Miami appears in the package as the clearest municipal Bitcoin experimentation node, while the evidence also states that deployment conditions vary across cities.
Executive and regulatory pattern — observed structural visibility
The builder-mode layer records executive resistance to mandatory CBDC integration and multiple comparative-regime absences, including no specialized digital asset licensing expansion, no Illinois-style biometric privacy regime, and no statewide AI licensing or certification requirements in the current evidence set.
Corridor pattern — observed structural visibility
The builder-mode layer records South Florida fintech growth, cross-border payment experimentation, Latin America-facing financial-services integration, migration of developers and venture-backed teams, and broader metropolitan and port-connected institutional density.
Statewide-coverage limits — observed structural visibility
The builder-mode layer records that the package is stronger on Miami-centered experimentation, South Florida corridor growth, and comparative-regime absence signals than on statewide municipal mapping, digital-infrastructure concentration, or full statewide AI-governance coverage.
8. Structural Exclusions
The canonical package records that the Florida package does not support characterizing Florida as any of the following:
- a custody-regime jurisdiction
- a DAO-wrapper jurisdiction
- a national routing spine
- a federal hosting corridor
- a frontier-model AI ecosystem anchor
- a hyperscale compute corridor
- a major Internet exchange concentration environment
- a comprehensively evidenced statewide data-center corridor
The canonical package records that it does not assign trust posture, routing role, coordination tier, Atlas surfaces, national significance, leadership positioning, readiness status, or ranking outcome. It does not prescribe deployment decisions.
9. Evidence Gaps
The canonical package records the following evidence gaps for Florida.
The canonical package records gap inheritance: signals.md, trust-dimensions.md, profile.md, and builder-mode.md inherit these evidence gaps without expansion. change-log.md records that inheritance rule and does not create a new evidence-gap set.
10. Change-Log Notes & Normalization Notes
Normalization procedure
- The change-log records that evidence.md was prepared as the base evidence layer for the Florida package.
- The change-log records that signals.md was derived strictly from evidence.md.
- The change-log records that trust-dimensions.md was derived from evidence.md and signals.md, and was constrained to stability-characteristic evaluation only.
- The change-log records that profile.md was derived from evidence.md, signals.md, and trust-dimensions.md, and was constrained to structural characterization only.
- The change-log records that builder-mode.md was derived from all prior Florida layers, and was constrained to interpretive guidance only.
- The change-log records that change-log.md records this normalization workflow only.
Structural exclusions (change-log attestation)
- The change-log records that structural exclusions were added and preserved in evidence.md and carried forward into downstream Florida layers based strictly on absent evidence in the upstream materials.
- The change-log records that no layer assigns routing role, coordination tier, Atlas surface, national significance, leadership positioning, readiness status, or ranking outcome.
- The change-log records: Surface assignment status: none.
Gap inheritance
- The change-log records that evidence.md established the Florida evidence-gap set.
- The change-log records that signals.md, trust-dimensions.md, profile.md, and builder-mode.md inherit those evidence gaps without expanding beyond the established evidence-gap set.
- The change-log records that change-log.md records that inheritance rule and does not create a new evidence-gap set.
Lens alignment confirmation
- The change-log records that Florida's package remains centered on the jurisdiction lens supported by the existing evidence set.
- The change-log records that legacy classification, routing, readiness, ranking, and deployment-prescription language was removed or rewritten where needed to maintain evidence-bounded normalization.
Normalization adjustments
- The change-log records that the evidence title was normalized to "# Florida — Evidence Layer".
- The change-log records that evidence content was reorganized into evidence-layer sections without adding new evidence.
- The change-log records that downstream files were rewritten into contract-compliant method, exclusions, and evidence-gap structures.
- The change-log records that trust, profile, and builder layers were aligned to inherit evidence gaps and to avoid surface or routing assignment.
Completion confirmation
The change-log records that Florida jurisdiction package normalization is complete for:
jurisdictions/us/states/florida/evidence.mdjurisdictions/us/states/florida/signals.mdjurisdictions/us/states/florida/trust-dimensions.mdjurisdictions/us/states/florida/profile.mdjurisdictions/us/states/florida/builder-mode.mdjurisdictions/us/states/florida/change-log.md
Topology metadata attachment
The change-log records that metadata.md was added using atlas.md corridor narrative fields: Corridor Group, Foundation Layer, Topology Completion Layer. The change-log records that this metadata is structural only and does not alter evidence, signals, trust interpretation, profile, builder-mode, or surface neutrality.