⚖MikeWatch Forks of the Mike legal-AI codebase, distilled for legal-tech readers
Home · emileriksenkeev/sydOS · this thread

emileriksenkeev turns each matter into a working wiki

This fork gives every matter a shared knowledge base that can inform the assistant tools around it.

knowledge-managementworkflow

The wiki uses Obsidian-style Markdown, stored in Supabase, a hosted database service. It lives alongside the project workspace, so the matter record has a place for evolving notes, context and linked references.

  • Auto-ingest brings material into the wiki without a separate manual copy-and-paste step.
  • Linting checks the wiki content for consistency.
  • Backlinks connect related notes so a reader can follow the matter's internal trail.
  • Entity extraction and the project assistant can read the wiki as a source, putting the accumulated matter context back into day-to-day tools.

That last move is the interesting one: the wiki becomes part of how the system understands a case, not a document left for someone to discover later.

So what Teams handling complex, long-running matters should look closely if they want their accumulated case knowledge to stay usable across assistant workflows.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

4 commits from emileriksenkeev/sydOS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
2eb90427 Syd OS: Plan B2 (phase 1) - matter wiki (Obsidian-flavored markdown in Supabase) emileriksenkeev 2026-07-11 ↗ GitHub
commit body 
- wiki_pages table (per-project, slug/title/category/content_md); migration applied
- read_wiki + upsert_wiki_page tools wired into the project assistant
- system prompt: wiki-first workflow (index/log/[[wikilinks]], Karpathy pattern);
  order of use = read_wiki -> search_documents -> read_document
- 'Build / Refresh Matter Wiki' built-in workflow (ingest) in both registries

Stored in Supabase (multi-user, access-controlled, backed up); Obsidian-compatible
format so a matter's wiki can be exported as a vault. Not coupled to Obsidian.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
ba263f30 Syd OS: Plan B2 (phase 2) - Wiki browser tab in projects emileriksenkeev 2026-07-11 ↗ GitHub
commit body 
- backend: /projects/:projectId/wiki REST (list, get, upsert, delete pages;
  export as Obsidian-compatible vault zip via jszip), project-access gated
- frontend: Wiki tab in ProjectPage - sidebar grouped by category, markdown
  rendering with clickable [[wikilink]] navigation, page editing, manual page
  creation, deletion, and one-click Obsidian vault export
- mikeApi: wiki client functions

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0e4a313e Syd OS: B2 polish - wiki auto-ingest, lint workflow, backlinks emileriksenkeev 2026-07-11 ↗ GitHub
commit body 
- Auto-ingest on upload: new docs in a wiki-enabled project get a
  source-summary page + log entry automatically (claude-haiku via
  WIKI_INGEST_MODEL; per-project serial queue; no-ops when the project
  has no wiki, when text is unextractable, or on any error)
- 'Lint Matter Wiki' built-in workflow: contradiction/staleness/orphan/
  coverage sweep with safe auto-fixes and a severity-rated report
- Backlinks: GET /wiki/page now returns pages linking to the requested
  slug; Wiki tab renders a 'Linked from' section with clickable chips

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
e3c46516 Syd OS: wiki becomes autonomous infrastructure emileriksenkeev 2026-07-11 ↗ GitHub
commit body 
- wikiBuilder.ts: headless agentic builds via runLLMStream (no chat/SSE) as
  the project owner. Debounced auto-build on document upload (bulk uploads
  collapse into one run, default 2 min after last change; WIKI_BUILD_DEBOUNCE_MS)
  and on document deletion. One build per project; concurrent requests
  coalesce. Model: WIKI_BUILD_MODEL (default claude-sonnet-4-6).
- Routes: POST /projects/:id/wiki/rebuild ({fresh} wipes pages and rebuilds
  from current documents only) + GET /projects/:id/wiki/status.
- Wiki tab: 'Rebuild from scratch' button (confirm), live 'building...' banner
  with status polling, auto-refresh of the page list when a build finishes;
  empty-state copy reflects automatic builds.
- Removed wikiIngest.ts (per-doc haiku summaries) - superseded by full
  debounced builds. Chat tools (read_wiki/upsert_wiki_page) remain for
  corrections, but the wiki no longer depends on the assistant.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-909.md from inside the repo you want the changes in.

⬇ Download capture-thread-909.md