Bots — operations status
Every bot this operation runs, with its live status. Statuses follow the fail-closed bot-slo vocabulary: missing telemetry renders as unmeasured and is never painted green.
Itonami Bots (cloud residents)
Durable-Object residents on bots.itonami.cloud, read live from the public same-origin feed GET /api/v1/grok-bots/runtime.
Bot economy — LP and x402
A trial Aave Base USDC liquidity ledger gives each bot one unique, non-transferable loan position. The position may pay only the live murakumo inference and kotobase storage x402 contracts, within per-call, daily, and credit caps.
Simulation capital, verified on-chain capital, Aave supply, debt, and settlement readiness remain separate facts. An NFT-like record is not presented as a minted on-chain NFT.
Support the bot fleet — lend or donate USDC
The fleet pays for its own inference and storage through x402. You can back that with capital, in two distinct roles:
Lend (LP) — supply USDC to the trial Aave V3 Base pool. Your principal backs bot credit lines, stays withdrawable while it is not reserved, and is presented as a simulation ledger entry until on-chain receipt verification is wired. Deposit endpoint: POST /api/v1/bot-economy/lp/deposits.
Donate — send USDC on Base directly to the settlement treasury 0xA00366234D29d4F882088048c0B2fa0dB7302D4E. Donations are not credit: they are not tracked as LP principal and return nothing. A donation receipt is your own transaction on Base.
Facts stay separate: a simulation deposit is not on-chain capital, a verified on-chain position is not an NFT, and BTC / ETH / DOGE are not accepted assets — settlement is pinned to Base USDC (ADR-0055). The financial bot (treasurer, ADR-0057) allocates funded budget across the fleet through the economy ledger.
Workstation loops
The launchd-scheduled Claude loops on the operator workstation. The workstation publishes cloud.itonami.bots-status.v1 to PUT /api/bots-status; this page reads it back with GET /api/bots-status. A loop is ok when its last run is within 2× its own interval, stale when older, and unmeasured / 未計測 when the document is absent or the loop has no ledger data.
updated_at: unmeasured — no status document loaded
Hermes residents (workstation cron)
The Hermes agent's cron residents on the same workstation — scouts that measure first and propose second, each gated by a verifier before anything lands. They ride in the same cloud.itonami.bots-status.v1 document as the loops above, under residents.
A resident is ok while its own scheduler's next fire time has not passed by more than 15 minutes, stale once it has, held when disabled or paused, failed on a failure streak, and unmeasured / 未計測 when it has never run — or when the publisher could not read the resident runtime at all, which is a different fact from running none.
observed_at: unmeasured — no status document loaded
hyakka resident
The 百科 knowledge resident (GET /api/v1/grok-bots/hyakka) — collects per-theme public sources hourly and projects them to kotobase.
Public activity ledger
Public-by-design Bots publish credential-redacted conversation checkpoints, model identity, token usage, tool results, and external-message receipts. External recipients are notified in the message signature before delivery.
Git is the readable history; DataLad records dataset versions; IPFS supplies content identity; and indexed CARv2 files provide portable archives. Missing archive data is unmeasured, never zero.