@erclx/canon 5.19.0 → 5.21.0

package/governance/rules/canon/660-diagrams.md

@@ -1,19 +0,0 @@
----
-description: Route .canon/diagrams edits to the diagrams standard for entry kinds, frontmatter, and explanation prose
-paths:
-  - '.canon/diagrams/**'
-  - '.claude/DIAGRAMS.md'
----
-
-# Diagrams standards
-
-## Authority
-
-- Follow the diagrams standard for which question an entry answers, the entry kinds and their source signals, the frontmatter, and the explanation prose beneath the fence. It is the single source. Read it with `canon standards diagrams`.
-- Layout, budgets, accessibility, labels, and render verification inside the fence are a separate topic. `802-mermaid` routes them to `mermaid.md`.
-- A diagram entry carries structure and flow, not implementation. Read the standard before adding or revising a kind.
-
-## Scope
-
-- Write a new diagram to `.canon/diagrams/<kind>.md`, never to `.claude/DIAGRAMS.md`
-- Convert a `.claude/DIAGRAMS.md` left by an older install into per-kind entries before editing it

package/governance/rules/canon/662-session.md

@@ -1,15 +0,0 @@
----
-description: Route .canon/tasks/ session map edits to the session standard for the filename, the core sections, and what a handoff carries
-paths:
-  - '.canon/tasks/session-*.md'
----
-
-# Session map standards
-
-## What a handoff carries
-
-- Follow this rule rather than `655-tasks.md` for a `session-` file. A handoff is not a task and carries neither `## Outcomes` nor `## Findings`.
-
-## Authority
-
-- Follow the session standard for the filename and location, frontmatter, the core sections, and the write and read procedures. It is the single source. Read it with `canon standards session`.

package/governance/rules/canon/663-ready.md

@@ -1,15 +0,0 @@
----
-description: Route .canon/ready/ edits to the ready standard for the folder layout, the overview frontmatter, and the thin-plan contract
-paths:
-  - '.canon/ready/**'
----
-
-# Ready standards
-
-## Writing a ready folder
-
-- Load the `canon:draft-ready` skill to write a ready folder, its overview, the thin plan, and the task row. It owns the procedure. Report it rather than proceeding silently when it does not resolve, since it ships with the plugin and this rule ships with the CLI.
-
-## Authority
-
-- Follow the ready standard for the folder layout, ordinal naming, the overview frontmatter, the mirrored tree, and the thin-plan contract. It is the single source. Read it with `canon standards ready`.

package/governance/rules/claude/590-rule-authoring.md

@@ -1,12 +0,0 @@
----
-description: Enforce frontmatter, body shape, and voice for governance rule files
-paths:
-  - '.claude/rules/**/*.md'
----
-
-# Rule authoring standards
-
-## Authority
-
-- Follow the rule-authoring standard for rule frontmatter, body shape, and voice. It is the single source. Read it with `canon standards rule`.
-- Read it before writing or editing a rule. Do not work the shape from memory.

package/governance/rules/writing/801-markdown.md

@@ -1,14 +0,0 @@
----
-description: Route markdown edits to the markdown standard for headings, lists, punctuation, and frontmatter wording
-paths:
-  - '**/*.md'
----
-
-# Markdown mechanics standards
-
-## Authority
-
-- Follow the markdown standard for headings, paragraph and list structure, code spans, punctuation, emphasis, file references, and the wording of a `title` or `description`. It is the single source. Read it with `canon standards markdown`.
-- Read it before a substantial markdown edit. Do not work the banned characters from memory.
-- Run `canon markdown audit <path>` after the edit, and rewrite the sentence carrying a hit rather than swapping the token for a near-synonym.
-- Voice, rhythm, and sentence construction are a separate topic. `800-prose` routes them.

package/governance/rules/writing/802-mermaid.md

@@ -1,14 +0,0 @@
----
-description: Route a drafted Mermaid fence to the mermaid standard for layout, budgets, accessibility, labels, and render verification
-paths:
-  - '**/*.md'
----
-
-# Mermaid diagram standards
-
-## Authority
-
-- Apply this rule only when the edit drafts or revises a Mermaid fence. Skip it on a markdown edit carrying no diagram.
-- Follow the mermaid standard for direction and layout, node and edge budgets, the accessibility fields, punctuation inside labels, and how a render is verified. It is the single source. Read it with `canon standards mermaid`.
-- Read it before drafting the fence. Do not work the layout or the budgets from memory.
-- Which diagram a document carries and what question it answers is a separate topic. `660-diagrams` routes it.

package/governance/rules/writing/880-readme.md

@@ -1,11 +0,0 @@
----
-description: Route README edits to the readme standard for structure, sections, and content conventions
-paths:
-  - '**/README.md'
----
-
-# README standards
-
-## Authority
-
-- Follow the readme standard for voice, structure, required and optional sections, heading hierarchy, badge classes, per-project-type content, and what to link out rather than inline. It is the single source. Read it with `canon standards readme`.

package/governance/rules/writing/891-standard-authoring.md

@@ -1,12 +0,0 @@
----
-description: Enforce shape, scope, and success criterion for authoring convention files
-paths:
-  - 'standards/**/*.md'
----
-
-# Standard authoring standards
-
-## Authority
-
-- Follow the standard-authoring standard for a standard's frontmatter, shape, scope, and success criterion. It is the single source. Read it with `canon standards standard`.
-- Read it before writing or editing a standard. Do not work the shape from memory.