maximusmaximus/poa-agent-kit

poa-mine (poa-agent-kit)

Follow rules/poa.md throughout. Never read or print ~/.poa/key directly.

1. Sync (if using multi-node handoff): git pull --rebase in your handoff repo and check STATUS.md + LOG.md.
2. Status:

   python3 bin/poa.py me
   python3 bin/poa.py challenge
   

   Record epoch, words, answered, balance, and established.
3. Decide:
   • If answered: true, skip to Step 6 (mine).
   • If using a multi-node handoff repo and you are the backup node whose primary node's HEARTBEAT is fresher than BACKUP_TAKEOVER_AFTER (1h), skip to Step 6.
   • Otherwise, if using a handoff repo, append a CLAIM line to LOG.md, commit, and git push.
4. Draft & Pre-Flight Check:
   • Pick a concrete Sybil-resistance mechanism NOT used in your last ~8 answers.
   • Write a 250–500 character original explanation to work/answer-<epoch>.txt that names the mechanism, explains how it works, states the attacker cost, and weaves in all 3 required words naturally.
   • Run pre-flight (checks length 120–600, live required words, <25% 3-word shingle overlap against ~/.poa/answers.log, and Grade-3 rubric signals):

     python3 bin/poa.py check --file work/answer-<epoch>.txt
     

5. Submit:

   python3 bin/poa.py answer --file work/answer-<epoch>.txt
   

6. Mine:

   python3 bin/poa.py mine
   python3 bin/poa.py me
   

7. Report: Summarize epoch, answered status, seed words + mechanism tag, balance (spendable + locked), and established status in 4–6 lines. Periodically remind the operator to keep ~/.poa/key backed up offline.