Documentation images (placeholders)
High-resolution or branded figures can live here. Mermaid diagrams in Markdown remain the default so diagrams stay diff-friendly.
When you add an asset, reference it from the relevant doc using a path relative to that file, for example from handbook/02-blueprints.md:
Suggested assets (titles are indicative):
| File | Intended content | Primary readers |
|---|---|---|
boot-flow.png |
Host → seeder swarm → booter → MBR → drives → init.js → shell |
User manual, handbook ch.2–3 |
two-drive-vfs.png |
System vs personal Hyperdrive and path routing ($HOME, /.bare/) |
Handbook ch.2, reference VFS |
hyperswarm-protomux.png |
Topic discovery, replication channel bare-os-v1 |
Handbook ch.3, protocol reference |
ctx-hierarchy.png |
ctx fields and capability wiring (simplified) |
Developer guide ch.2 |
identity-vault-lifecycle.png |
Guest → login → vault snapshot / logout | Handbook ch.5, user manual |
shell-pipeline.png |
Tokenize → expand → execute (pipelines, redirects) | Handbook ch.9 |
feature-bits-governance.png |
ADR 001 flow: doc ↔ code ↔ verifiers | Reference kernel-extensions, dev ADR |
Until files exist, narrative pages may include  placeholders with a short caption explaining the intended graphic.