I3417 — An observation can cite the mesh review that found what it records, and the reference stays in the candidate's body, never in its provenance

✕BLOCKED wave 5 · p3 · implementation profile · parallel safe

Part of knowledge-is-reconciled-before-it-is-reviewed — What a session proposes as knowledge is reconciled with what the repository already knows before a person reviews it, and a promotion stands on evidence that resolves.

Objective

Accept a review: reference carrying a mesh review request key among the evidence references of knowledge observe. The compose step keeps it in the candidate's Evidence body and never in provenance.derived_from, because a mesh review key does not resolve in every checkout. Document it in step 1 of the evolve skill.

Why

The owner's 2026-10-19 Cognitive Fabric pack asks the episode lifecycle to carry bounded signals from code review (campaigns/prismatic-way-cognitive-fabric-prompt-pack/prompts/03_KNOWLEDGE.md). Reusing observation.recorded adds no event and no store.

Current state

lib/knowledge.sh:187 accepts only file:, test:, commit:, issue: and claim: evidence. Reviews live in the mesh journal (apps/majordomus-cli/src/mesh/cooperation.rs:3829 answer_review), and share/events.yaml has no review event.

Desired state

A reviewer's finding can be recorded as an observation that names its review.

Scope

• lib/knowledge.sh
• test/cases/980_a_session_records_what_it_observed.sh
• docs/KNOWLEDGE.md
• site/content/docs/knowledge.md
• .ai/repo/skills/evolve/SKILL.md

Out of scope

• Reading the mesh journal from the deriver
• Turning review answers into observations automatically
• A review ledger event

Dependencies

• I3415✕BLOCKED knowledge promote refuses evidence that names no reference existing in this checkout, and knowledge.promoted records the references it stood on

Acceptance criteria

• knowledge observe accepts a well-formed review reference and refuses a malformed one without writing
• The derived candidate lists the review reference under Evidence and not in provenance.derived_from, and knowledge check passes in a clone without the mesh
• Step 1 of the evolve skill shows a review reference

Validation

• bash test/run.sh 980_a_session_records_what_it_observed 981_an_observation_becomes_a_grouped_candidate 3004_evolve_is_a_procedure_of_existing_commands
• majordomus plan validate

Evidence required

• case_an_observation_cites_its_review

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3417.yaml. Read it back with majordomus plan show I3417.