Fridai technology name registry

This is the bootstrap view of the global Fridai technology-name registry, created with the first application of the Fridai-wide naming standard. It records product/system airport aliases and canonical identifiers across the estate. As the corporate knowledge graph or service catalog becomes the live registry, this Git-controlled record remains an auditable knowledge source.

Candidate ideas are separated from allocated names so brainstorming does not silently become production configuration. Component artifacts—APIs, workers, daemons, packages, stores, queues, and jobs—belong to an allocated boundary and do not automatically receive their own airport alias.

Allocated

YQA notes

• YQA is Muskoka Airport’s IATA code (CYQA ICAO).
• Sanctuary is a Fridai metaphor for a quiet, internal knowledge-review and stewardship capability. It does not assert that the airport itself is an FBO.

YQA registry record

The unassigned fields are explicit RC promotion blockers, not implicit defaults. They must be resolved before this record becomes active.

Fridai Organization Infrastructure as Code — Cloudflare

This infrastructure repository does not receive an airport alias. org precedes the iac domain because it scopes the entire organization-level capability; cf then identifies the provider controlled by that capability.

Existing external allocation referenced by this project

YYZ is recorded here only to prevent collision. Its canonical registry remains in the YYZ project; this repository does not own or modify it.

Candidate catalog

These entries preserve the original naming stream but are not reservations. Each needs a real workload, owner, collision check, and migration-cost review before moving to Allocated.

Rejected or tombstoned