new, edit(context): spec new frontend for augment-from-db flow.

 On branch rebuild/turbo-rsbuild
 Your branch is up to date with 'origin/rebuild/turbo-rsbuild'.
 Changes to be committed:
	new file:   context-v/explorations/Augment-From-DB-Flow-Two-New-Microfrontends.md
	modified:   context-v/explorations/Augment-It-Has-Outgrown-One-Flow-The-Choose-A-Flow-Front-Door.md
	modified:   context-v/issues/Search-Providers-as-First-Class-SearXNG-Default.md
	new file:   context-v/specs/Augment-From-DB-Flow.md
	modified:   context-v/specs/Connector-Inventory-and-Per-Record-Palette.md
	modified:   context-v/specs/Entity-Pulse-Bundle.md
	modified:   context-v/specs/Pulse-Pattern.md
	modified:   context-v/specs/Record-DB-Resolver.md
	modified:   context-v/specs/Sparse-Person-Enrichment-Surface.md
	modified:   context-v/specs/Strategy-Curator-Entry-Point-for-Augment-It.md

Author: mpstaton

context-v/explorations/Augment-From-DB-Flow-Two-New-Microfrontends.md

@@ -2,13 +2,16 @@
 title: "augment-it has outgrown one flow — ROTATION is the CSV-augmentation pipeline's shape wearing a general-purpose name, and strategy-curator's promotion to its head is a splice, not a fit"
 lede: "augment-it started as one thing — augment a CSV, row by row — and ROTATION (shell/src/remotes.ts) is that flow's shape, hardcoded as THE numbered nav. Every use case since (DB-canonicalization for reach-edu's CRM exit, per-org/person corpus curation, now domain/thesis curation for humain-vc) has been reconciled onto that one array instead of recognized as its own flow. Strategy Curator's 2026-07-06 'promotion to the head of ROTATION' is the symptom: a domain-curation session doesn't hand off into recordCollector, but ROTATION was the only navigation primitive that existed, so that's where it landed. The fix isn't a bigger ROTATION array — it's a 'what are you trying to do?' front door that picks which flow mounts, so a use case that isn't CSV-row augmentation stops being forced to pretend it is."
 date_created: 2026-07-06
-date_modified: 2026-07-07
+date_modified: 2026-07-21
+date_first_published: 2026-07-07
 authors:
   - Michael Staton
 augmented_with:
   - Claude Code on Claude Sonnet 5
-semantic_version: 0.0.0.4
-status: Implementing
+  - Claude Code on Claude Fable 5
+semantic_version: 0.0.0.5
+status: Shipped
+post_ship_note: "The front door shipped 2026-07-07 as the FLOWS registry (shell/src/flows.svelte.ts) + dynamic bubble strip — see changelog 2026-07-07_02_ROTATION-Becomes-N-Flows. Five flows registered as of 2026-07-21."
 tags:
   - Exploration
   - Augment-It

context-v/explorations/Augment-It-Has-Outgrown-One-Flow-The-Choose-A-Flow-Front-Door.md

@@ -2,13 +2,15 @@
 title: "Search Providers as First-Class — Stand Up SearXNG as the New Default for Social Packs; Tavily Stays as a Peer; Per-Row Iteration as the Workflow We're Building Toward"
 lede: "The social packs route through Tavily today, but Tavily is a content-RAG index — wrong substrate for sparse-text JS-rendered social-profile pages. The fix is **not** to swap Tavily out. The fix is to make **search provider** a first-class concern in the architecture, stand SearXNG up as a peer, flip the common-seven social packs so SearXNG becomes their new default, and keep Tavily wired in as a peer for the content-RAG packs/bundles that will want it (deep-research, document extraction, annual-report summarization). The deeper goal — the reason this is more than a refactor — is that the product is being shaped around an **iteration loop**: a user finds a `not_found` or low-confidence response in the by-record triage view, suspects the provider is the issue, and wants to re-fire the same pack against the same row through a different provider (SearXNG → Brave → Google CSE → direct-API connector) until the accurate data surfaces with the fewest API calls. That loop only exists if providers are plural and selectable per-fire."
 date_created: 2026-05-26
-date_modified: 2026-05-28
+date_modified: 2026-07-21
 authors:
   - Michael Staton
 augmented_with:
   - Claude Code on Claude Opus 4.7
-semantic_version: 0.0.0.3
+  - Claude Code on Claude Fable 5
+semantic_version: 0.0.0.4
 revisions:
+  - 2026-07-21 — Status sweep, resolved. The core ask fully landed: SearXNG shipped as peer provider + social-pack default with provider_override on 2026-06-01 (changelog 2026-06-01_01), and the capability registry (registry/, register-connectors.ts booting searxng/tavily/serpapi/gdelt/google-news-rss) landed 2026-06-02 — going beyond this issue's Layer 1. Never done from the original plan: step 7's foundation-dataset smoke (the ≥60% acceptance number) and step 8's blueprint write-up. Those are noted, not blocking — the architecture the issue argued for is in production. (semver 0.0.0.4)
   - 2026-05-26 — Initial draft as "Switch Search Substrate from Tavily to SearXNG." Framed the move as a substrate swap with Tavily preserved as a side-effect. (semver 0.0.0.1)
   - 2026-05-27 — Reframed. The decision is **provider plurality as a first-class architectural concern**, not a substrate swap. SearXNG becomes the new default for social packs; Tavily stays as a peer for content-RAG packs; future providers (Brave, Google CSE, ProPublica NPO, Candid, LinkedIn-direct, MCP-server-as-provider) plug in via the same connector interface. Added §The iteration loop we're building toward — per-row, per-pack provider selection as a future product affordance. File renamed from `Switch-Search-Substrate-from-Tavily-to-Searxng.md` to `Search-Providers-as-First-Class-SearXNG-Default.md` to match. (semver 0.0.0.2)
   - 2026-05-28 — Layer 1 (the connector plumbing, proposed-work steps 1–6) landed in code. `connectors/{types,index,tavily,searxng}.ts` exist, `PackConfig` is provider-aware, all common-seven social packs default to `connector: 'searxng'`, `runOnePackSearch` dispatches on provider and accepts `provider_override`, and the SearXNG container + `settings.yml` are in `docker-compose.yml`. Steps 7 (foundation-dataset smoke / the ≥60% acceptance number) and 8 (blueprint write-up) remain, as does the per-record iteration UI in response-reviewer :3005. (semver 0.0.0.3)
@@ -23,7 +25,7 @@ tags:
   - Provider-Plurality
   - Iteration-Loop
   - Social-Search
-status: Open
+status: Resolved · Provider Plurality Shipped 2026-06-01 · Registry 2026-06-02 · Smoke Metric + Blueprint Skipped
 ---
 
 # Search Providers as First-Class — SearXNG Becomes the New Default for Social Packs