Conformance & the One-Way Valve
Standards conformance in Demiton is a property declared at the edges of the system, not a claim about internal storage. This page is the concrete “how it’s enforced” companion to OCDS and OC4IDS.
Conformance is declared per adapter
Section titled “Conformance is declared per adapter”Every adapter that touches procurement or delivery-reporting data declares its own conformance level:
| Adapter kind | Declares |
|---|---|
| Procurement adapters (AusTender, state portals) | ocds-1.1 |
| The snapshot publication path | oc4ids-0.9.5 |
| Native operational adapters (ERP, field ops, payroll) | none |
Nothing in the platform stores OCDS or OC4IDS as its native format. Internal facts keep their own typed structure; conformant output is projected wherever a boundary is crossed - on ingest from a government portal, or on publication out. See OCDS for what that projection looks like on the way in.
The One-Way Valve
Section titled “The One-Way Valve”Your tenant’s operational memory - site diaries, allocations, payroll reconciliations, anything produced by running your own business - never flows to Demiton’s public platform hub as a side effect of being in the system. The only route out is a project snapshot you explicitly choose to publish; the per-project OC4IDS emission that would carry a delivery record to a government client is not built yet.
That’s the One-Way Valve: data can flow from the public hub into your tenant freely (that’s how Market works), but it only flows back out through one deliberate, logged action - never silently, never automatically.
How the valve is enforced
Section titled “How the valve is enforced”There is exactly one way tenant data becomes public: it is published as a project snapshot. Three properties of that path are what make the guarantee hold.
- One writer. A single publication service is the only code in the platform permitted to insert, update, or delete a published snapshot. Nothing else can put a row on the public side, so there is one place to audit rather than a rule every future feature has to remember to obey.
- Validated before it persists. That service projects the snapshot into OC4IDS shape and validates it against the OC4IDS JSON Schema and its codelists before anything is written. A conformance failure is deterministic and non-retryable - the publication does not happen, and there is no silent fallback to publishing something unvalidated.
- Triggered, never ambient. Publication runs as an explicit workflow step. No scheduled sweep, harvest, or background job publishes tenant operational data.
The emission half is not built yet
Section titled “The emission half is not built yet”Snapshot publication exists and is validated; a per-project, consented OC4IDS emission - where you choose to report one project’s delivery data to one government client - does not. The workflow that prepares OC4IDS facts is staging only, and the EmissionConsent model has no production call site, so there is no emission path for a consent check to run on. Treat the consent half of the One-Way Valve as the intended design, not a shipped control.
Reads work the same way in the other direction: the public procurement endpoints serve only the award and contract stages anonymously. Planning and tender data requires an authenticated, entitled session.
Next steps
Section titled “Next steps”Frequently asked questions
- How does Demiton declare standards conformance?
- Every adapter in Demiton declares its own standard_conformance: procurement adapters declare ocds-1.1, the snapshot publication path declares oc4ids-0.9.5, and native operational adapters that don't touch either standard declare none. Conformance is a property of the edge that produced the data, not a claim about how it's stored internally.
- How is the One-Way Valve enforced?
- Tenant data can only reach the public side by being published as a project snapshot, and a single service is the only code in the platform permitted to write that table. It validates the OC4IDS projection against the OC4IDS schema and codelists before anything is persisted, and it runs only when a publish workflow is deliberately triggered. The per-project, consented OC4IDS emission is not built yet, so treat that consent guarantee as the intended design, not a shipped control.
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.