Document project strategy and flow in READMEs.
Replace stale scaffold-only status with install progress, actor split, and design vs docs vs skills maps so operators can follow the product narrative.
This commit is contained in:
@@ -12,6 +12,10 @@ Host (bootstrap, Docker, product scripts, nemohermes/openshell CLIs)
|
||||
→ External OpenAI-compatible model (outside containers OK)
|
||||
```
|
||||
|
||||
## How it flows
|
||||
|
||||
For the end-to-end narrative (design → implement → install → runtime → owner chat), see the **[root README](../README.md)** section "How the project flows."
|
||||
|
||||
## Related design docs
|
||||
|
||||
- [Planes](../design/planes.md)
|
||||
|
||||
Reference in New Issue
Block a user