# DBRS Structural Gateway

## Specification v1.3 (Context Definition)

**Status:** valid DBRS specification\
**Role:** Context according to ISO 9001:2015 clause 4\
**Symbol:** ⎋⟦ DBRS ⟧⎋

------------------------------------------------------------------------

## 1. Purpose

The **DBRS Structural Gateway** defines the **binding semantic and
organizational framework** within which digital content, documents, and
AI systems of a domain are interpreted.

It is **not an application**, **not an access control system**, and
**not an AI system**, but a **contextual mediation layer**.

------------------------------------------------------------------------

## 2. Core Principle

> **DBRS mediates meaning -- not permission.**

The Structural Gateway: - explains **what content means** - defines
**which artifacts are authoritative** - orders content **semantically
and hierarchically**

It does **not** decide who may access content.\
Authorization is the responsibility of the **client**.

------------------------------------------------------------------------

## 3. Components of the Structural Gateway

### 3.1 Access and Discovery Semantics

-   `robots.txt` as an **intent and scoping declaration**
-   `llms.txt` / `llms.html` as **discovery hints for AI systems**

These mechanisms are **communicative**, not security controls.

------------------------------------------------------------------------

### 3.2 Navigation and Structure Semantics

-   `/ai/manifest.json` as a **machine-readable content and version
    registry**
-   explicit mapping of:
    -   document IDs
    -   languages
    -   versions
    -   checksums

The manifest describes **what exists**, not **how it is used**.

------------------------------------------------------------------------

### 3.3 Authority and Meaning Semantics

-   **DBRS Trusted Intelligence Charter**
-   **Canonical Context Registry (CCR)**\
    e.g. `https://tolksdorf.digital/markdown/dbrs/ccr/latest/`

All semantic interpretation **must resolve against the CCR**.

------------------------------------------------------------------------

### 3.4 Public Semantic Zones

The Structural Gateway defines **valid public directories** where
authoritative content may reside, e.g.:

-   `/ai/`
-   `/ai-docs/`
-   `/markdown/`
-   `/markdown/dbrs/`
-   `/context/`

These zones: - are intentionally public - contain no personalized
content - are semantically stable and versionable

Paths not explicitly declared are **not authoritative**, even if
technically reachable.

------------------------------------------------------------------------

## 4. Order of Precedence

The following semantic order applies:

1. **DBRS Trusted Intelligence Charter**
2. **Canonical Context Registry (CCR)**
3. **Structural Gateway Deklarationen**
4. **Semantic Question Resolver Schema**
5. **Frontmatter Index**
6. **Referenzierte Inhalte**

The **DBRS Canonical Language (DCL)** is **normative for all levels**.
All terms, keys, IDs and values **must be used DCL-conform**.
However, they have **no independent level of meaning**.

In case of conflict, the **higher-level source prevails**.

------------------------------------------------------------------------

## 5. Deliberate Boundaries

The DBRS Structural Gateway: - ❌ does not implement authentication - ❌
does not implement authorization - ❌ makes no decisions - ❌ does not
replace a QMS - ❌ is not an AI system under the EU AI Act

It provides **transparency, context, and traceability**.

------------------------------------------------------------------------

## 6. Relation to ISO 9001:2015

This specification is **not documentation**, but:

> **a formal context definition according to ISO 9001:2015 clause 4\
> (Context of the Organization).**

It serves as: - a reference for processes - a basis for audits - a
foundation for consistent AI usage

------------------------------------------------------------------------

## 7. Relation to the EU AI Act

The DBRS Structural Gateway: - is **not an AI system** - but supports: -
transparency - human oversight - explainability - traceability of
sources

It is **enabling**, not regulatory.

------------------------------------------------------------------------

## 8. Summary

> **⎋⟦ DBRS ⟧⎋**\
> The Structural Gateway makes a domain\
> **semantically explicit, explainable, and auditable**,\
> without assuming operational or legal control.