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.0 KiB
Standing
Standing (REQ-006) is a Holder's measured history on the mesh. It is the anti-gaming metric: a Bayesian score with time-decay, diversity weighting, and voucher-weighting, minus slashes for bad behavior. For a Nomad, the headline is that the mesh cannot be gamed — Standing rewards real production and resists the obvious attacks (volume spam, self-dealing, fake vouches).
What Standing is, in plain language
Standing is not a count of transactions. It is a Bayesian score: the mesh starts with a prior, updates it from each observed action, and decays old evidence so a Holder cannot rest on a burst of activity from years ago. Diversity weighting means a Nomad who acts across many services, many Stands, and many bearers accrues more Standing than a Nomad who repeats the same action with the same counterparty. Voucher-weighting means a vouch from a Holder with high Standing counts for more.
Why it matters to a Nomad
A Nomad mostly reads Standing, not computes it. Two places it shows up:
- Choosing a service. Maps shows a service operator's Standing so a Nomad can pick an operator with a real history over a freshly-spun-up alternative (see Maps & Pay).
- The Freeholder path. Earning a Standing threshold in 3 categories is one of the four Freeholder signals (REQ-005). A Nomad who accrues Standing over time is on the path to becoming a Freeholder.
What Standing is not
Standing is not a custodial position, a tier you buy, or a reputation score you can farm. It is not legacy custodial history. The Bayesian + time-decay + diversity design is exactly what makes it hard to game: there is no single input a Holder can pump.
The math, deferred
The full Bayesian formula (priors, decay rates, diversity sub-tables, slash conditions) is documented in the Freeholders section — a Nomad does not need the math to use the mesh. See Six Principles for the covenant Standing enforces, and Reach for the identity a Standing accrues to.