docs: codify the warded kernel boundary #1253

Merged
coilysiren merged 1 commit from issue-1245 into main 2026-07-14 08:47:17 +00:00
Member

This change codifies the warded kernel boundary so later extraction work can decide whether a change belongs in the kernel or on an edge surface before splitting code.

It adds one canonical boundary page and links it from the docs index and agent entry page so the seam is easy to find during follow-on work.

  • What changed: define the kernel surfaces, edge surfaces, and the seam classification rules in docs.
  • Why: give extraction issues a stable boundary contract before any code moves.
  • Test/CI: ward exec lint-refs, ward exec test, and pre-commit run --all-files all passed.

closes #1245
ward.workflow: pull-request-and-merge

This change codifies the warded kernel boundary so later extraction work can decide whether a change belongs in the kernel or on an edge surface before splitting code. It adds one canonical boundary page and links it from the docs index and agent entry page so the seam is easy to find during follow-on work. - What changed: define the kernel surfaces, edge surfaces, and the seam classification rules in docs. - Why: give extraction issues a stable boundary contract before any code moves. - Test/CI: ward exec lint-refs, ward exec test, and pre-commit run --all-files all passed. closes #1245 ward.workflow: pull-request-and-merge
docs: codify warded kernel boundary
All checks were successful
test / test (pull_request) Successful in 34s
215aa34faf
Sign in to join this conversation.
No description provided.