LIVE FIELD ARRAY / 03 CHANNELS
Active lab channels
Infrastructure with memory
Home systems
Self-hosted services, network boundaries, observability, recovery, and the quiet work of keeping things dependable.- Service health is not the same as a process running.
- Recovery procedures should be tested before they become necessary.
- A useful dashboard links symptoms to the system that produced them.
Proof inside a boundary
Security research
Authorised labs, source-driven investigations, exploit chains, and notes that separate proof from assumption.- Define the authorised surface before touching the target.
- Preserve the evidence that distinguishes a finding from a guess.
- A reproducible chain is more useful than a dramatic screenshot.
Beyond the green build
Release practice
Signing, deployment, provider control planes, production checks, and the gap between built and genuinely shipped.- Local proof, release readiness, review, and public availability are separate gates.
- Control-plane state matters as much as source state.
- The real path includes DNS, certificates, credentials, and recovery.
PROVIDERDNS
CURRENT INSTRUMENT / ORBITDNSInfrastructure should explain itself before it changes.
OrbitDNS explores the inverse: begin with the intended operation, show exactly what will change, preserve provider-specific truth, and make dangerous actions understandable before they become difficult to reverse.
Open the OrbitDNS case file ↗ FIELD PROTOCOL / V.03
Before the first command, know the way back.
- SCOPE
Name the authorised surface and the boundary that must remain untouched.
- OBSERVE
Collect the smallest useful evidence before changing the system.
- RECOVER
Know how to return before proving that you can move forward.
- VERIFY
Test the real path, then state only what the evidence supports.
RECOVERED DOCUMENTATION / 03 PROTOCOLSThe Field Manual survived.
Security, delivery, and attention notes from the former Docs room, rewritten as concise procedures with their original context intact.
Open the Field Manual ↗