cloudinit-bot
82ae6cf5a2
Milestone v0.3 complete. Feature type, tags v0.2.x. Two work-streams shipped under one feature milestone: (A) Bearers skeleton + tests (D-020 pattern, 7 x/* packages, zero ext deps): - x/bridge (NEW): BridgeStatus enum (4), BridgeRoute by-ID-string refs - x/exit (NEW): ExitStatus enum (5), ExitRoute, DEXSwap (opaque venue) - x/bearers (EXT): OYSATLink surveillance-resistant LOCKED, OYQRCode idempotent - x/partner (EXT): AnchorCredential (custody-provider-id empty in skeleton) - x/hub (NEW): HubService enum (3), LendingCouponCapBps=800 LOCAL const (A-304) - x/services (NEW): ServiceKind enum (4), window-id by-ID-string ref (A-307) - x/bond (EXT): GrowthBond, ClampGrowth G-012 underflow guard, secondary market All packages >=93.3% coverage. Both lexicon firewalls green. G-003 intact. (B) Documentation deliverable (REQ-027 complete, 26-page MkDocs Material site): - README.md + mkdocs.yml + docs/index.md - docs/shared/ (7 pages): Six Principles, Bread Scale, Storage Pools, Watchers/Mirror, Lexicon, Vision - docs/nomads/ (8 pages): Reach, Stash, Bearers, Maps-Pay, Pacts, Standing, Window - docs/freeholders/ (8 pages): Signals, Standing, Stands-Guilds, Councils-Voice, Bonds, Partner Spectrum, Anchor Preview - docs/reference/ (2 pages): Architecture, Components - REQ-028: lexicon firewall extended to docs/ + README.md (lexicon_meta_docs_test.go, 5 tests incl G-013 walk-coverage + G-014 shared self-test) Phases: P0 -> v0.2.0, P1 -> v0.2.1, P2 -> v0.2.2, P3 -> v0.2.3, P4 -> v0.2.4, P5 -> v0.2.5, P6 -> v0.2.6 (milestone release). Requirements covered: REQ-010, REQ-022, REQ-023, REQ-024, REQ-025, REQ-026 (skeleton), REQ-027, REQ-028 (complete). IDEATE-01..08 ratified and delivered. ---ci--- project: oy phase: 6 milestone: v0.3 status: complete tag_base: v0.2.x phase_role: final milestone_complete: true requirements: covered: [REQ-010, REQ-022, REQ-023, REQ-024, REQ-025, REQ-026, REQ-027, REQ-028] partial: [] ---/ci---
2.1 KiB
Nomads
A Nomad is a person using the OpenYield mesh through a Reach — the protocol-level identity a Holder uses to act on the mesh without a custodian, a gatekeeper, or a legacy financial position. The Nomad path is the entry path: a Nomad is a Holder who has a Reach and a Stash and is on the way to earning the four Freeholder signals, but has not yet earned all four.
The Nomad path
The pages here cover what a Nomad does day-to-day on the mesh:
- Reach — the identity; the first Freeholder signal (REQ-005).
- Stash — the personal Storage Pool where a Nomad holds Bread (REQ-014).
- Bearers — how a Nomad reaches the mesh (REQ-019): Internet, OY-BLE, OY-WiFi-Direct, OY-LR live now; OY-SAT and OY-QR coming.
- Maps & Pay — finding services and paying for them.
- Pacts — the six contract shapes a Nomad encounters (REQ-020): Pause, Ground, Stance, Cover, Stand Registry, Hub API.
- Standing — the Bayesian anti-gaming metric (REQ-006), and why the mesh cannot be gamed.
- Window — the delegation primitive (REQ-015): scope, duration, rate-limit, audit-log, revoke.
Where a Nomad starts
A Nomad starts with a Reach and a Stash — that is enough to begin. From there the bearers carry value to the Stash, Maps finds services, Pay and the Window let a Nomad use them without giving up custody, and Standing accrues as the Nomad acts. A Nomad who earns the 90-day Stash signal, the Standing threshold, the Capital signal, and the Vouch signal becomes a Freeholder (see the Freeholders section).
Shared concepts
The Nomad path rests on the shared concepts: the Six Principles, the Bread scale, the Storage Pools, the Watchers & Mirror, and the Lexicon. The covenant is the same for every audience; the Nomad pages describe how it shows up in everyday use.