# AI Freedom Trust Federation Organization Map

AI Freedom Trust Federation should be organized as an umbrella with clear repository roles, maturity levels, and public expectations.

## Umbrella Layers

### 1. Public Trust Layer

Purpose: define the public mission, governance posture, repository standards, and visible project map.

Primary repository:

- `www.aifreedomtrust.com` - canonical public website and public-facing organization portal

Supporting repository:

- `AIFT-Forge` - profile, templates, doctrine, coordination patterns, and shared operating language

### 2. Infrastructure Layer

Purpose: build the technical foundation for sovereign automation, app hosting, provider nodes, naming, routing, deployment, and decentralized cloud workflows.

Primary repository:

- `VPS` - AIFT Cloud App Foundry, decentralized VPS, app builder, provider network, registry foundations, and deployment tooling

### 3. Applied Systems Layer

Purpose: prove the infrastructure and operating model through practical public services and real customer workflows.

Primary repository:

- `capital-city-provisions` - premium provisions business site, concierge flow, customer quote capture, route review, and operational tooling

### 4. Stewardship and Value Layer

Purpose: explore wallets, regenerative value, cryptographic trust interfaces, datasets, research models, and long-range federation experiments.

Primary repository:

- `Aether_Coin_biozonecurrency` - Aetherion wallet, regenerative value protocol, and AI-guided digital stewardship

Supporting / local work:

- `TheMindofAll` - local research/model workspace currently present on this machine

### 5. Incubation, Secondary, and Legacy Layer

Purpose: keep experiments visible without confusing them for active federation priorities.

Repositories:

- `biozone-harmony-boost` - older Lovable-generated TypeScript template; keep as incubating or archive after review
- `chktex` - forked utility; keep as external/forked dependency history, not an AIFT product

## Repository Status Labels

Use these labels consistently in READMEs and reports:

- `Active product` - actively maintained and public-facing
- `Infrastructure` - foundational platform or deployment tooling
- `Federation core` - shared doctrine, templates, coordination, or public identity
- `Research` - experimental, model, dataset, cryptographic, or protocol work
- `Incubating` - promising but not yet a primary public surface
- `Legacy` - retained for history, dependency, or reference
- `Fork` - external code fork that should not be confused with original AIFT work

## Immediate Cleanup Plan

1. Make `www.aifreedomtrust.com` the canonical GitHub Pages website repository.
2. Copy this static site into that repository root.
3. Add a short README to every public repo using the status labels above.
4. Add a standard issue template and pull request template to active repos.
5. Keep `capital-city-provisions`, `VPS`, `AIFT-Forge`, and `Aether_Coin_biozonecurrency` as the main public project set.
6. Decide whether `biozone-harmony-boost` should be revived, archived, or marked incubating.
7. Leave `chktex` marked clearly as a fork.