Agree what done means
Set scope, acceptance criteria, and authority before assessing the work.
Vinci Verifications
“Done” should come with something you can check.
Why we built it
We needed more than an agent saying it was finished.
Vinci Verifications is a series of repositories and tools we use to verify our own work, especially AI-generated work. We built it around a simple need: a completion claim should be something the team can examine, not just accept.
What it brings together
Ask for the evidence
Connect checks and their results to the artifact they actually cover.
Leave room for uncertainty
Keep untested conditions and unresolved findings visible.
What we share
A selected view of our internal work. Additional capabilities and details remain private until they meet our safety and internal review standards. Public availability is described on each page.
Scope and limitations
A technology family with selected public source components. Record validation is one part of checking work; it does not independently prove correctness or enforcement. Vinci Verifications is not a certification service.
Public implementation
Accountability expressed in software.
Vinci Contracts publishes types and validators for defining AI work, recording evidence, preserving approval boundaries, and expressing the scope of an assessment.
A bounded documentation task
Illustrative example using invented, non-sensitive details. This explains the records; it is not an executed worker run or a schema-valid payload.
Task
Correct two broken links in a sample README. Acceptance: both links resolve and the surrounding instructions stay unchanged.
Authority and owner
The maintainer allows a documentation edit and link checks. Publishing or merging requires the maintainer’s separate approval.
Artifact
A proposed README patch, identified by the digest of the exact revision being assessed.
Evidence
Attach the link-check output and the reviewed diff to the acceptance criteria. Record who produced each item and how it was checked.
Scoped verdict
An assessment could cover the two links at that revision. It would not establish application correctness, deployment readiness, or checks on future revisions.
These are Vinci implementations, not an adopted standard or certification. Schema validation alone does not establish enforcement by a consuming application.
The repository is public; no licence is declared in the reviewed repository metadata. Inspect the source and clarify reuse terms before adoption.
Start with the resources.
Explore our public models, technology pages, and documentation. If you have further questions or want to work with us, our contact details are there too.