Open Standards
Open Standards
Build software compatible with SensOS using public interface standards, conformance tests, and optional certification.
SensOS is an open interoperability platform with a proprietary reference implementation.
Anyone may build software that speaks SensOS interfaces. Public RFCs define those interfaces. Gemmina Intelligence retains the right to innovate privately on implementation quality, performance, and product experience.
How the ecosystem works
- Read the Charter — why standards are public and what they promise.
- Browse Public RFCs — stable interfaces, behavior, guarantees, and conformance.
- Run conformance tests — prove Compatible behavior against the published suite.
- Seek certification — optional official validation for partners and enterprises.
Who this is for
| Audience | What you get |
|---|---|
| Developers | Stable ABIs and lifecycle contracts without vendor lock-in theater |
| Partners | Clear integration surfaces and conformance gates |
| Enterprises | Audit-friendly standards plus optional Enterprise certification |
| Researchers | Public behavioral contracts suitable for reproducible study |
| Vendors | A level field for compatible products and competing implementations |
Start here
- Open Standards Charter
- Public RFCs
- RFC Namespaces — CORE · HEXT · HEKB · MCP · CAL · SensOS · MM · ITM
- Conformance Program
- Certification
- Documentation Philosophy
- Governance Process
- RFC Classification Policy
Reference surfaces
| Surface | Role | Governing namespace |
|---|---|---|
| Meaning Mapper | Reference service (meaning projection) | RFC-MM |
| semantic-annotator-core | Reference library (normalization RI) | (library; consumed by MM) |
| nvs-runtime | Reference runtime | CORE / NVS public RFCs |
| All implementing repos | Traceability & evidence | RFC-ITM |
Reference implementations clarify intent. Public Standards remain authoritative when they conflict with reference behavior.
Legacy note
RFC-SA001–SA005 are Superseded by RFC-MM001–MM005. Historical RFCs remain archived for traceability.
The boundary that protects the ecosystem
| Public (open) | Not public |
|---|---|
| Interfaces | Internal algorithms |
| Observable behavior | Optimizations |
| Guarantees | Runtime proprietary techniques |
| Conformance | Product internals |
| Compatibility | Trade-secret evaluation methods |
Open standards create a market. Proprietary excellence creates differentiation. SensOS is designed for both.