BC Observatoryunofficial, made by waldo
code change · otherAL Developmentofficial - Microsoftreviewed - checked by Opus

#114 Document the skill-vs-knowledge boundary so BC facts land in knowledge files

Documentation now clarifies that skills should contain mechanics while knowledge files hold Business Central facts, establishing a boundary to prevent facts from being duplicated or misplaced across skills and knowledge articles.

Open in Claude114.mdPull request #114

Pull request · merged into main on 2026-07-17 by JesperSchulz · 3 files (+35 -0), 2 AL · other · tier official · reviewed (checked by Opus)

What changed

  • Skills are finders/appliers that act on cited BC behavioral claims from knowledge files, not containers for BC facts
  • Negative knowledge (false-positive guards) is first-class and belongs in knowledge files, not inline in skills
  • New decision gate in write.md helps authors determine whether a knowledge file is the right artifact
  • Reviewer heuristic added: changes to what skills flag should almost certainly go into knowledge files
  • Rule against restating article facts inline in skills prevents duplication and drift

AL objects touched

  • skills/do.md: modified, not in the BC? snapshot
  • skills/write.md: modified, not in the BC? snapshot

Context

  • Systems: development
  • From the description: “nothing tells an author where a new BC fact (or a false-positive guard) belongs”

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).