Every translator we build — for any client, from any source system — is governed by one standing standard. We publish it because a method you can inspect is a method you can hold us to.
Nothing enters the core unless it is a valid SIGNET object. Pinned schema version, applicable profile, validated before write. Validation is not a report that runs afterwards; the write path refuses invalid objects.
Core agents emit SIGNET only. Outbound formatting into a destination system's dialect is translator work, never core work.
No foreign shape crosses the membrane. No source field name appears in any core object, prompt, or tool schema. Fields with no SIGNET home are routed through the extension mechanism or deliberately dropped — with the omission recorded in the mapping specification, where it can be seen and challenged.
A translator recasts; it does not create. No inference, no enrichment, no gap-filling. Ambiguity quarantines with a declared reason code. This is not caution — it is what makes a canonical core canonical. An object you cannot trace is an object you cannot trust, and a translation that guessed is a record that lies politely.
Five gates, in order, every time:
Mapping specification — signed by the data owner before build starts. Deliberate omissions are recorded, not silent.
Golden suite — fixtures in, expected objects out, including negatives that must fail on exactly the declared reason codes. Green in CI before anything ships.
The translator — deployed at the edge and verified in-environment before any downstream agent depends on it.
Reconciliation harness — per-batch balance checks: totals reconcile, counts match source, lifecycle sequences obey the state machine.
Operations handover — replay procedure, quarantine triage, halt and resume. The client operates; we stand behind the build.
Translating agent and version, source reference verbatim, mapping-spec version, timestamp. Auditable by construction.
Completion events per batch; rejection events per quarantined record — reason code and source reference, never the payload.
The write path refuses invalid objects. Validation is enforcement, not reporting.
Re-running a batch produces no duplicates. Any historical window replays. Replays version; nothing is silently overwritten.
Every feed carries a quarantine ceiling. A batch that exceeds it halts and alerts — a systematically broken feed is an incident, not a data-quality statistic.
Every translator declares its mode — translate-on-ingest or streaming. Translate-on-read into the core is prohibited.
The Translator Standard is Score Networks' delivery constitution, maintained by us and applied without exception. Where our mapping work surfaces gaps in the open standard itself, we file extension issues with Concert — implementation pressure is how standards improve.
See the translators built this way →