steering-conventions

Maintain append-only discipline for vault updates by preserving history and enabling auditable changes rather than overwriting existing notes, using a consistent date+source header and compact provenance lines to track all modifications.

Standardize date format and data provenance in an Obsidian vault by enforcing a consistent date+source header for every entry, adding one provenance marker per note, and applying append-only discipline to preserve history and enable auditable changes.

Format agent-written notes with wiki-links, Dataview, and Tasks plugin syntax by following Obsidian formatting guidance that enforces uniform presentation, including tags, callouts, and a standard review queue entry format to handle ambiguous data safely.

Use append-only discipline to track timeline observations across meetings and projects by applying standard provenance markers and date+source headers to each entry, preserving history and enabling auditable changes for agent-written observations.

Provenance markers and a review queue entry format are needed when handling ambiguous data in vault notes, ensuring source confidence is indicated and ambiguous entries are safely queued for review rather than directly integrated.