# Meridian investigation and response history

Three authored fictional follow-up questions use the existing case-record and case-claim-history 0.1.0 contracts at canonical commit `88bcbfcc8b17af30837313aff596cec8e1bde43a`. Two questions have replies and inconclusive reviews; the third has no reply and remains unassessed. No real correspondence was sent.

`questions.json` and `method.md` are pinned authoring inputs. The builder renders `correspondence.txt` and `review-log.md` deterministically, preserves the original field and specimen snapshots, and adds a separate observation containing workflow sources. It adds investigations and response events to a new case snapshot without changing earlier case memberships, histories, timestamps or results.

Requests are source assertions; replies are response-event declarations; reviewer interpretations are separate assessment claims. The existing contracts do not supply a response-to-request edge. Thread association and workspace destinations are explicitly editorial navigation, not new standard fields. Day-only message dates remain day-only. `recordedAt` is the assigned packet recording instant, not a message timestamp. Proposed actions are not completed work.

Reproduce with the built pinned checkout and original Meridian root:

```sh
node build.mjs /path/to/disclosureos . ..
```

Source digests and canonical references are checked separately from authenticity and scientific interpretation, which remain unperformed. Missing replies do not establish refusal, restriction or absence of data elsewhere.
