Unblock a task
A blocked task is not a request for help — not yet. It goes through a resolution loop first, and by the time you see it, there is a report that tells you what was tried and why each attempt failed.
What already happened before you were asked#
The task was observed, searched against everything Tharas knows about this repository, given an explicit hypothesis, researched, and handed a set of ranked repair strategies. Each strategy was attempted through the same jailed engineer the rest of the pipeline uses, and verified against the unchanged QA gate.
Only after that budget is spent do you hear about it — and even then nothing waits for you.
Reading the resolution report#
- Root cause
- What the strategist concluded was actually wrong, stated before research ran rather than after.
- Strategies tried
- Each with its confidence, risk and cost, in the order they were attempted.
- Why each failed
- The verification result for each attempt — usually the fastest route to the real problem.
- Metrics
- Attempts, cost, and whether anything regressed.
Nothing waits for you
A task the loop could not repair is not a card to approve. The rest of the build carries on, the task is set aside with its reason, and telling Tharas in the conversation how you would like it to work builds it again.