Skip to content

Feature request: lock syntax + propagation for verified facts #1

Description

@bambam624

A feature request around protecting verified facts from drift.

AI agents sometimes change small details in statements that are already true and verified — a date shifts by a day, a quote gets paraphrased, a name flips. For any workflow where an entry has to match its source exactly, quiet drift between drafts is a real problem.

I'm working on a "lock" format so verified statements aren't silently changed. Two pieces:

  1. A lock syntax that's visible in the markdown, so any agent working in the vault recognizes it and refuses to edit what's locked.
  2. Propagation — if a locked fact is updated in one canonical file, the change flows out to every note that references it, instead of every note holding its own copy that can drift.

Questions:

  • Is anything like this already on the roadmap, or have you considered a verified-fact pattern for the skill?
  • If not, would you be open to a contribution? I'd rather build it into the skill's conventions than fork around it.

Thanks for the skill.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions