openwiki-wiki/quickstart.md

Robin's Local Knowledge Base

This is Robin's personal OpenWiki — a local, growing knowledge base that synthesizes notes, recurring themes, open questions, commitments, and personal logistics from configured sources.

What this wiki is

• Personal brain — durable notes about Robin's life, work, people, projects, and recurring patterns.
• Synthesis layer — OpenWiki connector ingestion writes raw data under ~/.openwiki/connectors/<connector>/raw; this wiki is the opinionated, deduplicated map on top of that evidence.
• Living document — pages evolve as new connector data lands. Each update run reviews open-questions.md and refreshes the relevant canonical pages.

How this wiki is organized

Page	Purpose
/quickstart.md	This page — orientation, navigation, status.
/open-questions.md	Unresolved questions about Robin's memory/wiki. Active, Answered, Stale.
/themes.md	Recurring topics and signals index — terse table.
/commitments.md	Work tasks, follow-ups, approvals, scheduled items.
/personal-logistics.md	Personal errands, appointments, travel, life admin.
/sources/	Per-connector evidence indexes (one page per active connector).

Current status

• Wiki state: initialized — Hacker News, the local Obsidian vault, and Tavily web search are active and feeding /sources/hackernews.md, /sources/git-repo.md, /sources/web-search.md, and /themes.md.
• Connectors: Hacker News, git-repo, and web search active. Gmail, Slack, Notion, and X are not yet configured — see "Adding sources" below.
• Last update: see /.last-update.json — the latest source run is git-repo (obsidian-robin-1 2026-08-01 18:10 UTC). Vault HEAD remains 1a81e485 with no new commits or newly observed working-tree paths, so no canonical synthesis pages changed. The preceding HN-only run (hackernews-1 2026-08-02 18:00) is now the third consecutive empty pull (after 2026-08-01 18:00 and 2026-07-31 18:00): feeds: [] and queryResults: [] — connector completed normally at fetchedAt: 2026-08-02T18:04:23.938Z with no items. Two was a probable outage; three is a confirmed sustained outage on the HN lane and warrants an unscheduled check of ~/.openwiki/connectors/hackernews/config.json and Algolia / HN API status before the next scheduled pull — without that, the lane should be paused rather than scheduled. No theme row Last-seen was refreshed (zero in-scope evidence); the source-backed rows (class-organoid-3d-bioprinting, hermes-agent-v0-19-quicksilver, agent-memory-architecture, china-cde-cell-gene-therapy-rules-2026, china-order-no-818-clinical-translation, MiniMax-m3) keep their 2026-07-30 / 2026-07-29 Last seen. No new commitments, no new open questions, no new personal-logistics items. The prior multi-connector run (2026-07-31 cycle covering HN + web-search + git-repo) remains documented on /sources/hackernews.md as the previous empty pull; previous material-evidence run was the 2026-07-30 cycle documented on /sources/web-search.md pull 7. The standalone Tavily web-search pull on 2026-08-02 18:07 (web-search-1) is the third consecutive fully-failed pull (after 2026-08-01 18:09 — unrecorded at the time, gap-filled now — and 2026-07-31 18:06): all 10 queries in the same lane returned "error": "fetch failed" with no answer text and no result URLs. Scope and query phrasing are unchanged from pulls 1–7 (which all succeeded), so the failure is Tavily-side / upstream. Pull 7 (2026-07-30 18:04 UTC) remains the canonical last successful Tavily pull; an unscheduled check of TAVILY_API_KEY validity, Tavily status page, and rate-limit posture is warranted in parallel with the HN-lane check above, with a "pause the lane" fallback if Tavily status can't be confirmed.

How to use this wiki

• Ask questions about the wiki — Robin can ask things like "what's on my plate this week?" or "what recurring themes have you noticed?" and answers come from these pages first.
• Update on demand — openwiki personal opens the personal chat; openwiki personal --update "<message>" ingests configured connectors and refreshes synthesis pages.
• Trust labels — facts use confirmed, source-backed, watchlist, or saved-context so Robin can see how solid each claim is.

Adding sources

When Robin is ready, configure connectors to start populating the wiki:

• Gmail — openwiki auth google (needs Google OAuth refresh token)
• Slack — openwiki auth slack (needs Slack user token with search:read for definitive self-message search)
• Notion — configure Notion MCP via ~/.openwiki/connectors/notion/
• X / Twitter — openwiki auth x (needs OPENWIKI_X_ACCESS_TOKEN)
• Web Search — set TAVILY_API_KEY (active; see /sources/web-search.md)
• Hacker News — public feeds, no auth needed
• Local git repo — point the git-repo connector at a repo path

Auth instructions and env var names live in the OpenWiki operations docs and ~/.openwiki/skills/write-connector.md.

Backlog

Deferred until Robin configures connectors or asks for specific documentation:

• Gmail evidence index — /sources/gmail.md (no Gmail connector configured yet)
• Slack evidence index — /sources/slack.md (no Slack connector configured yet)
• Notion evidence index — /sources/notion.md (no Notion MCP configured yet)
• X / Twitter evidence index — /sources/x.md (no X connector configured yet)
• Hacker News evidence index — /sources/hackernews.md (active; last refreshed 2026-08-02 18:00 UTC — third consecutive empty pull, see HN source page)
• Web search evidence index — /sources/web-search.md (active; last refreshed 2026-08-02 18:07 UTC — third consecutive fully-failed Tavily pull after 2026-08-01 18:09 and 2026-07-31 18:06, see source page)
• Git repo evidence index — /sources/git-repo.md (active; last refreshed 2026-08-01 18:10 UTC — covers Robin's Obsidian vault)
• Project / people / company pages — only created when durable entities emerge from ingested data

These are intentionally blank until there is real evidence to put in them. Populating them with placeholders would dilute the synthesis layer.