augment-it/plans
- Path
- plans/index.md
Plans
- 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. - 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.
- Augmentation-state preservation and snapshot promotion — the operator’s CSV is the system of record, the filesystem is the truth, and
/promote-snapshotis 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-snapshotjoins the corpus filesystem into a fresh CSV version with system columns. No register, no write-hooks. - 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Didi chat joins the Org Workbench — first agent action: verify a team page and turn it into approved people objects - Point didi at an org’s team page: people objects land in state, not the DB — only on approval does it write persons and affiliations.
- Didi crawl — three targets (links, streams, team members), the relevance brief, and staged team ingest - One
organization.crawlcapability over Anthropic’s server-side web_search, driven by a per-workspace, operator-editable relevance brief. - 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.
- 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.
- 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.
- Give the services a shared tsconfig base — fold ten byte-identical service configs onto a new
tsconfig.services.json, reconciledecile-mcp’s real delta, fold two duplicated package configs onto the existingtsconfig.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.jsondid this for the apps and works. - 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.
- 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. - 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. - 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.’
- Migrate off the deprecated
natspackage to the@nats-io/*scoped v3 client — swapnats@2for@nats-io/transport-node@3across all 10 services, drop the removedJSONCodecin favor ofJSON.stringify+msg.json(), and prove the inter-service bus still round-trips live before committing -nats→@nats-io/transport-nodev3 across 27 files: mechanical, except the removedJSONCodecrewrites every encode and decode. - 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.
- 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.
- 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.
- Prompt-Template-Manager — Walking Skeleton Plan - Author
{{column}}templates and run them per row —prompt-runneris the only container that calls the Anthropic API. - 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.
- 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.
- Run-as-First-Class-Operation — Pair Pack-Runner with Prompt-Template-Manager, Make Runs Legible Across the Pipeline - Lift
Runfrom a string id buried on each response into a real entity, so any surface can see which batch produced what it’s showing. - 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.
- 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.
- SurrealDB MCP + a verification skill — querying augment-it’s canonical layer directly, starting with FreedomFest 2026
- 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.
- 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.
- 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 -
socialsand its list-shaped siblings render as 12px JSON; a shape-detecting extractor makes every URL clickable and drops the clutter. - 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.
- 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.
- 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.