The Naming Doctrine.

One system. Three layers. Three names.

One name for building. One name for selling. One name for recording.

The caterpillar, the butterfly, the chrysalis.

Three roles in one transformation. Each name does work the others can't.

• The Carrot is the caterpillar. Internal. Agile. Eats everything in front of it. Not for public eyes — too earthy, too playful, too "ours" to leak.
• SDV is the butterfly. Public. Clean. Tells the supplier what they get in one acronym: Same-Day Verified. Three letters. No questions.
• VT Ledger is the chrysalis. The record of transformation. The hash that proves it happened. The bridge between the playful internal and the clean external.

Where each name appears. Where each name does not.

The line between internal and public is a hard line. Cross it the wrong way and the brand leaks.

When building the SDV landing page

• Use SDV as the public name. Headline, subheadline, buttons, form, hero copy.
• Do not put "Carrot" on the public page — except possibly in URL or metadata.
• The VT Ledger appears as a clean compliance band: "SHA-256 Sealed · VT Ledger"

SDV — Same-Day Verified

Supplier Verification. Same-Day. Guaranteed.

SHA-256 Sealed · VT Ledger

Every tonne you send gets a unique cryptographic hash on the
Verification Toll Ledger. You can verify it anytime.
No login. No request. Just the proof.

When talking to Dario or any builder

• Call it "The Carrot" internally. That's the code name.
• The spec document can be named THE_CARROT_SDV_SPEC.md
• The public page is SDV.

When talking to suppliers or clients

• Call it SDV — Same-Day Verified.
• If they ask about the VT Ledger, explain: it's the record of verification. A hash you can check. Proof your material was verified. Proof your meals were funded.
• If they ask about "The Carrot," you can smile and say nothing. Or tell them it's an internal name. Or make up a story. Your choice.

Same water. Different bucket.

The VT Ledger is not a separate system. It is the record of verification.

Every tonne that goes through SDV (The Carrot) is recorded on the VT Ledger. That ledger connects to the wider verification toll system — processing, compliance, extra services. But for the supplier, it stays simple: a hash they can check.

They don't need to see the toll. They don't need to see the processing options. They just need to see the proof.

Where each name is allowed. Where each name is forbidden.

A surface-by-surface map so nothing leaks. If a surface isn't on the list, default to SDV in public, Carrot in private.

Internal stays Carrot. Public face slides to SDV underneath.

Every existing Carrot document (MD-274 / MD-281 / MD-293 / MD-303 / MD-304 / MD-305 in the Three-Anchors trilogy) keeps its internal language. Nothing is renamed in the Library. The public layer migrates only.

Rule. The Library is the vault. The vault keeps every name it ever knew. The public layer wears whichever face is correct for that audience. Both are true at once.

What the outsourced builder needs. Nothing more.

A drop-in spec that respects the naming doctrine. The page itself is not being built here — this is just the ingredients list for whoever builds it.

What is explicitly not in this MD: the SDV landing page itself, the VT Ledger UI, the hash-check endpoint, any database migrations. This MD is naming doctrine + builder brief only. The build is outsourced — or, on day three, sovereign-built.

Two days. One builder. One fallback.

The clock is sealed inside this document because a deadline that nobody writes down is a deadline that nobody keeps.

One-line translations for every audience.

Pin this somewhere visible. When in doubt, read the right line out loud.