Assess factory backlog and record first implemented delivery

docs/proposals/prj-helixforge-factory/AGENTS.md

@@ -0,0 +1,38 @@
+# Proposed project agent instructions
+
+This packet is staged in the Custodian. Until project adoption, changes here
+prepare the proposal only; do not register it as an unrelated Custodian workplan
+or claim it is an active project.
+
+After adoption, repo slug is `prj-helixforge-factory`; proposed workplan prefix
+`HFACT-WP-` must be checked with the authoritative registrar before first index.
+
+Orient with `GOAL.md`, `SCOPE.md`, genesis, source workplans and `dependency-map.md`.
+Read the generated `.custodian-brief.md` when available. Use State Hub HTTP at
+`http://127.0.0.1:8000` locally, `http://10.43.68.154:8000` on railiance01;
+use an enabled edge relay only with its explicit configuration. Direct requests
+carry `X-StateHub-Component: prj-helixforge-factory` and canonical `/workplans/`
+and `/tasks/?workplan_id=...` routes.
+
+Check this project's unread inbox and mark reviewed messages read. Do not send
+messages to other owners without user authorization. Refer to existing
+GLAS-WP-0015 threads and receipts to avoid repeated requests.
+
+Implementation remains in participating repos under their instructions.
+Advance only within existing grants and session authorization. Do not infer
+permission for secrets, publication, deployment or paid execution from this
+proposed programme. Before any credential need, run `warden route find` and
+`warden route show`; ops-warden issues SSH certificates, while OpenBao/platform,
+KeyCape and the relevant policy/approval owners retain other responsibilities.
+Never place secret values in work records or logs.
+
+Update source task statuses as work progresses. Record significant decisions
+as source-backed decision records and the supported Hub decision projection.
+At session close log a concise `POST /progress/` event and run
+`statehub fix-consistency` after workplan edits. If the CLI/API is unavailable,
+retain evidence of the failed sync and request operator recovery; do not claim
+queued or failed writes are central success.
+
+Before finishing or archiving, create live owner records for actionable
+residuals, name their IDs in the completion record, and verify synchronization.
+No production implementation belongs in this coordination repository.