design¶
- zenoh-topology-service/
- Recommended git flow strategy for AI agent teams in goat
- Rapid adaptation with AI — the bones
- Architecture spine — decision → ADR → block → code
- CI discipline
- Cluster worker execution environment
- Code-review process for completed blocks
- Complexity budget and substrate encapsulation
- Confidential Outsourcing — Architecture and Pilot Pattern
- Deliberate Deltas — How goat Diverges From a Vanilla Netbird / WireGuard ZTOL Deployment
- Design system — GOAT-Net visual + verbal language
- Engineering Baseline — How goat Aligns With Industry Best Practice
- Foundational Engineering Health Self-Assessment
- Entity vocabulary — living glossary for cross-cutting fabric entities
- Minimalism under network constraints
- Multi-agent team management — design
- NetBird Feature Usage — What We Use, Why, and How
- Partner Reference Architecture (PRA) — minimal Zenoh-on-ZTOL recipe
- PR Governance — synthesis layer
- Protecting mission-critical data — how Quality of Service works on the fabric
- Scout — ad-hoc human-defined agent, proof case 2 of 2
- Zero-knowledge self-hosted secret stores: fact sheet (checked 2026-10-31)
- Session-bus event layer — design
- Skill audience model — who a skill serves, and where its human guide lives
- goat-sre-agent — Scout-class peer for incident triage + action
- Staged delivery — the shape every major build-out takes here
- WireGuard, Netbird, and What Makes This Different
- Worktree hygiene — keeping per-session worktrees bounded
- Zenoh as an API substrate
- The Zenoh topology service