---
id: change/bcquality/114
type: change
title: "#114 Document the skill-vs-knowledge boundary so BC facts land in knowledge files"
summary: 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.
tier: official
language: en
tags:
  - other
  - main
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:12:24.818Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: b9c57ba6f993feeac860c24808865045be926167
evidence:
  - kind: code
    url: https://github.com/microsoft/BCQuality/pull/114
    title: "microsoft/BCQuality#114: Document the skill-vs-knowledge boundary so BC facts land in knowledge files"
    date: "2026-07-17"
    commit: b9c57ba6f993feeac860c24808865045be926167
    t: null
    quote: nothing tells an author where a new BC fact (or a false-positive guard) belongs
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 114
repo: microsoft/BCQuality
source_id: bcquality-prs
url: https://github.com/microsoft/BCQuality/pull/114
kind: pr
base_branch: main
major: null
merged_at: "2026-07-17T10:15:23Z"
author: JesperSchulz
author_type: User
community_contribution: false
labels: []
change_class: code
change_kind: other
behavior_change: false
breaking: false
files:
  count: 3
  additions: 35
  deletions: 0
  al: 2
apps: []
objects_touched: []
objects_unjoined:
  - path: skills/do.md
    status: modified
    reason: not-in-snapshot
  - path: skills/write.md
    status: modified
    reason: not-in-snapshot
obsoletions: []
backports: []
fixes_issues: []
work_items: []
systems:
  - development
quote: nothing tells an author where a new BC fact (or a false-positive guard) belongs
joined_against:
  major: null
  commit: null
---

# #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.

[Pull request](https://github.com/microsoft/BCQuality/pull/114) · 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).