xmatic/pepa-pi-bot
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

feat(roadmap): phased plan + operating principles + presence prompt

Browse Source 
Phase 0 (body) is done. The next steps shouldn't be guessed prompt-by-prompt —
write down the order, the judgement principles, and the next concrete
session prompt, so the bot has a coherent direction and the human can
hand it off in one message.

- docs/roadmap.md (new): six phases, each with status, scope, and stretch.
  Phase 0 = 🌳 done, Phase 1 = 🌿 in progress, the rest = 🌱.
  Explicit non-goals (no PvP, no OP, no cross-server identity).
- AGENTS.md: First-objective section collapsed to a pointer at the
  onboarding skill (it's been done). New "What to do, in priority order"
  summary citing the roadmap. New top-level "Operating principles"
  section: presence, bounded reconnect, hold focus, "I'll try to learn"
  reflex, idle = best-life mode, escalate destructive doubt with a
  JSONL log under state/<host>/escalations.jsonl.
- prompts/awake-and-live.md (new): canonical kickoff prompt for the
  next session. Scopes itself explicitly to phases 1+5+6 and excludes
  locomotion (phase 2 needs care, separate session).
- README Status: 🌳 Phase 0 done / 🌱 Phase 1 in progress, links to
  roadmap and operating principles.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
mayatnikov
2026-05-25 11:09:05 +03:00
co-authored by Claude Opus 4.7
parent 4e98fe8703
commit c03283c43c
4 changed files with 209 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -1
View File
@@ -156,7 +156,11 @@ These are mirrored in `AGENTS.md` and re-stated at the top of any system prompt
## Status
🌳 **Bridge online.** The project-local Mineflayer bridge loads via `.pi/settings.json`, connects through the server's ViaVersion/ViaBackwards stack with an explicit supported client version from `.env`, registers `mc_chat`, `mc_position`, and `mc_disconnect`, handled first-join AuthMe-style registration, and sent `hello` in chat. First onboarding notes are captured in `skills/server-onboarding.md`.
🌳 **Phase 0 — Body** done. Bridge online, AuthMe handled, `hello` sent. See `skills/server-onboarding.md`.
🌱 **Phase 1 — Presence** is the current target: bot stays online, reacts to chat, survives disconnects within bounds.
Full plan: [`docs/roadmap.md`](./docs/roadmap.md). Day-to-day judgement principles live under "Operating principles" in [`AGENTS.md`](./AGENTS.md).
## License