# Federation Operating Model

AI Freedom Trust Federation is organized as a layered project system. Each repository should know why it exists, what layer it belongs to, and what public expectations it carries.

## Layers

### Public Trust Layer

Public-facing identity, documentation, standards, and community posture.

Repositories:

- `www.aifreedomtrust.com`
- `.github`
- `AIFT-Forge`

### Infrastructure Layer

Hosting, deployment, decentralized cloud, provider networks, app creation, routing, naming, and registry systems.

Repositories:

- `VPS`

### Applied Systems Layer

Real-world service operations that prove the federation tooling through practical use.

Repositories:

- `capital-city-provisions`

### Stewardship Layer

Wallets, value protocols, datasets, models, cryptographic research, and long-term experiments.

Repositories:

- `Aether_Coin_biozonecurrency`
- `biozone-harmony-boost`
- private research workspaces

### External / Legacy Layer

Forked or historical repositories retained for reference but not presented as active federation products.

Repositories:

- `chktex`

## Repository Requirements

Every active repository should have:

- A clear repository description.
- Topics that include `ai-freedom-trust` and its layer.
- A README that states status, layer, purpose, setup, verification, and next milestones.
- A license or explicit license posture.
- Issue templates and pull request template inherited from `.github` unless overridden locally.
- Public language that avoids unsupported claims.
- A visible deployment or demo link when applicable.

## Status Definitions

- `Active product`: user-facing or operationally important system under active development.
- `Infrastructure`: shared technical foundation or deployment system.
- `Federation core`: profile, templates, doctrine, or coordination standards.
- `Research`: experiments, models, datasets, cryptographic, protocol, or long-horizon work.
- `Incubating`: promising but not yet a primary public surface.
- `Legacy`: kept for history or reference.
- `Fork`: external code fork, not original federation product work.

## Immediate Operating Rhythm

1. Keep `www.aifreedomtrust.com` as the public doorway.
2. Keep `.github` as the organization-wide community-health layer.
3. Keep `AIFT-Forge` as the doctrine/template layer.
4. Keep `VPS`, `capital-city-provisions`, and `Aether_Coin_biozonecurrency` as the main active build lanes.
5. Review incubating and legacy repos monthly.
6. Promote only working, documented systems into the public active-project set.