Process
How the Federation works
The patterns behind every Federation build: two layers, cause and reaction, and a workflow that ends only when the result is verified live.
The two-layer architecture
Every node in the Federation has two layers that are always separate and never merged.
| Layer | What it does | Examples |
|---|---|---|
| Technical (silent) | Does the work: middleware, ring functions, bots, autonomous tasks. Never speaks to people. | Agent Zero middleware; Nova build and maintenance bots |
| Persona (voice) | Named and voiced. Speaks to people, represents the line, and triggers the technical layer. | Nova AI; Spine, the persona of Agent Zero |
Cause and reaction
One thing causes a reaction that is for evolution, repair or maintenance.
Nothing in the Federation acts alone. A person speaks to a persona. The persona triggers the technical layer. The technical layer builds, then keeps checking what it built before, adds new technology and repairs what has drifted. Each action sets off the next useful one, so the system maintains itself without being restarted.
- Cause: a request, a failure, or a new tool appearing.
- Reaction: the matching layer responds by building, repairing or upgrading.
- Result: the change is verified and recorded, and becomes the next cause.
The build workflow
- Audit first. Look at everything that already exists before deciding anything. Use what we have and add what's missing.
- Picture the finished result. Describe the end state, what the visitor sees from start to finish, then work backward to the pieces.
- Build in broad strokes, in one pass. Batch the fixes into a single complete build rather than many small, costly ones.
- GitHub is the origin. Code goes straight to the repository. Nothing waits on a local copy.
- Plain HTML. Every word is readable without JavaScript, by people, search engines and AI.
- Verify live. Check every page and link on the real address. A build is done when it works, not when someone says it's done.
- Cross-check. Fixing one thing can break another, so all the affected sites get re-checked, not just the file that changed.
- Remove what's broken. Anything that doesn't work comes out. Nothing dead is left dangling.
Operating rules
Design for the thinnest pocketbook
Everything works at zero budget on free tiers. Paid tiers are wired in and switched off, ready when money arrives.
Always an alternative
Every service has a fallback. No single provider can stop the Federation.
One source of truth
Each kind of thing has one canonical home. For products, Gumroad wins and every site matches it.
Honesty without accusation
Every report is a lead to verify, not proof and not a lie. When something is wrong, find the broken mechanism.
Related: YAML Data Hub · Nova AI systems · Archives