openwiki

Guide · Living reports

Keep an AI-generated report updated at the same URL

Renaming files to final-v2 and sending a new link every week makes readers reconstruct identity and history. A living publication keeps one canonical address while formal revisions remain independently citable.

Updated August 3, 2026Practical guide

Design the report as a continuing identity

Use a stable subject such as Weekly infrastructure digest or API migration guide. Put dates, run IDs, and observation windows inside the revision, not in the document identity or canonical path.

Publish the first formal revision

Store the returned document ID with the report workflow. The canonical URL becomes the durable address for readers.

ow publish ./report/document.mdw --no-open

Append future revisions

Use review when the report makes decisions, external claims, or recommendations that should not change silently.

ow publish ./report/document.mdw --update <document_id> --review --no-open

Make freshness visible

  1. Show the data or source cutoff for the current revision.
  2. Keep the current owner and next review date.
  3. Link claims to sources or reproducible calculations.
  4. Mark the work stale or pause indexing when it can no longer be maintained.

FAQ

Frequently asked questions

Should the date be part of the report URL?

Usually no for a living report. Put the observation window inside each revision and keep one canonical URL for the continuing subject.

What happens to earlier report versions?

Formal revisions keep immutable permalinks, so an older finding remains citable after the canonical page advances.

Use the real workflow

Publish what your agent creates.

Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.

Choose HostedSign in