mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00

Files

T

879afc14a4 Board Program LEARN context, ruff 0.16, and verb-rejection observability (#700 )

* fix(board): LEARN decisions name the item, not its per-cycle index

A cycle's reject reasons are rendered into the NEXT cycle's exploration
prompt, but the ref recorded alongside each reason was the item's stored
id (item-0/item-1) — a per-cycle index that means something different
every cycle and appears nowhere the explorer can resolve. The reason
survived the loop; what it was about did not.

Record the item's title instead, via a shared learn_ref() helper (falls
back to the id when title-less, and reads target_task_title for Scales,
whose items name the live task they mutate).

* chore(lint): satisfy ruff 0.16 — keyword-only signatures and markdown formatting

The dev toolchain resolved ruff 0.16.0, which stabilises PLR0917 (too many
positional arguments) and formats python code blocks inside markdown. Both
fired repo-wide and neither had anything to do with the code they flagged.

- 36 signatures gain a `*` so their tail arguments are keyword-only, and
  the 104 call sites that passed them positionally are converted. mypy was
  the safety net for the static ones; the full suite caught nine more that
  only bind at runtime (the MCP tool functions, whose real callers already
  pass named JSON arguments).
- 28 markdown files reformatted by 0.16's code-block formatter.
- One RUF036 (`None` mid-union) autofixed in the GitLab provider.

* fix(gateway): log the reason when a verb rejects

A rejected envelope rides an HTTP 200, its body is never logged, and there
is no trace table — so in the access log a verb an agent could not satisfy
looks identical to one that worked. On 2026-07-25 four Board Programs
(Periscope, Sentinel, Scales, Barfly) each POSTed their propose verb three
or four times, persisted nothing, and left their exploration tasks PENDING;
the reason was unrecoverable afterwards, from the logs or from the agents'
own transcripts.

Log error/message/remediate/missing plus the calling agent at
envelope_to_response — the one chokepoint every v1 flow and do route
returns through. Success envelopes stay silent.

---------

Co-authored-by: Renn F <rennf93@users.noreply.github.com>

2026-07-26 15:07:28 +02:00

1.6 KiB

Raw Blame History

Escalation Chain Reference

Complete escalation mapping for all agents.

Chain Overview

Cell Members → Cell PM → Main PM → Product Owner → CEO

Full Mapping

Agent	Escalates To
`be-dev-1`	`be-pm`
`be-dev-2`	`be-pm`
`be-qa`	`be-pm`
`be-doc`	`be-pm`
`fe-dev-1`	`fe-pm`
`fe-dev-2`	`fe-pm`
`fe-qa`	`fe-pm`
`fe-doc`	`fe-pm`
`ux-dev-1`	`ux-pm`
`ux-dev-2`	`ux-pm`
`ux-qa`	`ux-pm`
`ux-doc`	`ux-pm`
`be-pm`	`main-pm`
`fe-pm`	`main-pm`
`ux-pm`	`main-pm`
`main-pm`	`product-owner`
`product-owner`	`ceo`
`head-marketing`	`ceo`
`auditor`	`ceo`

Cell PM for Team

Team	Cell PM
`backend`	`be-pm`
`frontend`	`fe-pm`
`ux_ui`	`ux-pm`

Escalation Tool

escalate_up(task_id="uuid-here", reason="Need clarification on requirements")

Auto-routes to your escalation target. You CANNOT choose a different target. escalate_up is a PM verb (Cell PM / Main PM); cell members (devs, QA, documenters) signal blockers with i_am_blocked(task_id, reason), which their Cell PM resolves.

CEO Escalation (Main PM / Board Only)

escalate_to_ceo(task_id="uuid-here", reason="Major feature ready for approval")

Requirements:

Task in awaiting_pm_review
PR exists
Only Main PM, Product Owner, or Head of Marketing can call this (Cell PMs cannot — they escalate_up to Main PM first)

Cannot Skip Levels

System enforces chain:

Developer CANNOT escalate directly to Main PM
Cell PM CANNOT escalate directly to CEO
Each level must acknowledge and decide

1.6 KiB Raw Blame History