How Aeonite operates
Aeonite is a neutral publication space for specifications and test suites related to meaning-aware data interchange.
What is Aeonite?
Aeonite exists to publish specifications, publish conformance test suites, and preserve those artifacts long-term. It does not operate products, services, or tooling.
Who runs Aeonite?
Aeonite is operated under a custodial editorial model. There is no membership, voting body, steering committee, or foundation governance.
Specifications are maintained by an editor acting as a steward of clarity and consistency, not as an authority over implementations.
Does Aeonite have members or a community?
No. Aeonite does not:
- have members, collect dues, or grant representation,
- run forums, Slack, Discord, or mailing lists,
- operate as a community organisation.
How are decisions made?
Decisions take only one form: publishing artifacts.
- publishing specifications,
- publishing test suites,
- publishing clarifications,
- publishing new versions.
There are no votes, approvals, or endorsements.
How does Aeonite handle feedback?
Draft specifications may be published for review. Feedback is used to:
- identify ambiguity,
- identify contradictions,
- improve clarity,
- improve test coverage.
Feedback does not create obligations, imply consensus, grant influence, or determine direction. Once a specification is published as final, feedback does not modify that version.
How is ambiguity resolved?
If a specification allows multiple interpretations, Aeonite resolves ambiguity by:
- clarifying the specification text,
- adding or updating test cases,
- publishing the clarification as a versioned update.
Ambiguity is resolved through artifacts, not discussion or consensus.
What defines conformance?
Conformance is test-defined.
- If an implementation passes the relevant test suite, it conforms.
- If it does not pass, it does not conform.
There is no certification process, approval authority, or exception handling.
Conformance is binary and version-scoped.
Does Aeonite certify or endorse implementations?
No. Aeonite does not certify implementations, endorse tools, recommend vendors, or maintain implementation registries. Implementations are independent and replaceable.
Can anyone implement Aeonite specifications?
Yes. Aeonite specifications and test suites are published under permissive, irrevocable licenses. No permission, registration, or agreement is required to implement them.
How are versions handled?
Aeonite versions are permanent.
- Once published as final, a version does not change.
- Its test suite does not change.
- Its conformance rules do not change.
- New versions may be published alongside old ones.
Older versions remain valid indefinitely.
Roadmap and capture resistance
Aeonite does not publish roadmaps, timelines, or future commitments. Specifications are published when they are ready.
Aeonite is intentionally structured to resist capture: there is no central authority to seize, no registry to control, and no certification power to acquire.
Summary
Aeonite operates by publishing immutable artifacts. It defines conformance mechanically, not politically. It has no members, no certifications, and no authority beyond its specifications and tests.