Declared Jurisdiction

Kind: principle

Layer: Structural Core

Record: architecture:declared-jurisdiction

Severity: mandatory

Scope: repository, root, file

Canonical: Ontology

A design rule that a naming gate reads from one declaration the roots it governs, the containers and buckets under each, the classes of file exempt from the grammar, and the trees another system authors or resolves by name, which are exempted once and never governed.

Listed in Architecture principles, after Glob-Resolvable Tree and before Bounded Nesting Depth.

Requires

• Governed Root
• Container Level
• Flat Bucket
• Ignore Declaration
• Ecosystem-Fixed Name
• Structurally Exempt File
• Compound Marker

Reinforces

• Explicit Boundaries
• Single Source of Truth

Enables

• Bounded Nesting Depth
• Glob-Resolvable Tree
• Backward Compatibility

Conflicts with

• Ignore-List Silencing
• Depth-Relief Container
• Claimed Foreign Tree
• Duplicated Authority

Contracts

• Taxonomy Jurisdiction
• Container Ladder

Violated by

• Shape-Inferred Jurisdiction
• Ignore-List Silencing
• Per-Check Exemption List

Refactored by

• Declare the Root
• Place the Folder in an Existing Container
• Remove the Ignore Entry
• Collapse the Exemption Lists

Severity

• mandatory

Category

• Taxonomy / Classification / Naming

Enforced by

• rules/entrypoints/taxonomy.entrypoint.ts

Enabled by

• Derived Naming Registry

Linked from

• Placement is a grammar
• Domain Architecture
• Contracts / Interfaces / Compatibility
• Schema / Canonical Data / Semantics
• Taxonomy / Classification / Naming
• Schema / Canonical Data / Semantics
• Taxonomy / Classification / Naming
• Taxonomy
• Severity levels

in this codebase

• checkPlacement