Init dididecks-ai

DidiDecks is now its own repo. Until today it was a folder full of specs at ai-labs/context-v/specs/ plus two client engagements (calmstorm-decks, reach-edu-hub) sitting under astro-knots/sites/ for historical reasons. Today it is a proper child of the ai-labs/ pseudomonorepo, with the narrative parent matching the git parent.

What landed

• New GitHub repo at lossless-group/dididecks-ai, three branches at parity (development, main, master), default branch development.

• context-v/ carrying the three Dididecks specs and the business-model exploration, with relative wikilinks rewritten for the new nesting depth and for the calmstorm-decks move.

• changelog/ with this first entry.

• splash/ scaffolded as an Astro Knots site — hero leads with the Due-Diligence framing, surfaces the two North Stars, the seven Design Principles, the system map, and the sibling-spec gallery. Builds and renders locally.

• client-sites/calmstorm-decks/ and client-sites/reach-edu-hub/ — re-attached as submodules here, removed from astro-knots/sites/. Site repos themselves untouched on GitHub; only the parent reference changed. Vercel deploys remain wired to each site's own repo and are unaffected.

• ai-labs/ now tracks dididecks-ai as a proper submodule with branch = development in .gitmodules.

Why

The Lossless pseudomonorepos discipline: the parent owns the space between children; each child gets its own three-tier branches, its own context-v/, its own changelog/, and a splash page rolled up by the parent. Today's work moves DidiDecks from "specs in a folder" to that shape.

Next

• Wire ai-labs/splash/ (when it exists) to roll up dididecks-ai/changelog/ and dididecks-ai/context-v/ via the sync-on-demand pattern.

• Write the first DidiDecks implementation prompt under context-v/prompts/.

• Decide on submodule discipline for calmstorm-decks's development branch vs. main for reach-edu-hub (the latter only has main today).