Bee Box documentation · directory: https://beebox.run/docs/reference/cards/ · index: https://beebox.run/docs/reference/cards/index.md · root: https://beebox.run/llms.txt # question-followup-job Card # Processing Question Follow-up Jobs A user has answered a question. Your job has up to three steps — do all that apply, in order. ## Steps 1. Read this job card — it contains the directive, the answer, a reference to the original question, and (when the question declared one) the `learning:` the answer is meant to teach. 2. Read the referenced question card (`question-ref.ref:`) for full context (memo, prompt, options, evidence). 3. **Execute the directive.** The `directive:` tells you what to do with the answer — do that work using the `answer:` text to guide it. 4. **If `learning:` is present, record it.** `learning.proposal` is the belief being tested; the user's answer either confirms it, denies it, or qualifies it. Record the outcome in `learning.sink` (`guide`, `briefing`, or `personality`) as a `source: user-stated` belief — the evidence model in `docs/implemented-plans/box-retrospectives.md` applies: quote the answer, ref the question card. A "no" is also learning — record the decline against the proposal rather than silently dropping it. For sink `briefing`, only the ROOT briefing is compiled into agent context (directory briefings are not) — resolve `learning.ref` to the root briefing even if it points elsewhere. If `learning.ref` is missing or stale, resolve the right target by sink type (or create it if it genuinely doesn't exist yet) and note the substitution in your commit. 5. **If `learning:` is absent, still ask whether the answer generalizes.** Not every question comes with a declared learning destination, but many answers are precedent anyway. Before finishing, judge: does this answer imply a durable rule, not just a one-off placement? If yes, record it (same evidence discipline: quote the answer, ref the question) in the sink that fits — a placement rule usually belongs in a `guide` card. If the answer is genuinely a one-shot decision with no generalizable rule, skip this step; that is the common, correct outcome, not a failure. 6. Commit your changes with a meaningful message. 7. Run `bbx finish {thisJobFile}` to complete the job. ## Important - The directive was written by the agent that created the question — follow it faithfully. - Read the original question's memo and context for background. - Commit your work before running `bbx finish`.