didi.sh · one credential, three services

One login to fast-track
DD-ready materials.

The didi.sh services produce diligence-grade material for venture work —memos that cite their sources, decks that hold up in the data room, and augment-it, the research corpus that grounds them both. One didi.sh ID opens all three.

Invite-only while in build — the identity service is live in walking-skeleton form; invites open with increment 3. Follow the build log.

  • 3 services
  • 1 credential
  • 7 ship notes
  • 1 context docs

the services

Three doors. One key.

Each service stands alone — its own repo, its own deploy, its own job. The credential is the only thing they share.

memosactive build

MemoPop AI

Investment-memo platform for VC firms. A Tauri 2 desktop client driving a Python multi-agent backend (LangGraph, 30+ agents) over FastAPI. Memos that cite their sources — diligence-grade by construction.

  • tauri
  • sveltekit
  • langgraph
  • fastapi
decksearly architecture

DidiDecks AI

Code-first slide-deck operating system for receiving-side, due-diligence-grade content. Decks as code: versioned, verifiable, on-brand — with live client engagements carried as private submodules.

  • decks-as-code
  • due-diligence
  • astro
augment-itactive build

Augment It

Web tooling for augmenting data with AI. Module-federated microfrontends — record collection, source curation by strategy or thesis, prompt running — over a canonical entity registry. The research substrate that grounds the memos and the decks.

  • module-federation
  • svelte-5
  • rsbuild
  • surrealdb

the credential

How the didi.sh ID works.

A consumer service ever sees three artifacts. If you can read a datasheet, you know the whole system.

No passwords, ever. No self-serve signup — every holder is invited. Accounts are created from the app you're working in, not on a portal you get bounced through. Spec of record: Id-Didi-Sh-Identity-Service.

the build log

Stamped as it ships.

full changelog →context-v →