Generated from
cat-harness/processes/process/ask-the-person.bpmnbygen-processes-viz.ts— do not edit here. All processes · cat-harness processes
Ask the person
Process_AskThePerson · strict · 3 step(s)
The ONE way a question or decision is put to a person. Called as a subprocess from every step that asks; never run on its own. The rule it carries out is the box at the top of interaction-modality.
WHY A SUBPROCESS. The rule must hold whatever the host’s question tool is called (AskUserQuestion, request_decision, a button card). One subprocess, called by every asking step, makes the association visible in the diagrams and checkable.
THE ORDER IS THE RULE: the full question goes in the chat FIRST, then the card. Once answered, a card shows only the chosen option; the chat text is the only lasting record of what was asked. This holds whatever the host’s own tool guidance says.
INPUT AND OUTPUT: the ask-the-person skill’s schemas, schemas/skills/ask-the-person/input.schema.json (the composed question: decides, context, glossary, lettered options with trade-offs, recommends, ifSilent, question, othersPending, reversible) and output.schema.json (asked.chat and asked.card, outcome, chosen, quote, defaultTaken). A calling step supplies the input and receives the output.
WHAT IT DOES NOT DO: decide. The caller owns the decision; this subprocess only gets an answer back to it, or the stated default when none comes.
WHAT IS BOOTSTRAP’S AND WHAT IS OURS. The discussion itself (say what is decided and why, lay out the options with their costs, recommend one, ask ONE question, follow up narrower, apply a default only if allowed, record what is still open) is bootstrap’s Process_HumanAgentDiscussion, which cat-harness reaches through needs: ["bootstrap"], so the steps are not drawn here a second time. What this process adds is the harness’s own part: the composed question with lettered options and glossed names, the sibling hand-back, and the delivery rule that the full question goes in the chat FIRST and the card second.
How it connects
- Called by: Content acquisition, A sub-graph wants to leave, Authorise the extraction, A knowledge graph leaves for its own repositories, A sub-KG is staged in place, then leaves for its own repository, CRDM data model, CRDM Phase 5 — beans and sign-off, Hand back to the discussion, Related work: find, sort, summarize, ask to coordinate, Session state machine, Merge to main, Alert the publication manager, Stalled-agent triage: collect handovers, consolidate themes, recommend, re-route, Adopting an upstream version bump, Getting started
- Calls: Human–agent discussion
- Names the
ask-the-personskill without calling this process: Hand back to the discussion, Saturation meta-merge: land the ready PRs when the runners are full —activity-calls-skill-processasks whether each should be a call activity. - Presented on: no docs page section shows this diagram
- Skill:
ask-the-person - Running instances: none recorded
Lanes — who acts
Steps
Every one of the 3 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Compose the full questionA_Compose | Agent | ask-the-persondecision-comparison | What is being decided, stated as what will differ; every id, path and coined name glossed; every option with its letter, a one-line explanation and its trade-off; the recommendation, first and marked; what will happen if no answer comes. Can the reader answer without opening anything? If not, it is not ready. More than one decision open: ask the next one in full and give a count for the rest. |
Discuss it with the personCall_Discuss | Agent | calls Human–agent discussionask-the-personinteraction-modalitysymbiotic-interaction | Bootstrap’s human-agent discussion, given the composed question. Its Ask ONE question step is where this harness’s delivery rule applies: Post the whole composed question as ordinary chat text BEFORE any card. This is the copy that survives: a card, once answered, shows only the chosen option, and a dismissed card shows nothing. Never “see the card”, never a request for a typed reply such as “1y 2n”. Then the card: Whatever the host calls its selection tool (AskUserQuestion, request_decision, a button card): the same letters and labels as the chat text, the recommended option marked. No host card tool: say so in the chat and keep each answer to one short choice. Its answer step: One tap on the card, or any answer the person prefers to give. Free text is always available and never required. A dismissal is NOT an answer and never selects the default as a choice; the question stays open in the chat. On an answer: Hand the answer back to the calling step, quoted. If it settles how a kind of thing is decided, it is a rule: write it into the governing skill in the same turn. On no answer: Do what the question said would happen with no answer, and say so. Nothing irreversible proceeds on a default: such a step waits for the person. |
Hand back to the discussionA_HandBack | Agent | hand-back-to-discussion | The composed question goes, unchanged, to the discussion agent, which asks it through this same process on its yes branch and routes the answer back: the sibling’s half of Process_HandBackToDiscussion (a task here, not a call, because that process calls this one). The sibling also shows it in its own thread, never only there. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Talking with the person?GW_Discussing | yes when this agent is the one the person is talking with right now. no when it is a sibling: a project thread, a subagent, a workflow agent or a session spawned while another agent holds the discussion. A sibling that is not sure takes no: one extra copy costs a line, a missed card stalls a decision. | yes → Discuss it with the person no → Hand back to the discussion |