What is currently wrong with this network

Why this page exists

This network is licensed under the Maher License 2.3, whose Part H incorporates a register of structural harms — injuries that follow from how a system is built and financed rather than from anyone operating it badly. One of those harms, HX-15, is the harm an ethics instrument produces by itself: adopting the instrument reduces external scrutiny faster than it reduces harm, so the published commitment becomes a shield. The register's own test for whether an adopter is sincere is cheap to check and hard to fake — has the adopter ever published a finding against itself?

This page is that finding. It is generated from the same data the notices on every article are generated from, so it cannot quietly diverge from what readers are shown in place. If it ever contains only remediated items, it has become the thing it was built to prevent.

A caveat we are obliged to state plainly

ML-2.3 has not been reviewed by counsel in any jurisdiction, nor by a qualified scholar. Its author says so himself, and several of its devices — the condition/covenant split and the Scale Gate in particular — have enforceability that varies significantly between legal systems. The extension of Ḥifẓ al-ʿAql (preservation of the intellect) from intoxicants to attention-engineering is a reasoned analogy by a non-scholar, filed as open question RAT-16 and published as contested. Nothing on this page asks you to accept that analogy; the duties we have taken on stand on the documentary evidence independently.

One defect in the instrument itself

We verified the register we rely on, rather than citing it on trust, and it is incomplete. The copy of HX-000 v2026.09.4 we hold details eleven harms in the full eight-part form and then stops: HX-12, HX-13 and HX-14 exist only as rows in the summary table. This matters operationally, because ML-2.2 §H.3(a)(v) makes part of HX-14 an absolute prohibition refused irrespective of forum — so a licensee is presently bound by an absolute whose content is not published, and cannot read what it prohibits. It is filed upstream as DEF-2026-050, severity blocking. We state it here because relying silently on an instrument we know to be incomplete would be the same failure in a different direction.

How to report something we have missed

The register names a further harm, HX-16, for exactly this situation: a finite list of harms becomes a ceiling rather than a floor, because the unnamed harm starts to look permitted by omission. Nothing in our compliance authorises a structural harm by reason of its absence from this page. If you can name one of ours that is not listed, tell us and it will be added with the date it was reported, whether or not we can fix it.