No description
| .devcontainer | ||
| cmd | ||
| docs | ||
| ent | ||
| fe | ||
| pkgs | ||
| scripts | ||
| .dockerignore | ||
| .gitignore | ||
| compose.validation.yaml | ||
| compose.yaml | ||
| Dockerfile | ||
| Dockerfile.coturn | ||
| Dockerfile.dev | ||
| Dockerfile.validation | ||
| go.mod | ||
| go.sum | ||
| Vagrantfile | ||
Networkd Docs
This directory is the authoritative documentation set for Networkd.
Read Order
- status.md
- plan.md
- progress.md
- architecture/models.md
- flows/README.md
- Relevant documents under
architecture/,api/, anddeveloper/
For a clean checkout to successful node-mainline validation flow, start with developer/zero-to-green.md.
Source Of Truth
status.md: expected project baseline and stable intentplan.md: delivery plan, known deviations, and correction pathsprogress.md: append-only implementation, validation, and current-state logapi/: expected contractsarchitecture/: expected designflows/: expected process flows with diagrams and model slicesdeveloper/: how to work on the project nowuser/: pre-release operator notes, not product-grade documentation
Archive
Historical material from earlier iterations lives under archive/.
archive/legacy-docs/: older human-facing docs kept for reference onlyarchive/memory-bank/: imported working-memory notes from an earlier workflow
Nothing under archive/ is authoritative unless a newer document explicitly points back to it.