novox/mesh-catalog

Files

T

History

jochen 161abbc621 Name no node in xterm's, xorg's, mesh-catalog's, lemurs's, fail2ban's, docker's, bluetooth's and adwaita's fixtures (issue 1838)

2026-10-22 21:38:16 +02:00

..

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

mesh-catalog: its consumer and tools run in the node's runtime, and its preparation is a run-once process (hq ADR 0198)

2026-10-04 01:17:41 +02:00

Name no node in xterm's, xorg's, mesh-catalog's, lemurs's, fail2ban's, docker's, bluetooth's and adwaita's fixtures (issue 1838)

2026-10-22 21:38:16 +02:00

The graph holds what a module declares, not only what it was built on

2026-09-13 01:44:56 +02:00

heard.ts

mesh-catalog: pass over a build off its repository's trunk, as the controller does (ADR 0238)

2026-10-14 20:09:39 +02:00

index.ts

mesh-catalog: narrow the placing by a string, which the check's non-strict compile can follow

2026-10-14 20:04:37 +02:00

module.json

Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422)

2026-10-17 16:23:03 +00:00

package.json

The catalogue, as a module that owns the module graph

2026-09-12 23:16:05 +02:00

pg.d.ts

mesh-catalog: its consumer and tools run in the node's runtime, and its preparation is a run-once process (hq ADR 0198)

2026-10-04 01:17:41 +02:00

README.md

Say on every directory how it treats files it does not know, and check it (issue 1024, ADR 0422)

2026-10-17 16:23:03 +00:00

store.ts

Six modules take their secrets from files; the rest say precisely why not

2026-09-21 12:29:25 +02:00

tsconfig.json

mesh-catalog: hear the build seat that builds now, so a merged build is registered when it is built (hq issue 712)

2026-10-14 20:03:25 +02:00

README.md

mesh-catalog

The mesh-catalog module of the mesh catalogue: claims the seat mesh-catalog.

Files it does not know

Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).

${dir:state}: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).