Proof Ledger Markdown
Each important claim can be recorded in a Markdown ledger with its status, evidence and review.
← Back to BIMCheck Lab
Open source · v3.0.0Public GitHub project
WinCreator — Proof-gated engineering for AI agents
AI agents that must prove what they claim to have completed.
WinCreator turns an important technical claim into a ledger entry, an executed command, captured evidence and a separate review. The goal is to reduce optimistic self-validation, context loss and unproductive correction loops.
proof-ledger.mdcapture #014
CLAIM-014The check was executed.
- 01Claimrecorded in the ledger
- 02Commandexecuted and captured
- 03Attestationlinked to the claim
- 04Reviewseparate verdict
The method
A technical claim is not evidence yet.
WinCreator makes the transition visible between what is claimed, what was actually executed, what was captured and what was reviewed.
Separate capture and review
Commands and outputs are captured; the Builder role is separated from the Reviewer role at levels that require it.
Risk-adapted levels
Lite, Standard and Regulated organise the expected level of control according to the work context.
Verified characteristics
What the public repository documents.
The points below are presented without extending the project's actual documented scope.
- Open-source project under the MIT licence, public version 3.0.0.
- Markdown Proof Ledger, installable package and Python 3.10 to 3.13 compatibility.
- Command and output captures linked to claims through attestations.
- Builder / Reviewer separation for Standard and Regulated reviews.
- Redaction controls, output limits and private captures to reduce exposure of sensitive data.
- Documented tests on Ubuntu, Windows and macOS; Skill Creator and Agent Skills validations.
Important limitation
A verifiable trace is not a certification.
WinCreator does not make AI infallible, replace human review, automatically certify a result or guarantee regulatory compliance. It structures the elements needed to examine the work.
HMAC can help a key holder detect a modification. It is neither a public signature nor an independent transparency log; the key holder should not be confused with a trusted third party.
The BIM connection
Two controls, one principle: a claim is not evidence.
In an IFC audit, BIMCheck verifies model data: object class, property, classification, unit or deliverable. In WinCreator, the control applies to evidence associated with technical and agent work. The verified objects differ; the traceability requirement is the same.
See the IFC audit method