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---
47 lines
2.3 KiB
Markdown
47 lines
2.3 KiB
Markdown
# Anchor Preview
|
|
|
|
An **Anchor** (REQ-023) is the fourth and highest tier of the
|
|
[Partner Spectrum](partner-spectrum.md) (REQ-018) — the first **institutional**
|
|
Partner tier. Anchors are coming in v0.3 P4. This page previews what an Anchor
|
|
is and what the v0.3 skeleton will deliver; the runtime behavior is deferred
|
|
to v0.4+.
|
|
|
|
## What an Anchor is
|
|
|
|
An Anchor is a Partner that carries an **AnchorCredential**: a jurisdiction
|
|
(e.g., "EU-MiCA"), a custody provider, and a set of attestation references.
|
|
The Anchor tier is how the jurisdiction-light mesh interfaces with
|
|
jurisdiction-bound institutional actors without becoming them. An Anchor
|
|
holds a credential; the [Holder](../nomads/reach.md) still holds their
|
|
[Stash](../nomads/stash.md). The mesh says **custody**, **compliance**, and
|
|
**jurisdiction** — never the legacy institutional words banned by the
|
|
[lexicon](../shared/lexicon.md).
|
|
|
|
## What is coming in v0.3 P4
|
|
|
|
v0.3 P4 (REQ-023) extends `x/partner` with the `AnchorCredential` struct and
|
|
a `Partner.AnchorCredential()` accessor (returns nil for non-Anchor tiers).
|
|
The four-tier `PartnerTier` enum (Op, Master Op, Pier, Anchor) is **unchanged**
|
|
— v0.3 adds Anchor-specific fields, not a new tier. The custody-provider-id
|
|
field is a by-ID-string reference to `x/hub` (the Hub API, coming in v0.3 P5),
|
|
empty in the v0.3 skeleton because the Hub is not live until P5/v0.4. This is
|
|
the P4→P5 ordering edge: `x/hub` in P5 references Anchor partner-ids from P4.
|
|
|
|
## Why Anchors matter to a Freeholder
|
|
|
|
A Freeholder engaging an Anchor gets a Partner with a verifiable credential
|
|
and a custody/compliance relationship — useful for cross-jurisdiction routes
|
|
and institutional [bonds](bonds.md). The Anchor's [Standing](standing.md) and
|
|
attestations are visible so the Freeholder can verify the Anchor is real
|
|
before opening a [Window](../nomads/window.md). See
|
|
[Partner Spectrum](partner-spectrum.md) for the other three tiers, and
|
|
[Councils & Voice](councils-voice.md) for how the Mesh Council can suspend or
|
|
revoke an Anchor.
|
|
|
|
## What v0.3 does not deliver
|
|
|
|
The v0.3 skeleton is types + tests only (D-035): the `AnchorCredential`
|
|
struct, the accessor, and the `ListAnchors()` keeper alias. Live custody
|
|
routing, attestation verification, and the Hub API integration are v0.4+
|
|
runtime work. See [Components](../reference/components.md) for the full
|
|
module map. |