Publishing workflow
Publishing is the controlled path a governed dataset walks to become a certified product: ownership confirmed, contract declared, evidence in place, approval recorded. Certification at the end is derived from what the checks show, so a certified badge means the checks actually pass. Consumers see the honest state, including when a product is not there yet.
A staged path runs from governed dataset to certified product, through draft, evidence, approval, and certification, with each gate checked against live evidence.
Missing evidence blocks progression, so a product cannot certify around a gap.
Maker-checker applies to the publication decision, with both the proposal and the approval sealed on the ledger.
Agents assemble the draft, including metadata, a proposed contract, and the evidence pack, and a human makes every call that changes state.
Certification stays derived after publication: when checks degrade, status downgrades on its own and an issue opens.
Failed checks close only through verified closure. The evidence has to pass again, and nobody hand-closes the issue.
Draft
The owner selects governed datasets, names the product, and declares its contract, and agents can prepare most of it for review.
Evidence
Required checks run: lineage resolves, quality gates pass, and ownership and attestations are current. A check that cannot run blocks the stage.
Approve
A reviewer sees the assembled evidence pack and approves or sends it back under maker-checker.
Certify
The product goes live in the registry with a status that keeps tracking the evidence.
“How did this product get certified, and who signed off?”
The full path is on the ledger: the proposal, the evidence pack the reviewer saw, and the maker-checker approval. Certification itself is derived from the checks, so the badge reflects evidence, not assertion.
“Can someone publish a product without the evidence behind it?”
No. Missing evidence blocks progression, and a check that cannot run blocks the stage. A product cannot certify around a gap.
“What happens when a certified product's checks start failing?”
Status downgrades on its own and an issue opens for the owner. The issue closes only through verified closure, meaning the evidence has to pass again, so consumers always see the honest state.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.