Deterministic checks

Rules

Canon rules say what the checker can report. Severity remains explicit by writing surface; the site does not turn advice into a rule or invent missing guidance.

adjacency

adjacency.valid-context

Name a shared Formation family with its arity scope, and do not mix state and magnitude annotations in one construct.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition

composition.dyad-formation

Use an admitted typed dyad Formation core and full identity.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition.harmony

Compose one capacity and one domain into the asserted harmony member.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition.interaction

Use a declared interaction type with admitted operand kinds and directionality.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition.pair

Use two distinct capacity-domain harmony cells concatenated in 4×5 grid order.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition.path-transition

Use a named path with its declared direction, endpoints, inverse, and typed support contract.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition.pattern

Use a declared pattern member with one annotation mode.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

composition.single-formation

Use an admitted typed single Formation core and full identity.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

notation

notation.forbidden-forms

Write a cell as two concatenated letters, capacity then domain. Separate a list of cells with commas; do not put a comma inside a cell. Do not join cells with a slash or an underscore, and do not write state with colons. Magnitude uses 0 for centered or a signed digit 1–3, never a repeated sign.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

ordering

ordering.canonical-order

Keep harmony operands, state scales, pattern axes, and Formation slots in their Canon-authored semantic order.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

orthography

orthography.canonical-form

Write recognized Canon terms with their authored case, plural, inflection, and hyphenation.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

punctuation

punctuation.canonical-separator

Use × between component harmonies, concatenate two canonically ordered cells for one emergent harmony-pair token, and use commas for ordinary lists or tuples.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

terminology

terminology.confusable-context

Use a known Canon term only for the semantic kind and scope established by its authored relationships and the surrounding construct.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

terminology.membership

Use only known Canon entries, composition members, and child addresses in explicitly typed or positively evidenced Canon constructs.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning

terminology.preferred-form

Use each Canon entry's canonical name instead of an authored less-preferred or deprecated form.

  • product: error
  • marketing: error
  • public: warning
  • docs: warning