A Gord Holdings company on the FlashyOS meshRoadmapFlashyOS ↗

PackageFlashyOS

@flashyos/wallet-wdk

Governed economic agency for FlashyOS agents on Tether WDK: the AAO WalletCapability, a FlashyOS authorizer client, an MCP elicitation handler, and a WDK policy rule that defers to the authorization plane.

version 0.1.0 · measured 2026-10-30 from a checkout · source: flashyos/packages/wallet-wdk (private repository; the package is on npm as @flashyos/wallet-wdk) · public face flashyos.com

npm i @flashyos/wallet-wdk

The one description of a spend the plane, the signer and the agent all agree on: OperationRecord — kind, chain, asset, amount in base units, destination — derived from a real call by an extractor, never guessed. A call no extractor can read is refused, not passed through.

FlashyOSAuthorizer asks the plane for a verdict on a record — ALLOW with a signed SpendAuthorization, ESCALATE with a decision id a human will resolve, or DENY with a code — and FlashyOSWalletCapability is the same thing as an AAO WalletCapability, so an agent built on @flashyos/aao declares it like any other capability.

The package an agent runtime, a signer or a stranger verifying our records installs. It carries no dependency on the FlashyOS API: an agent asks the authorization plane for a SpendAuthorization and the plane answers with a signed decision, so the thing that moves money and the thing that decides never share a process.

Edge cases — each one paid for once

The MCP elicitation handler fails closed on every error path

createElicitationHandler has no path by which an error becomes an approval — an unreachable plane, a call no extractor recognises, or an escalation that never resolves in time all turn into decline, never a silent ALLOW, and a human is still consulted through the plane’s Decision ladder for whatever grades high enough to need one.

A verdict it cannot parse is never silently ALLOW

AuthorizerRefused carries the plane’s own error code and AuthorizerUnreachable says the plane did not answer at all, while verifyReceipt and verifyExport run entirely offline — a stranger can check a receipt or a hash-chained export against a public key alone, with no account, token or API call involved.

An optional dependency must also be one the package BUILDS without

esbuild resolves and bundles a string literal inside import() however carefully the try/catch around it is written, so a present @tetherto/wdk subtree inlined the lazy import, the try/catch went dead, and nothing was red. Externals are now derived from optionalDependencies in the tsup config and a test is the alarm for the silent half (flashyos, docs/record/one-lockfile-two-trees.md).

One lockfile, two Node versions, two trees

npm drops an optional subtree whose engines the running Node cannot satisfy silently. CI ran Node 22 and the deploy ran Node 20, so the same commit built green on CI and red in production at a step named after a package neither commit had touched. The versions agree now and a test refuses the divergence.

Published to a registry is committing, not serving

This package and its two siblings went live on npm on 2026-09-22 and reached no catalog, no case study and no thesis — zero references anywhere a stranger deciding to depend on it would read. The distribution floor in flashyos measures that; the coverage gate on this site refuses it.

← Full catalog · The doctrine behind the tools · Adopt one