Simplification and rejection criteria

Simplify Atlas when a semantic primitive adds authoring and review cost without changing useful generated navigation, explanation, lifecycle understanding, provenance, or agent behavior. Context records that repeat anchors and structures that shared consumers cannot interpret consistently are specific warning signs.

Reject or redesign the portal framework when:

• each project needs custom semantic mapping, routes, or UI components;
• the portal adds ceremony before opening known material;
• each selection destabilizes the reader;
• the portal hides provenance; or
• the implementation cannot meet accessibility and performance requirements.

Do not promote or expose a publication build until it enforces exact profile selection across source reads, generated documents, indexes, search, routes, diagnostics, and caches. Reject a build or deployment package that widens selection through shared Point identity, semantic edges, or document links.

Reduce or abandon the broader project if one shared implementation cannot generate a credible portal from conforming Atlases. Apply the same decision when generated context does not justify its authoring, review, validation, and maintenance costs. Prior investment, a successful conformance suite, or the Atlas metaphor is not sufficient reason to continue.