Index legible AI-assisted expression

[raelovejoy]

Summary

• Add a concise Wiki entity for Legible AI-Assisted Expression.
• Index the concept in the Lexicon and preserve the core sentence in Phrases & Motifs.
• Record the title and core sentence conservatively as jointly coined: Rae supplied the underlying framing and examples; the compact wording emerged through AI-assisted synthesis.
• Route readers to the public canonical concept instead of duplicating its substantive treatment.

Why

The concept now has a stable identity, explicit provenance, relationships to existing entities, and a cross-project application. The Wiki is the appropriate routing and archaeology layer; the full argument remains in Root-Sequence/root-sequence#15.

Verification

Initial branch verification before the provenance/public-boundary correction:

• python scripts/check_public_boundary.py
• python scripts/prepare_site.py
• python scripts/generate_project_lenses.py
• mkdocs build --strict --site-dir _site
• Public/private boundary passed; 27 canonical entities and 13 project lenses generated; strict site build passed
• git diff --check

The follow-up edits only corrected Markdown provenance wording and removed an access-restricted project reference from the new entity. Those local checks were not rerun in this automation, so the earlier verification is not presented as a fresh post-edit run.

Documentation coherence

• Nearest README/index checked
• Root README checked
• STATUS/current-state documentation checked if applicable
• ROADMAP/planning documentation checked if applicable
• Architecture/decision records checked if applicable
• Cross-project/ecosystem references checked if applicable
• Canonical detail remains in one appropriate place rather than being unnecessarily duplicated

The Lexicon and phrase index are the relevant discovery surfaces. The root Wiki README and architecture remain accurate and are unchanged.

Notes / unresolved questions

• Draft dependency: Canonize legible AI-assisted expression root-sequence#15 should establish or revise the canonical concept before this routing entry is merged.
• Access-restricted project applications are intentionally omitted from the public Wiki entity; private routing belongs in the private layer once the public identity is established.