# .museattributes — Knowtation vault merge-strategy defaults.
# Written by `muse init --domain knowtation`.
#
# These three rules encode the core merge semantics for a Knowtation vault.
# They are pre-populated because they are almost always correct for any vault;
# override by adding higher-priority rules above them.
#
# Documentation: docs/reference/muse-attributes.md

[meta]
domain = "knowtation"

# Rule 1 — Frontmatter sets (tags, entities, attachments) are independent.
# Tag and entity additions from both branches should always accumulate; the
# three-way merge engine can never produce a useful diff-of-diffs for set
# dimensions.  strategy = "union" accumulates all additions and honours
# deletions only when both branches agree.
[[rules]]
path      = "**/*.md"
dimension = "frontmatter"
strategy  = "union"
comment   = "Tag/entity/attachment sets are independent — accumulate additions from both sides."
priority  = 20

# Rule 2 — Inbox notes are locally-authoritative.
# Capture plugins write inbox notes from the local message interface; the
# remote branch should never silently overwrite a local capture.
# strategy = "ours" keeps the local (left) version and discards any remote
# edit to an inbox note whose source_id already exists locally.
[[rules]]
path      = "inbox/**"
dimension = "*"
strategy  = "ours"
comment   = "Inbox captures are local-authoritative; remote edits are discarded."
priority  = 10

# Rule 3 — Archived notes are immutable.
# Once a note moves to archive/ it should not change.  Prefer the local
# version; treat any remote edit as an accident rather than an intention.
[[rules]]
path      = "archive/**"
dimension = "*"
strategy  = "ours"
comment   = "Archived notes are immutable; local version is always preferred."
priority  = 10