docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
This commit is contained in:
parent
53ccbcb4b3
commit
6739bb903d
1 changed files with 736 additions and 701 deletions
|
|
@ -15,13 +15,13 @@
|
|||
//! enumerated and re-emitted, and an enumeration that can silently drift
|
||||
//! advertises a boundary it does not hold. A wide grant that says so beats a
|
||||
//! narrow one that only looks narrow. The narrower shapes, and what they would
|
||||
//! cost, are in `docs/trust-boundary/security.md`.
|
||||
//! cost, are in `docs/2-handbook/trust-boundary/security.md`.
|
||||
//!
|
||||
//! The **hive** stanza has no such problem and is therefore narrow: that path
|
||||
//! names its principal, so scoping it to the reader's own name costs nothing
|
||||
//! and drifts nowhere. Do not widen it to match the agent stanza — the
|
||||
//! asymmetry is the point, and only holds if a one-per-hive credential is
|
||||
//! stored under [`Kind::Hive`] — see docs/trust-boundary/security.md.
|
||||
//! stored under [`Kind::Hive`] — see docs/2-handbook/trust-boundary/security.md.
|
||||
//!
|
||||
//! A hive reads nothing under `swarm/services/` or `swarm/controller/`. A swarm
|
||||
//! service's OIDC client secret is read under a certificate that is not a
|
||||
|
|
|
|||
Loading…
Reference in a new issue