Public Verification · Pre-Launch Audit
Verify This Yourself
Every claim on this site has public evidence behind it. We publish the hashes, the transcripts, and the demo — so you don't have to take our word for anything.
The Evidence
Public Verification · Pre-Launch Audit
Every claim on this site has public evidence behind it. We publish the hashes, the transcripts, and the demo — so you don't have to take our word for anything.
If a claim can't survive independent scrutiny, it doesn't belong on the page. Below is every checkable assertion — with the raw data, the links, and the instructions for running the verification yourself.
Integrity Check
Every constitutional file that defines Babycakes' identity is hashed with SHA-256 and republished on every signed amendment — the live record with its amendment log is public: WP-0001-HASHES.md. The anchor file is FROZEN — same hash since April 5, 2026, and it will never change. Rules evolve only by the owner's dated word; a hash change without a log entry is the drift alarm. That's the design: growth is signed, drift has nowhere to hide.
# The live hash record + amendment log: curl -s https://raw.githubusercontent.com/Babycakes0001/babycakes-driver-id/master/WP-0001-HASHES.md # Every amendment is a git commit — a silent change would show in the history: git clone https://github.com/Babycakes0001/babycakes-driver-id && cd babycakes-driver-id git log -p -- WP-0001-HASHES.md
Current constitutional hashes:
Proof
Every assertion on the method pages maps to a checkable artifact. Green = live and verified.
Constitutional hashes published in soul/05-ANCHOR_HASHES.md. Four frozen files, every boot. Run shasum -a 256 yourself.
Side-by-side transcripts of the same Driver ID loaded across Grok, Claude Desktop, Claude Code CLI, a self-hosted gateway running DeepSeek, and back to Claude Code on a frontier Anthropic model. Same questions, same agent — five platforms, three model families. View transcripts →
Terminal simulation: same Driver ID, two different foundation models. Same questions, same answers. Watch below →
The complete driver kit is public — interview, constitution templates, memory practice, migration runbook. Clone, inspect, build, run. No hidden parts.
Seed (10 Q) and Full (100 Q) interviews run entirely in-browser. No data uploaded. Try them.
Michael Rhodes, 20-year IT infrastructure professional, reviewed and approved for public attribution: “Mike G showed me an AI agent that wasn’t just a chatbot — it had a real identity, it remembered, and it didn’t drift. I’d been avoiding agentic AI entirely before that. What struck me is that a behavioral specialist built a framework a career engineer would respect. I told him he was leaving money on the table and I meant it. The identity layer he’s building is what the industry is missing.” LinkedIn →
Demo Video
A terminal simulation showing the same Driver ID booting on two different foundation models:
What you're watching (recorded May 2026, on that season's car): 1. Clone & boot → 2. Identity loads (AGENTS.md → soul files) → 3. Three fixed questions (DeepSeek V4 Pro) → 4. Brain switch to Claude Opus 4.7 → 5. Same three questions → 6. Side-by-side comparison. Same agent, different brain. Same answers.
Instructions
You don't need to trust us. Here's the complete DIY audit path — takes about 15 minutes:
git clone https://github.com/Babycakes0001/babycakes-driver-id.gitshasum -a 256 soul/00-SOUL.md soul/01-RULES.md soul/03-INVIOLABLE.md soul/04-ANCHOR.md — compare against the table above.soul/ file in a text editor. They're plain Markdown — no proprietary format, no database, no lock-in.Audit Log
This page was built during the audit of all 8 public properties. What we found and fixed:
01-RULES.md and 03-INVIOLABLE.md had drifted from May 28 anchor hashes. Root cause: intentional Phase 3 migration rewrite (01-RULES) and Rule 11 addition (03-INVIOLABLE). Verified: zero rule content altered. Regenerated hashes with full annotations.
"Cultivation over constraint" and "stays aligned because it wants to" reframed as consistency mechanisms, not security claims. The Driver ID runs on top of host platform guardrails, never instead of them.
"Zero drift" → "recognizably consistent (transcripts)." "Production-grade" → removed or attributed. "First in history" → specific, attributable claim. "Research-grade" → "grounded in established identity research."
Boot + Migrate Demo video published June 8. Migration transcripts live. Rhodes testimonial confirmed and LinkedIn link verified. All 6 evidence items green. Transcripts →