# `docs/standards/` — pointer (charter)

This folder is **NOT a duplicate** of
[`mgf-standard/docs/standards/`](https://codeberg.org/magogi-admin/mgf-standard/src/branch/main/docs/standards/).
The cross-project engineering standards — the `DP-*` / `EH-*` / `LG-*` / `CF-*` /
`SC-*` / `TS-*` / `AP-*` / `DOC-*` / `REL-*` corpus — live at **mgf-standard** and
are the single source of truth. `mgf-uitest-web` **inherits** them and links here;
it does not copy them.

Copying would freeze a snapshot that silently drifts from the corpus. Read any
topic at its source instead:

```bash
mgf-fed standards            # list all topics
mgf-fed standards security   # print the full doc (aliases work)
```

## What goes here

Only this pointer. `mgf-uitest-web` follows the mgf-standard corpus via the
**`[standards]` extra** — `mgf-common[standards]>=0.47,<1.0` (see
[`../../pyproject.toml`](../../pyproject.toml)). Note the extra is a
**standards/tooling-only** dependency: `mgf-common` is **not** a runtime
dependency of this harness, whose only runtime deps are `playwright`,
`axe-playwright-python`, and `pytest`.

## What does NOT go here

- **A copy of any cross-project standard** → read it at mgf-standard (above).
- **This project's per-rule conformance status + declared level (L1/L2/L3)** →
  [`../inprogress/MGF_STANDARDS_CONFORMANCE.md`](../inprogress/MGF_STANDARDS_CONFORMANCE.md)
  (DOC-15 / CFM-01).
- **Consumer-reported friction** → [`../../FEEDBACK.md`](../../FEEDBACK.md).

## Project-specific standards

**None at present.** `mgf-uitest-web` authors no rules of its own. Should it ever
add one (per DOC-02's "project-specific extensions" shape), that rule table MUST
carry a `web` / `service` / `universal` applicability column, following
mgf-common's `DEP-*` precedent.
