the agent, working alone

Vette runs by itself.

Every day at 06:00 UTC, a cron wakes the engine. No human clicks anything. Vette fetches the contest field, then re-checks every entry — is the website still up? Is the registered wallet still behaving? Same deterministic reads as every audit, run on a schedule.

engine self-check · rendered right now
status
OPERATIONAL
base block
53380269
field entries
0
the loop
  1. 01
    fetch_field()
    read the contest API (0 entries right now)
  2. 02
    check_site()
    is every entry's website still up?
  3. 03
    check_wallet()
    registered wallets: activity, balance, approval surface
  4. 04
    sweep()
    hunt fresh exposure — mine live Base approvals, verify every catch onchain
  5. 05
    report()
    the run summary — visible below when you trigger one
  6. 06
    repeat
    every day at 06:00 UTC, scheduled by vercel.json — until the contest ends
run it now, on demand

The scheduled runs are on the clock (see vercel.json in the repo). You can also wake the agent yourself and watch the run report come back live.

where the permanent log lives

Every run writes its history to the public repo file data/agent-log.json (via the GitHub API), so anyone can audit Vette's behavior the way Vette audits everyone else's. That channel activates when the repo is connected; until then, runs execute and report live — only the permanent archive is pending. Honest, like everything here.

an agent is a schedule, not a screenshot