Lotus Family Strength Map and cross-repository conformance audit

[safal207]

Purpose

Turn the Lotus Family Audit from one-time repository fixes into a repeatable cross-repository strength system for Pythia, CML, and LS.

Current confirmed baseline

Layer	Pythia	CML	LS
Bilingual Lotus contract	✅	✅ merged via CML #211	✅ merged via LS #918
Explicit no-authority boundary	✅	✅	✅
Exact-head evidence	✅	✅	✅
Stale-evidence / supersession rule	✅	✅	✅
Regression protection	✅	✅	✅
Test executed by CI	✅	✅	✅
Judgment/memory/guidance separated from execution	✅	✅	✅

Strength model

The family is considered strong only when every repository preserves all six operational layers:

1. Contract — English and Russian semantics remain equivalent.
2. Evidence binding — evidence is attached to an exact head SHA.
3. Supersession — changed head or inputs invalidate prior evidence.
4. Regression protection — contract invariants are executable tests.
5. CI discovery — those tests are actually run by required CI.
6. Authority firewall — assistant judgment, memory, or guidance never grants ownership, approval, execution, delivery, or merge authority.

Next implementation slice

• Define a canonical machine-readable Lotus Family conformance manifest.
• Add repository adapters for Pythia, CML, and LS.
• Add a cross-repository audit command that reports PASS / DRIFT / UNKNOWN.
• Require exact repository ref and commit SHA for every audit result.
• Emit a durable evidence artifact with checked files, invariants, and hashes.
• Add fixtures proving that bilingual drift and missing CI discovery are detected.
• Keep audit judgment separate from external merge or deployment execution.

Acceptance criteria

• A semantic authority-boundary deletion in either language fails the audit.
• A contract test that exists but is not executed by CI is reported as DRIFT.
• Audit output identifies the exact repository and commit checked.
• Unknown or inaccessible evidence is reported as UNKNOWN, never PASS.
• No audit result itself grants merge, delivery, or execution authority.

Safe sequence

specification → fixtures → local audit engine → repository adapters → CI integration → exact-head review → staged adoption

[safal207]

Implementation has started in draft PR #231.

Current exact head: 22dee84fb1639fa461d182211a791471a74fff88.

The first slice includes the Pythia/CML/LS manifest, deterministic PASS / DRIFT / UNKNOWN auditor, exact-ref and exact-SHA binding, SHA-256 evidence, CI-discovery checks, seven regression tests, and an explicit audit_only authority boundary.

No merge or deployment authority is implied by the audit result.