What SEED Clearance does today

SEED Clearance helps an existing AI assistant act with explicit permission. It does not ask you to switch assistants. It adds a local control layer around the assistant you already use.

What it does

• Creates a local identity for you.
• Registers your assistant under that identity.
• Gives that assistant a signed permission slip.
• Sets a sandbox budget for approved test actions.
• Writes approved and denied actions into a signed local log.
• Exports proof that can be verified later.
• Verifies local provider claims with Ed25519 signatures and a provider signing key pinned by the consumer policy.
• Revokes the assistant so later requests are denied.
• Connects through local MCP or HTTP bridges for Claude Desktop, Cursor, Continue, and generic MCP hosts.

How to think about it

SEED Clearance is closer to a permission system than to a chat product. Your assistant still does the talking and planning. SEED decides whether a controlled action is allowed, records the result, and gives you a way to prove or revoke that authority.

The payment step in the current release path is a sandbox payment intent. It proves the permission and logging loop without moving real money.

The seed-clear API service is live for P2/P3 challenge, BBS+ verification, replay protection and signed receipt. A3-G4/G7 now proves the bounded product-origin chain bridge: consume, materialize, fund, release, claimable-balance query, and hosted public proof. Earth/Mars validator runtime alignment is proven on e63c2a0. There is still no `MsgClaim`, wallet payout, hosted reward center, public claim action, hidden amount reward, or W7 private payment.

The local Trust Loop also proves a provider claim can be signed, checked by a consumer policy, accepted, then refused after revoke. That local evidence does not by itself prove chain anchoring, protocol settlement, or protocol Provider BLS verification.

What comes later

Wallets, live payment settlement, provider marketplaces, autonomous browser control, autonomous shell execution, and a full in-house assistant are separate products or later integrations. They need separate evidence before they appear as public product claims.

Public reward counters, claim buttons, payout settlement, homeostasis mutation, and private-payment rails stay absent until their closure gates pass.