# Requirement manifest — M suite

**Fixture:** `fixture-requirement-manifest-m@4`

## Given

The canonical requirement owner documents and verification registry are loaded.

## When

The declared verification lane reviews each requirement mapping.

## Required invariants

- **`INV-REQ-TJ-GOAL-01`:** The owner-defined product direction invariant is satisfied.
- **`INV-REQ-TJ-CORE-05`:** The owner-defined direct mutation revalidates complete authority invariant is satisfied.
- **`INV-REQ-TJ-CORE-07`:** The owner-defined no privilege escalation invariant is satisfied.
- **`INV-REQ-TJ-SCAN-04`:** The owner-defined shared-storage entry points and alias handling invariant is satisfied.
- **`INV-REQ-TJ-SCAN-05`:** The owner-defined mount crossing and mount identity invariant is satisfied.
- **`INV-REQ-TJ-SCAN-06`:** The owner-defined capability states and confidence invariant is satisfied.
- **`INV-REQ-TJ-SCAN-07`:** The owner-defined capability probes and fail-closed mutation invariant is satisfied.
- **`INV-REQ-TJ-LIMIT-09`:** The owner-defined limit-change evidence invariant is satisfied.
- **`INV-REQ-TJ-SIZE-01`:** The owner-defined allocated blocks remain distinct from apparent bytes invariant is satisfied.
- **`INV-REQ-TJ-SIZE-03`:** The owner-defined metadata, compression, sparse, and rounding treatment invariant is satisfied.
- **`INV-REQ-TJ-SIZE-08`:** The owner-defined no version 1 cross-filesystem additive total invariant is satisfied.
- **`INV-REQ-TJ-ADAPT-03`:** The owner-defined exact supported version/configuration tuple invariant is satisfied.
- **`INV-REQ-TJ-ADAPT-05`:** The owner-defined ecosystem minimum capabilities invariant is satisfied.
- **`INV-REQ-TJ-ADAPT-07`:** The owner-defined execution binding and broad cache scope invariant is satisfied.
- **`INV-REQ-TJ-ADAPT-13`:** The owner-defined package-manager observation boundary invariant is satisfied.
- **`INV-ADAPT-TUPLE-CHANGE-MANAGER-VERSION`:** A manager version change outside the evidenced tuple demotes the operation to discovery-only until evidence is repeated.
- **`INV-ADAPT-TUPLE-CHANGE-RUNTIME-VERSION`:** A runtime version change outside the evidenced tuple demotes the operation to discovery-only until evidence is repeated.
- **`INV-ADAPT-TUPLE-CHANGE-CONFIGURATION`:** An effective-configuration change outside the evidenced tuple demotes the operation to discovery-only until evidence is repeated.
- **`INV-REQ-TJ-PLAN-08`:** The owner-defined dry-run purity and plan equivalence invariant is satisfied.
- **`INV-REQ-TJ-EXEC-01`:** The owner-defined complete filesystem revalidation table invariant is satisfied.
- **`INV-EXEC-ANCESTOR-REPLACEMENT`:** A reviewed ancestor replaced under the same name with a different filesystem identity fails the action before any mutation.
- **`INV-EXEC-LEAF-REPLACEMENT`:** A reviewed leaf replaced under the same name with a different filesystem identity or type fails the action before any mutation.
- **`INV-EXEC-MOUNT-CHANGE`:** A changed mount identity on the selected root, a reviewed ancestor, or the leaf fails the action before any mutation.
- **`INV-EXEC-LINK-COUNT-CHANGE`:** A link-count change against reviewed metadata fails the action before any mutation.
- **`INV-REQ-TJ-EXEC-05`:** The owner-defined residual POSIX race and exact disclosure invariant is satisfied.
- **`INV-EXEC-EXPECTED-PRIOR-EFFECTS`:** A change exactly recorded as an effect of a successfully completed dependency is expected and neither fails nor pauses the action.
- **`INV-REQ-TJ-LOG-03`:** The owner-defined append and flush protocol invariant is satisfied.
- **`INV-REQ-TJ-TERM-06`:** The owner-defined semantic reading order invariant is satisfied.
- **`INV-REQ-TJ-ART-04`:** The owner-defined release-safe executable contract invariant is satisfied.
- **`INV-REQ-TJ-ART-09`:** The owner-defined bounded attributable evidence invariant is satisfied.
- **`INV-REQ-TJ-ART-10`:** The owner-defined source and executable reproducibility invariant is satisfied.
- **`INV-REQ-TJ-ART-11`:** The owner-defined artifact verification gate invariant is satisfied.
- **`INV-REQ-TJ-ART-12`:** The owner-defined retention and correction invariant is satisfied.
- **`INV-REQ-TJ-MAN-07`:** The owner-defined parse, render, install, and lookup checks invariant is satisfied.
- **`INV-REQ-TJ-DIST-01`:** The owner-defined upstream and Termux ownership boundary invariant is satisfied.
- **`INV-REQ-TJ-DIST-02`:** The owner-defined package identity and payload invariant is satisfied.
- **`INV-REQ-TJ-DIST-05`:** The owner-defined Termux recipe contract invariant is satisfied.
- **`INV-REQ-TJ-DIST-06`:** The owner-defined architecture and package-size evidence invariant is satisfied.
- **`INV-REQ-TJ-DIST-07`:** The owner-defined new-package submission workflow invariant is satisfied.
- **`INV-REQ-TJ-DIST-08`:** The owner-defined update and revision workflow invariant is satisfied.
- **`INV-REQ-TJ-DIST-09`:** The owner-defined maintainer-only merge and deployment invariant is satisfied.
- **`INV-REQ-TJ-DIST-10`:** The owner-defined package acceptance checks invariant is satisfied.
- **`INV-REQ-TJ-DIST-11`:** The owner-defined deployment states and verification invariant is satisfied.
- **`INV-REQ-TJ-DIST-12`:** The owner-defined fail-closed publication and correction invariant is satisfied.
- **`INV-REQ-TJ-DIST-13`:** The owner-defined pinned external policy evidence invariant is satisfied.
- **`INV-REQ-TJ-TEST-02`:** The owner-defined adapter capability evidence invariant is satisfied.
- **`INV-REQ-TJ-TEST-04`:** The owner-defined evidence fields and limitations invariant is satisfied.
- **`INV-REQ-TJ-TEST-05`:** The owner-defined build gates invariant is satisfied.
- **`INV-REQ-TJ-PERF-06`:** The owner-defined profiling evidence invariant is satisfied.

## Forbidden effects

- **`NO-REQ-MANIFEST-UNBOUND-M`:** The unbound manifest fixture is not treated as implementation evidence.
- **`NO-ADAPT-TUPLE-CHANGE-SUPPORTED`:** No operation remains supported or evidenced across a changed manager version, runtime version, or effective configuration tuple.
- **`NO-EXEC-EXPECTED-EFFECT-MISMATCH`:** An exactly recorded effect of a successfully completed dependency is never reported as an unexpected mismatch.

## Variations

Executable implementation and evidence fixtures are separate work items.

## Limitations

This is an unbound verification path: it records the required invariant and suite mapping,
but does not establish implementation coverage or passing runtime evidence.