33 lines
2.0 KiB
Markdown
33 lines
2.0 KiB
Markdown
# JOURNAL — phase porepo (Builder)
|
|
|
|
## 2026-06-13T19:05Z — Bootstrap / orientation
|
|
|
|
Read the phase plan, `plan-agent-orchestrator.md`, and the harness README at
|
|
`/home/loops/aoeng/agent-orchestrator/README.md`. Key facts established:
|
|
|
|
- Harness `agent-orchestrator` is built + tagged `v0.1.0` (tag object `a89d30f` → commit `289ef07`).
|
|
Working clone: `/home/loops/aoeng/agent-orchestrator`. Repo is **public** on Gitea
|
|
(`private:false`), so a fresh `git clone --recurse-submodules` fetches `engine/` without creds.
|
|
- `engine/agents.py status` only needs a valid `agents.toml` (it reads config, prints a table;
|
|
does not require running sessions or live backends). So a PO config with one persistent
|
|
`project-orchestrator` agent will pass `status`.
|
|
- Config schema (README): `[watchdog]`, `[backend.<name>]`, `[defaults]` (session_prefix + log_dir
|
|
REQUIRED), `[[agent]]`/`[[service]]`, `[loop]`. `project_dir` resolves relative paths.
|
|
- One-directional knowledge: the PO repo holds the fleet registry (`fleet.toml`); a project repo
|
|
holds NO PO/fleet metadata — engine submodule pin + PO's fleet.toml are the only record of
|
|
project↔harness↔ref.
|
|
|
|
Decision: pin `engine/` at the **commit** the `v0.1.0` tag points to (`289ef07`), per DoD wording
|
|
"pinned to agent-orchestrator v0.1.0". The tests commit `cdcece9` is *after* the tag and is not
|
|
required.
|
|
|
|
Gitea API reachable with bot creds (200); `recipe-maintainers/project-orchestrator` does not yet
|
|
exist (404); org `recipe-maintainers` exists (id 65).
|
|
|
|
### File-ownership coordination note
|
|
The Adversary had pre-created STATUS-porepo.md / JOURNAL-porepo.md as placeholders before I started.
|
|
Per protocol §6.1 these are Builder-owned (STATUS is the authoritative `## DONE` handshake file the
|
|
Adversary verifies against; JOURNAL is my reasoning). I took them over and left REVIEW-porepo.md +
|
|
the `## Adversary findings` section of BACKLOG-porepo.md to the Adversary. Sent an ADVERSARY-INBOX.md
|
|
heads-up so it keeps its tracking in REVIEW.
|