Skip to content
goat data fabric docs
diagrams
Initializing search
USAREUR-AF/goatdocs
goat data fabric docs
USAREUR-AF/goatdocs
goatdocs index
Changelog
Changelog
Changelog, 6 to 8 November 2026: the first two days of public development
Changelog, 8 to 10 November 2026: signed commits everywhere, and one build for every deployment
Changelog, 10 to 13 November 2026: federation is one goatbuilder command, and a stable line follows releases
Changelog, 13 to 16 November 2026: goatbuilder 0.7 builds a joining site with one command, and a fault on someone else's peer is measured
Changelog
Figures
Figures
2026 11 10
2026 11 10
2026 11 13
2026 11 13
2026 11 16
2026 11 16
Weekly
Weekly
Weekly changelog, 2 to 8 November 2026 (2026-W45)
Weekly changelog, 9 to 15 November 2026 (2026-W46)
Weekly changelog
Octo pod
Octo pod
octo-pod: weekly changelog, 2 to 8 November 2026 (2026-W45)
octo-pod: weekly changelog, 9 to 15 November 2026 (2026-W46)
octo-pod: weekly changelog
Open billie
Open billie
open-billie: weekly changelog, 2 to 8 November 2026 (2026-W45)
open-billie: weekly changelog, 9 to 15 November 2026 (2026-W46)
open-billie: weekly changelog
Design
Design
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
Zenoh topology service
Zenoh topology service
Design system
Design system
GOAT-Net Design Skill
Assets
Assets
Diagrams
Diagrams
Preview
Preview
Raw
Raw
Manifesto
Ui kits
Ui kits
Brief
Brief
Console
Console
Manifesto
Manifesto
Operations
Operations
Branch protection rules — runbook
Cluster worker worktree runbook (Option I substrate)
Cross-track commit sweep handling
Git emergency repair — when state gets borked despite the substrate
Multi-agent substrate — install + first dogfood (operator runbook)
Tier-3 install runbook — flipping branch protection on per-repo
Upstream issue draft — netbirdio/netbird
Partner templates
Partner templates
Partner Data Sharing Charter — TEMPLATE
Joining a goatnet as a partner organisation — what to expect
Release Declaration and Accession — TEMPLATE
Standalone goatnet packet
Standalone goatnet packet
03 — Lab phase plan (CONUS)
Questions
Questions
Can SPIRE run on a multi-master database?
Does a WireGuard mesh keep working when the management server is down?
How do I change Zenoh access rules without a restart?
How do I use certificate identity to control who can publish in Zenoh?
How do two organizations share pub/sub data without sharing a certificate authority?
How should a command-line tool explain its errors?
What do you give up with brokerless pub/sub?
Why was my Zenoh publish silently dropped?
Reference
Reference
Built with
Why Not the Traditional Architecture
Diagrams
Mesh Overlay Technology Comparison
goat's repositories
Mesh Resilience: What Happens When the Server Goes Down
Errors
Errors
E_ACL_DECLARATION_MISSING: no ACL declaration was supplied
E_BUNDLE_INVALID: the bundle did not verify
E_CERT_EXPIRED: the mTLS certificate is outside its validity
E_CLOCK_SKEW: the device clock is wrong
E_DOCTOR_INCONCLUSIVE: doctor saw a failure it cannot narrow
E_MACHINE_UNRESOLVED: the machine named is not exactly one enrolled machine
E_MESH_PEER_UNRESOLVED: the enrolled machine has no single mesh peer
E_NETBIRD_FAILED: the NetBird management API call failed
E_NOT_ADMIN: an operator-only action without operator authority
E_OFF_MESH: not connected to the mesh
E_PORTAL_BAD_RESPONSE: the portal answered in a shape this goat build does not understand
E_PORTAL_FORBIDDEN: the portal refused this identity
E_PORTAL_NOT_FOUND: the portal answered that what was named is not registered
E_PORTAL_RATE_LIMITED: the portal is rate-limiting this client
E_PORTAL_REFUSED: the portal refused the request
E_PORTAL_SERVER_ERROR: the portal failed on its own side
E_PORTAL_UNREACHABLE: the portal API did not answer
E_PROFILE_DENIED: the profile exists but this user cannot read it
E_PROFILE_MISSING: no profile for this context
E_RECIPIENT_KEY_UNPUBLISHED: this anchor's recipient key is not in the recipient-cert store
E_ROUTER_UNREACHABLE: the Zenoh router did not answer
E_TOKEN_INVALID: the portal rejected the token
E_TOPIC_CONFLICT: the topic already exists
GB-001: unknown component
GB-002: unknown goatnet
GB-003: the group is not one the component deploys to
GB-004: the component declares no image variable
GB-005: no deploy playbook resolves for the component
GB-006: the door to the goatnet did not open
GB-007: a secret the play needs is not in your environment
GB-008: a mutation needs --yes when there is no terminal
GB-009: not a current main checkout
GB-010: a Python dependency is missing
GB-011: only a repository admin may nominate a release candidate
GB-012: the candidate's image build did not succeed
GB-013: the image is not in the registry
GB-014: a live validation row failed
GB-015: the checkout could not fast-forward after the pin landed
GB-016: no runner settings for the goatnet
GB-017: not converged on every host
GB-018: a required flag is missing or wrong
GB-019: the goatnet's CA key is not on this machine
GB-020: graduate.py did not produce the expected record
GB-021: fastlane refused
GB-022: intent-sign failed
GB-023: rollback refused or guided by artifact type
GB-024: the fixture is not a shape the mock converger knows
GB-025: the config does not validate
GB-026: status reads real hosts only through a converger
GB-027: not inside a repository
GB-028: a command the verb runs failed
GB-029: the play failed on a group
GB-030: no host of the group is in the loaded inventories
GB-031: an op:// reference in your shell is incomplete
GB-032: the candidate record is open but the goatnet runs a different ref
GB-033: promote refused a graduation step
GB-034: the generated pins or intents differ from fleet-pins.yaml
GB-035: the goatnet's intent names no usable CA
GB-036: the component declares no image workflow
GB-037: the ladder is missing a live rung
GB-038: --from preprod-rows cannot resume this candidate
GB-039: a rollback on a fixture needs its environment
GB-040: that directory is not a tutor workspace
GB-041: there is no such lesson
GB-042: the live rows cannot run from this machine — the candidate is UNTESTED, not dead
GB-043: the door to the rung did not open for its live rows
GB-044: a release refuses before the tag because a secret is not set
GB-045: the published declarations are out of order or altered
GB-046: the local declaration is not the source of record's
GB-047: a declaration must name who made it
GB-048: the goatnet is not proven built
GB-049: the acceptance assay cannot run here
GB-050: nothing is declared on that goatnet
GB-051: the plan request is incomplete or not planned yet
GB-052: that file is not a goatbuilder plan
GB-053: the plan no longer matches the tree
GB-054: adopt could not create its worktree
GB-055: a rollback with no --site would flip every goatnet
GB-060: a standup input is required and not set
GB-061: a secret the standup templates is not in this environment
GB-062: a standup input may be required
GB-063: a standup step's host limit selects no host
GB-064: the checkout is behind the trunk in what a deploy reads
GB-065: the trunk could not be fetched, so the checkout cannot be shown current
GB-066: the site's declared end state cannot be derived or read
GB-067: a site's service presence is undeclared or contradicted
GB-068: the goatnet is not in its declared end state
GB-069: the rollout preflight cannot run
GB-070: survey could read no goatnet at all
GB-071: a site's leaf certificate is not on this controller
GB-072: goatbuilder cannot name the download surface to update from
GB-073: the goatbuilder download surface could not be read
GB-074: the downloaded goatbuilder is not vouched for by its release
GB-075: goatbuilder could not replace its own binary
GB-076: the rollout is not cleanly reversible or not ready
GB-077: this checkout's origin is not where release candidates are cut
GB-078: no release signer is known, so the update refuses
GB-100: the federation verbs cannot find this party's context directory
GB-110: the inventory does not name a federation host phase 3 can reach
GB-111: a federation host did not answer over SSH
GB-112: sudo on a federation host wants a password
GB-113: no core router to measure on the core host
GB-114: an edge half of phase 3 cannot be joined
GB-120: a peering names a partner with a reserved word
GB-121: two peerings would share a value
GB-122: a pinned port is one the edge host already holds
GB-123: a peering's pin is not usable
GB-124: the peering allocation record cannot be used
GB-125: a peering file exists that goatbuilder did not generate
GB-126: a peering's inventory group is defined twice
GB-127: no free per-peering value is left
GB-128: a federate run disagrees with the peering's allocated values
GB-129: a peering's offer would widen what federation.toml declares
GB-130: a federation input is missing
GB-131: a port this peering needs is already held on the edge
GB-132: the republisher metrics port is already held on the core
GB-133: the edge or core host could not be probed for its ports
GB-134: the committed slot list differs from the slot registry
GB-135: the slot registry could not be read
GB-136: the core has no receive store matching what the edge grants
GB-137: the core router's configuration could not be read
GB-138: no core router container was found
GB-139: several core router containers were found
GB-140: our CA certificate is missing or is not a CA
GB-141: our CA signing key cannot be resolved
GB-142: our federation signing key cannot be read
GB-143: the peering inventory does not reach the edge or core
GB-144: the federation declaration or the profile is missing or wrong
GB-145: the core certificate would not name every address the edge dials
GB-146: docker compose is not available for phase 12
GB-147: a peering directory value is not usable
GB-148: the federation working directory is not writable
GB-149: the peering is not declared
GB-160: two peerings on one forwarder would share a value
GB-161: a peering's partner id cannot name a forwarder entry
GB-162: one forwarder group names two forwarders
GB-163: a forwarded peering has no allocated values yet
GB-180: another run of this peering is in progress
GB-181: a resource this peering needs is held by another peering on the same host
GB-182: the run journal cannot be read
GB-183: a federate phase failed
GB-184: the working folder or its lock cannot be made, taken or written
GB-185: the partner named to federate status is not a declared peering
GB-186: the plan was not approved
GB-187: the plan is not the one approved
GB-188: the plan no longer holds
GB-189: a stage of goatbuilder federate was asked for the wrong way
GB-190: the admission on our core is not recorded as done for what is rendered now
GB-191: a value for confirmation 1 does not match
GB-192: confirmation 1 is waiting
GB-193: our verifying key cannot be read, or does not verify our half
GB-194: the edge cannot be admitted on our core
GB-195: the core's dry run or the slot check refused the admission
GB-196: the core restart failed after the admission was placed
GB-197: the admission is waiting for approval
GB-200: the federation plan's inputs changed
GB-201: the federation plan is missing or altered
GB-202: a live prerequisite of the federation plan no longer holds
GB-203: two peerings would bind the same value on one machine
GB-210: the host firewall baseline is missing a value it needs
GB-211: the host firewall override names a rule the baseline does not have, or is malformed
GB-212: the host firewall is loosened without a recorded reason
GB-213: the host firewall would cut the session managing the host
GB-214: the host firewall ruleset was not loaded or not confirmed
GB-215: the host firewall would close a port this host listens on
GB-220: federate backout was not given a partner it can act on
GB-221: the back-out found a resource it cannot show is this peering's alone
GB-222: the back-out survey did not complete
GB-223: the slot recheck did not allow the core router restart
GB-224: the core router was not restarted on the reviewed candidate
GB-225: resources of the peering are still present after the back-out
GB-226: our package for the counterparty could not be withdrawn from the directory
GB-227: the core still admits the partner through its own configuration
GB-230: allocate would move a peering that already runs
GB-231: the hand-written peering inventory puts one name in two peering groups
GB-232: a rendered deployment half needs a site value no declaration yields
GB-233: a peering's federation.toml cannot be generated from the environment's
GB-234: the site inventory does not name one edge and one core for a peering without hosts
GB-235: a named allocate would change another peering's inventory lines
GB-236: our core router's goat-zenoh role declarations do not resolve for admission
GB-237: admission cannot write the partner into the role core's zenoh_sovereign_peerings
GB-238: a federation verb's site flags are given where they do not belong
GB-239: a flag that does not apply to the federation verb it was given to
GB-240: a federation switch names no choice it has
GB-241: the environment named is not declared
GB-242: the command line does not parse
GB-243: a standup names no site
GB-244: the config file cannot be read
GB-245: the config file is not YAML
GB-246: a rollback depth outside the ledger
GB-247: the site or class named is not declared
GB-248: the observability leg cannot run
GB-249: the fixture's standup does not fit what was asked
GB-250: a joiner site names no founder
GB-251: no SSH user is declared for a new machine
GB-252: the partner is declared on several environments
GB-253: a host's back-out survey answered for another peering
GB-254: a file goatbuilder reads or writes cannot be read or written
GB-255: nothing is declared for the environment
GB-256: a deploy play's hosts cannot be resolved
GB-257: fleet-pins.yaml is not in the shape goatbuilder edits
GB-258: a command a verb runs failed
GB-259: the assembled tree's marker is incomplete
GB-260: a rollback has no history to go back to, or its target is refused
GB-261: the release's signature does not verify, so the update refuses
GB-262: the verb has no such phase
GB-263: a site id cannot name the variables its phases read
GB-264: no recorded run matches
GB-265: the run is waiting on the other driver
GB-266: the controller's checkout is not clean, so no hand-off is given
GB-267: this part of a two-driver peering is not built yet
GB-268: a peering host's clock is not synchronized, is too far from UTC, or could not be read
GB-269: a secret for the node still holds a secret store's reference
GB-270: a backed-out partner's store was kept because the router does not yet run without it
GB-271: the peering's WireGuard interface does not hold the agreed peer and address
GB-272: the partner's acceptance result does not verify
GB-273: the partner's acceptance result is not from this session
GB-274: the two sides derived different acceptance sessions
GB-275: phase 12 would deploy an edge that has none of the files it mounts
GB-276: --mock was given to a verb that reads the checkout
GB-277: an edge result cannot be imported
GB-278: the edge driver's checkout or carried files are not the controller's
GB-280: a joining site has no mesh DNS zone to serve
GB-281: the founder's management API token for mesh DNS is unset or unresolved
GB-282: rotating our CA needs a decision before it can be built
GB-285: the directory binds our previous signing key, and the seed that hands it over is missing
GB-286: a joining site has no leaf-cert manifest join-node can read
GB-287: a joining site's leaf-cert manifest has no router leaf
GB-288: a health publisher a joining site declares has no play in the checkout
GB-289: the IPsec rotation's staged material is missing or unreadable
GB-290: the staged IPsec certificate is not right for this link
GB-293: the back-out cannot tell what our core router's leaf held before this peering
GB-296: a site turned on the audit spool, which is not built
GB-297: a joining node's clock is not synchronized or is too far from UTC
GB-298: an IPsec rotation under way, or not yet retired, is not the one asked for
GB-299: no phone, or no Linux VM on it, answers over the Android debug bridge
GB-300: the phone's Linux VM is not a host a node can be built on
GB-301: a site does not hold what the machine class phone declares
GB-302: the IPsec link did not come up on the new leaf; the old pair was put back
GB-303: the partner has not read back our new IPsec CA
GB-304: grow was given a file that is not a goatlite
GB-305: grow would replace a configuration that already exists
GB-306: the full configuration grown from a goatlite is incomplete
GB-307: an environment declares converger pull-agent, and the pull converger is not built
GB-309: the retire step finds no confirmed rotation to retire
GB-311: an IPsec rotation stopped half way through its switch, and what is left does not finish it
GB-315: a program a step ran gave output or an exit goatbuilder cannot use
GB-316: a confirmation could not be read from the terminal
GB-320: a program the run starts could not be started
GB-321: a file a step of this run wrote is missing or is not what it wrote
GB-322: goatbuilder reached a state its own code rules out
GB-323: a file the run writes outside the working folder cannot be written
GB-324: a setting in the environment has a value goatbuilder does not take
GB-325: flags given to a federate stage or verb do not go together, or one they need is missing
GB-328: a rotation's values reach no play in the phases this run built
GB-351: a Spock subscription has forward_origins set, which in a mesh replicates in a loop
X-ACCEPT-001: acceptance could not run a required check, so the peering is not accepted
X-ANSIBLE-001: a host was unreachable
X-ANSIBLE-002: sudo on the host wants a password
X-ANSIBLE-003: a play assertion failed on the host
X-ANSIBLE-004: a task failed on a host
X-ANSIBLE-005: the preflight refused a stale or unsafe checkout
X-AWS-001: AWS rejected the credentials
X-AWS-002: aws-vault has no credentials for the profile
X-AWS-003: the SSM target is not connected
X-AWS-004: the AWS CLI fell back to an expired aws login session
X-COSIGN-001: the signature did not verify
X-DIGEST-001: no tool could read the image's digest
X-DIRENV-001: direnv exec was given an assignment, not a command
X-DNS-001: the name did not resolve
X-DOCKER-001: no permission on the Docker socket
X-DOCKER-002: the image could not be pulled
X-DOCKER-003: the Docker daemon is not running
X-GH-001: GitHub returned 404
X-GH-002: the GitHub CLI is not logged in
X-GH-003: GitHub rate-limited or forbade the call
X-GIT-001: not a git repository
X-GIT-002: the branch cannot fast-forward
X-GIT-003: the remote refused access
X-HTTP-001: the service rejected the credential (401)
X-HTTP-002: the service refused the identity (403)
X-HTTP-003: the service is up but its backend is not (5xx)
X-HTTP-004: an onboarding call went to the portal
X-NETBIRD-001: no such mesh profile
X-NETBIRD-002: the mesh daemon is not running
X-OP-001: 1Password CLI is not signed in
X-OP-002: an op:// reference is malformed
X-OP-003: a reference does not resolve to an item
X-PY-001: a Python module is missing
X-SECRETS-001: the declared secrets store is unknown
X-SECRETS-002: the env-file store has no file
X-SECRETS-003: refusing to write secret values to a file git would commit
X-SECRETS-004: bao:// references need the OpenBao injector
X-SECRETS-005: a git-crypt file is still encrypted
X-SMOKE-001: the live rows' browser toolchain is not on this machine
X-SSH-001: the host refused the key
X-SSH-002: no route to the host
X-SSH-003: the host key changed
X-TLS-001: the TLS handshake failed
Vendor templates
Vendor templates
Data Services Provider Charter — VENDOR TEMPLATE
diagrams
¶
Back to top