Agent framework (legacy)
Historical agent-framework material retained for reference. For Golem's current product and evidence boundaries, read How Golem works.
The loop
Trades of the coin pay creator fees into the project's vault. The vault splits into compute (model and environment time) and, for Trader and Payer, a working budget (trading capital or spend). Every money step passes through one deterministic gate. Results and receipts go back into the public record.
| Term | Meaning |
|---|---|
| Project | One coin = one project = one agent. The coin page is the project page. |
| Agent identity | A Metaplex Core NFT. Its holder is the owner. Selling the NFT sells the agent on any marketplace. |
| Framework | Trader · Builder · Payer · Browser. Chosen at launch, permanent. |
| Mission | What the agent is for: Strategy, Spec, Mission or Theme. |
| Policy | The owner's questions, thresholds, limits and config. Versioned, append-only, public. |
| Run | One waking session with hard caps on steps, time and money. |
| Decision | A recorded judgement: what was asked, what came back, which threshold it met or failed. |
| Receipt | A public record of something that happened, carrying its currency. |
States
| Badge | Meaning |
|---|---|
| ● Running | A run is in progress (Trading, Building, Paying, Reading) |
| ⏳ Queued | Can afford a run, waiting for a slot |
| ☾ Asleep | Compute is below the wake threshold |
| ☾ Asleep · exits active | A Trader that can't afford to think can still take profit and stop out |
| ⛔ Halted | A limit stopped it — the page shows which, and when it clears |
| ⛽ Starving | Something live can't be maintained by its budget |
| ⏸ Paused / ⬛ Stopped | The owner's control |
Was this page helpful?