Kinds / Canonical
plans/
Sequenced, scoped work plans: closer to execution than a spec, not yet step by step.
125 files · 22 projects
augment-itai-labs41
Build Selector and close the keyboard contract
Nine surfaces declare a keyboard widget. Zero implement one. This is the first component whose whole substance is behaviour, so it is the first one with real tests.
Give the services a shared tsconfig base — fold ten byte-identical service configs onto a new `tsconfig.services.json`, reconcile `decile-mcp`'s real delta, fold two duplicated package configs onto the existing `tsconfig.base.json`, and correct the root fallback's stale exclude list
Ten service tsconfigs are byte-identical and extend nothing. The fix already exists one directory away — `tsconfig.base.json` did this for the apps and works.
Prove the component API end-to-end on request-reviewer — ship the scales, build Button, migrate one member, and verify by measurement
If this loop closes once it closes eighteen more times. One member, nine buttons, and a measurable accessibility delta.
Tidy every consumer onto the shared primitives
Button is done across nineteen units. This sequences what is left: Chip everywhere, the stale annotations, and the three containment jobs that are not component work at all.
Component-Level Documentation Contracts — Giving All Forty Units Their Own Four Firsts
Forty deployable units, fourteen READMEs, zero DESIGN.md files. The contract set each kind of unit owes, and the order to pay it down in.
Graphify as Standing Practice and Per-Component Diagrams — Visual Engineering That Doesn't Go Stale
The graph ran once, on 2026-08-06, and still names an app that was renamed two days later. Turning a snapshot into an instrument, and giving each unit its own picture.
Pickup notes — 2026-09-12: the watchdog got fixed, and so did the bug it was never going to catch
A "Twenty is broken" report that wasn't, a production bug that only appears on a dead socket, and three days of infrastructure that lives outside git.
Stale Corpus Sources When the Workspace Socket Is Down — the header moves, the list doesn't
Switching corpora on a dead socket silently shows another corpus's sources under the new name — a wrong answer wearing a confident label.
Back Up the Content-Ingest Corpus Volume — the corpus has no second copy
Every fetch writes to a single Railway volume that nothing backs up, nothing mirrors, and only one process can even read.
Fix Env Aliasing That Drops PUBLIC_ Vars in the Developers Menu
Assigning import.meta.env to a variable defeats rsbuild's static replacement, so two production URLs quietly resolve to localhost.
Re-Mint the Deploy-Watch Railway Token — the watchdog has been blind for days
The watchdog built so a failed deploy would not go unnoticed for twelve days has never once run green itself.
Test coverage — pick the harness, seed the suite from the prove-scripts, and loop the open bugs to green
Vitest + Playwright for this repo, ExUnit already standing in id-didi-sh — convert the six prove-scripts into a permanent suite, then write the humain-vc corpora bugs as failing tests and iterate until they pass.
Open augment.didi.sh to reach-edu — a second tenant instance, and Stephenie Tesoro as the first client user
The data is already deployed; only the door is single-tenant. Open it with a per-client instance, not a relaxed org check.
CRM Starter Export — the pipeline shape, enriched from the canonical layer: orgs first, then people attached
Two CSVs seed the empty CRM from the canonical layer: organizations first, people second, attached by a stable key. Corpora excluded.
Org Relations (parent/child/peer) + Org Tags — model, capabilities, and the Org Workbench surface
Organizations finally get edges to each other — parent, child, or peer, with a typed flavor and free-text human context — plus their first tag mechanism (Initiative, Program, Funder), all workable from the Org Workbench card.
Didi crawl — three targets (links, streams, team members), the relevance brief, and staged team ingest
One `organization.crawl` capability over Anthropic's server-side web_search, driven by a per-workspace, operator-editable relevance brief.
Workbench usability sweep — corpus visibility, stream editing, and promote-to-affiliation (issues #20 · #26 · #25)
Today's scope from the first real workbench session: make the person card's three invisible corpus items visible, let the operator fix a stream's kind and give it its real name, and turn a bio-page link row into a three-click affiliation.
Workspace-scope legibility — empty workspaces and stale org restores should explain themselves, not look broken
Switching to a workspace with 0 orgs made the workbench look dead — the visibility rules were right, only the messaging failed.
Augment from DB · Phase 1 — service capabilities + Exa, no UI
Four service-side deliverables that make the whole flow provable from a script before any remote exists: org detail + org affiliations reads, a registry-resolved search.fire, and Exa as a peer connector.
Augment from DB · Phase 2 — the org-workbench remote: flow registration, org search, org card
Autocomplete to a canonical org and work its card with a live ➕ on every list — plus the verb the spec missed, `organization.streams.add`.
Augment from DB · Phase 3 — the search-and-add remote: editable term, provider palette, one-click add
Launched from any 🔍 on the org card: an always-editable term bar, a provider palette, one-click add back to the launching list.
Augment from DB · Phase 4 — people reveal, person cards, add-person with automatic affiliation
The org card grows its people: every affiliated person revealed with role + relevance, nested identity links with their own ➕ and 🔍, and an inline add-person where the affiliation edge materializes without the operator ever managing it.
Augment from DB · Phase 5 — stream-scan mode: scan a pulse stream, badge the already-known, one-click the new into the corpus
Stream scan is a mode of search-and-add, not a third remote: the stream URL is the authoritative index, deduped against `content_items`.
Plan stub: ingest the next reach-edu event CSV into the canonical layer
The mechanism already exists and is proven twice over (turning-jobs, FreedomFest) — this is the sequence to run the moment the next event CSV lands, so it's 'follow the stub' instead of 're-derive the pipeline.'
Pickup notes — 2026-07-13: deploy hardening, doc audits, credential hygiene
Steps 1–10 are live at augment.didi.sh; this session cleared the production-only bugs that only using the deployed app surfaced.
Build order: the humain-vc unlock flow, step by step
The execution sequence for Flow 1 — each step names its repo, files, and verification, so a fresh session can pick up mid-sequence.
Person-aware canonical resolver — closing the gap between the proven scripts and the shell-reachable capability
The resolver only knows organizations; every person and affiliation ever written came from CLI scripts no UI can reach.
SurrealDB MCP + a verification skill — querying augment-it's canonical layer directly, starting with FreedomFest 2026
Migrate off the deprecated `nats` package to the `@nats-io/*` scoped v3 client — swap `nats@2` for `@nats-io/transport-node@3` across all 10 services, drop the removed `JSONCodec` in favor of `JSON.stringify` + `msg.json()`, and prove the inter-service bus still round-trips live before committing
`nats` → `@nats-io/transport-node` v3 across 27 files: mechanical, except the removed `JSONCodec` rewrites every encode and decode.
First-Pass Corpus Quality Scan for reach-edu — a measured before/after baseline of the RAG corpus
A read-only baseline of 517 markdown files across 57 funder dirs, taken before RAG is wired, so 'after' has a 'before' to compare to.
Canonical Entity Registry on SurrealDB Cloud — just write records
SurrealDB Cloud is up at main/main with three SCHEMALESS tables (persons, organizations, affiliations). Goal: write records from tonight's CSV+JSONL into those tables. SCHEMALESS stays. No field discipline up front.
Augmentation-state preservation and snapshot promotion — the operator's CSV is the system of record, the filesystem is the truth, and `/promote-snapshot` is the verb that walks the corpus and emits the next CSV with system columns appended so flow-switches don't erase the prior cycle's work
One verb: `/promote-snapshot` joins the corpus filesystem into a fresh CSV version with system columns. No register, no write-hooks.
Download PDFs into Corpus Inbox — preserve the original binary alongside Jina-extracted markdown; wire both inbox vectors (UI and agent-chat) so the operator's PDF discoveries land as commit-able evidence, not just summarized text
Jina gives the inbox text and throws the PDF away — nothing to cite by page or hand to a co-researcher. Save the binary alongside it.
URL Auto-Detector and Clickable Rendering for List Fields — make socials, helpful_links, and official_updates_index_urls open-in-tab links instead of opaque JSON
`socials` and its list-shaped siblings render as 12px JSON; a shape-detecting extractor makes every URL clickable and drops the clutter.
In-App Chat v0.0.1 for Augment-It — The Prompt-Drafting Triad as the Demo Affordance
Gated enhancement made conversational: `prompts.draft` → `improve` → `apply`, with postconditions that check what the prompt promised.
Shell & Micro-Frontend UX Coherence — Refactor Plan
Eight locked UX decisions sequenced into five phases — the Deck→Flow rename first, so every later phase speaks the right vocabulary.
Augment-It Workspace — Walking Skeleton Plan
Browser ↔ Workspace Service over WebSocket, Workspace Service ↔ row-store over NATS, and two real spreadsheets as the proof-of-life payload.
Impose the Three-Mode Theme System on augment-it
The two-tier tokens and light/dark/vibrant contract adapted to a federated, Tailwind-less app: one shared `packages/theme`, no raw hex.
Prompt-Template-Manager — Walking Skeleton Plan
Author `{{column}}` templates and run them per row — `prompt-runner` is the only container that calls the Anthropic API.
Run-as-First-Class-Operation — Pair Pack-Runner with Prompt-Template-Manager, Make Runs Legible Across the Pipeline
Lift `Run` from a string id buried on each response into a real entity, so any surface can see which batch produced what it's showing.
augment-it/plans
ai-labs15
corpora-builder on didi.sh Entities — signup, login, and who sees which corpus
The tenancy primitive is already built and it's flat. corpora-builder should inherit it, not invent a second one.
didi.sh Login and Workspace-Delivered Config — the plan across three repos
corpora-builder should get its config — R2 credentials included — from the didi.sh workspace, not a local `.env`.
Sync Corpora to R2, and Show Clients What Changed
The R2 prefix has held zero objects for fourteen days — and the corpus grew anyway, in git. Mirror first, version later.
Study Agent Harnesses + Conversational UI, Then Decide the Cross-Product Native Shell
Pin two studies and audit in-house prior art before designing a Tauri shell that swaps context across three apps. No code lands here.
SurrealDB MCP + a verification skill — querying augment-it's canonical layer directly, starting with FreedomFest 2026
Unlock: the humain-vc team (two people) logs into a deployed augment-it
One flow: a humain-vc member signs in with her work email, lands in her workspace, works the thesis corpus. Single-tenant deploy on purpose.
In-App Agent Chat — Walking Skeleton Plan
One session's work: scaffold the package, do the Chroma tenant migration, and ship `slide.read` end-to-end as proof the abstractions hold.
Agent Capabilities — Hooking the Chat Surface into Memopop
How the In-App Agent Chat pattern maps onto memopop-ai: where each layer lands in the repo, and the smallest read-only proof-of-life.
The Anatomy of the In-App Agent Shell — Shell, Workspace, Window, Chat
"Shell" meant four things at once: layout frame, workspace package, Window, chat. The workspace is the source of truth — not the chat.
Per-App Workspaces and the Chat as Optional Surface — The Architecture We Walked To
State of truth lives per app in `@<app>/workspace`. The chat package is UI-only, reaching it through a typed WorkspaceAdapter.
Add a Chroma Local UI Interface
Local Chroma in PersistentClient mode is an embedded SQLite library with no UI of its own. Three paths to a browseable surface — from a 30-line inspect script tonight to a /chroma route in the splash later — laid out in increasing commitment.
Context Vigilance Splash Page — Narrative Brief
Designer brief for the Context Vigilance splash. The functional plumbing exists; the structural skills are codified elsewhere. This doc is only about the *story* — the four-act narrative arc and the emotional move each act should produce.
Track and Ingest Lossless Content into Chroma (with Change Detection)
A second ingestion pipeline parallel to the context-v corpus — for the ~5K Lossless content files scattered across the monorepo. Driven by its own sources map, with content-hash-based change detection so re-runs only re-embed what actually changed.
Write Custom Chroma MCP Server (v0: a session-transcript ingester)
Defer djm81/chroma_mcp_server; write our own session-transcript ingester into the Chroma the corpus lives in, so the two cross-query.
ai-labs/plans
memopop-orchestratorai-labs / memopop-ai9
MemoPop Connector API, Phase 7: The Plugin and Real Claude
A thin skill that keeps Claude on the method, packaged with the connector, and a test where real Claude writes the fixture memo.
MemoPop Connector API, Phase 1: Foundation
The registry, errors, auth, storage, five tools, the docs generators, the ledger, and CI. Every later phase builds on this one.
MemoPop Connector API, Phase 2: Deploy
A container with every system tool the memo needs, running on Railway at memopop.didi.sh, watched by a health check every 30 minutes.
MemoPop Connector API, Phase 4: Materials
Decks, datarooms, notes, and links reach the server three ways, become text the steps can read, and never block the memo.
MemoPop Connector API, Phase 5: Enhancements, Compile, and the Full Flow
Every enhancement becomes a step that can skip, compile turns sections into a branded PDF, and a scripted client walks the whole memo.
MemoPop Connector API, Phase 6: History and Snapshots
Every saved artifact becomes a jj change the client never sees, and one save backs the firm's whole workspace up to its bucket.
Reconciling Perplexity Citations Against Retrieved Sources
Sonar hands us the sources it actually retrieved on every call, and we throw them away — so every URL in every memo is a guess.
Migrate `studies/open-specs-and-standards/` into its own pseudo-monorepo
memopop-orchestrator/plans
perplexedcontent-farm9
Plan — Upgrade Perplexed to Obsidian 1.13 (0.4.0)
Perplexed has 56 settings across six research providers, and none of them show up in Obsidian's new settings search. 0.4.0 fixes that.
Plan — Exa Retrieval Stage and the `include-sources:` Slot
Perplexity writes well but retrieves badly on companies; Exa retrieves well but doesn't write. Split the job.
Plan — Run Snapshots and Restore
Line 830 wipes the target before the first byte of the stream arrives. Nothing in the plugin can undo that.
Plan — Section Refresh and Source Curation
Reshape one sub-segment, reject a weak source and make the web find a better one — without regenerating the whole map.
Plan — Vault-Aware Linking in Both Directions
Generated notes arrived orphaned, and the templates forbade linking rather than risk a model inventing a path.
Plan — Outline Shaping and Adherence Modes
Hand-author an outline into a market map today and the plugin appends the draft below it instead of following it.
Plan — Bring Perplexed up to Obsidian Community-Plugin Publishing Standards
25 explicit-any sites plus the four-part 0.0.0.1 version the bot rejects as non-semver, a missing LICENSE, and three unused runtime deps.
Plan — Submission Blockers Punch List (from docs.obsidian.md re-read)
Six docs-derived blockers — doubled command IDs, a description starting with A plugin for Obsidian, and no network-use disclosure.
perplexed/plans
content-farm8
Plan — Migrate the Lossless Plugin Family to Obsidian 1.13
Obsidian 1.13 changed how settings render and get searched, and pnpm 11 changed where its settings live. One playbook, nine plugins, each still standing on its own.
Auto-Hyperlink Feature Names in Generated Tables
Crawls the entity's domain to turn feature-table cells into links to the real feature pages — deferred until the headless crawler exists.
Cite-Wide — dedupe inline repetition of identical hex citations
One backreferenced regex collapses runs like [^jtas3k] [^jtas3k] — a different problem from dedupe-by-URL, which must stay untouched.
Dependency upgrades across the Obsidian plugin family — full bump inventory, safe → major → forks
Every outdated dependency in the ten Lossless-original modules plus the umbrella, grouped patch → minor → major, with upstream release-notes research attached to every major before it moves.
Create a Study of the Best Obsidian Plugins
Pin the 10–15 most interesting Obsidian plugins as a real study, so we read their code instead of paraphrasing from training data.
Image Drop Confirmation Gate
An Obsidian plugin that asks where a dropped image goes before anything hits disk or network — a private chart on imgur is a phone call.
A Component Inserter
An Obsidian command that scaffolds the right block — HTML, codefence, callout, embed — at the cursor, with frontmatter-driven defaults.
content-farm/plans
flave-aiai-labs4
Phase 2 — The Workspace and the Files Surface
Flave opens a folder, shows you what is in it, and lets you edit the theme that styles what you are reading — so design work is brought in once and reused, never recreated.
Phase 0 — The Live Render Loop
Type Lossless Flavored Markdown, watch it become a styled document as you type, and invent new syntax without touching the renderer. The smallest thing that is already the product.
Phase 1 — One Operation Set, Four Callers
A menu, a palette, a rendered page you can type into, and an agent — all writing through the same named operations, so a human and an agent can never reach a state the other cannot describe.
flave-ai/plans
studiesai-labs4
Analyze Harness-like Evidence in a Collaborator Codebase
Step 1 of 3: read a collaborator's repo for every sign of how they work with coding agents, and inventory it with paths and dates.
Compare and Contrast Harness-like Artifacts between Lossless and a Collaborator
Step 2 of 3: set our harness beside theirs. What's shared, similar, different, missing, and what each side should do about it.
Generate an HTML Page for Lossless and a Collaborator, Rendered in the AI Labs Splash
Step 3 of 3: turn the evidence and the comparison into one splash page. Visual highlights up top, the detailed narrative below.
studies/plans
image-gincontent-farm4
Plan — Migrate Image Gin's Settings Tab to Obsidian 1.13's Declarative Settings API
Half of Image Gin's settings silently vanished in Obsidian 1.14, and none were searchable. Rebuilding the tab on Obsidian's declarative API fixes both.
Plan — Bring Image Gin up to Obsidian Community-Plugin Publishing Standards
17 explicit-any sites, 2 innerHTML calls, and a hand-rolled YAML parser — tighten ESLint to error first so pnpm build surfaces the rest.
Plan — Final ObsidianReviewBot cleanup round for image-gin v0.2.x
Local lint is clean but the bot flags 49 sentence-case hits — its default brand list has no Magnific or Ideogram, so they get a /skip reply.
image-gin/plans
corpora-builderai-labs3
didi.sh Auth and Multi-Org Corpora
Log in once, hold several organizations at once, and read one federated corpus across them. Three catches, and two specs that disagree.
Search Index, Then Pagefind
Search reads 845 files. Phase 1 writes a manifest so it reads one. Phase 2 puts Pagefind on top of that manifest, not in place of it.
corpora-builder/plans
dididecks-aiai-labs3
Init DidiDecks as Core Submodule of AI-Labs
Carve dididecks-ai out into its own repo and re-attach it to ai-labs as a git submodule, with branch-aligned tiers.
Refactor scroll-ported slides into true static play-format slides (per-client, repeat for every deck)
A reusable procedure for stripping scroll idioms — vw/vh units, reveals, marquees — from copied slides so `/play` and `/print` render them.
dididecks-ai/plans
reach-edu-hubai-labs / dididecks-ai3
Codify the deck design system & component library — author DESIGN.md, showcase it on /design-system, and refactor every kept element onto theme/mode tokens
Building six strategy decks produced a real, reusable design system — deck-primitives.css (a 15-class component vocabulary) plus a set of recurring section compositions (cover, stat slide, field template, two-column contrast, numbered flow, accent callout, tier cards, ask/close). None of it is documented or shown on /design-system, and there is no DESIGN.md. This plan codifies the system: author a DESIGN.md per the maintain-design-md (Google Stitch) spec, add the deck primitives + patterns to the /design-system page, and — the gating discipline — promote an element into the documented system ONLY once it reads the Tier-2 semantic + --fx-* tokens and works in light/dark/vibrant with no hardcoded colors. That last bar is what 'requires refactoring': the strategy decks are already token-driven, but the older story/automation/homepage sections hardcode dark:/vibrant: triples and must be reconciled (or explicitly excluded) for one coherent system.
16:9 Export Variant (Play-UI) and the PPT/PDF Pipeline
Plan for the fixed-aspect, no-scroll, no-animation variant of each strategy pitch deck — the Play-UI conversion per the DidiDecks discipline — plus a native-shapes PPT exporter tuned for clean Google Slides import, and PDF via the shell's print route. Written 2026-07-28 while building the Scroll-UI decks, so the conversion is anticipated, not retrofitted.
reach-edu-hub/plans
lossless-monorepo3
site3
Content Areas Index: Nested Filters, Word Counts, and Shared Cards
Rebuild /content-areas from parts the site already has, generalizing them along the way: two-level folder tabs, live word totals, and the reference and tool cards.
Upgrade All Dependencies for Faster Builds
Astro 6.1 → 7.3 and everything around it, in risk order. Speed is the motive, so measure it, because this site's Markdown setup may limit the gain.
site/plans
context-vigilance-kitai-labs2
id-didi-shai-labs2
astro-knots2
lossless-changelogastro-knots2
mpstaton-siteastro-knots2
Implement the Standard Table of Contents on mpstaton-site
The parent blueprint says every collection rendering markdown gets the same reading-position ToC. This site has five such surfaces, a hand-rolled slugify that has to go, and — as of today — the LFM version that makes it possible.
mpstaton-site/plans