Atlas

Resource

Open questions

Unresolved product, authoring, publication, interoperability, adoption, and governance questions.

Resource open-questions

Product value

  • Can the shared portal mature from a two-corpus design proof into a hardened framework without project-specific semantic mapping or UI development?
  • Which real tasks improve materially because one Point retains identity across several perspectives?
  • At what project size, rate of change, or coordination cost does the semantic layer become worthwhile?

Authoring

  • Can people and software agents choose Map and Area questions consistently without extensive training?
  • How much review effort is required to prevent duplicate identities, vague contexts, and stale lifecycle state?
  • Which authoring assistance is useful without hiding the source files or inventing semantics?

Publication and reader experience

  • What publication-build contract and tests can prove that unselected material never enters pages, navigation, indexes, search, routes, diagnostics, or caches?
  • Can direct-document access remain clear as the shared portal adds complete relation, continuation, attachment, and policy behavior?
  • Which compact or contextual reader arrangement best preserves orientation, continuation, and cross-context understanding while maintaining direct-document parity?
  • Which accessibility and performance budgets are required before a portal can be treated as a credible control surface?

Ecosystem and stewardship

  • Can another team implement the contract from the specification and fixtures without repository-specific knowledge?
  • Which distribution form is useful without prematurely centralizing Atlas around one package or service?
  • How should extensions become shared standards, remain local, or be retired?
  • Which governance process can evolve the format without making weak decisions expensive to reverse?

Where this Resource is used

7 uses

Original Atlas material: CC0 1.0 Universal or 0BSD. Referenced material retains its own terms.

Reading this Atlas

Atlas connects project documents to the claims, decisions, and perspectives they inform. It helps readers find relevant material and understand why it matters.

Explore the portal

  1. Start with a Map, then narrow the view through its Areas.
  2. Search for a phrase, title, or Point identity. Filter results by type.
  3. Open a Point for its explanations, related Points, and sources. Follow source links for the underlying material.

Quick reference

Map
A durable project perspective organized around one central question.
Area
A concern within a Map. Areas can overlap; memberships explain why a Point belongs.
Point
One claim, decision, constraint, question, or other coherent item with its own identity.
Context
An explanation of how the same Point matters in another Map.
Relation
A directed link between Points with an explanation, such as support, dependency, or replacement.
Resource
An addressable document or other material.
Content
The primary material for an Atlas item.
Reference
Material linked as evidence, background, implementation, history, or an example.

Missing links do not mean that no relationship exists.

Read the state

Posture describes the author's stance: asserted means presented as applicable or believed; open, unresolved; proposed, a candidate; intended, a desired or selected future state.

Lifecycle describes standing: active means current context; historical, retained prior context; superseded, replaced by another Point; withdrawn, retracted.

Asserted does not mean verified. Intended does not mean implemented. Source links provide material to assess these claims.