The review runs today as a written service. These screens show how the case file is designed to work: evidence, review and approval in one place. A designed prototype on sample data. Not a live platform.
Five screens from a TrustChain case file, from intake to the approval gate. This is a preview. The full walkthrough is clickable: open a flagged marker, record a decision, try the locked disclosure button.
A deck or data room is read against what a GCC institutional desk applies. The intake flags an ownership mismatch.
The software behind the service
Evidence, review and approval in one case file.
The review runs today as a written service. The software below is how it is designed to run: eight screens that follow one case from intake to the audit record. It is designed, not built, and every screen uses sample data.
Software: designed, not builtSample data only
The case flow
Eight stages, one case.
The same file moves from overview to record. The layout does not change between stages.
01Overview
02Intake
03Evidence
04Review
05Conflict
06Approval
07Disclosure
08Record
Screen set
Eight screens, one decision each.
All data is sample data. The software is designed, not built.
01 · Case overviewOne screen answers where the case stands, by category, and what needs a person. The verdict is visibly not issued.Design decision: Show a pending verdict, never a score alone.05 · Conflict resolutionTwo sources side by side, a required reason and an audit trail. Nothing is overwritten.Design decision: A person decides, and the reason is recorded.06 · Approval gateFive conditions, three met. The release button is locked and says why.Design decision: AI can flag and propose. Only a named person approves.
See all eight screens
02 · IntakeAnswers are structured fields. A difference from the public record is flagged while the founder is still typing.Design decision: Catch conflicts at intake, not at review.03 · EvidenceEvery document shows what it supports, where it came from and who reviewed it.Design decision: Provenance is a column, not a footnote.04 · Marker reviewOne marker, one state, one source. A reviewer scans eight rows and knows where to look.Design decision: Three states only: verified, waiting, conflict.07 · DisclosureEach recipient sees each section at a set level, and nothing before approval.Design decision: Disclosure is set per section and per recipient.08 · Case recordOne case file with one reference and one audit log. The layout is the same at every stage.Design decision: The product behaves like a case file, not a dashboard.
States
Three marker states, and only three.
Fewer states means a reviewer can scan a case in seconds.
Verified
State
Verified
Evidence meets the stated criteria, with a reviewer and a date.
Waiting
State
Waiting
Evidence is requested or submitted and has not been reviewed.
Conflict
State
Conflict
Two sources disagree. A person resolves it and records the reason.
Human control
AI can flag and propose. Only a named person approves.
The approval gate lists its conditions, shows which are met and stays locked until they are. The release is a decision, and the record shows who made it.
Software may
Flag and propose
Highlight a conflict, suggest a marker state, draft a summary for a reviewer.
A person must
Decide and approve
Resolve a conflict, set a state, release a disclosure.
Start with the service that is live.
The 44-marker readiness review is how TrustChain works today.