Point
Portable files enable independent processing
Ordinary Markdown and JSON-compatible metadata, public schemas, deterministic rules, and fixtures let another implementation consume Atlas without one runtime.
- Posture
- asserted
- Lifecycle
- active
The interoperable core is a bounded set of ordinary files with explicit schemas, deterministic discovery and resolution, stable vocabularies, and executable examples. An implementation can read those sources without a database, hosted API, hidden index, or dependency on the reference validator.
Portability includes semantics, not only syntax. Another processor must assemble one Point identity, retain every source record, preserve extensions, and derive the same indexes. The independent reader demonstrates that the current contract is implementable separately, while broader ecosystem adoption remains unmeasured.
PortabilityText files, public schemas, and deterministic fixtures are the transport contract independent processors can implement.
Portability is tested through published schemas, exact fixtures, deterministic ordering, and a separate processor rather than file readability alone.
JSON front matter and Markdown bodies make inspection possible, but independent interpretation requires more. The conformance corpus pins safe parsing, resolution, diagnostics, output gating, and normalized provenance so another implementation can demonstrate agreement rather than claim compatibility informally.
Conformance evidenceSchemas, fixtures, ordering rules, and a second reader turn textual portability into observable interoperability evidence.
Normalized modelIndependent comparison targets the full normalized model, not merely whether both tools can parse the files.
The second processor demonstrates that the implementation contract can be rebuilt from schemas and valid data without one shared runtime.
The independent reader uses its own discovery, parsing, assembly, reference, and normalization code. Its agreement with the reference output is stronger evidence of portability than a second command that wraps the same implementation, while its limited invalid-input scope remains explicit.
Independent processingRebuilding the model without validator imports demonstrates that schemas and data, not one runtime, carry the contract.