v0.11.0 — Working Draft

@
Working Draft release.

Added

• Extension conformance rules — executable cross-object checkers for onboarding, auction, and identity extensions, wired into CI. All four shipped extensions now have machine-backed conformance. Governance: commodity-risk resubmission merge record.
• Five P2P/SRM extension specs (Working Drafts, spec-first) — receipt & governed three-way match; supplier performance; contract amendments; framework agreements & call-offs; negotiation under per-term mandates. Schemas and conformance rules follow per-extension after review.

Full changelog: CHANGELOG.md.
@

v0.8.0 — Auction extension

Added — Auction extension

Process-layer objects Auction (a profile of the sourcing flow; reverse / english / dutch / sealed-bid / multi-criteria via auctionType + deterministic rules) and Bid.

The auction rules and canonical bid record are normative and operator-independent — any conformant operator closing the same bids under the same rules MUST reach the same Award. The close reuses Decision/Award; eligibility ties to SupplierQualification; the bid history is a hash-chained Event trail. Open auctionType codelist; reverse-auction worked example. Modelled on Prozorro's neutral-core architecture: price formation in the standard, UX in the operators.

Includes auction/ demo (deterministic bidding agents + auctioneer, runner, conformance-verified).

v0.4.0 — Conformance harness

[0.4.0] — 2026-06 — Working Draft

Added

• Conformance harness (conformance/) — the machine-runnable suite behind the
  "SIGNET Certified" mark. Implements CDM §13 and the certification neutrality
  rules CN-1…CN-4.
  • levels.md — Core vs Full levels; requirements C-DOC, C-EVT, C-PROV (Core)
    and F-MAP, F-SEM (Full); CN neutrality rules.
  • certification.md — the identical-for-all certification process.
  • runner/run-conformance.js — runs the suite against any implementation via a
    small adapter, emits a machine-readable report, computes the level achieved.
  • adapter/reference-adapter.js — a complete conformant implementation (reaches
    Full); adapter/broken-adapter.js — deliberately non-conformant, failed
    by the harness at C-EVT and F-MAP, proving the suite discriminates.
  • Positive + negative document fixtures (invalid documents that MUST be rejected).
  • report-schema.json — schema every conformance report conforms to (CN-4).
• CI now runs the harness on every commit: the reference implementation must reach
  Core+, and the broken implementation must be rejected.

Changed

• tools/signet-to-ubl.js refactored to export a pure toUBL(invoice) function
  (shared by the CLI, the harness, and the website); CLI output unchanged.

v0.3.0 — Complete process layer + Peppol BIS Billing bridge

Working draft expanding SIGNET to the full procurement lifecycle and proving EN 16931 / Peppol BIS Billing convertibility. Stewarded by Concert Foundation. Licensed CC0 1.0.

v0.2.0 — complete process layer

• JSON Schema for Need, Evaluation, Award, Contract, Order, Catalogue, Obligation, Invoice (OCDS-aligned lifecycle)
• EN 16931 building blocks (Unit, InvoiceLine, VatBreakdown) with Business-Term mappings
• EN 16931-mapped Invoice carrying 33 Business Terms/Groups — basis for the EU ViDA cross-border e-invoicing claim
• BT-mapping annotations preserved under Draft-07 via allOf-wrapped $ref
• New worked examples: need, contract, invoice (€6,200 net + €1,302 VAT @ 21% = €7,502 payable)

v0.3.0 — provable Peppol BIS Billing convertibility

• tools/signet-to-ubl.js — dependency-free SIGNET Invoice → UBL 2.1 (Peppol BIS Billing 3.0 / EN 16931) reference transform
• tools/verify-ubl.py — reconciles every key Business Term and the monetary totals; exits non-zero on mismatch
• examples/invoice.ubl.xml — committed projection output
• CI runs the transform + verification on every push — "convertible to Peppol BIS" is continuously proven, not asserted

Notes

• This is a faithful reference projection, not a substitute for official Peppol XSD + Schematron validation.
• Still targets JSON Schema Draft-07; a move to 2020-12 will be considered before v1.0.

Full changelog: CHANGELOG.md

v0.2.0 — Complete process layer

Working draft completing the SIGNET procurement lifecycle. Stewarded by Concert Foundation. Licensed CC0 1.0.

Added

• Complete process layer — JSON Schema for the remaining OCDS-aligned lifecycle objects: Need, Evaluation, Award, Contract, Order, Catalogue, Obligation, Invoice.
• EN 16931 building blocks in the foundation definitions: Unit, InvoiceLine, VatBreakdown, with field-level Business-Term mappings.
• EN 16931-mapped Invoice carrying 33 Business Terms/Groups (BT-1…BT-158, BG-4/7/23/25) — the structural basis for the EU ViDA cross-border e-invoicing claim.
• New worked examples: need.json, contract.json, invoice.json (arithmetically consistent: €6,200 net + €1,302 VAT @ 21% = €7,502 payable), all CI-validated.

Fixed

• BT-mapping annotations on $ref fields are preserved under Draft-07 by wrapping the reference in allOf (Draft-07 ignores keywords beside a bare $ref).

Note: v0.2.0 and v0.3.0 were published together; this tag marks the process-layer milestone. v0.3.0 adds the proven Peppol BIS Billing transform on top.

v0.1.0 — Working Draft (Request for Comments)

First public working draft of the SIGNET Canonical Data Model — the open standard for governed procurement networks, stewarded by Concert Foundation. Licensed CC0 1.0.

This is a draft published for community review. Field-level definitions illustrate the model's shape and are not yet frozen.

What's in v0.1.0

• Foundation layer: Identifier, Party, Value, Period, Classification, Item, Credential, Document, Provenance, Score
• Process layer (initial): SourcingEvent, Submission, Policy
• Agent layer: SyntheticAgent, Mandate, Decision — synthetic agents as first-class, governed, accountable participants
• Trust layer: Event, Consent
• JSON-LD @context aligning to ePO, PROV, and W3C VC
• Closed and open codelists (CSV), worked examples, and CI validation

Notes

• The JSON Schema is the source of truth. Where prose and schema disagree, the schema wins.
• Targets JSON Schema Draft-07 for tooling compatibility; a move to 2020-12 will be considered before v1.0.
• Profiles and bridges to OCDS, EN 16931, UBL/Peppol BIS, W3C VC/DID, and the EU eProcurement Ontology.

Feedback welcome via issues and discussions. See CONTRIBUTING.