HEART Cities
Designation record
Designation requires a competent local authority, defined geographic and system scope, affected populations, current local Source Profiles, applicable Domain Profiles, one or more Deployment Profiles, Seven Axiom and remedy analysis, evidence and data plans, professional and assurance arrangements, fiscal and anti-capture controls, public status, and any federation delegations.
An incomplete initiative may be described as a HEART City candidate or municipal HEART pilot only when its gaps are stated. It must not claim designation.
Separate but composable records
| Record | Governing responsibility |
|---|---|
| Local Authority Record | Who authorized what, through which instrument and limits. |
| Local Source Profile Set | Applicable law, policy, procurement, contract, and other source authority. |
| Deployment Profile Set | Each covered system class, service, use, and operating context. |
| Domain Profile Composition | Domain safeguards, evidence, competence, and conflicts. |
| Affected-Person and Remedy Plan | Notice, participation, challenge, human review, remedy, accessibility, and non-retaliation. |
| Evidence and Data Plan | Verifiable Conditions, provenance, access, retention, privacy, security, and disclosure. |
| Professional and Assurance Plan | Guardian scope, independence, assessment route, HVC, and Registry boundaries. |
| Federation Delegation Schedule | Every delegated function, owner, limit, funding term, review, and revocation route. |
| Fiscal and Anti-Capture Record | Budget, restricted funding, related parties, conflicts, and continuity. |
| Public Status Record | Current scope, limitations, material changes, and designation state. |
These records may share one controlled package, but a summary cannot silently replace their distinct responsibilities.
Authority remains local and bounded
The city or other competent body retains lawful policy and coercive authority. HEART supplies trust architecture; it does not become the government. The Foundation stewards shared canon but does not automatically become deployer, assessor, credential issuer, or local operator.
An RFE is optional. Formation alone confers no assessment, credential, Registry, legal, or funding authority. Unlisted powers are not delegated.
Current status boundary
No operational HEART City has validated this architecture, and no city is represented here as designated. Claims of reduced harm, improved trust, lower cost, regulatory compliance, or superior governance require their own evidence.