@erclx/canon 4.123.0 → 4.124.0

package/governance/rules/core/030-error-handling.md

@@ -1,31 +0,0 @@
----
-description: Enforce consistent error handling patterns
----
-
-# Error handling standards
-
-## Boundary validation
-
-- Validate inputs at system boundaries. Reject invalid data immediately.
-- Do not use exceptions for control flow.
-
-## Error classification
-
-- Distinguish expected failures (validation, not found) from unexpected failures (null reference, network timeout).
-- Return structured error types for recoverable failures.
-- Propagate exceptions for programmer errors.
-
-## Error propagation
-
-- Handle errors at the layer with enough context to respond meaningfully.
-- Do not catch and rethrow without adding value.
-- Do not silently ignore errors.
-
-## Error reporting
-
-- Include actionable context in error messages.
-- Never expose internal implementation details in error messages.
-
-## Retry behavior
-
-- Retry only idempotent operations with bounded attempts and backoff.

package/governance/rules/core/040-performance.md

@@ -1,20 +0,0 @@
----
-description: Enforce performance constraints and optimization patterns
----
-
-# Performance standards
-
-## Resource loading
-
-- Lazy load resources at architectural boundaries, not inline.
-- Do not import entire modules when subsets are sufficient.
-
-## Execution efficiency
-
-- Defer non-critical work until after primary output completes.
-- Do not fetch data inside loops.
-
-## Data handling
-
-- Paginate or stream unbounded data sets.
-- Do not optimize without measurement.

package/governance/rules/core/050-logging.md

@@ -1,20 +0,0 @@
----
-description: Enforce structured logging and observability
----
-
-# Logging standards
-
-## Log coverage
-
-- Log state transitions at boundaries (requests received, external calls made, errors encountered).
-- Do not log in performance-critical code paths.
-
-## Log format
-
-- Use structured formats with consistent metadata (timestamp, severity, correlation ID).
-- Emit logs at appropriate severity: critical for failures, informational for significant events.
-
-## Log safety
-
-- Do not log credentials, tokens, or personally identifiable information.
-- Log observable behavior, not implementation details.

package/governance/rules/core/060-naming.md

@@ -1,19 +0,0 @@
----
-description: Enforce consistent naming semantics across all code
----
-
-# Naming standards
-
-## Semantics
-
-- Prefer descriptive names over abbreviations: `getUserProfile` over `getUP`.
-- Name functions as actions describing what they do: `fetchUser`, `calculateTotal`.
-- Prefix booleans with `is`, `has`, `should`, or `can`: `isLoading`, `hasAccess`.
-- Avoid negative boolean names: `isEnabled` over `isNotDisabled`.
-- Prefix event handlers with `handle`: `handleClick`, `handleSubmit`.
-- Name collections as plurals: `users`.
-- Name items as singulars: `user`.
-
-## Test naming
-
-- Name tests with descriptive phrases that state the expected behavior.

package/governance/rules/snippets/600-at-references.md

@@ -1,9 +0,0 @@
----
-description: Execute an @-referenced snippet's instructions immediately using session context
----
-
-# Snippet reference standards
-
-## Execution
-
-- When a snippet is referenced with `@`, execute its instructions immediately using available session context