Point three design documents at the code that exists for them
Their subject matter has been built and proven for days and their frontmatter still said code: [] — which is what the cross-cutting view is generated from, so it was claiming nothing existed for the substrate, the node lifecycle and delivery.
This commit is contained in:
@@ -1,7 +1,10 @@
|
||||
---
|
||||
layer: to-be
|
||||
status: designed
|
||||
code: []
|
||||
code:
|
||||
- mesh-host examples/substrate-first-node.lock
|
||||
- mesh-host internal/apply
|
||||
- mesh-lab test/integration/mesh.test.ts (a bare machine becomes a mesh)
|
||||
updated: 2026-08-30
|
||||
decisions:
|
||||
- 02-DECISIONS/0004-a-node-and-how-it-joins.md
|
||||
|
||||
@@ -1,7 +1,10 @@
|
||||
---
|
||||
layer: to-be
|
||||
status: designed
|
||||
code: []
|
||||
code:
|
||||
- mesh-host internal/link/enrol.go
|
||||
- mesh-control internal/token
|
||||
- mesh-control internal/inventory/nodes.go
|
||||
updated: 2026-08-27
|
||||
decisions:
|
||||
- 02-DECISIONS/0004-a-node-and-how-it-joins.md
|
||||
|
||||
@@ -1,7 +1,10 @@
|
||||
---
|
||||
layer: to-be
|
||||
status: designed
|
||||
code: []
|
||||
code:
|
||||
- mesh-control internal/builder
|
||||
- mesh-control cmd/mesh-control (build, build --behind, push, status)
|
||||
- mesh-control internal/inventory/builds.go
|
||||
updated: 2026-08-28
|
||||
decisions:
|
||||
- 02-DECISIONS/0010-delivery.md
|
||||
|
||||
Reference in New Issue
Block a user