[TRUST AND TRACEABILITY]
Traceability built into your work with CODICE.
We explain in plain language what is recorded in the platform, how to read a receipt reference and what the future LutinX integration will add.
What is recorded
- Confirmed agreements and orders
- Agreed project changes
- Deliverable approvals, version by version
- Invoices and verified payments
- Partner attributions (when part of your mandate)
How to read a receipt
A hash links a precise document version, a reference identifies the receipt and the server records the registration date. Future blockchain anchoring will add an external proof to this information.
The reference alone does not prove content authenticity and is not a legally certain date: it identifies an internal record you can compare over time.
Available now
- Internal recording of key operations
- Digital fingerprint (hash) of each confirmed version
- Unique receipt reference and registration date
- Version and decision history for your project
- Authorised document downloads
Next integration
- LutinX ID for verified identity
- Person/company verification (KYC)
- LutinX blockchain anchoring with external proof
Clearly planned: no “active KYC” or “active blockchain” badge is shown until the integration is real.
What you can see depends on your mandate: clients and Partners review only the versions and decisions that concern them, via their workspace or an authorised sharing link.
Frequently asked questions
Does the reference prove the content is true?
No. The reference identifies the record; the digital fingerprint lets you compare one version against another, it does not certify authenticity.
Is this already blockchain?
The status depends on the individual receipt. Today recording happens in CODICE’s internal ledger; LutinX anchoring is a future, separate integration.
Are documents public?
No. Access is reserved to authorised subjects. The future network will receive minimised digests according to the integration, not automatically published documents.
Can I verify a record?
Yes: through your CODICE workspace or an authorised sharing link showing the version, fingerprint and status of the record.
Traceability built into your work with CODICE.
Talk to CODICE