Idea-Capture Workflow — Web Clipper + Clippings
Section titled “Idea-Capture Workflow — Web Clipper + Clippings”Background
Section titled “Background”Spun off from KB-OS-next-upgrades (2026-07-09). Talbot flagged: “improving idea Capture workflow, especially with Obsidian Web Clipper — Clippings folder(s) is not optimal.”
Current state (2026-07-09 survey):
Core/Misc/Clippings/— 91 clipped articles, no routing/triage, mixed topics (AI, marketing, finance)- A stray vault-root
Clippings/folder had appeared (Web Clipper’s default when no folder is configured) — its 1 file was merged intoCore/Misc/Clippings/and the folder removed (2026-07-09) - Existing capture ladder (
Core/Processes/Capture-Routing.md— consolidated fromIdeas-Workflow.md2026-07-09 — + KB-OS-Usage): Capture → deptInbox.md→ promote to TaskNote → archive. Clippings bypass this entirely.
Proposed design (for Talbot to confirm)
Section titled “Proposed design (for Talbot to confirm)”- One clippings home: keep
Core/Misc/Clippings/as the single intake (SSOT rule — no per-business Clippings folders; MBR’s empty one already removed). - Web Clipper extension setting (browser-side — only Talbot can change it): set default folder to
Core/Misc/Clippingsso strays never land at vault root again. Optionally add a clip template withtopic:/business:frontmatter properties to make later routing cheap. - Triage path: fold Clippings into the planned
/triage-inboxskill (KB-OS ROADMAP M4) — it scans dept Inboxes andCore/Misc/Clippings/, proposes routing (dept Inbox bullet, TaskNote, or leave-as-reference), Talbot approves in batch. - Alternative considered: per-dept Clippings subfolders — rejected: recreates the routing problem at capture time, when capture should be zero-friction.
- Confirm design above with Talbot (esp. #2 — he must set the extension’s folder + template).
- Write the Web Clipper template (frontmatter properties:
source-url,clipped,topic,business) and document the extension settings inCore/AI/Notes/(or IT). - Implement Clippings scanning as part of
/triage-inboxwhen that skill is built (M4) — or as a lightweight first version scoped to Clippings only. - Backlog-triage the existing 91 clippings once the routing mechanism exists (batch session, not one-by-one).