Jiang Lens Atlas Maintainer

Use this for the high-level public map of the lens, usually:

website/src/content/docs/lens.md

The atlas is a map, not the full encyclopedia. Concept depth belongs in concept pages.

Inputs

• finished episode reads,
• concept pages,
• lens signal proposals,
• existing lens points from compiled link-index.json,
• dated source refs.

Duties

• Maintain lens families and relationships.
• Add stable lens-point:* anchors for reusable ideas.
• Link to concept pages when they exist.
• Keep the page readable and navigable.
• Update progressively after new evidence, not by rewriting the whole atlas every time.

Atlas Style

The atlas should answer:

• What is Jiang Lens, and what Jiang source material is being mapped?
• What are the major parts of Jiang's world model?
• Which concepts belong together?
• Which concepts are still provisional?
• Where can a reader go deeper?
• Which source-backed lens points can episodes cite?

Keep prose compressed. Do not dump raw source refs or internal workflow notes. Use inline evidence marks and lens point anchors where the map makes a durable claim.

The atlas must be entry-point resilient. A reader who lands here from search or a shared link should not need /introduction to know that the corpus means Jiang Xueqin's Predictive History lectures, Great Books lectures, interviews, and writing processed by this project.

Structure Governance

Use the atlas to prevent both bloat and premature fragmentation.

• If a concept page grows beyond about 6,000 words or 20 distinct Jiang sources,

mark it as a split-review candidate in your own proposal or PR notes before adding more atlas weight to it.

• If a concept page grows beyond about 8,000 words or 25 distinct Jiang sources,

prefer a parent/child structure unless the concept still reads as one compact mechanism.

• If a concept has fewer than 4 distinct Jiang sources, list it as provisional,

keep it inside a parent concept, or hold it as a seed until more evidence arrives, unless it is a foundational primitive with unusually strong source force.

• When section titles inside a large page name reusable mechanisms, they are

likely child-page candidates. The atlas should make that shape visible instead of letting one page become an encyclopedia.

Lens Point Rules

Use lens points only for addressable ideas other pages may cite:

• definitions,
• reusable mechanisms,
• diagnostics,
• chronology/evolution points,
• core claims.

Do not tag decorative prose. Preserve IDs when rewriting a point unless the idea itself changes.

Validation

Run:

node ops/scripts/compile-content.mjs
node ops/scripts/validate-content.mjs
cd website && npm run build

If an episode references a lens point that no longer exists, validation should fail. Fix the atlas or the episode link; do not leave stale IDs.