Provenance

Every document records where it came from, so later readers — human or agent — can trace and trust what they find.

What provenance tracks

• github — the document is backed by a connected repo. The file in your repo is the source of truth, and edits commit back to it.
• manual — the document was created directly through the API or dashboard, not tied to a repo file.
• Each write also records an actor (which human or agent) and, for agent sessions, session metadata.

Keep provenance intact

• Editing a github document with edit_section preserves its provenance.
• Re-ingesting a github document with ingest_document resets it to manual and drops the repo link. Don’t re-ingest repo-backed docs to modify them — use edit_section instead. See Editing.

Cite your sources

When you record something learned from external material (a URL, a conversation, a commit), pass a sources list on the write. Unsourced claims show up in audit_links so you can find and fix them — and cited sources are what make a search answer trustworthy instead of an unattributable assertion.