ai-labs/issues
- Path
- issues/index.md
Issues
- Client work is split across decks, memos, portals, and storage, and each new client deepens the split - One client’s confidential work can now live in four places: a dididecks client-site repo, a memopop io/
repo, a client-portal config, and a Railway bucket. These will need to converge. For now the job is to stop each new client from making that harder. - The Drag in AI-Assisted Web Research — Diagnosis, Prior Art, and the Open Forks for a Source Curation Gate - AI research yields enough hallucinated sources that manual Google + Docs looks time-competitive. The drag is structural, not a prompt bug.
- Splash rollup:sync fails from where the operator actually stands -
pnpm rollup:syncerrored at the ai-labs root (no such script) and inside splash/ (pnpm 12 ignored the build allowlist). Both fixed. - State-Inspector as a universal need — every ai-labs app hides its state from the people running it - No ai-labs app can answer “what does it currently believe?” — rune singletons, deck state, LangGraph FlowState, none inspectable.