🐒 Building in public

Turtle Lab

The public edge of TurtleBlock AI: build notes, learner-approved projects, WorldSpec artifacts, experiments, reflections, and things we learned by making them.

Private conversation, public artifact

A Turtle conversation is private by default. Turtle Lab is not a raw Discord feed. A learner chooses what becomes public: a project title, a WorldSpec snapshot, selected build outputs, selected dialogue, and reflection.

private dialogue β†’ persistent WorldSpec β†’ learner chooses what to publish β†’ curated Turtle Lab artifact

Field-test sparks

Before public learner publishing is switched on, these are curated examples from the project author's own Turtle tests. They show the kind of meaning Turtle needs to preserve instead of collapsing everything into a few keywords.

What will appear here later

Discord Turtle Lab

The preferred experience is for /turtle idea:... to start a persistent Turtle Lab session and, next, a dedicated Discord thread. The learner should then talk normally with Turtle while the same WorldSpec evolves underneath the conversation.

Persistent WorldSpecs

Each session receives a session ID and WorldSpec ID. Turns and WorldSpec revisions are stored separately so the learner's original language, Turtle's interpretations, and subsequent revisions remain distinguishable.

LLM conversation + RAG + security

Turtle's conversational layer uses the Turtle Charter as trusted instruction while learner language, retrieved material, Discord history, Minecraft text, and prior model output remain untrusted project data.

learner turn β†’ retrieve bounded context β†’ Turtle Charter β†’ LLM dialogue β†’ WorldSpec delta β†’ deterministic validation β†’ persist revision β†’ reply
Next implementation target

Activate D1 Turtle Lab persistence in production, then add Discord thread continuation so ordinary messages revise the same WorldSpec. After that, wire the opt-in publication projection that feeds this gallery.