# Source labels to narrative

The preferred working flow is: label the sources, have an assistant assemble
the narrative, then review the resulting edition. The operator does not need
to decide where every attachment belongs before the argument can be drafted.

## Source labels

Keep the original file and give it a short descriptive name. Add a plain note
when a particular page or box matters. Include the date shown by the source
when available; leave missing dates unknown.

Useful labels identify an observation, for example:

- Welcome packet — rent and concession summary.
- Office-use panel — visible digital-signature appearance.
- Mailing receipt — acceptance date shown.
- Ledger — accelerated-rent posting.
- Voice note — the contributor's account recorded after an event.
- Recorded call — the captured request, transfer, or response, with a time range.

For audio, retain the original and identify the recording type. A transcript or
redacted excerpt is a separate derivative with its own version and source link.
The claimed event date, archive intake date, and blockchain anchor date are
separate observations. See the [audio workflow](../entry/audio-records.html)
and [artifact design](CALL-RECORDING-ARTIFACTS.md).

A label describes the source. It does not make an unexplained conclusion such
as “fraudulent signature” or “valid debt.” The PDF's visible signature artwork,
the existence of a cryptographic signature, its verification result and the
meaning of the approval are separate questions.

## Assistant assembly

Use the labels and actual source bytes to identify the event sequence, the
specific disputed issue, the supporting material and any gaps. Keep quotations,
documented facts and inferences distinguishable. An unfamiliar signature
appearance alone does not establish fabrication, approval scope or signer
identity.

Select reusable Commons statements/documents by their exact CIDs where they fit.
Connect them to the individual case's sources and requested action. Preserve
source references so the reader can follow each factual claim. A claim may
remain an open question rather than becoming a categorical assertion.

Source labels and notes stay with the case records and their catalog.
Private identifying details stay in the local home database. Commons is the
public library of reusable text and public references, not the destination
for SSNs or a private case's source packet.

## Review and publication

Review the composed narrative, source descriptions and attachment order as
one edition. Existing exhibit identifiers can be retained when an earlier
edition already uses them. Manual placement remains an optional editorial
tool; it is not a prerequisite for labeling sources.

Freeze the selected statement versions, source references and order only after the
edition has been reviewed. Existing CID-named statements and snapshots are
immutable; a changed argument or edition gets a new CID.

This note records the preferred authoring workflow. It does not claim an
automatic AI narrative service or new source-labeling interface is already
implemented in the public Commons reader.

The [October 20 signed-edition direction](SIGNED-EDITIONS.md) removes the
paragraph-length editorial assumption. HTML authoring, a signed PDF edition
and an external wallet/ledger commitment are distinct artifacts and stages.