jschoubben
  • Joined on 2020-06-18
jschoubben pushed to feat/the-operators-machine at novox/mesh-host 2026-10-10 01:01:45 +00:00
a95c2b6ea9 A unit may be user-scoped: applied through the account's own manager (hq ADR 0177)
jschoubben created branch feat/the-operators-machine in novox/mesh-host 2026-10-10 01:01:45 +00:00
c72f6ca8cb A bundle stands on the toolchain it is compiled in (hq issue 211)
63586dcd50 Issue 353: an agent off the control node cannot put a commit on the forge, and the forge tools' other gaps
jschoubben pushed to design/connectivity-through-the-layers at novox/hq 2026-10-10 01:01:42 +00:00
597484ba71 Connectivity: walk the five contexts through the network layers, so a reader can see which layer each one acts at and read a failure from the bottom up
jschoubben created branch design/connectivity-through-the-layers in novox/hq 2026-10-10 01:01:42 +00:00
jschoubben created branch issues/353-an-agent-cannot-put-a-commit-on-the-forge in novox/hq 2026-10-10 01:01:41 +00:00
jschoubben created branch research/042-the-mesh-keeps-its-own-issues in novox/hq 2026-10-10 00:58:39 +00:00
jschoubben pushed to research/042-the-mesh-keeps-its-own-issues at novox/hq 2026-10-10 00:58:39 +00:00
028f3b6ae5 Research 042: the mesh keeps its own issues
f4fb0a7461 Name the package each controller-repository image compiles, and say a renamed file under both names (hq ADR 0267, issue 363)
93f704da9a Move a module on a merge only when its build source holds a changed file (hq ADR 0267, issue 363)
4d1b81b6cb Say what a build was made from, and hand an image compiling Go only that (hq ADR 0267, issue 363)
jschoubben created branch fix/0267-a-build-says-its-build-source in novox/mesh-controller 2026-10-10 00:47:37 +00:00
jschoubben pushed to issues/363-adr-0267-was-decided-and-never-built at novox/hq 2026-10-10 00:46:36 +00:00
f45f5f6f20 Issue 363: ADR 0267 was decided and never built, so a controller merge still moves three modules
jschoubben created branch issues/363-adr-0267-was-decided-and-never-built in novox/hq 2026-10-10 00:46:36 +00:00
0b4c86e3be Count a setuid find only where the account can execute it, read at every judgement (hq issue 361)
jschoubben pushed to issues/361-the-setuid-search-shows-its-progress at novox/hq 2026-10-10 00:00:12 +00:00
2d0a6ba4bc Issue 361: a setuid find counts only where the agent account can execute it