ai-labs/explorations
- Path
- explorations/index.md
Explorations
- A Syncbox for Client Document Folders — Where Does History Actually Live? - The ask is one product. The prior art says it’s three layers, and nothing on the shelf does all three on a bucket.
- ChromaDB as Context Improvement Across Everything, Everyone - A founding-team demo reframed Chroma: not a place to put embeddings, but an ingestion layer for agent traces and session transcripts.
- Cloud Variant of the Dididecks-AI Workspace — Recreating Local Privacy When the Filesystem Isn’t Yours - Clients who won’t install a desktop app still need the privacy local-fs gives for free. What a cloud runtime would have to do explicitly.
- Collate Context Files into Context Vigilance as Repo & Project - A long-running, everywhere-distributed practice — context-v/ across a tree of pseudomonorepos — finally graduates into a project of its own, with a collator, a splash, and a vector index.
- Corpus-Grounded Generation — Memory & Graph Layers for Producing Decks and Memos Without Drift - A pipeline where every factual sentence in a deck or memo traces to a source span — and the model abstains when it can’t.
- Cross-Product Native Agent Shell — Synthesis and Architecture Decision - Resolves the fork the in-app-agent docs left open — extend memopop-native or build standalone — against sixteen pinned repos’ actual source.
- didi.sh — One Login, One Agent, Three Services - memos, decks, and augment-it become one family coordinated by exactly two shared planes: a common identity service and one agent named didi. Consumer one is live; the local-auth question is now closed.
- In-App Agent Chat — As-Built vs. As-Specced (Internal Audit) -
@lossless/in-app-agentwas never built — augment-it inlined the WorkspaceAdapter pattern into@augment-it/workspaceinstead. - In-App Chat as the Agent Surface for Client Apps - Rather than design a button for every client request, wire one chat surface loaded with our patterns and context. The chat is the menu.
- Memory Layers for the In-App Chat Package - Maps the eight pinned memory systems onto roles in the chat package, and picks the v1 stack given we already lean on Chroma.
- Remote Mount Contract for @lossless/in-app-agent — How the Chat Surface Drives Federated Views Without Owning State - How the chat surface drives federated views without owning state: capability invocation goes through the per-app workspace, never the chat.
- Secrets for Collaborators Who Will Never Open a Terminal - Collaborators who will never open a terminal still carry API keys — so serve capabilities from a remote MCP plane, secrets held server-side.
- Shared Auth for Applied AI Labs - Three sibling apps need login; none is at Auth0/Clerk scale. A small owned system: OAuth, invites, org-scoped roles, a roll-up seam.
- Two Clients, One Flow — Corpora by Domain-Type, Auth, and Deployment Converge - reach-edu wants corpus→memos by strategy, humain-vc by thesis — and typed domains, shared auth, and deployment all came due at once.
- When Claud Code and When Pi