Regulatory Infrastructure,
Not a Compliance Tool.
UCVreg separates operational systems from regulatory liability. It preserves what was declared at issuance — and makes it verifiable years later.
This is how EU market access is protected under enforcement.
The Structural Gap Between ERP and Regulation
Operational systems (ERP, PLM, PIM) manage current production state. When data is corrected, previous values are overwritten.
Regulation does not evaluate the present. It evaluates the historical issuance state.
You may need to prove:
- • What supplier was declared.
- • What material composition was published.
- • What compliance data was attached to a specific batch.
Years after the product left your warehouse.
ERP mutation and regulatory permanence are structurally incompatible.
UCVreg exists to bridge that gap.
Separation of Operational Mutation and Regulatory Truth
In operations, updating data is normal.
In regulation, rewriting history creates exposure.
UCVreg introduces a structural boundary: Only sealed regulatory artifacts cross from operations into public or enforcement domains.
Core Architecture Modules
Snapshot Engine
Captures structured product data at the exact moment of issuance and freezes it into a permanent artifact.
- Generates deterministic cryptographic hash
- Prevents retroactive modification
Versioned Passport Model
Regulatory compliance is not static. Material changes create new regulatory versions. Operational edits do not overwrite published versions.
v1.0 and v2.0 coexist.
Each batch resolves to the correct version.
Cryptographic Anchoring
Each published record produces a SHA-256 hash derived from canonical structured data. Public endpoints re-calculate and verify integrity.
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Append-Only Event Journal
Post-issuance lifecycle events are appended. Nothing is rewritten.
- Repairs, recalls, and inspections logged
- Cryptographically linked to origin snapshot
Multi-Tenant RBAC Enforcement
Role-based access control enforced at the API level. No implicit permissions. No cross-tenant visibility.
From ERP Output to Regulatory Artifact
UCVreg does not replace your ERP. It consumes structured output.
ERP remains operational.
UCVreg handles regulatory permanence.
Built for Regulatory Evolution
EU regulations evolve through Delegated Acts. New product categories enter scope. Schema requirements change.
UCVreg preserves historical records under the rules they were issued. New records follow updated schemas.
Long-Term Regulatory Stability
Products may remain in circulation for over a decade. Compliance records must remain verifiable for the same duration.
ERP migrations, software upgrades, or vendor changes must not erase regulatory truth.
UCVreg is architected for archival durability.
Isolation Without Complexity
- Tenant-level logical isolation.
- Separate encryption keys per tenant.
- Strict API-level access enforcement.
No data leakage across supply chain actors.
Explore Security & IntegrityTenant Boundary
What UCVreg Is Not
Document Storage
We do not build SharePoint. We build verifiable data structures.
An ERP Extension
We separate liability from operations. We do not extend mutable systems.
A PDF Generator
Static files cannot be programmatically verified. We anchor JSON-LD.
Consultancy Workflow
We provide structural enforcement, not project management advice.
UCVreg anchors regulatory state.