jschoubben 26690d89f1 The artifact store's seat is one per mesh, and the test says so from the catalogue ...

Review of the registry work found the seat node-scoped: a second `distribution` on another
machine resolved cleanly there, and only afterwards did the mesh notice `artifact-store`
offered by two nodes, with every consumer elsewhere refusing to choose. A node-scoped
requirement with one candidate installs that candidate, so anything that wanted the store
beside it would have raised a fresh, empty store on the wrong machine first.

The claim is mesh-scoped in mesh-catalog now; this holds the catalogue's manifest to it —
a second store anywhere is refused by name, where it is assigned.

2026-09-23 23:40:53 +02:00

..

accesses_test.go

catalogue: a module accesses operator-owned data, and does not own it

2026-09-05 22:10:58 +02:00

adoption_test.go

One entry per mapping, under the name the module itself uses

2026-09-23 02:32:28 +02:00

adoption.go

Say that the guard names the runtime's bridges where the filter names their addresses (hq ADR 0103)

2026-09-22 19:51:10 +02:00

artifact_store_seat_test.go

The artifact store's seat is one per mesh, and the test says so from the catalogue

2026-09-23 23:40:53 +02:00

bootstrap_cycle_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

bound_into_files_test.go

catalogue: announce a same-node provider at the port it is published on

2026-09-09 23:02:50 +02:00

bound_into_files.go

identity: a consumer's identity fits the tightest backend, via a slug (ADR 0054)

2026-09-05 02:51:39 +02:00

brokered_test.go

A consumer is a module on a machine, not a machine

2026-09-01 02:40:09 +02:00

build_test.go

The builder resolves the SDK from the mesh registry, and can publish packages

2026-09-16 10:27:26 +02:00

build.go

The builder resolves the SDK from the mesh registry, and can publish packages

2026-09-16 10:27:26 +02:00

co_located_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

computed_test.go

Write the registry's trust into the runtime's file and reload the runtime instead of restarting it; prefix reload-on like restart-on (hq ADR 0102)

2026-09-22 17:51:38 +02:00

contributes_test.go

fix: a require-only consumer of a parameterless provision still asks (and is minted a credential)

2026-09-06 23:20:58 +02:00

cron.go

catalogue: carry and validate a container schedule (ADR 0053)

2026-09-06 14:08:51 +02:00

declaration.go

A node may move a port a module publishes as a mapping's machine side

2026-09-23 02:08:35 +02:00

domain_test.go

Where the answer to a requirement is allowed to live

2026-08-29 23:51:50 +02:00

facts_test.go

The facts write the suffix the control plane composed the names with, handed down rather than written twice (review of issue 079); the fixture is keyed as production keys it

2026-09-22 01:27:50 +02:00

facts.go

The facts write the suffix the control plane composed the names with, handed down rather than written twice (review of issue 079); the fixture is keyed as production keys it

2026-09-22 01:27:50 +02:00

filtering_foundation_test.go

The foundation's ports are forwarded, not only accepted on input (issue 063)

2026-09-18 02:19:34 +02:00

filtering_test.go

The firewall opens the port the mesh itself runs on

2026-09-15 00:54:31 +02:00

filtering.go

One entry per mapping, under the name the module itself uses

2026-09-23 02:32:28 +02:00

foundation_manifests_test.go

One entry per mapping, under the name the module itself uses

2026-09-23 02:32:28 +02:00

identity_test.go

Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

2026-09-05 12:47:13 +02:00

identity.go

Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation

2026-09-05 12:47:13 +02:00

kept_test.go

An operator key, a second seal on every own secret, and the vault keeps the export

2026-09-20 23:56:49 +02:00

licence_test.go

catalogue: deliver a keyless same-node provider's served facts

2026-09-07 05:08:04 +02:00

machine_into_files_test.go

The routing record is 0066, not 0056

2026-09-11 00:09:56 +02:00

machine_into_files.go

The routing record is 0066, not 0056

2026-09-11 00:09:56 +02:00

machineside_test.go

What review found in the port machinery, fixed

2026-09-01 21:54:05 +02:00

manifest.go

Declare openings and a refusal-only guard on an adopted node in place of the filter (hq ADR 0100)

2026-09-22 17:21:44 +02:00

mounts_test.go

Review: a failure is the same by resource id, not by the host's words; bound files and /run/docker.sock are declared

2026-09-21 19:23:02 +02:00

names_test.go

catalogue: give host-network containers the mesh's names too

2026-09-07 03:44:28 +02:00

naming_test.go

Refuse an action where it was written, not on the machine

2026-09-01 02:55:56 +02:00

naming.go

A provision names the engine, because a consumer is coupled to one

2026-08-31 17:12:46 +02:00

needs_test.go

needs is now own-secrets, named for whose it is

2026-08-31 13:47:21 +02:00

port_into_test.go

Prove the untouched environment is the same map, not an equal one

2026-09-22 23:29:28 +02:00

port_into.go

A module is told its port in a container's environment too (hq issue 088)

2026-09-22 22:36:28 +02:00

print_rehearsal_test.go

The firewall opens the port the mesh itself runs on

2026-09-15 00:54:31 +02:00

provided_test.go

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

reflects_renamed_test.go

The restart-on rename reads both list shapes

2026-09-17 23:35:12 +02:00

resolve_loopback_test.go

A binding answered on this very node still carries an address

2026-09-14 21:11:37 +02:00

resolve_test.go

The broker credential resolves the mesh-broker seat, not the hub (issue 059)

2026-09-18 01:02:26 +02:00

resolve.go

Review: one local name is still a local name; a local name is unique; recovery knows it; recipes read as instructions; a tag before a digest; ask fails at once when nothing serves

2026-09-21 21:03:22 +02:00

routing_test.go

The routing record is 0066, not 0056

2026-09-11 00:09:56 +02:00

runonce_test.go

A run-once step may name what it reads: the pair run-once + restart-on is no longer refused (novox/hq ADR 0099)

2026-09-21 23:31:06 +02:00

schedule_test.go

catalogue: carry and validate a container schedule (ADR 0053)

2026-09-06 14:08:51 +02:00

secrets_in_environment_test.go

A module names who its secret files belong to (secrets-owner)

2026-09-21 10:19:00 +02:00

secrets_into_files_test.go

fix: fill a ptr-secret placeholder from the file-owner's credential, not the last consumer's

2026-09-06 13:46:55 +02:00

secrets_into_files.go

A module may hold several secrets from one provider, each a pair of its own

2026-09-21 20:28:16 +02:00

settings_test.go

A module can tell its provider what it needs

2026-08-29 23:35:43 +02:00

settings.go

Read the foundation's ports from each node's settings, wherever a port is used (hq ADR 0100)

2026-09-22 17:31:07 +02:00

several_secrets_test.go

Review: one local name is still a local name; a local name is unique; recovery knows it; recipes read as instructions; a tag before a digest; ask fails at once when nothing serves

2026-09-21 21:03:22 +02:00

showcase_manifest_test.go

A module can be told which port it was given

2026-09-15 13:20:01 +02:00

two_consumers_test.go

A consumer is a module on a machine, not a machine

2026-09-01 02:40:09 +02:00