PackageFlashyOS
@flashyos/wdk
The FlashyOS agent object: identity, authority, wallet, memory and partners behind one interface. Create an agent, give it an identity, provision financial capabilities on Tether WDK, set its permissions, let it transact, record what it did, coordinate it with other agents — through one object, one event system, any chain WDK reaches.
version 0.1.0 · measured 2026-10-30 from a checkout · source: flashyos/packages/wdk (private repository; the package is on npm as @flashyos/wdk) · public face flashyos.com
npm i @flashyos/wdkOne object, two sides: FlashyOrganization is what humans do — create agents, set and revoke authority, register addresses, set settlement policies, resolve decisions, read the ledger — and FlashyAgent is what an agent does with its own token. No method on the agent can widen its own authority; no method on the organization moves money.
Refusals are values, not exceptions: denied (the plane), refused (the signer), escalated (a human is needed) and unrecognised (no extractor vouches for the call) all come back with a code and a reason. Only a transport failure throws, as TransportError, and it is never mistaken for a verdict.
Edge cases — each one paid for once
transact() re-derives the call before proposing it, every time
The chain id picks the extractor that re-derives what an EVM transaction, a TRON transaction, or a swap/bridge protocol call actually does before anything is proposed to the plane — adding a chain WDK reaches is an extractor pack and a signer backend, and nothing in this package’s own interface has to change.
flashyos-run wires the object from environment variables alone
The bundled CLI runs a module’s default export (agent, org) => … with FlashyOrganization pre-wired from FLASHYOS_* environment variables and every event emitted as a JSON line on stdout — the same object an integration test drives directly through InProcessTransport, so a demo and a test exercise identical code.
A workflow_dispatch has no branch restriction
Two packages in this plane reached public npm from commits main did not reach; on one the versions matched, so every version check saw agreement. Both publish workflows now fetch full history and refuse a commit the default branch does not contain.