Skip to content

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

goatbuilder 0.7.0, 0.7.1 and 0.7.2 are published. With them, goatbuilder join-node builds a joining site with no manual step after the node is reached: it enrolls the node, issues its certificates, and deploys its data router, health publishers, front door and mesh DNS. A goatnet can also measure a fault on a peer it does not own, such as a clock that runs ahead or a client that refuses the router's certificate, and show it per peer. The whole-repository tag goatcore/v0.7.1 is cut, and the branch stable points at it.

This entry covers all 33 public USAREUR-AF repositories, because a change in one usually lands with matching changes in others. Seven of them opened in this window: awesome-goat, first-bite, hello-galaxy-first-bite, hello-galaxy-record-consumers, open-entity-gateway, first-bite-env and goat-cloud (section 7). A new page, repositories.md, lists every public repository with one line on what it is. The entry follows the entry for 10 to 13 November.

In short

  • Move to goatbuilder 0.7.2 with goatbuilder update, and build on goatcore/v0.7.1 or stable. 0.7.0 gives every refusal a code and lets join-node build a joining site. 0.7.1 adds the site's mesh DNS, key rotation and both sides' acceptance. 0.7.2 adds goatbuilder grow and the rotation of an IPsec peering's credentials. Do not rotate a forwarder carrier key with 0.7.2 (section 1).
  • goatbuilder join-node builds a joining site, including its own mesh DNS. Only reaching the node stops the run. The portal, the id console and the onboarding engine still run only at a goatnet's first site (section 2).
  • A running peering's leaves can be rotated, and one command completes both sides' acceptance. goatbuilder federate rotate <partner> leaves and goatbuilder federate test <partner> --bilateral are in 0.7.1. Neither is measured yet on a peering between two standing goatnets (section 3).
  • Backing a peering out removes the partner's data whole. A partner's data lives in its own store, and the store is dropped when the peering ends. Where two peerings share an edge and a core, the back-out keeps what the other peering uses (section 3).
  • Every goatbuilder verb shows its work. standup, join-node, deploy and federate list every value with its source, a failed phase carries its error code and fix, and each run is timed step by step (section 4).
  • A fault on a peer you do not own is measured per peer. goat health --domain peer shows which peer's clock is ahead (section 5).
  • Every site of a goatnet will write, and the first site is its hub. ADR 1165 and ADR 1205 are accepted. The guard that lets only the hub make a platform admin is built. Most of the design is not built (section 6).
  • A goatlite can be handed over to the full preset. goatbuilder grow, in 0.7.2, rewrites a goatlite's configuration into a full one with the same values. It changes the checkout and never a host (section 7).
  • first-bite decodes binary messages from a link and can publish them to a goatnet. Its release 1.1.0 is published, with a worked example, an example overlay and two companion repositories. goat-cloud, also new, keeps an owner, a purpose and a lifetime on every cloud resource. The documents also describe a moon pod as a learning tool (section 7).
  • Workflows pin their actions by commit and start read-only. The leak gate also reads the names of added and renamed paths (section 8).

What to do

If you Do this Why
run goatbuilder 0.7.1 or older Run goatbuilder update. It replaces the binary with the release your goatnet serves, after it verifies the release's signature and checksums. goatbuilder update --check shows the served version and changes nothing. With no goatnet to update from, download goatbuilder/v0.7.2 0.7.2 carries every change of 0.6.1, 0.7.0 and 0.7.1, among them the resume of a federate run killed in phase 11 (goatcore #597)
run goat Run goat update. It installs the goat release your goatnet serves, after it verifies the published checksum. goat update --dry-run shows the version first The newest goat is 0.5.19. This window has no new goat release, and changes described as on main are not in 0.5.19
build on goat and want a fixed reference Pin goatcore/v0.7.1, or follow the branch stable stable points at it. It is the tree that goatbuilder 0.7.1 was released from
plan to rotate a forwarder carrier key Wait for the correction, which is in review (goatcore #839). Do not run goatbuilder federate rotate <partner> carrier with 0.7.2 In 0.7.2 the command does not complete a carrier rotation, and the partner's acceptance then fails. On a peering with no carrier it reports success and changes nothing
want to check a downloaded release before installing it goatbuilder update verify-release <dir> --signer <owner>/<repo> --version <x.y.z> It makes the checks goatbuilder update makes, and installs nothing (goatcore #655)
script around goatbuilder status Run it without --mock. It reads the hosts, changes nothing, and exits 3 while any machine is pending or unknown Error GB-026 is retired (goatcore #648)
federate Keep the edge and core hosts' clocks synchronized. Phase 1 refuses a host that is unsynchronized or over the offset budget, with GB-268 The router rejects data stamped more than 500 ms ahead (goatcore #731)
add a node with join-node Keep the node's clock synchronized. Phase 3 refuses a node that is unsynchronized or more than 250 ms off, with GB-297. JOIN_NODE_CLOCK_BUDGET_MS changes the budget The check runs before anything on the node changes (goatcore #766)
declare converger: pull-agent in goatbuilder.yaml Remove the line. doctor and every verb that pushes to hosts refuse such an environment with GB-307 No pull converger is built, and the earlier releases pushed to such an environment (goatcore #803)
script around goatbuilder federate backout Handle GB-293 as well as GB-221. GB-293 is the stop for a core leaf that no admission recorded, when no other peering is set up The plan shows such a leaf as unknown and names the choice to make (goatcore #716)
run an ipsec-fips peering After you move to goatbuilder 0.7.2, apply both sides of the peering in one window. The first apply restarts strongSwan once on each edge and drops that peering's link briefly The edge role now sets make_before_break for credential rotation (goatcore #763)
issue certificates on a network that permits DNS only to its own resolver Set acme_dns_resolvers and acme_dns_skip_authoritative_checks for the goatnet. With the authoritative check skipped, Traefik waits acme_dns_propagation_delay, 90 seconds by default, before it asks for validation Traefik asked two public resolvers, and issue and renewal failed on such a network (goatcore #806, #944)
replicate between sites with Spock Leave forward_origins empty on every subscription, which is the default. The install refuses any other value with GB-351 In a mesh of three or more sites a forwarded change returns to its origin without end, and the lag and exception alerts stay silent (goatcore #967)
run the audit subscriber on MinIO Expect a deploy to fail when nothing cleans up stalled multipart uploads. Set MinIO's stale_uploads_expiry, or use a release that keeps the lifecycle clause The deploy used to warn and continue (goatcore #739)
open a pull request with an unsigned commit Read the comment the check leaves on your pull request; it names the commit and the repair verified-commits now tells the author (.github #4, goatcore #660)

Who should read what

If you Read Because
build on goat, or pin it 1 which release and which tag to use, and what each carries
add a site or a node to a goatnet 2, 6 what the command builds for you, and what a second site does not run yet
federate with another goatnet 3 acceptance by both sides, key rotation, and what a back-out removes
run a goatnet 4, 5, 9 what a run prints and records, a new health domain, and deploy fixes
are learning goat, or teach it 7 the learning program, what a moon pod is for, and first-bite
contribute code or documents 8 what a fix must show, and what CI runs for your pull request

Each pull request's page names its author and any co-authors.


1. Releases

goatbuilder 0.7.0, 0.7.1 and 0.7.2 are published, and 0.7.2 is the release to run: goatbuilder update installs it from your goatnet, or download it from the release page. goat stays at 0.5.19, and goat update installs the goat your goatnet serves. goatcore/v0.7.1 is the signed tag for the whole repository at the commit of goatbuilder 0.7.1, and the branch stable points at it.

The release plan to goatbuilder 1.0 has six steps: 0.5.3 made federation one command, 0.6.1 made runs show their work and 0.7.0 made join-node build a joining site, and all three are published; the 0.7.x releases, of which 0.7.1 and 0.7.2 are published, let a joined site run cut off; a 1.0.0 release candidate is proven on hardware and by people outside the team; 1.0.0 freezes the surfaces

Change What you see PR
goatbuilder/v0.7.2, published 15 November federate rotate <partner> ipsec-leaf and ipsec-ca rotate an ipsec-fips peering's IPsec credentials. goatbuilder grow hands a goatlite over to the full preset. A failed phase prints its fix once. One behavior change: the first apply restarts strongSwan once on each ipsec-fips edge. One known issue: federate rotate <partner> carrier does not complete a carrier rotation. Both are in the "What to do" table goatcore #936, #763, #804, #911
goatcore/v0.7.1, published 15 November The whole-tree tag at the commit of goatbuilder 0.7.1. stable moved to it. Its notes list the versions that go together: goatbuilder 0.7.1, goat 0.5.19, goat-relay 0.1.0, snitch 0.1.1 and the grant-crypto SDK 0.1.0, with saltlick v0.5.0 or later as the peering directory
goatbuilder/v0.7.1, published 15 November join-node runs a joining site's mesh DNS, refuses a node whose clock is off, and builds a phone node on a fixture. federate rotate <partner> leaves and federate test <partner> --bilateral are commands. The edge driver of a two-driver peering runs its part of phases 1 and 3. Three behavior changes: GB-307, GB-297 and GB-293, each in the "What to do" table goatcore #861, #787
goatcore/v0.7.0, published 14 November The whole-tree tag at the commit of goatbuilder 0.7.0, and the first tag stable pointed at in this window
goatbuilder/v0.7.0, published 14 November Sections 2 to 4 of this entry as they stood on 14 November: every refusal names its code, every verb lists its values with their sources, status reads real hosts, and join-node has no manual phase after reaching the node. An undeclared peering exits 1, refused, where it exited 2 goatcore #746
goatbuilder/v0.6.1 The peering link restarts when its interface does not hold the agreed peer, so a federate run killed in phase 11 resumes. An interface that lacks the agreed peer is named as GB-271 goatcore #597, #610, #646
goatcore/v0.6.1 The whole-tree tag at the commit of goatbuilder 0.6.1. stable moved to it. goatenv, the example environment, builds with it goatenv #11
Verify a release without installing it goatbuilder update verify-release checks the keyless signature over SHA256SUMS and every file against it goatcore #655
The changelog of goatbuilder is rendered One file per entry; the release renders CHANGELOG.md from them, so two pull requests never edit the same lines goatcore #623, #639
Compatibility follows each release The configuration files and the command baseline of each release are kept, the newest being 0.7.1, and every pull request is compared with the newest goatcore #631, #634, #675, #676, #562, #563, #776, #886
A deprecated item warns A deprecated command, flag or value still works and prints one line on stderr that names its replacement, and a report's -o json document lists it. The list is empty today. CI holds the deprecation period of ADR 1228, and the kept exit codes, once the last release is 1.0 goatcore #798, #818, #800, #813, #826
Upgrades are tested on every platform The upgrade tests run on each platform goatbuilder ships for, and a federation started on any pinned 0.x release is finished by the current build goatcore #801, #855
A release run again on a later day gives the same result The release drivers and the soak tests no longer depend on the date goatcore #621, #622, #628

The gate that decides 1.0 is goatbuilder-v1-gate.md. It sets no dates: a release is cut when its rows pass. Rows whose named test passes on main now read "measured" there, each with its evidence (goatcore #794, #872, #917, #951).

The gate's group D, the scope of 1.0, is decided (goatcore #946). 1.0 ships the push converger only, and a pull converger arrives later as a value of converger:. A phone node stays a full joiner for 1.0, and a lighter profile for a phone is a later value of the phone class. The decision adds rows for what it leaves before 1.0, each not built: the push converger behind the converger interface, per-machine pending and unknown in the -o json documents, and how long a phone may be off the network before it must be seeded again. ADR 1198, which makes the converger a configuration value, is accepted.

2. One command builds a joining site

goatbuilder join-node used to stop twice for a person, and left the site's data router, certificates, health publishers and mesh DNS as steps done by hand. It now runs phases 1 to 15 in order and stops only at phase 1, where a person reaches the node.

goatbuilder join-node builds a joining site's setup key, enrollment, certificates, data router, health publishers, front door and mesh DNS with no manual phase; a phone node and the guard that lets only the hub make a platform admin are built and run in tests, without a phone or a standing goatnet; the portal, the id console, the onboarding engine and the mail queue at every site are designed and not built

Change What you see PR
No manual phase after reaching the node Phase 10 enrolls the node with a single-use setup key minted where it is used and never stored; nobody types netbird up. Every secret reference passed to a node is resolved first. Gate row H2 now states this requirement goatcore #661, #940
The site's certificates The joining site's leaves are minted and staged before its router starts, the audit subscriber's with the others goatcore #715, #737
The data router Deployed at the joining site by the command goatcore #699
Health publishers The ones the site declares are deployed goatcore #718
The front door Set up when the site declares signal federation off goatcore #721
Mesh DNS at the site (ADR 1235, proposed) Phase 13 runs a replica of the goatnet's zone on the site's core node and registers the site's own nameserver group. A site cut off from the first site still resolves the goatnet's service names. standup does the same for a joining site goatcore #678, #785
A clock check before any change Phase 3 reads the node's own time service and refuses a node that is unsynchronized or more than 250 ms off (GB-297). When the time service does not answer, the run says the clock is not verified and goes on goatcore #766
Signal federation from standup goatbuilder standup <env> --site <joiner> turns the joining site's signal federation on with the steps join-node uses goatcore #824
A third site Phases 1 to 15 run for a third site that declares federation off goatcore #613
What the site does not run is stated Every site's end state declares every service a cut-off site needs, and no service is declared for the first site only. join-node names each service the joining site does not run yet as a gap, with the gate row that closes it. A declared service that no step builds, such as the monitoring stack on a single-host site, is named in the plan and in the summary. The end state declares the data router and admit-audit at every site that replicates, and names a joining site's own SPIRE server as a gap (ADR 1164, designed) goatcore #612, #637, #671, #953, #968
A phone as a node join-node --class phone --via usb builds a node in the Linux virtual machine of an Android phone, reached through the Android debug bridge. It is built on a fixture and not measured on a phone through the tool. An Android app starts the virtual machine when the phone boots goatcore #747, #743
Smaller machines Every container memory limit and the Postgres memory settings are variables whose defaults are the earlier values goatcore #615

The design is "join-node builds the whole declared site" (goatcore #604). A join-node run that also passes phase 1 with no person is in review (goatcore #869).

3. Federation: acceptance by both sides, key rotation, two drivers and back-out

One command can now complete both sides' acceptance of a peering, and one command rotates a running peering's leaves. Backing a peering out removes the partner's stored data whole and leaves every other line of the core's configuration as it was.

Change What you see PR
Both sides' acceptance in one command goatbuilder federate test <partner> --bilateral runs phase 14 on a session both sides derive from the agreement. Each side signs its result, the result crosses the fabric, and the other side verifies it under the key bound at phase 5. It is opt-in, and phase 14 is unchanged without the flag. A combined PASS in which each side holds only its own surfaces is designed, and its build is in review (goatcore #815) goatcore #654, #659, #719, #720, #752, #786, #789, #808, #791
Key rotation as a command goatbuilder federate rotate <partner> leaves replaces a running peering's leaves, and a leaf rotation that was interrupted finishes or rolls back. rotate <partner> carrier is meant to rotate the forwarder carrier keys. In 0.7.2 it does not complete a carrier rotation, and the correction is in review (goatcore #839). After a signing-key rotation, phase 5 hands the peering directory over to the new key, signed by the key it replaces, and prints GB-285 and publishes nothing when it cannot. Rotation of the WireGuard peering key is built as a library, and its command is in review (goatcore #854). Neither rotation command is measured on a running peering goatcore #667, #680, #701, #734, #689, #683
IPsec credentials, in 0.7.2 rotate <partner> ipsec-leaf and rotate <partner> ipsec-ca switch an ipsec-fips peering to a leaf an operator staged, confirm that the link authenticated again, and put the old pair back when it did not. rotate <partner> ipsec-ca also needs --partner-holds-ipsec-ca <sha256>, the partner's read-back of the new CA's fingerprint (GB-303). A stopped rotation resumes with the same id, and --retire <id> removes the key that was set aside once phase 14 has passed goatcore #763, #828
A party's CA rotates without a gap (ADR 1242, accepted) A party announces its next CA in version 2 of the package. The outbound republisher reads a version 2 agreement as it reads version 1, and does not act on the announced CA. The CA rotation is not built, and rotate <partner> ca is refused with GB-282, whose message names rotate <partner> leaves as the step to take meanwhile goatcore #822, #891, #894, #931
A partner's data is dropped whole (ADR 1234, accepted) goatbuilder federate backout <partner> takes the partner's entry out of the core's peerings file, restarts the router without the partner's store, and removes the store. Deletion by record, key or person is not built and is not planned goatcore #614, #629
Back-out is measured The back-out scenario passes every one of its checks in the federation test environment, on both shapes of core goatcore #554, #547, #640
Back-out with two peerings Backing out one of two peerings keeps the core leaf the other still uses, and removes the peering's entry from the edge's host firewall. With no other peering set up and no record of what the leaf's paths held, the back-out stops with GB-293 and names the choice. A scenario in the federation test environment backs one peering out while the other carries traffic goatcore #716, #788, #812
Two drivers A peering opts in with drivers: two. The edge driver runs phase 1's edge checks and phase 3's edge half, and prints a code that the controller confirms when it imports the result and runs its core half. The hand-over of phase 2 is in review (goatcore #860), and phases 11 to 14 are not built goatcore #601, #690, #608, #717, #736
A judged SKIP is recorded A host-allocation SKIP in a plan says which case it is and what clears it. goatbuilder federate plan <partner> --accept host-allocation records the operator's acceptance inside the plan hash, so the approved hash covers it goatcore #753, #779
Data keeps arriving across a restart Reception held across a restart of each core and of each edge in the federation test environment, in two consecutive runs goatcore #873
A partner's earlier run is never taken for the current one In both sides' acceptance, a partner run's stamp carries its challenge and its start time in one value. Two values written apart could disagree, and our side then refused the partner's real result goatcore #792
The forwarder, brought up by the command A scenario in the federation test environment has goatbuilder federate apply a peering's forwarder in phase 2 from the forwarder: declaration, with one side behind a NAT router that forwards nothing inbound goatcore #928
A clock check before a peering Phase 1 refuses a peering host whose clock is unsynchronized or over the budget (GB-268) goatcore #731
Running a phase again changes nothing Phase 10 places nothing and restarts nothing when the admission is in place; phase 13 keeps a newer partner bundle; federate status resumes from the first phase it cannot show passed goatcore #692, #698, #632, #712
The link's read-back reads the peer The WireGuard and carrier read-backs compare each peer's public key and allowed address. An edge driven from a workspace gets the certificates it mounts, or GB-275 says why goatcore #662, #663, #658

4. Every verb shows its work

The previous entry described runs that name each command and leave a record. That now holds for standup, join-node, deploy and federate, and each run also lists every value it uses with where the value came from.

Change What you see PR
Every value with its source run.json and the dry run list each value with its source: a file and line, a derivation, an environment override, a default or an allocation. A secret shows its source and never its value goatcore #649
status reads real hosts One row per machine and component: converged, pending or unknown. It runs no play and writes nothing goatcore #648
Phases of every verb are in one catalog standup, join-node and deploy have phase catalogs, held to the plan each verb prints, so goatbuilder explain answers for their phases. release and fastlane each have their eight steps in the catalog, so goatbuilder explain release and explain fastlane answer too goatcore #651, #703, #862
A failed phase is interpreted A failed standup, join-node or deploy phase carries the matching error code, its likely cause and its fix. The fix prints once, on its own Fix: line, and an incomplete phase 14 names goatbuilder federate <peering> --from 14 to resume it goatcore #652, #669, #703, #911
Every refusal has a code Each refusal of goatbuilder names its catalog code, and a stop after a printed view says why. Every error goatbuilder federate raises carries a code too (GB-315 to GB-325), except federate allocate for an undeclared peering, which keeps exit 2. The same work for the rest of goatbuilder is in review (goatcore #870) goatcore #560, #656, #668, #867
Each run is timed standup, join-node and teardown write one row per step to a timings file in the state directory. Each row names its cause: ok, or the catalog code of the failure. standup times the operator's step at phase 11 and names the slowest phases goatcore #802, #805, #814
A setting that nothing implements is refused An environment that declares converger: pull-agent is refused with GB-307 by doctor and by every verb that pushes to hosts goatcore #803
One page per error code Generated from the catalog and served on the documentation site, one URL per code goatcore #666, goatdocs #26
The contract says so Clause C11, legibility, is in the deploy contract beside C1 to C10, with its conformance test goatcore #647

5. Faults on peers you do not own

A goatnet has peers its operators do not own: a partner's router, a contributor's laptop. When such a peer misbehaves, the goatnet now measures the fault at its own router, names the peer, and shows the reading; it never disconnects a peer automatically.

Change What you see PR
The decision (ADR 1232, accepted) One five-stage path: measure at the router we own, attribute to an owner, tell the admins, the owner and the peer, track, and close when the reading is clean. The first notice to an owner is approved by an operator. Stage 1 and the displays are built; the rest is designed goatcore #594, #735
A clock that runs ahead The reader goat-peer-health counts the router's timestamp rejections per peer and publishes a reading on ops/peer/health/<site>. When the local clock is suspect, no peer is blamed goatstuff #82, #89
A client that refuses the router's certificate A second detector counts ended TLS handshakes per alert name and lists absent peers as candidates goatstuff #91
The feed for the second detector The feed keeps the router's log line for a TLS handshake that a client ended. peer_health_tls_alerts_logged says whether the site's router logs that line, and while it is false the reader reports that part of its reading as not measured. goat_zenoh_rust_log sets the router's log level goatcore #745
Deploying the reader Role peer-health, play ops/ansible/peer-health-deploy.yml -e target=<group>, a router access rule and a pin row goatcore #730
Reading it goat health reads the peer domain and this machine's own router verdict. goat health --domain time lists clocks a neighbor observed, apart from the site's own. panoscope and the map show the domain, and panoscope's /top shows trust refusals goatcore #728, #733; goatstuff #84, #90, #92
Trust refusals in the CLI goat health --domain peer and goat top show the second detector's reading. Declared peers that hold no session are listed as candidates, apart from peers at fault. This is on main, and goat 0.5.19 does not carry it goatcore #744

6. Sites that run cut off

The design in which every site of a goatnet can admit people and machines while cut off from the others is accepted, together with the rule that makes one site the hub. Most of it is not built, and today the portal and the id console run only at a goatnet's first site.

Change What you see PR
ADR 1165 and ADR 1205 are accepted Every site writes. The hub is the first site by default, and only the hub makes a platform admin. A cut-off site joining 1.0's gate is group I of the gate goatcore #682
Only the hub makes a platform admin A trigger on the sign-in service's identities table refuses a platform-admin grant written at a site that is not the hub, and removes the group from such a grant when it arrives by replication. It is built and run in the partition harness. The refusals in the services that make a grant are designed goatcore #722
An alert when the guard refuses spock-drift-watch counts the refused grants, and the alert SpockCeilingRefused fires on a new one. It is measured in the partition harness and not on a deployed monitoring stack goatcore #727
The hub-directive applier is installed site-bootstrap.yml applies the role at each replicating site that names a hub. Written; not yet run against a host goatcore #596
A schema change reaches every site coordinated-upgrade.yml migrates each site's database in turn before it starts that site's services. Replication no longer stops at a site whose schema lacks a new column goatcore #749
Replication conflicts are counted in every database The management host's exporter runs the Spock conflict and exception counts in every replicated database, and the alert SpockSlotWALNearLimit reads the series the exporter emits goatcore #710, #831
A subscription that would loop is refused The install refuses a Spock subscription with forward_origins set, with GB-351, and an alert fires on one. With forwarding on in a mesh of three or more sites, each change goes on to the next site and returns without end while every subscription still reads replicating goatcore #967
The gate asks for a measured verdict per write path Gate row I6: no write class is turned on at every site while one of its write paths has no measured verdict goatcore #771
Proposed: a joiner runs the replication core ADR 1233, proposed, revised with the end-state change in section 2 goatcore #607, #671
Proposed: two independent SPIRE servers at a site ADR 1236, proposed, with its trial amended; nothing in a running goatnet changes goatcore #665, #896
Proposed: rebuild a site from nothing ADR 1237, proposed: a site or an environment is rebuilt from nothing and a checked extract of its identities, rolling or all down goatcore #672, #684
Designed The audit of a cut-off site and a capped spool for a phone; a batch of certificates minted ahead; the console's outbound mail queue goatcore #611, #605, #697, #714

Not in main: how each write class is turned on, checked and rolled back is merged into the branch island/integration (goatcore #624), and reaches main when that branch is promoted. A report of the rows that a heal replaced by last-write-wins is in review against the same branch (goatcore #691).

7. Learning and documents

The learning program is written down as a ladder of ten rungs and a lane beyond it, and the documents state once what a moon pod is for. Seven repositories opened; five of them decode binary messages from a link, put the records on a goatnet, and show what to build on them.

Change What you see PR
The learning program (ADR 1238, proposed and in use) The learner ladder stays at ten rungs. A lane named "Beyond the ladder" holds operating, proof-of-value and advanced modules; a module whose tooling is not built is marked frontier: true goatcore #681, #688, #679; goatstuff #85, #86
A moon pod is a learning tool (ADR 1239, proposed) The documents no longer offer a moon pod for real data flow or call bare metal sovereign goatcore #687; goatdocs #28; goatstuff #87; zagros-moon-pod #19; hello-galaxy-zagros-pod #8
first-bite, a new repository first-bite decodes binary messages off a link against a declarative dictionary and publishes them as JSON records. Its tool bite takes an interface document to a dictionary. Publishing to a goatnet is optional, behind the cargo feature goat, which is off by default. The record carries typed values, and CBOR is a selectable encoding first-bite #40, #44, #61, #46
first-bite v1.1.0, published 15 November A security block in the configuration states the level each path is held to: TLS or mutual TLS, and a minimum TLS version. mind, the program that listens and decodes, refuses to start when a path cannot meet it, and mind security show and check report it. The record socket is plaintext and is refused off loopback under a block. first-bite delivers Cursor-on-Target events to a TAK server over UDP or TCP with TLS. Sinks deliver before a run ends, and exit status 3 means records were abandoned first-bite #62, #68, #8
A worked example for first-bite hello-galaxy-first-bite has five runnable steps: decode a capture, tap a link, turn an interface document into a dictionary, publish to a goat fabric, and make Cursor-on-Target events. It builds first-bite v1.1.0 hello-galaxy-first-bite #1, #3
Consumers of first-bite's records hello-galaxy-record-consumers is a worked example on Kubernetes. first-bite posts decoded records over HTTP, a receiver makes its PostgreSQL tables from the dictionary's JSON Schema, and a board shows the latest status per source. The data's owner grants who may post and who may read hello-galaxy-record-consumers #3
Records as tracks open-entity-gateway publishes the records first-bite decodes as tracks over open interface standards: Cursor-on-Target, SAPIENT and ASTERIX CAT062. Vendor adapters are separate packages
An overlay for first-bite first-bite-env is an example overlay: dictionaries and one site's configuration over first-bite at a pinned release. It is a template for a private overlay, and every document, address and name in it is invented first-bite-env #1
goat-cloud, a new repository goat-cloud is for cloud environments where every resource has an owner, a purpose and a lifetime: a tag contract, a registry of infrastructure code, a scanner, cleanup behind safety gates, and cost visibility, for AWS, Azure and Google Cloud. One default changed after it opened: a contact address taken from a resource tag is accepted only in the admins' mail domains unless contact_allowed_email_domains lists others goat-cloud #5, #2, #3
An index of every repository repositories.md lists every public repository in the organization with one line each, and CI compares the page with GitHub. awesome-goat links to it goatdocs #33, #34; awesome-goat #2
A goatlite is handed over to the full preset goatbuilder grow, in 0.7.2, reads goatlite.yaml and shows the difference leaf by leaf, the files it writes and the files it hands over. It asks, or needs --yes, then writes ops/goatbuilder/goatbuilder.yaml, takes the generated header off the files the goatlite's render wrote, and removes goatlite.yaml. It changes the checkout only, never a host, and refuses with nothing changed on GB-304, GB-305 or GB-306. goatbuilder.yaml takes three optional fields for it: deploy.cloud, deploy.owner and deploy.cross_goatnet. It is measured on the fixture and has not run on hardware; the other steps of the growth design are not built goatcore #765, #804, #951
Tutorial 2 checks replication in both directions goatbuilder assay <founder-site> reads the subscriptions the first site holds from each joining site. Replication that works in one direction only no longer passes goatcore #830, #843
Tutorial 3 matches the command The federation tutorial reads as goatbuilder federate runs at phases 5, 6, 10 and 14, and says that each side still needs its own probe launcher goatcore #913, #916
The Hello Galaxy tutorial checkpoints The sync keeps a clone's own files and records its checkpoints again goatcore #844; hello-galaxy-goatenv #13, #14
A goatlite skill for a coding agent The README has one line that hands the goatlite tutorial to an agent goatcore #670
AGENTS.md in every repository Each repository tells a coding agent how to build, test and contribute there .github #5, goat-client #3, saltlick #13, open-billie #25 and the hello-galaxy repositories
The documentation site for machines and for questions llms.txt and llms-full.txt, a context7.json, and eight pages titled with the question they answer goatdocs #23, #24, #25, #27
The relay The documents state that the relay built from the written wire-protocol specification is released and in service goatcore #702, #713; goatdocs #29
Work others build on goat The README points to the list awesome-goat goatcore #732, awesome-goat #1
Proposed: decoys as a detection layer ADR 1247, proposed, designed and not built: decoys are generated on demand from a seed. The mechanism is public, and each goatnet's placements are private goatcore #947
Proposed: stock upstream NetBird and WireGuard ADR 1248, proposed: goat follows stock upstream NetBird and WireGuard, and retires each of its own departures when upstream offers the same. A watch list names the departures goatcore #952

8. Contributing and CI

A fix now shows its failure on main before its pull request opens, and CI runs less for a pull request that changes only documents. Workflows pin their actions by commit and start with read-only permissions.

Change What you see PR
A fix shows its failure first CONTRIBUTING.md: a pull request that fixes a defect links the failing run or test on main goatcore #588
The check tells the author verified-commits comments on the pull request when a commit is not verified .github #4, goatcore #660
Documents-only pull requests goatbuilder-pr runs only the documents' configuration examples for a pull request of documents only goatcore #685, #704, #568
ADR index rows are rendered The index rows of new ADRs come from the ADR files goatcore #636
A run on main is never cancelled The next push to main no longer cancels the run before it goatcore #618
A stacked pull request runs the same workflows Six workflows ran only for a pull request into main. They now run for a pull request based on another pull request's branch, and a check lists the workflows a pull request should have run goatcore #750, #751
Workflows pin actions and start read-only (ADR 1246, proposed) External actions are named by full commit, with the version in a comment. Workflows start with a read-only token, and a job that publishes keeps its own scope. A checkout of the base branch under pull_request_target takes no ref from the event. docs records the rules and the OpenSSF Scorecard result per check goatcore #915, #895, #927, #941
Release assets are signed one by one The release workflows of wg-cp0 and the grant-crypto SDK sign each asset as <asset>.sigstore.json and attach build provenance, beside the signature over SHA256SUMS goatcore #904
The leak gate reads path names The gate scans the names of added and renamed paths, and more shapes of key and token, in every repository that carries it goatcore #958, goatdocs #35, goatenv #12, goatrodeo #16, goatstuff #98, hello-galaxy-goatenv #15
The hermetic tier protects a shared machine It refuses to run on a shared machine and puts back what it changes goatcore #760
Debian hosts in CI The hermetic deploy tier runs on Debian 13 hosts as on Ubuntu hosts. A check refuses an apt source fixed to Ubuntu in any role a joining site runs goatcore #755, #853
Generated files are held to their source .envrc.example and the goat command reference are regenerated and compared in CI goatcore #627, #635, #633
The two-sovereign test runs in stages One build stage and four scenario stages, each with its own cache key goatcore #602, #603, #638, #643
The weekly changelog merges itself The weekly run merges its own pull request when every check passed goatdocs #22
A weekly page for a repository that stands alone A repository that does not build from goatcore, such as octo-pod or open-billie, gets its own page in the weekly listing goatdocs #30

9. Fixes for a running goatnet

These fixes change what a deploy does on a host. None needs action unless the "What to do" table lists it.

Change What you see PR
A sign-in deploy never recreates the database ory-deploy.yml reads the Postgres password itself and starts services with --no-deps goatcore #593
containerd's root is checked where it runs The docker-engine role reads the running containerd's root before writing its configuration, and fails with containers running on a mismatch goatcore #664
The audit subscriber Its lifecycle steps run mc with a writable HOME; a deploy fails when nothing cleans up stalled multipart uploads goatcore #595, #739
Rollback reaches a goatnet as deploy does The rollback driver uses the goatnet's declared door and passes --site from the canary goatcore #644, #723
Values reach phases as values An in-process init and standup's phases get their values as run state, not through the process environment goatcore #641, #642, #740
Certificates on a network with its own resolver acme_dns_resolvers and acme_dns_skip_authoritative_checks set, per goatnet, the resolvers Traefik uses for DNS-01. The defaults are the earlier values. When the authoritative check is skipped, Traefik waits acme_dns_propagation_delay, 90 seconds by default, before it asks for validation goatcore #806, #944
Alert summaries name the site A summary takes the site from the series, or from Prometheus's external label when the series has none goatcore #889, #893
Two alerts that could not fire PostgresWalDirNearVolumeCapacity compares a host's WAL with that host's data volume and counts the WAL once. The management host's signal-server alerts fire per server goatcore #903, #901
The edge router refuses a mixed setting The role goat-zenoh-edge refuses bridge mode while goat_zenoh_edge_core_cn is set goatcore #850
The access-rule examples agree with the repository The ACL taxonomy declares the goatnets the matrix declares, and the example warrant matrix and the warrant gate agree with the repository's own registry goatcore #770, #782
The status page's stamp The isitup list stamp carries the source commits and nothing else goatcore #762
A comparison that read no machine ops/goatbuilder/c3-agreement.py exits 2 and names a verify report that read no machine goatcore #809
A path with a space stays one argument Four role tasks pass their paths to commands as a list of arguments goatcore #849
Acceptance says what it did not check A row that is N/A names the services it left unchecked, and a declared service that no row checked reads UNKNOWN goatcore #880
Dependency advisories The feeds shim takes the fixed quinn-proto and quinn-udp. In goatcore, Rust dependencies in seven lock files and Go modules in eight service modules moved to versions that fix published advisories, and the advisories that do not apply are recorded beside each Rust lock file goatstuff #83; goatcore #907, #908, #925, #909

10. Still in progress

These areas were moving when the window closed. Status words are the ones the repositories use.

Area State Watch
Both sides' acceptance to a combined PASS Open: each side observes its own refusal and SPIRE rows in a session; a proposed ADR lets phase 14 pass on the combined verdict goatcore #815, #816, #885
Acceptance probes Open: a probe launcher on a deployment's edge hosts; probe identities issued per run; phase 14 fired from one machine goatcore #919, #945, #961
Key rotation Open: a correction to rotate carrier; phase 5 takes a partner's new package, and rotate transport runs; version 2 of the package with a next CA, which the peering directory hosts; an IPsec rotation proves the leaf the link signs with goatcore #839, #854, #897, #898, #899, #962; saltlick #14
Federation belongs to goatbuilder Open: ADR 1225 moves to accepted, and gate row B8 to measured goatcore #948
Two drivers and the forwarder Open: phase 2 hands the federation interface to the edge driver; forwarder: declares its machine's SSH user, interface and SSH sources (GB-339) goatcore #860, #934
Pacing between partners Open: accept_hz is a lane's aggregate ceiling, and the republisher paces to it; the republisher drains its queue when it is stopped goatcore #879, #888, #963
The host firewall on an edge Open: the peering plays require the host firewall baseline on an edge (GB-279) goatcore #696
The hub alone makes a platform admin Open: an access-rule cutover made while cut off updates existing policies only (GB-295) goatcore #708
Replication Open: the exporter reads subscription lag and status in every database; a report of rows a heal replaced, against island/integration goatcore #847, #691
A joining site Open: join-node runs from phase 1 to 15 with no person goatcore #869
A goatlite Open: goatlite's standup and teardown texts; tutorial 00 says what standup and doctor print goatcore #965, #960
What status reports per machine Open: each machine row of an -o json document carries its state: converged, pending or unknown goatcore #954
A phone node Open: how long a phone node may be off the network, how it is seeded again, and the lighter peer profile goatcore #956
Errors and phases Open: the rest of goatbuilder raises its errors with a code, and the federation library's refusals carry codes in goat and goatbuilder; the phase catalog describes teardown and the back-out goatcore #870, #920, #921, #929, #930, #937, #942, #864
The gym Open: modules for an outside service, quality of service, events from a model at the edge, and coordination goatstuff #88, #94, #95
Catalogs and scorecard Draft: publiccode.yml and code.json for government code catalogs; a weekly OpenSSF Scorecard run goatcore #694, #695
first-bite beside the other ways onto the fabric Open: an open-billie example whose decoder is the first-bite library and a dictionary; the federation example runs its verbs from goat or goatbuilder open-billie #26; hello-galaxy-cross-env-federation #5
Contributors' open work Open: context completion, federation declarations kept during regeneration, the Raspberry Pi image checksum, the listener and ingress ADR; dependency and image pins (HaterAndrew); the edge's peering port, pytest in parallel (joshkor1982); Azure relays and certificates goatcore #444, #447, #449, #577, #592, #353, #437, #12
goatlite WIP; the two-person drill is its gate goatlite.md

The maintainers' public roadmap, github.com/orgs/USAREUR-AF/projects/8, lists open issues and pull requests by status.

About this entry

  • Window. Pull requests merged from 13 November 2026 16:10 UTC to 16 November 2026 05:36 UTC, in every public USAREUR-AF repository.
  • What "merged" means here. A change is described as part of goat only when it merged into a repository's default branch. A pull request merged into any other branch is reported as in review.
  • The weekly listing. weekly/ lists every merged pull request by kind, one page per ISO week, generated with no person or model in the loop. Written entries explain; the weekly listing is the complete record.