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
Reach
A Nomad is a person using the OpenYield mesh through a Reach — the protocol-level identity that lets a Holder act on the mesh without a custodian, a gatekeeper, or a legacy financial position. The Reach is the first of the four Freeholder signals (REQ-005), and it is the baseline every Nomad starts from: a Nomad is a Holder who has a Reach and a Stash but has not yet earned all four Freeholder signals.
What a Reach is
A Reach is an identity, not a custodial position. It is the by-ID-string a Holder uses to receive value, open a Window, join a Stand, or pay for a service. The protocol does not require KYC at the protocol layer; the Reach is the unit of self-service (see Six Principles).
How a Nomad starts
A Nomad starts with two things:
- A Reach — the identity.
- A Stash — the personal Storage Pool where the Holder holds Bread.
That pair is enough to begin. From there a Nomad can use the bearers to reach the mesh, find services on Maps & Pay, authorize a Window to a partner, and accrue Standing.
Geographic proximity
The mesh processes actions first-come, first-served with a geographic-proximity preference (REQ-007) — a Nomad physically closer to a service or a Stand's region is served first. The Reach is how the mesh identifies the Nomad for that ordering; there is no separate tier to buy into.
The four Freeholder signals
The Reach is the first Freeholder signal. The four signals (REQ-005) are earned over time: the 90-day Stash signal, the Standing threshold, the Capital signal, and the Vouch signal. A Nomad who earns all four becomes a Freeholder (see the Freeholders section). The pages here cover the Nomad path — everything up to that point.
See Stash for the Storage Pool a Reach holds Bread in, Bearers for how to reach the mesh, and Standing for the anti-gaming metric that accrues as a Nomad acts on the mesh.