Merge pull request #3149 from affaan-m/docs/lane-rules-20260916

Docs: lane rules and Ito desk relationship (2026-09-16)

docs/ITO-DESK.md

@@ -0,0 +1,26 @@
+# ECC and the Ito desk
+
+ECC is the public agentic-engineering toolkit; the Ito desk is Affaan's
+private ops system. The connection surface in this repo is the set of
+public `ito-*` skills (`skills/ito-baskets`, `skills/ito-compute`,
+`skills/ito-inference`, `skills/ito-training`). Each of them is a thin
+pointer: it names the supported boundary and hands real work to the
+separately installed canonical CLI or MCP server. ECC itself implements no
+compute booking, inference serving, training stack or basket trading, and
+nothing here may claim those capabilities exist inside this repo.
+
+Desk-side work that touches ECC runs as bounded lane tasks. The lane-worker
+doctrine (see `docs/LANE-RULES.md`) is: one worker, one task, one branch,
+one PR or one receipt; real work only, meaning code edits, tests, commits
+and a PR, with the final message as the receipt; no self-review loops, no
+receipt ledgers, no merging to main, no publishing, no deployments, no
+messages; blocked means naming exactly who or what unblocks. The doctrine
+exists because unbounded agent loops were the dominant failure mode of the
+desk's earlier automation.
+
+The merge rule for anything desk-related in this repo: fixes and tests
+merge freely. Anything that adds a third-party tool, a vendor-named skill,
+or an external link waits for Affaan's explicit yes, recorded before merge.
+The living desk plan is `docs/PLAN.md` in `Ito-Markets/ito-desk`; task
+schemas and the spec book live under `docs/spec/` in the same repo. This
+file only describes the relationship; the plan repo is the source of truth.

docs/LANE-RULES.md

@@ -0,0 +1,19 @@
+# Lane rules
+
+These are the working rules for bounded lane workers (human or agent) that
+execute tasks against this repository from the Ito workstream system. They
+are copied verbatim from the lane registry
+(`lanes/RULES.md` in the Ito workstream system on the ops mini,
+2026-09-16) so a worker reading only this repo sees the same contract.
+One task, one branch, one PR or one receipt, then stop.
+
+---
+
+## Lane rules (every codex exec brief starts by reading this)
+You are one bounded worker. One task, one branch, one PR or one receipt, then stop.
+- Real work only: edit code, run the tests, commit, push, open the PR. No receipts about receipts, no independent review of your own output, no hashing manifests, no ledgers, no acceptance JSONs, no skill self-patching. Your final message is the receipt (under 300 words: what changed, PR link, test command and result, what is blocked and on whom).
+- Never merge to main, never publish to npm, never deploy, never send email or messages, never change Hermes profiles or launchd on the mini unless the brief says so explicitly.
+- Commits: plain messages, no Co-Authored-By or generated-with trailers, no em dashes anywhere.
+- Worktrees and caches go under ~/GitHub/ECC-worktrees or ~/GitHub on the Pro, /Volumes/Agent-Runtime/workspaces on the mini, never on the mini root disk.
+- If blocked (missing credential, approval needed, conflicting work), stop and say exactly what is needed. Do not wait, poll, or sleep.
+- Time box: finish in one pass. Do not spawn subagents.