A shared language for inspectable intelligence
Rosetta is an open semantic and provenance protocol under active development. It explores how people, models, tools, and institutions can exchange claims while preserving the context needed to interpret and evaluate them.
A document tells you what was written. A provenance record helps you inspect where a claim came from, which transformation produced it, and what evidence or authority was attached. Rosetta aims to make those relationships explicit and interoperable across systems.
What the protocol brings together
- Meaning: structured representations that make distinctions explicit instead of relying on an opaque transcript.
- Provenance: links between sources, claims, transformations, and records of what occurred.
- Memory: source-aware records that can remain useful beyond an individual interaction.
- Governance: explicit boundaries around authority, policy, and consequential action.
A receipt is evidence of a recorded event or relationship. It is not a guarantee that a claim is true, that a source is reliable, or that an implementation satisfies a regulatory obligation.
Why institutions should care
For enterprises and banks, the research addresses traceability across automated workflows and the human decisions that govern them. For governments, it concerns inspectable information exchange and accountable authority. For academia, it provides public representational contracts and research questions that can be tested independently. For investors, the public repository exposes the distinction between the long-term thesis and the engineering evidence available today.
These are intended application areas, not claims of certified compliance, production deployments, or validated commercial outcomes.
Evaluate the foundations
The repository contains working foundations alongside proposed designs. Evaluate individual packages, specifications, and conformance fixtures against your requirements; the research program is not a single finished product.
Inspect Rosetta on GitHub to review the current implementation, contribute a reproducible issue, or propose an interoperability evaluation.