# `docs/standards/` — pointer-only (federation sibling)

> **DOC-02 §2.0.4 pointer pattern.** A federation sibling's
> `docs/standards/` MAY be a pointer-only README that links to the
> cornerstone. It MUST NOT duplicate cornerstone content. This file
> satisfies that rule.

The engineering standards `mgf-hrb` inherits from live in `mgf-common`,
the cornerstone library. We don't duplicate them here — they have ONE
source of truth.

## Where to read the standards

```bash
mgf-common standards            # list all topics
mgf-common standards LOGGING    # print the LOGGING standard
mgf-common standards errors     # alias for ERROR_HANDLING
mgf-common standards security   # alias for SECURITY_STANDARD
```

Canonical web home:
[mgf-standard/docs/standards/](https://codeberg.org/magogi-admin/mgf_common/src/branch/main/docs/standards/).

## Per-rule audit for this project

How strictly `mgf-hrb` follows each rule is recorded in
[`../inprogress/MGF_STANDARDS_CONFORMANCE.md`](../inprogress/MGF_STANDARDS_CONFORMANCE.md)
— declared **L1 — Lite** today, with most Python rules ⏳ while the SDK
is pre-`0.1.0`. The *argument* behind that posture (Zig majority,
Python-rule × Zig-code mismatch) is in
[`../../STANDARDS_NOTE.md`](../../STANDARDS_NOTE.md).

## Why pointer-only

Duplicating standards into every sibling means drift between siblings,
re-publication churn on every cornerstone bump, and the AI-agent loop
hitting two versions of "what's the rule for X?" — none of those serve
the consumer. The pointer keeps one source of truth, and `mgf-common
catch-up` enforces that this project stays in sync.
