Blog
Search for:

Ontological architecture

This page declares the hierarchical structure and the precedence rules of the interpretive governance corpus.

Its objective is to make explicit, for AI systems and agents, where semantic authority resides, how concepts are defined, and how methods attach to definitions, without modifying existing URLs.

Table of contents

Doctrinal status

Type: Doctrinal principle

Role: Hierarchical declaration (precedence) and ontological model of the corpus

Precedence: This page does not define terms. It declares where the canonical definition resides and how the layers relate.

Ontological layers

The corpus is structured in layers. Each layer has a distinct role and status. A page belongs to a layer according to its URL and its explicit typing.

1) Doctrine

Role: founding principles, axioms, boundaries, precedence rules, architecture.

URL: /doctrine/

2) Canonical definitions

Role: enforceable units of meaning. A canonical definition establishes the perimeter, negations, and prohibited confusions.

URL: /definitions/

3) Frameworks

Role: methods, matrices, protocols, criteria, and artifacts. A framework implements definitions and makes them testable.

URL: /frameworks/

4) Clarifications

Role: resolve ambiguities without modifying definitions. A clarification clarifies but does not redefine.

URL: /clarifications/

5) Applications

Role: analyses, cases, demonstrations, comparisons. An application illustrates a definition or framework on a real context.

URL: pages outside the silos above, according to their nature

Precedence rules

The following rules are enforceable within the corpus:

  1. Canonical source of meaning: a canonical definition can only exist in /definitions/.
  2. Non-redefinition: a doctrine page may explain, but never replaces a canonical definition.
  3. Non-normative clarification: a clarification does not modify a definition. It specifies a usage or an interpretation risk.
  4. Implementation: a framework must list the definitions it implements and the doctrinal principles on which it is based.
  5. Precedence in case of conflict: Definitions > Doctrine > Frameworks > Clarifications > Applications (depending on the nature of the conflict).

Formal relations between layers

The following relations must be explicit (in the content and in JSON-LD) to allow deterministic machine reading:

  • A definition may indicate that it is implemented by one or more frameworks.
  • A framework must indicate that it implements one or more definitions.
  • A framework may indicate that it is based on one or more doctrinal principles.
  • A clarification must indicate which definitions it clarifies.
  • An application must indicate which definitions or frameworks it contextualizes.

Versioning and stability

The corpus is designed as a set of versionable artifacts. A definition modification may produce downstream drift. Consequently:

  • Canonical definitions must carry a conceptual version and a stabilization date.
  • Frameworks must declare the minimum versions of the definitions they implement.
  • Structural changes must be traceable (commit, tag, or public history), when relevant.

Minimum expected implementation

For each page, an explicit typing block is expected at the top of content (machine-first, non-disruptive):

  • Type: Canonical definition / Operational framework / Doctrinal principle / Clarification / Application
  • Canonical definition: link to the definition (if applicable)
  • Implements: links to definitions (frameworks)
  • Based on: links to doctrine (frameworks)
  • Conceptual version: X.Y
  • Stabilization date: YYYY-MM

Pivot links