Start with a small record, not an archive

Ownership does not require saving every message. Keep the material that changes a future decision or helps someone reproduce the work.

The fixed synthetic workshop brief needs five records: workshop source notes, the content-brief task, the first brief and review, the corrected final brief, and the checkpoint export. These reader-safe names identify no person, account, computer, or customer.

Give every file one responsibility

The source file confirms the audience, two-hour offer, and confirmed-detail constraint. The task limits the brief to those details. The draft introduces “Saturday sessions are available.” Independent review identifies the unsupported sentence. The corrected output removes it, and the checkpoint keeps schedule and price unknown.

Mixing all five records into one growing document creates ambiguity. A later reader cannot tell which sentence came from the source, which came from judgment, and which was removed after review.

Add provenance a person can read

Provenance answers where a piece of information came from and how it changed. The W3C PROV model distinguishes things, activities, and responsible parties so relationships can be described consistently.

A small text workspace does not need the full ontology. It can borrow the useful questions:

  • What is this file?
  • Who or what supplied it?
  • When was it created or revised?
  • Which earlier item did it use?
  • Which later item replaced it?

For synthetic material, mark the invented status near the top. That label prevents a demonstration note from being mistaken for a business fact.

Prefer readable formats for the durable layer

CommonMark defines a consistent Markdown syntax for headings, lists, links, and other text structures. A consistent syntax reduces ambiguity when different tools open the same file.

Readable text is a useful durable layer for notes, tasks, reviews, and checkpoints. Binary assets can remain separate and receive descriptive entries in the workspace. The choice is about inspectability, not a claim that one format suits every artifact.

Test whether you control the record

Copy the five synthetic records into a new folder. Open them with a different text editor. Trace the Saturday statement from the first brief through review and removal.

The test passes when the relationship remains understandable without the original conversation. If meaning depends on hidden history, the workspace does not yet carry enough context.

Fit and limits

This approach suits briefs, research notes, procedures, and similar knowledge work. It is less useful for disposable ideation. It also does not replace dedicated systems required for regulated records, complex media production, or specialized structured data.