Skip to content

Token Reports and Agent Loop

kadubon edited this page Jul 1, 2026 · 1 revision

Token Reports and Agent Loop

Token reports are v0.9 JSON reports for checking whether a useful intervention can be reused safely in Node.js and TypeScript agent systems.

Main Reports

  • token-extraction-pipeline-report: turns a finite trace into a candidate token.
  • token-admissibility-report: checks provenance, guard/failure contract, mechanism reuse, leakage, dependency closure, verifier binding, transport scope, lifecycle, and authority envelope.
  • token-lineage-report: records origin and dependency-aware hashes.
  • token-dedup-report: separates exact aliases and near duplicates.
  • token-interface-standard-report: checks whether the token exposes the fields a runtime expects.

Typical Commands

npx pic-ts token extract-pipeline --trace trace.json --compact
npx pic-ts token admissibility --token token.json --compact
npx pic-ts token dedup --tokens tokens.jsonl

What They Do Not Mean

Token reports do not mean that a claim is settled, a provider may be called, a command may be executed, or abstraction capital has been admitted.

Search Terms

ALT token, abstraction liquidity token, TypeScript token report, Node token report, token extraction, token admissibility, token lineage, token deduplication, leakage audit, capital admission, residual ledger.

Clone this wiki locally