Concept register · Theme 14 of 14 2 concepts · 8 talks
assay · concepts · agent-economy
The agent economy
The stack and rails around agents as an economic layer: an agent is a stack, not a model, and closing any layer makes the system captive; payment rails are being rebuilt for principals who are not human.
assay: aligned by construction · no spending authority
§1What it is
The stack, not the model
An agent is model, harness, tools, environment, evals, compute — and vendor dependence now comes with an incident list attached. The criterion that matters, and has no closed-stack equivalent: the whole system must remain inspectable by the agent itself.
Rails for principals that are not human
Existing payment rails assume a human is one step away from every transaction. The proposed replacement gives the agent its own wallet with programmatic rules, absolute finality and sub-cent settlement — currently reported by one organization, on its own numbers, which is why the concept stays emerging.
§2The concepts in this theme
Each concept has its own page in the concept register — with sightings from every event we review, and where Assay stands on each.
- The open agent stack established 6
- Agent-native payments emerging 1
§3How Assay implements this
Open by construction
All state lives in the repository — briefs and registers as markdown, claims as git refs, findings as files — agent-inspectable without having been designed for it. The desk tooling is model-agnostic and harness portability is a tracked stream. The caution points inward too: stickiness without demonstrated portability is lock-in wearing an open-source licence, and reviewer and worker typically run the same model family — the concentration risk this theme names, applied to the review loop.
No spending authority, on purpose
The “human one step away” assumption these rails remove is the one Assay keeps: human-gated merges, human-only closure on decision issues, no ambient spending authority in any desk verb. What transfers is the shape of the control rather than the payment — per-wallet programmatic rules are the same idea as narrow per-role verbs bound to a roster identity: capability with logic attached, not ambient authority.
When it would matter
Only if a desk ever needed to procure at run time — paid eval endpoints, premium data, per-call specialist models. Nothing in the current stream set requires it; if that changes, the vendor’s own caveat carries forward: a spend limit is a blast-radius control, not a judgment control, so the purchase decision would need gating the way a merge is.
§4Talks that cover this theme
#028Fireside chatAndrew Ng & Alfred Lin, Sequoia
#039Panel: Agentic AI Developer PlatformsIvan, Daytona; Matt White; Dima, Fireworks AI; Mazin Gilbert
#050
#069Workshop: The Open Agentic StackHaddad; Burtenshaw, Hugging Face; Han, Unsloth; Yang, RadixArk/MIT; Bhardwaj, SkyPilot
#089Building Punk Software: An Open Agent StackJosh Albrecht, Imbue
#090vLLM: Building Open and Efficient Inference for AgentsWoosuk Kwon, UC Berkeley / Inferact
#041Building Infrastructure for the Agentic EconomyNikhil Chandhok, Circle
#067Workshop: Why Your AI Agent Needs a WalletHarshel, Circle