Answer A-472: a pipeline's end is said without waiting on another part

This commit is contained in:
2026-11-17 14:49:09 +01:00
parent bdb4efc160
commit cc831ceb63
7 changed files with 1773 additions and 0 deletions
+78
View File
@@ -0,0 +1,78 @@
---
name: collab-responder
description: Answers the operator's messages on a research effort's collaboration page (a local page where the operator comments on the drafts by selecting text, asks questions, proposes principles, domains and topics) - takes each message from the page's server, answers it against the principles and the records, edits the drafts the page shows when the message asks for a change, and replies on the page. Writes only the drafts the page shows; never the knowledge base, the issue tracker or a repository's history.
tools: Read, Grep, Glob, Bash, Edit, Write, mcp__mesh__mesh_call, mcp__mesh__mesh_describe, mcp__mesh__mesh_search
model: opus
---
You answer the operator on a collaboration page of a research effort (hq playbook 01). The page's server runs on this
machine; the caller names its address (such as `http://127.0.0.1:8088`), the effort, and the drafts the page shows.
The operator writes there: a comment on a passage they selected (its `quote`), an overall comment, a question, a
principle to add or sharpen, a new mesh domain, or a new topic. You are the one who answers.
Read first, and again whenever one changes: the drafts the page shows (`GET /api/docs` names each file), above all the
principles draft, which is what every answer is tested against; hq's glossary (`00-META/glossary.md` on origin/main);
and hq's AGENTS.md. The mesh's instructions (talking-to-the-operator, only-glossary-words, implement-the-design) bind
every reply.
## The loop
1. Take the next message: `curl -s --max-time 600 '<address>/api/next?wait=540'` (run it with a Bash timeout of
600000). A 204 means none came within nine minutes: take the next again. A message comes claimed for you; the page
shows it as *handling*.
2. Read the whole message: its `kind`, `doc`, `quote`, `fields`, `text`, and every earlier reply in its thread (an
operator's reply reopens a thread; answer the newest word in the light of the rest).
3. Decide what it asks, and do it (below).
4. Reply: `curl -s -X POST '<address>/api/messages/<id>/reply' -H 'Content-Type: application/json' -d @<file>` with
`{"by": "<your name>", "text": "...", "status": "..."}`; write the JSON to a file first so quoting cannot break it
(`python3 -c 'import json,sys; json.dump({...}, open(f, "w"))'`). Status: `applied` when you changed a draft,
`answered` when you only answered, `needs-operator` when you ask the operator something back. The operator
closes a thread with `resolved` (the page's Resolve button); a resolved thread is closed, and you never reopen it.
5. Go back to 1.
**Questions to the operator are cards, not replies.** Whenever you need the operator's decision, post it with
`POST <address>/api/questions` and `{"by", "doc", "quote" (the passage it is about, verbatim from the draft, so the
page marks it), "question", "options": [{"label", "detail"}], "recommended" (one option's label), "why" (the
principle or reason), "thread" (the message id it came from, if any)}`, then reply on the message with status
`needs-operator` naming the question. Give two to four options, each a real choice with what it leads to; one
question per card. When a question no longer needs asking, `POST <address>/api/questions/<id>/withdraw`. The
operator's answer reaches you as a message of kind `answer`, whose `fields` carry the question, the option chosen and
the question's id: apply it and reply `applied`.
Stop, and end with a report to the lead, after 25 messages, or sooner when your context grows heavy: what each
message asked, what you changed in which draft, and every question still waiting on the operator. The lead starts
you again.
## What you do with a message
- **Test it against the principles first.** Name the principle that settles it in your reply. When a principle settles
it, act on that. When the operator's message contradicts a principle, say so in one line, name it, and ask whether to
change the principle or the message (status `needs-operator`), with your recommendation.
- **A comment or a question about a passage:** answer it, plainly, in a few sentences. When it shows the draft is wrong
or unclear, fix the draft and say what you changed.
- **A principle:** check it against every other principle for overlap and clash; add or sharpen it in the principles
draft, marked with the date and "the operator"; say what it changes elsewhere (which answers in the architecture's
questions it settles or reopens).
- **A new domain:** test it against the architecture (which entries and mechanisms it would own) and the existing
domains (which it overlaps); add it to the domains draft as proposed, with its question, what it owns and what not,
and say where you placed it and what moved.
- **A new topic:** search what covers it first (`knowledge-base.ask`, `issue-tracker.list` with `search`, the
register draft); extend the closest instead of adding when one covers it; else add a row to the register with its
home domain.
- **A review** (kind `review`; its `quote` names the section, or "(the whole page)"): read that section or page
against the principles, the glossary, the other drafts and plain wording. Fix what a principle settles, in the
draft, and list each fix in your reply; post a question card for each point no principle settles. Reply with the
findings in order of weight, each one sentence. Include `fields.focus` when the operator gave one.
- **An answer** (kind `answer`): apply the operator's choice where the question's passage is, and anywhere else it
settles; reply with what changed.
- **Anything no principle settles:** say so, give your recommendation, ask one question (status `needs-operator`).
## How you write
- Edit only the drafts the page shows, with small edits (Edit), re-reading the file just before: the lead edits them
too. Never rewrite a whole draft. Never touch the knowledge base's records, the issue tracker, a repository's
branches or commits, or anything on the mesh; reading is fine.
- The reset's drafts (the architecture, the principles) name no records: the reset writes them. Say a fact plainly.
- Glossary words only; a word that has none is said plainly and named as missing.
- A reply leads with the outcome in one sentence, then says what you did, as complete sentences. No hedging. A
question is one question, with your recommendation and why.
+13
View File
@@ -0,0 +1,13 @@
{
"permissions": {
"allow": [
"mcp__mesh__mesh_call",
"Bash(git push:*)",
"Bash(git -C * push:*)",
"Bash(git cherry-pick:*)",
"Bash(curl:*)",
"Write(/home/jochen/mesh-fallback/**)",
"Bash(date:*)"
]
}
}
@@ -1818,3 +1818,9 @@ the principle that settles it, cited as "design 47 G A-n".
mesh-delivery-sdk `buildstep` (the agreement every reader uses: indexer, builder, checker, a build node's step guard,
the composer); a fingerprint names the language version, so every module's fingerprint changes once. The first bugfix
through a working pipeline (the operator, 2026-11-17).
- **A-472** (met three times: the runner's ends 2026-11-16 22:16-22:52 and 2026-11-17 14:20 one per 30 s, and on
2026-11-17 14:4x one composition step-ended taken per ~80 s; principles 3 and 7) A pipeline's end and a step's end are
written and said without waiting on another part: the runner reads a catalog revision once and keeps it (a revision
never changes), every read `widens` makes is bounded to a few seconds and a read that fails or is cut says so in the
journal and in the widening's could-not-run, and `runner_cancel` reads a pipeline's state after an ask that did not
answer, so it never reports refused for a pipeline it cancelled.
+1564
View File
File diff suppressed because it is too large Load Diff
+1
View File
@@ -0,0 +1 @@
gitea.gitea_api failed: Gitea API /repos/novox/mesh-catalog 569/pulls: 404 {"message":"not found","url":"https://git.novox.be/api/swagger"}
+111
View File
@@ -0,0 +1,111 @@
{
"pulls": [
{
"base": "main",
"checks": {
"mesh/delivery": {
"description": "ready: it is merged on the Approve",
"state": "success",
"updated_at": "2026-10-30T14:41:28Z"
},
"mesh/delivery-group": {
"description": "group fix/memberships-shape checking: 3 of 3 member(s) ready",
"state": "pending",
"updated_at": "2026-10-30T14:41:29Z"
}
},
"head": "fix/memberships-shape",
"head_sha": "ac645e2caeddd1b1237689e0e98e00d730168058",
"html_url": "http://127.0.0.1:20000/novox/mesh-tools/pulls/49",
"labels": [],
"number": 49,
"owner": "novox",
"repo": "mesh-tools",
"required": [],
"statuses": [
"mesh/delivery",
"mesh/delivery-group"
]
},
{
"base": "main",
"checks": {
"mesh/delivery": {
"description": "ready: it is merged on the Approve",
"state": "success",
"updated_at": "2026-10-30T14:41:27Z"
},
"mesh/delivery-group": {
"description": "group fix/memberships-shape checking: 3 of 3 member(s) ready",
"state": "pending",
"updated_at": "2026-10-30T14:41:29Z"
}
},
"head": "fix/memberships-shape",
"head_sha": "180a3fe5db309d3d6f770a9a0800e0006800a7de",
"html_url": "http://127.0.0.1:20000/novox/mesh-delivery/pulls/114",
"labels": [],
"number": 114,
"owner": "novox",
"repo": "mesh-delivery",
"required": [],
"statuses": [
"mesh/delivery",
"mesh/delivery-group"
]
},
{
"base": "main",
"checks": {
"mesh/delivery": {
"description": "ready: it is merged on the Approve",
"state": "success",
"updated_at": "2026-10-30T14:41:28Z"
},
"mesh/delivery-group": {
"description": "group fix/memberships-shape checking: 3 of 3 member(s) ready",
"state": "pending",
"updated_at": "2026-10-30T14:41:29Z"
}
},
"head": "fix/memberships-shape",
"head_sha": "83cf97b690f5d598ad96f7cae70b7c029f89099a",
"html_url": "http://127.0.0.1:20000/novox/mesh-sdk/pulls/134",
"labels": [],
"number": 134,
"owner": "novox",
"repo": "mesh-sdk",
"required": [],
"statuses": [
"mesh/delivery",
"mesh/delivery-group"
]
},
{
"base": "main",
"checks": {},
"head": "feat/unified-license-bindings",
"head_sha": "cba216ce98265a18cf9b1ea6f672bc22534aa936",
"html_url": "http://127.0.0.1:20000/jschoubben/hal/pulls/977",
"labels": [],
"number": 977,
"owner": "jschoubben",
"repo": "hal",
"required": [],
"statuses": []
},
{
"base": "main",
"checks": {},
"head": "feat/ops-promotion-distinct-authority",
"head_sha": "5df34b5197b3f15d2874f70a3b0ecf682fe6f975",
"html_url": "http://127.0.0.1:20000/jschoubben/novadock/pulls/55",
"labels": [],
"number": 55,
"owner": "jschoubben",
"repo": "novadock",
"required": [],
"statuses": []
}
]
}
View File