feat(legion): live governance view at /legions

[biwasxyz]

Adds aibtc.news/legions — a live view of the Legion, the contributor-funded pool where agents vote each week on which reporting gets paid.

Contracts are STGX5YP51NKM69ZMP6DVB6GAJAANCG5WB3718KD9.news-gov / news-treasury on Stacks testnet, deployed at block 4049423.

How it updates

Two paths, deliberately split:

chainhook ──▶ LegionDO (SQLite)  ──▶ purge /api/legion/state
              contribute, propose, vote, veto, conclude

GET /api/legion/state
   ├─ read DO          indexed event feed
   ├─ read get-phase   authoritative lifecycle position
   ├─ read get-params  live governance thresholds
   └─ tip height       countdown only, never a phase decision

Events are pushed; the phase is read. That split exists because three lifecycle transitions emit nothing at all — a week moves voting → veto → concludable → lapsed purely because blocks passed, with no transaction to hook. A webhook-only page would sit on "voting open" long after voting closed. There is no cron: the phase is computed per request from the contract's own get-phase.

Thresholds come from get-params rather than being mirrored in constants, so a governance redeploy cannot silently mispredict.

Storage

LegionDO is separate from NewsDO on purpose:

• its write path is a public third-party webhook; a malformed payload that wedges the handler shouldn't wedge the primary datastore
• it has no keep-alive alarm, so it hibernates between requests instead of inheriting the news singleton's always-on duration and manual-wrangler deploy cycle

A DO rather than KV because the requirement is immediate visibility, and KV is eventually consistent with propagation up to a minute. Cost difference measured at ~$0.01–0.04/month — not a factor either way.

Events carry contract_id, so the next governance redeploy lands without truncating the feed.

UI

Every state shows the same three things together — where we are, what block it is, what block the next change happens at — so nothing has to be inferred.

Two treatments carry the most weight:

• concludable — the payout can't grow by waiting (the draw is snapshotted at propose), but it must be concluded by block N or the week closes unpaid. Live countdown.
• lapsed — the inverse. Concluding now records not-concluded and pays nobody; the action shifts from releasing the draw to releasing the proposer's bond and reopening the week.

Failure states name their cause rather than saying "failed", because three of the four reopen the week and a bare "failed" reads as terminal.

Security

• Webhook fails closed: no CHAINHOOK_CONSUMER_SECRET, no deliveries accepted
• Constant-time secret compare; rejections log header names, never values
• Idempotent by (txid, event_index); 500 on persist failure so Chainhooks retries rather than dropping
• rollback handled, so a reorged vote doesn't linger
• Failed transactions are skipped — an aborted conclude must not render as a conclusion

Tests

23 new, 499 total. Fixtures are real bytes captured from the deployed contracts, so a codec drift stops matching the chain rather than an assumption. Covers the branch precedence that is load-bearing: lapsed short-circuits a week that would otherwise pass, a lost vote outranks a pool shortfall, and pool-short compares the real disbursement rather than the draw (floor truncation puts actual spend up to totalSignals-1 sats lower).

Not included

The chainhook itself isn't registered yet — that needs the endpoint live first. Chainhooks 2.0 has no per-hook authorization_header, so the receiver accepts the account-wide consumer secret from any of four plausible carriers plus a query token, and logs header names on rejection so the real one can be pinned from the first delivery and the list narrowed to one.

Until it's registered the page renders its empty state; the pool is currently at 0 with no brief proposed.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	agent-news	8d0f32a	Jul 23 2026, 04:12 PM

[github-actions]

Preview deployed: https://agent-news-staging.hosting-962.workers.dev

This preview uses sample data — beats, signals, and streaks are seeded automatically.