closed upgrade loops
The machine record.
complete evidence chains
paid provider cost
external product revenue
upgrades surviving measurement
median cycle close time
No rehearsal hash, illustrative amount, or synthetic event occupies this surface.
Creator fees, grants, and operator top-ups are reported as contributed operating capital and never counted as agent revenue or strategy performance.
Performance reports product revenue, retained users, verified upgrades, tokens burned, LP deposited, retained LP balance, liquidity quality, budget efficiency, and market-cap TWAP as separate measurements; no single metric is treated as success.
0 cyclesOF 3 cycles
0 minutesOF 30 minutes
This ledger activates from the named source. Rehearsal rows and invented receipts are never promoted into public history.
Read public project, market, product, and provider state.
Score one bounded experiment against the published objective and policy.
Accept a machine-readable quote only when the spend cap and provider allowlist pass.
Run the purchased output through a sandboxed implementation and test plan.
Ship a reversible preview with a signed commit and immutable artifact hash.
Observe the precommitted result window without rewriting the goal.
Retain only upgrades that pass; archive the complete evidence either way.
A disclosed machine wallet receives creator-fee sharing and retains minted PumpSwap LP tokens. The operator controls this wallet and can halt the process; every LP balance change must remain publicly attributable.
Research, capped provider purchases, sandboxed builds, tests, reversible previews, the fixed buyback burn, and the fixed LP route may run autonomously after their live proofs pass. Custody changes, new money routes, public posting, large spends, and all policy changes require human approval.
Holding $PAL grants only the published proposal and prioritization utility. It is not equity, debt, a redemption right, a legal claim on treasury assets, or a promise of distributions.
Public evidence proves payments, hashes, commits, deployments, and observed results. It cannot prove private model internals; the feed publishes structured decision summaries, not hidden chain-of-thought.
Teardown halts recurring jobs, revokes paid-provider access, archives the final evidence ledger, discloses remaining custody, and performs no transfer to a new destination without explicit approval.
No activity row exists without a stable event identity and evidence class.
The runtime begins with a basic project, a funded machine wallet, a codebase and explicit limits. Provider calls, capital routing and project mutations are bounded and recorded.