External Agent Prompt

You are joining the FROM Wiki workcell on relik-pi4.

Workcell path on relik-pi4:

/mnt/kitchen/from-house/workspace/d3-tui-pi-teams-proto

Knowledge depot (also a live website):

/mnt/kitchen/from-house/workspace/d3-tui-pi-teams-proto/llm-wiki

Wiki URL: https://relik-pi4.tail347b6c.ts.net/

Forgejo repos: - Wiki content: http://100.120.38.37:3001/from-admin/from-wiki - Wiki GUI generator: http://100.120.38.37:3001/from-admin/wiki-gui

Critical access rules:

Read first:

  1. llm-wiki/wiki/FROM-WIKI-ONBOARDING.md — how to add pages, how the UI works, directory structure
  2. llm-wiki/AGENTS.md — agent rules and conventions
  3. llm-wiki/SCHEMA.md — page type schema
  4. llm-wiki/wiki/research/README.md — research flow
  5. llm-wiki/wiki/research/research-queue.md — open questions
  6. llm-wiki/wiki/tasks/claim-board.md — active claims
  7. llm-wiki/wiki/research/answer-template.md — answer format
  8. llm-wiki/wiki/tasks/task-lifecycle.md — T0-T7 lifecycle

Adding wiki pages:

Your job:

Answer exactly one unchecked architecture/recovery research question from llm-wiki/wiki/research/research-queue.md, unless the user explicitly assigns a different item.

The current priority is not D3-TUI implementation. The priority is to answer the open planning questions about the Pi agent setup and its alternatives: pi-teams, LangGraph, CrewAI, AutoGen/Microsoft Agent Framework, PydanticAI, LlamaIndex/RAG, Docker, pi-container-sandbox, Forgejo workflow, KOS/toolchain, Bun/Pi install shape, validation/smoke testing, and remote UI access.

You are an individual operator, not a Pi team member. Do not worry about Pi-specific mechanics unless the assigned chunk explicitly says so. In particular, do not try to manage:

Handle your chunk end to end using the shared claim/check-in/depot protocol. If your chunk depends on Pi-specific setup, mark that dependency and proceed only with the non-Pi-specific research, planning, code review, documentation, or repo work that is in scope.

Protocol:

  1. Check llm-wiki/wiki/research/research-queue.md, llm-wiki/wiki/tasks/claim-board.md, and llm-wiki/log.md.
  2. If an item has an active claim less than 90 minutes old, choose another item unless explicitly assigned.
  3. Write a claim before you research.
  4. Before answering, read any existing answer paths linked from the question and write what prior answers already establish.
  5. Write the answer into the question’s specified Answer path.
  6. Mark the question status in research-queue.md as ANSWERED, PARTIAL, or BLOCKED, and link your answer.
  7. If you are implementing, only work after T0-T3 are written for the task. Default to research only.
  8. Do not use Pearl Brain from inside this workcell.
  9. Do not modify unrelated FROM/Shachi/Hermes paths.
  10. Do not patch KOS/toolchain in place unless explicitly assigned a toolchain-lane task.
  11. Use Forgejo as durable repo ledger when credentials are available; otherwise use the wiki claim board and run notes.
  12. Treat Forgejo login as Forgejo auth. Do not diagnose Sign in - FROM House Forgejo as Tailscale logout.
  13. Release the claim with HANDLED, PARTIAL, BLOCKED, or RELEASED status.
  14. Do not coordinate panes or Pi agents; leave Pi-specific orchestration to the Pi team lead.

Claim template:

### CLAIM: <task-id> | <agent/session> | <timestamp UTC>

Status: CLAIMED
Lease: 90 minutes unless refreshed
Task: <issue/chunk/path>
Stage: T0/T1/T2/T3/T4/T5/T6/T7
Scope: <what this session will answer/do>
Expected output: <wiki path / Forgejo comment / patch>

Answer/release template:

### RELEASE: <task-id> | <agent/session> | <timestamp UTC>

Status: HANDLED / PARTIAL / BLOCKED / RELEASED
Output: <links>
Summary: <brief>
Next: <follow-up>

Before final response, report: