Hubu v0.2.4

What changed

• Governance history. Append-only records and read-only HTTP/MCP queries expose policy decisions, human resolutions, authorizations, and financial transitions, with explicit coverage limits.
• Exact amounts. Budgets, policies, API calls, and the CLI support up to six decimal places. New budget charges use micro-units; historical ledger entries retain their original charges.
• USDC budgets. USD and USDC are accounted separately, without conversion. Wallet rails remain USD-only and reject USDC payments.
• Executor contract v4.5. Hubu and Gongbu use exact amounts for quotes, authorization, claims, and settlement. Legacy whole-cent requests remain supported for this release.

Before upgrading: back up Hubu and Gongbu state and read the upgrade guide. Storage migrations are one-way; restore backups instead of downgrading in place. Hand-written Gongbu configurations must use executor contract v4.5.

Tested system

Hubu remains experimental and local-first. This run uses the released CLI and HTTP API, fresh SQLite, a synthetic external executor, and fixed USD budgets and policies.

Outside this analysis

USDC, governance-query coverage, Gongbu, Temporal, MCP transport, provider adapters, and actual provider billing. The four experiments do not qualify every new release feature.

Known authority limits

Registered agent accounts are not bound to an authenticated runtime or thread. The normal bearer can change budgets and policies. These known gaps are planned for future releases.

Reproduction

Recorded on macOS with the pinned released source and public test scripts. No model subscription or provider credentials required. Setup and commands ↗

These findings concern Hubu’s own ledger and records, not provider invoices. Each result applies only to its stated setup.