Two competing MASTER_INDEX.md, and the README nav points at neither

[beyondnetPeru]

There are two files called MASTER_INDEX.md, and the README's navigation points at neither:

• ./MASTER_INDEX.md — 12 lines, six links
• ./reference/core/control-center/taxonomy/MASTER_INDEX.md

A reader who finds one has no way to know the other exists.

The fix

Decide which is canonical, and make the other link to it rather than duplicate it. Either
direction is defensible — the point is that one of them stops competing.

One thing to know before you start

The root MASTER_INDEX.md is on the sixteen-document entry surface
(ADR-0126), so if you
edit it you must edit MASTER_INDEX.es.md in the same pull request, with the same number of
## and ### headings. The other file is outside the surface and has no such requirement.

Done when

node .harness/scripts/ci/01-validate-docs.mjs and
node .harness/scripts/ci/04-check-bilingual-parity.mjs both pass, and a reader landing on
either file can reach the other.

---

What is not your problem

This repository runs a large number of governance checks against itself. If one goes red on
your PR for a reason unrelated to your change, say so in a comment and a maintainer will sort
it out — do not try to fix the harness to get green. Specifically not yours: anything under
.harness/scripts/ci/ reporting on the gap board, ADR registry, maturity or coverage floors;
Governance guards; release-pipeline and provenance failures; and bilingual findings on
documents outside the sixteen-file entry surface (ADR-0126).

New here? CONTRIBUTING.md has the setup. Short version: fork, npm install,
npm run build. Commits need a Signed-off-by line — git commit -s, and a hook adds it if
you forget.