White Paper Amendment A — Authority Clearing Network

Status: Initial implementation specification, Version 1.0.

Purpose

GoGuides adds a separate authority-clearing layer above its existing evidence, provenance, interpretation, and public trust infrastructure. The existing GoGuides system remains intact.

Shared-state primitive

The primitive is Current Delegated Authority State: a current, independently checkable record of how much delegated authority remains available for a machine action.

Machine flow

A requesting system asks GoGuides to reserve authority. GoGuides atomically checks current state, replay/idempotency, revocation, expiry, and remaining authority. It then issues a signed clearance. The receiving system validates that clearance against GoGuides immediately before acting and returns a receipt afterward.

Why independent clearing matters

Independent systems cannot safely reconstruct one another's current delegated authority from static credentials, old tokens, or local logs. A neutral shared state prevents replay and conflicting consumption while creating an auditable machine-action record.

Neutrality

Payment, API access, or clearing volume does not alter GoGuides AI Rank, public eligibility, evidence, or trust decisions.

Initial state model

Authority states: ACTIVE, FROZEN, REVOKED. Clearance states: RESERVED, INDETERMINATE, CONSUMED, RELEASED.

Evidence

Authority transitions and clearance transitions are recorded in an append-only, per-authority hash-chained event log. Signed clearances use Ed25519. Live validation remains authoritative because signed credentials can become stale after freeze, revocation, expiry, or a prior action.

Commercial boundary

The clearing service is a metered B2B API layer. GoGuides can charge for clearing, validation, receipt processing, reconciliation, volume, service levels, and retained evidence without degrading free public trust data.