augment-it/explorations
- Path
- explorations/index.md
explorations
- Agent-Chat Skills and Commands — Candidates List - The chat’s verb roster is four prompt-focused capabilities. A running list of shell scripts that should graduate into chat-callable verbs.
- Augment from DB — the org-first workbench flow, and the two new microfrontends it needs - A flow that starts from SurrealDB, not a CSV: pick an org, reveal its people and pulse streams, augment through pluggable search packs.
- augment-it has outgrown one flow — ROTATION is the CSV-augmentation pipeline’s shape wearing a general-purpose name, and corpora-curator’s promotion to its head is a splice, not a fit - ROTATION (
shell/src/remotes.ts) is the CSV-augmentation flow hardcoded as THE nav — every other use case gets spliced onto it. - Augment-It Prior Art Survey — What’s Already Been Built, and What It Tells Us - Two prior attempts exist — Tanuj’s three federated repos and Michael’s bolt monolith. Both cover the core; neither is what we ship.
- Best Way to RAG Over the Corpus — design space for retrieval-augmented operations on augment-it’s per-client corpus, given the structured frontmatter we just earned - 245 corpus files carry
funder_slugandpublished_at, so retrieval is facet-filter-first — embeddings handle the residual about-ness. - Bolt-Era API Provider Widget Analysis - The bolt widget picked Claude, GPT, or Perplexity per prompt section. The widget dies in the rewrite; the multi-provider shape stays.
- Bolt-Era Codebase Analysis - A faithful architectural map of the bolt monolith — React + TS + Vite + Supabase + zustand — lifted from its own
specs/folder. - Bolt-Era Highlight Collector Analysis - The only existing description of the highlight-collector stage — one of two that never got split into Tanuj’s microfrontend repos.
- Bolt-Era Main Container UI Analysis - The bolt shell’s five-column layout and auth gate — prior art for the rewrite’s open question: one host shell, or a host per app?
- Bolt Monolith As Built — The archive/bolt-code Branch - The earliest augment-it is a Vite + React monolith on
archive/bolt-code: feature-richer than the federated repos, architecture we discard. - Bolt-Era Prompt Section Analysis - Prompt templates as MDX-rich, variable-aware, edit-toggle-preview blocks — the pattern prompt-template-manager should probably adopt.
- Bolt-Era Record Collector Analysis - Cross-reference against
Tanuj-Record-Collector-As-Built— the diff between bolt-era and forked shows which patterns survived federation. - Design Language Audit — July 2026 - The hand-counted baseline audit that measured the state of augment-it’s CSS before the design system shipped. Superseded as the counting mechanism by design-drift.mjs.
- Entity-Profile Augmentation Workflow — Common Social + Vertical-Specific Sources, Per Entity Type - Two tiers replace prompt-by-prompt column filling: packs as atomic source-bound units, bundles as workflow-shaped compositions of packs.
- Federation and Bundler Decision — Bun + Rsbuild + Module Federation, Workspace State, Optional Chat - We federate: Module Federation on rsbuild, bun over turbo, and state of truth in
@augment-it/workspace— chat is just one consumer. - Forced One-By-One Tag Selector — a pulse-dimension pattern for deliberate triage instead of lazy bulk-tick - Bulk checkboxes produce uniform half-considered tags. Present one tag at a time — apply / skip / skip-rest — and each decision gets made.
- Funder-Fit Engine — Org-Anchored Corpora and the Bidirectional Story↔Funder Cycle - Fundraising matches both ways — funder→story and story→funder — on one org-anchored corpus. The differentiator is KAG, not plain RAG.
- In-App Browser vs Browser Plugin for Corpus Add — bridging the operator’s own search into the per-record corpus without leaving the cockpit - Adding one operator-found URL to a funder’s corpus is a ten-step round-trip out to Google and back. In-app browser, or browser plugin?
- Inbox Sort by Agent Tasks — moving the inbox from a flat 86-item pending queue into a task-typed work surface where the operator sees what’s next and the agent does the safe parts automatically - 86 pending inbox files render identically, so the operator context-switches between four task types on every scroll.
- Joined People UI and the Network-First Pivot — augment-it’s sibling-flow to org-first augmentation, and the canonical/proprietary layer split underneath it - Org-first and people-first are two pivots on one join — and the split that matters is canonical (shareable) vs proprietary (client-only).
- JuiceFS — POSIX-Over-Object-Storage (Explored, Then Set Aside for rclone-to-R2) - JuiceFS is a network drive needing a kernel extension, not Dropbox — wrong shape for local-first corpus work. Superseded by rclone-to-R2.
- LinkedIn Network Explorer — slicing your own connection graph by geography for curated invites, when LinkedIn won’t let you query it directly - LinkedIn won’t tell you which of your own connections live in Manhattan. The data export plus augment-it’s enrichment cascade is the path.
- Multi-Agent Research Fan-Out Per Row — The Real Shape of Augment-It’s Capability Runtime - Capabilities aren’t LLM calls — five research agents run per row in parallel, so the runtime needs (rows × agents) fan-out.
- Operator-built flows beyond the universal pipeline — the default augmentation path is a dud for most edge cases, and the cheaper-than-microfrontend escape is a view-spec the agent-chat composes from natural language and the UI renders generically - The default flow lands cleanly on 17 of 96 reach-edu records. The escape isn’t a microfrontend per scenario — it’s a generic spec-renderer.
- Per-Client Privacy and the Path Off Local — when does single-operator-local-only stop scaling, what stack do we reach for, and how do we architect today so the move is cheap when it comes - Per-client corpus privacy and a client wanting login hit the same week. Not a stack decision — which choices keep the move off local cheap.
- Syncthing for Collaborator Access to the Corpus (R2 Backup Already Decided) - R2 already won the backup leg — rclone, not a live mount. This is the separate, still-open question: could Syncthing give other humans live access to the same corpus, without breaking the single-writer discipline that’s kept things sane so far?
- Tanuj’s Prompt-Manager As Built - Full CRUD-shaped prompt UI over a hardcoded
samplePromptsarray — no store, no data flow. Keep the schema, throw away the implementation. - Tanuj’s Record-Collector As Built - The most-finished of Tanuj’s three splits. One idea survives: the prompt template auto-generates from the imported CSV’s columns.
- Tanuj’s Request-Reviewer As Built — The Module Federation Proof - The only place Tanuj got federation working — a shared
RecordCard— while the augmentation logic sits copy-pasted from record-collector. - The Gap Between What We Preach and What We Practiced - Forty deployable units, one git repo, zero component-level design systems or changelogs. An honest audit of augment-it against the three recommendations we make to clients.
- The Moat Is Grounded Deliverable Production, Not Chat - Chat-over-documents is commoditizing; the moat is the last mile — a shippable deck or memo with every claim traceable to source.