SANSA v1 Drafts

SANSA is the Semantic Address NameSpace Abstraction. It defines a common way for consumers to address, resolve, and query semantic information without depending on the physical implementation that stores or generates that information.

SANSA is independent within the Aeonite ecosystem. AEON, AEOS, AES, runtime object graphs, databases, services, and other systems may implement SANSA, but none of those systems owns the abstraction.

Draft Set

• addressing-v1 defines the SANSA address model and selector vocabulary.

• resolve-v1 defines deterministic structural resolution over SANSA address expressions.

These documents are draft-stage because their foundation-layer behavior is now implemented and exercised by AEON TypeScript and the standalone @altopelago/sansa implementation.

Related Proposals

The following SANSA v1 documents remain in ../proposals/ while their surfaces continue to evolve:

• query-v1

• conformance-v1

• extensions-v1

• meaning-validation-integration-v1

• mutate-v1

Design Boundaries

SANSA separates semantic interaction from representation, validation, persistence, and runtime implementation.

• AEON defines how meaning is represented.

• AEOS defines how meaning is constrained.

• AES defines how meaning is persisted.

• SANSA defines how meaning is accessed.

• Meaning validators define how domain rules are interpreted and reported.

• Future mutation consumers define how accepted change intent is authorized, orchestrated, and applied.

SANSA does not require data to originate from AEON. It requires only that a conforming implementation expose a deterministic semantic namespace to consumers.