TCD TCD Proof View receipt

CLC 12 Capstone / visual story

Make AI less invisible.

AI gives an answer. TCD leaves a small receipt.

Before Can I build it?
Middle Can it be checked?
Now Can people see it?
01 Ask
02 Task
?
03 Answer
04 Result
TCD
✓

Map

From answer to trace.

The website shows one simple idea: an AI step should not disappear after it happens.

01
Request
Hidden middle
02
Result
03
Receipt
✓
Check later
No raw prompt No raw answer Small record Saved reference Checked later

Receipt

The receipt, split into simple pieces.

Instead of showing one huge JSON file, I broke the receipt into layers a non-technical viewer can understand.

Profile

This was a local proof run.

    Not a transcript

    Not everything.

    It does not save the full conversation.
    Not a screenshot

    Not just a picture.

    It creates structured information that can be checked.
    Small record

    A trace.

    Enough to look back at one selected AI step.
    Capstone lesson

    Visible.

    I learned to turn code into something other people can see.

    Path

    The demo became a small story.

    The receipt summary is not just a code file. It shows a path: run, save, verify, restart, verify again.

    01

    Run

    POST /diagnose
    02

    Record

    receipt_issued
    03

    Save

    durable_committed
    04

    Check

    POST /verify
    05

    Restart

    after_restart
    06

    Pass

    all_checks_pass

    Checks

    What the receipt demo proved.

    I translated technical pass/fail fields into a simple checklist.

    ✓
    Receipts on runtime_receipts
    ✓
    Public view receipt_public
    ✓
    Signature signature_verified
    ✓
    Rule linked policy_bound
    ✓
    Saved evidence_durable
    ✓
    Lookup works receipt_ref
    ✓
    By ref verify_by_ref
    ✓
    By bundle verify_bundle
    ✓
    Storage storage_window
    ✓
    After restart restart_safe
    ×
    No raw prompt not included
    ×
    No raw answer not included
    ×
    No secrets not public
    ×
    No private DB not public
    ✓
    All pass all_checks_pass

    Boundary

    Clear project boundary.

    I learned that a serious project should also say what it does not show.

    Shown

    • ✓ Redacted receipt summary
    • ✓ Verification result
    • ✓ Durable save status
    • ✓ Restart-safe lookup
    • ✓ Simple visual explanation

    Not shown

    • × Private runtime source code
    • × Signing secrets
    • × Raw prompts or answers
    • × Private SQLite database
    • × Unredacted local logs

    Learned

    Code became a story.

    My Capstone is not only about making a system work. It is about making a hidden process understandable.

    Build

    make it real

    Test

    check the edges

    Reduce

    remove noise

    Explain

    make it clear

    Final reflection

    A good project should be visible.

    I learned that building is only one part. The next part is making the process clear enough for someone else to understand, question, and trust.

    Public GitHub → Receipt sample Contact