Govern one AI workflow before its blind spots become incidents.
An instrumentation review and a decision-path assurance report — for one workflow where a silent change to the instrumented path creates real risk. CI gate implementation is separately scoped follow-on.
Defined deliverables
Instrumentation review
A written assessment of the workflow's trace coverage around one agreed failure risk, flagging where instrumented steps are not captured and which steps' disappearance should page someone.
Recommended baseline shape
The report recommends a golden-baseline shape for your workflow. Committing and validating that baseline in your repository is follow-on work unless separately quoted.
Suggested governance policies
Suggested policies (structural divergence, required steps, claim support, allowed models, or others agreed at kickoff) appear as recommendations in the assurance report — not as a live ruleset committed to your CI.
Recommended next gate (report only)
The assurance report recommends a CI gate approach. Implementing the gate in your GitHub Actions or GitLab CI is separately scoped follow-on work — not included in the $4,500 pilot.
Decision-path assurance report
What current evidence establishes, remaining gaps, recommended baseline and policies, and a recommended CI gate approach — written for an auditor or customer conversation.
Two calls
Kickoff and handover, plus written async support throughout, answered within two business days.
What the instrumentation review examines
Workflow evidence
One representative run and one synthetic or redacted failure scenario for the selected workflow.
Trace vocabulary
Whether the current events and priorities make the important execution steps visible.
Evidence gaps
Where the trace is missing, ambiguous, or too weak to support a dependable automated gate.
Next decision
Whether to implement internally, request separately scoped help, gather better evidence, or stop.
Intake before payment
Request
Submit a synthetic or redacted description of one workflow and its failure risk.
Accept
Confirm the written scope, review emphasis, and kickoff timing.
Invoice
An invoice is issued only after both sides accept the scope and timing — 50% on signature, 50% on delivery, net 15. There is no self-serve checkout at this scope.
Kickoff
The 30-day engagement begins on the agreed kickoff date after the first invoice.
Handover
Receive the baseline, the policy ruleset, the CI gate, and the audit and provenance report.
Clear boundaries
It does not include code written or debugged in your repository, a broad application rewrite, hosted infrastructure, a managed dashboard, multiple workflows, on-call or incident support, legal advice, an SLA, indemnity, or compliance certification.
DProvenanceKit evaluates observable, instrumented execution. It does not expose hidden chain-of-thought, guarantee factual correctness, or detect every possible AI failure. Keep secrets and confidential client data out of the public intake.
Bring one workflow and one failure risk.
Submitting the intake starts a fit and scope review. It does not create a contract or payment obligation.
Use synthetic or redacted information in GitHub. Send sensitive requirements through a private channel.