Governance and oversight model

YieldGuard governance begins with product boundaries, evidence controls, and change discipline. Lens, Intel, Shadow, Packets, API, Assisted workflow, and Assurance share a requirement for clear ownership, source control, methodology versioning, and release evidence.

YieldGuard Ltd acts as a technology provider. It does not custody client assets, hold private keys on behalf of users, provide investment advice, act as broker or dealer, or perform discretionary investment management. Regulated activities, which can arise, must be performed by authorised external parties.

Workflow expansion follows readiness gates. Lens can ship with public-safe Macrovision data; Intel and Shadow can ship after data freshness and replay checks; Packets can ship after deterministic evidence export; Assisted workflow can ship only after identity, object authorisation, telemetry, rollback, and approval controls pass.

Data, methodology, and proof oversight

Macrovision data, which appears in Lens, must carry source, as-of time, freshness state, confidence, and methodology version. Public data must stay separate from customer-specific workflow and must never expose private database or operational details.

YieldGuard proof artefacts should include Decision Room summaries, committee packet JSON and HTML, TrustReceipt concepts, replay status, and offline verification, which the underlying system can support. Public website copy should reference those artefacts as evidence surfaces, not as live investment execution.

Oversight is measured through release evidence, source freshness, deterministic replay, packet completeness, access logs, and pilot scorecards. A product tier should graduate only when its evidence, security, and operational gates are satisfied.