Add a plain-language Why This Matters section before the principles

[NetworkTheoryAppliedResearchInstitute]

First of the six review points: a summary of why this matters, before the principles.

The problem

The document opens with three dense paragraphs carrying Janus, Toffler, Acemoglu and Robinson's narrow corridor, the Red Queen effect, two NTARI papers and the Leviathan in four forms — then goes straight into the principles. A reader who did not follow that theory had nothing to stand on when the principles arrived.

The new section

Why This Matters

Every system that coordinates people exercises power over them, whether it means to or not. That is not a defect; coordination requires it. But power stays healthy only when something checks it — not a check on paper, but real people with real stake, close enough to act. Most platforms now move at the speed of the network while everything built to hold them accountable moves at the speed of meetings, and a check that arrives late is not a check at all. JFA's answer is to stop treating coordination and accountability as two systems: same software, same people, same speed.

No jargon, no citations, no terms of art. It restates in plain words what the three preceding paragraphs argue in theory — not a check on paper is the paper Leviathan, a check that arrives late is not a check at all is the velocity gap — so the concepts stay available to a reader who skipped the apparatus.

The trim, which needs your eye

The third introduction paragraph ended:

JFA is built to close that gap from inside: the community that coordinates is the community that checks, the two capacities exchanged continuously in the same software at the same speed, disciplined layer by layer by the cost of leaving. It is a shackled Leviathan in code.

Compare the first principle, four paragraphs later:

Shared Responsibility. The community that coordinates the economy is the same community that checks the coordination. The two functions are exchanged continuously — never split into rulers and ruled.

That is the same sentence twice, near-verbatim, and adding a third plain-language statement of it would have made three. The principle keeps it, since that is where a reader looks for it. The paragraph now ends on the shackled Leviathan, which is what it was building toward:

JFA is built to close that gap from inside, disciplined layer by layer by the cost of leaving. It is a shackled Leviathan in code.

The duplication predates this PR — worth flagging separately in case you would rather keep both and cut something else instead.

Remaining from this review

• Expanding Economy & Information (E&I) at first use in each paragraph — still carries the open question that 9 paragraphs use it and none twice, so a strict per-paragraph rule retires the abbreviation entirely.
• Citing Moore (1988) and Greco (2009) for endogenous mutual credit in the introduction, which the structure article cites and the document does not.

🤖 Generated with Claude Code

[NetworkTheoryAppliedResearchInstitute]

Translations: after adoption. Required by CONTRIBUTING ## Translations and missing from my original description — flagging it late rather than not at all.

The English is authoritative and still under review. These seven amendments touch overlapping parts of the introduction, principles, layer bodies and references, so translating each separately would mean seven passes over seven languages against text that may still change in review. Recommend one translation pass covering every adopted amendment once this review closes.