v0.3: Auditable AI second brain for multi-context developers

Executive summary

The EU AI Act Article 50 enforcement window opens on 2026-08-02 with penalties up to €15M or 3% of global turnover for missing provenance on AI-authored content. Synapse already has the propose/sanction queue (BR-12.3) that aligns conceptually; what is missing is provenance frontmatter on accepted proposals, an immutable audit log, and syn pending replay for reproducibility, the three primitives that turn the existing v0.2 surface into an AI-Act-grade local-first second brain, a positioning no SaaS competitor can credibly copy.

v0.3 should ship that core auditable plus the MCP-native expansion (resources + prompts + server-card.json + Tasks) that the MCP 2026-07-28 RC moved from optional to expected, and two ingestors (GitHub, Linear) that resolve the adoption bottleneck. Theme: “Auditable AI Second Brain: shipped before the deadline.”

1. Context and premisses

What state is assumed

• v0.2.0 shipped on 2026-05-25 with 13 MCP tools (4 local read + 4 federation read + 5 write proposals via pending queue), 24 CLI subcommands, workspace federation with a structural privacy gate (BR-12.4 / SYN-79), filesystem-only freshness advisory (SYN-93 Phase 1 / ADR-011), last_modified_commit indexed per entity (SYN-68).
• 94 tests green, clippy clean under -D warnings.
• Cargo.toml at 0.2.0. ADR index covers 001-007, 009-011 (008 is a documented gap).
• The propose/sanction queue (BR-12.3) is the load-bearing invariant: MCP cannot write to the workspace without syn pending accept.

What is explicitly off-limits in this brief

• v0.5 semantic layer. Embeddings, sqlite-vec, hybrid ranking, the embedding backend ADR (SYN-89): all reserved.
• HTTP / SSE MCP transport. Backlog (SYN-207).
• Schema declarable per-workspace. Architecturally heavy; v0.4 or v1.0.
• syn-lsp LSP companion. Worth doing, wrong cycle.
• Cursor / Copilot territory. Synapse is the business context layer, not the coding assistant layer. v0.3 must not blur that.

Triggers for this brief

1. v0.2 closed 24/24 tickets; the team needs a defensible next theme.
2. The MCP spec 2026-07-28 release candidate moved several capabilities from optional to expected, opening a window to differentiate before SaaS catches up.
3. EU AI Act Article 50 sets a concrete deadline that aligns with Synapse’s existing safety surface.

2. Market scan

2.1 Multi-context pain points devs actually complain about (2025-2026)

The chronic gripes from devs running 5+ contexts are structural, not “yet another note-taker”:

• Cross-context bleed in AI assistants. A consultant in Cursor or Claude Code on Client A’s repo gets autocompletes contaminated by Client B’s vocabulary because the assistant has a single global memory. Notion AI and Mem.ai both struggle here: “personal graph” features (Glean rolled one out in late 2025) actively fight isolation by design.
• Workspace silos that can’t talk when you want them to. Obsidian vaults are isolated by file path but offer no first-class “ask across vaults”; Logseq has the same gap. Multi-vault graph queries are still an open issue on Obsidian’s forum in early 2026.
• Re-onboarding tax. Senior ICs across multiple contexts lose 15-30 min reorienting per context switch (Datadog State of AI Engineering 2026). Backstage / Cortex solve this for the company, not for the human spanning multiple companies.
• Mem.ai / Reflect “auto-organize” black box. Power users distrust LLM-managed graphs because they can’t see why something was linked or tagged. Loud on r/PKMS in early 2026.
• Tana / Anytype paradigm tax. Supertags and Object-types take weeks to internalize; consultants juggling 5 clients can’t afford that ramp per workspace.
• No tool gives “what’s stale per context” across multiple workspaces. Linear / Jira tell you what is open in this instance; nothing tells you “Project X has had zero activity for 21 days and three open commitments” across all your contexts.

What this means for Synapse: lean into per-workspace identity (different “voice” per SYNAPSE.md), make federation queries explainable (show which workspace each hit came from with a relevance reason), and make the freshness advisory cross-workspace by default for the new syn audit stale command.

2.2 MCP ecosystem maturity (2026)

State of the art as of MCP spec 2026-07-28 RC:

• Stateless servers + .well-known discovery (SEP-1649 → /.well-known/mcp/server-card.json) is the new default. Stateful is niche.
• Tasks extension for long-running work (indexing, reindexing, embedding generation): devs expect MCP servers to expose progress, not block.
• MCP Apps (server-rendered UI snippets): consumed by Cursor, Zed, Claude Desktop.
• Resources are now expected, not optional. The de-facto pattern: a server exposes resource://workspace/manifest and resource://entity/{id} as canonical URIs. Tools mutate; resources are addressable read state.
• OAuth / OIDC for auth is now mandatory for remote MCP. Local servers (Synapse’s case) skip this but should still expose a “consent scope” descriptor.
• De-facto default servers devs install: GitHub, Linear, Slack (all official Anthropic), Filesystem, Playwright, Postgres, Sentry. ~2,000 servers in the public registry.
• Audit-resource pattern is emerging: servers expose resource://audit/recent listing the last N tool invocations with timestamp and caller: pushed by Glean / Notion enterprise demands.

What this means for Synapse: ship .synapse/server-card.json; expose entities and manifest as MCP resources (not just tools); implement the Tasks extension for reindex / federated_search; expose resource://audit/recent derived from the pending queue plus the new audit log.

2.3 AI auditability + safety: where the bar sits

EU AI Act Article 50 enforcement starts 2026-08-02. Penalty ceiling: €15M or 3% of global turnover. What is now table stakes:

• Machine-readable provenance on AI-authored content. C2PA-style metadata + an invisible marker. Notion’s audit log already records MCP server connected and User information read events; Glean syncs ACLs in real time and logs every retrieval.
• Decision traces. Gartner’s context graph framing (Mar 2026): record what triggered the AI action, what context informed it, what rule governed it, what was the outcome. Not just “AI did X.”
• Pre-action approval, not post-hoc review. Pre-action approval has become the canonical “calibrated autonomy” pattern. Batch approval of 10-50 items is the productivity sweet spot.
• Reproducibility. Every AI write should be replayable from inputs.

What this means for Synapse: the propose/sanction queue is already aligned. Gap to close: (a) stamp every accepted proposal with provenance frontmatter (x-ai-source, x-prompt-hash, x-model, x-decision-trace-id); (b) maintain an immutable audit log of every accepted / rejected proposal in .synapse/audit.ndjson; (c) snapshot the context that informed each proposal so syn pending replay <id> re-runs against the same inputs.

2.4 Engineering knowledge graphs: where they fail the senior IC

Glean ($7.2B valuation, $200M ARR), Sourcegraph (code graph), Cortex / Backstage / Port (service catalogs). Where they break:

• Org-bounded. A senior IC at a big company with side consulting can’t carry their graph across employers. The graph dies with the badge.
• Service-catalog tools (Backstage / Cortex) are about services owned, not decisions made. ADRs, RFCs, post-mortems, and “why we picked X over Y” live elsewhere.
• Glean’s personal graph is still SaaS. Any consultant under NDA can’t legitimately point it at client data.
• Code graph ≠ decision graph. Sourcegraph knows the call graph but not “why this module exists.” The 2026 context graph trend (Foundation Capital, Gartner) is exactly this fusion.
• No first-class “person ↔ project ↔ org ↔ api” model that survives job changes. LinkedIn is too coarse; Obsidian does not enforce types.

What this means for Synapse: the 6-entity model (project, person, entity, api, task, note) is already the right shape. Differentiator to lean into: the graph belongs to the human, follows them across employers, and federates into an employer workspace (read-only) rather than living in it. This is the me.synapse portable identity bet in §6.

2.5 Integrations that actually have ROI

Real adoption signal, ranked by dev value:

1. GitHub PRs + issues. Highest ROI by miles. PR titles, descriptions, review threads, merged commits = ground truth of “what shipped.”
2. Linear issues > Jira. Devs want Linear ingestion; they have to live with Jira.
3. Calendar (Google / Outlook). Mostly for “who did I meet about Project X this week”: surprisingly high ROI for consultants billing hours.
4. Slack threads (selective). Whole-Slack ingestion is noise; thread-by-URL capture is the pattern that won (CodeRabbit, Granola).
5. Browser history / page capture. Arc is dying; Dia / Comet / Atlas rising. Lightweight “save this tab to Synapse with a note” beats full history sync.
6. Meeting transcripts. Granola, Fathom, Otter: devs want decisions and action items, not the transcript. Structured extraction wins.

What this means for Synapse: prioritize GitHub + Linear as syn ingest adapters that emit proposals into the pending queue (every imported entity is reviewable). Calendar and Slack-thread-by-URL come next. Skip full Slack / browser-history ingestion.

2.6 Sleeper trends the obvious list misses

• Decision-graph + code-graph fusion (Foundation Capital, Gartner): pairing what the code does with why we decided it. No local-first tool does this.
• Meeting-as-input, decisions-as-output. Granola-style “extract decisions and owners” is replacing “save the transcript.”
• Personal-graph-as-portable-CV. The Glean personal-graph idea leaking into consumer territory: people want a knowledge graph they own.
• MCP servers as the “agent’s keyboard.” Devs are abandoning ChatGPT plugins and assistant-specific integrations because MCP is becoming OS-level (Apple Intelligence MCP support shipped in iOS 19.2 beta).
• Provenance-first writing. Every AI-authored paragraph stamped with model + prompt hash + retrieval set. The C2PA metadata norm from images is propagating to text.
• Cross-workspace queries with capability disclosure: federated read where each workspace publishes what it allows others to see. Almost no one ships this.

What this means for Synapse: the moat is the intersection: local-first + MCP-native + typed entities across workspaces + human-owned graph. v0.3 should make that intersection legible.

3. Cross-check vs prior hypotheses

The internal brainstorm proposed 8 blocks (A-H). The market scan filtered them:

Net adds the market scan exposed that were not in the internal brainstorm:

• Decision-trace frontmatter stamps (x-ai-source, x-prompt-hash, x-model, x-decision-trace-id): became a hard requirement because of EU AI Act.
• syn pending replay <id>: re-runs the prompt against the original context snapshot. SaaS cannot copy this (no client-side snapshot).
• Immutable audit log at .synapse/audit.ndjson, separate from the pending queue.
• .well-known/mcp/server-card.json with capability disclosure for federation.
• MCP Tasks extension on reindex and federated_search so long-running work reports progress.

4. Positioning

Defensible moat: the intersection: local-first auditable AI second brain that the human owns across employers. SaaS competitors structurally cannot ship 3 of those 4 attributes together; their business model requires data lock-in. v0.3 makes the intersection legible.

5. Recommendation

Theme

“Auditable AI Second Brain: shipped before the deadline.”

Prioritised blocks

Explicit non-goals for v0.3

• Embeddings / semantic search (v0.5).
• syn agent autonomous loop (v0.4).
• TUI / syn ui (backlog).
• syn-lsp LSP companion (v0.4 or v1.0).
• Schema declarable per workspace (v0.4 or v1.0).
• HTTP / SSE MCP transport (backlog).
• Full Slack / browser-history ingestion (deliberately rejected in §2.5).

6. Disruptive bets

Three to five non-obvious ideas the SaaS lane cannot easily copy:

Bet 1: Portable knowledge identity (me.synapse bundle)

Problem. A consultant or senior IC working across N employers / clients has their professional identity fragmented and re-typed in every workspace. cliente-alfa has person/romulo-febasi with email + role + expertise; cliente-beta has a re-typed version; personal-brain has a third. When the engagement ends, the professional memory (projects touched, decisions signed, expertise validated) stays trapped in a workspace that does not travel with them. Glean’s Personal Graph solves this conceptually but is SaaS: tied to the employer’s Glean subscription and lost at exit. LinkedIn is coarse, public, and not typed.

Solution. A signed bundle (~/me-romulo.synapse, ~10KB) carrying:

• The human’s canonical person entity (email, social handles, bio, skills as tags).
• Attestations of past involvement: “I worked on api-pagamentos at cliente-alfa in 2025 as tech-lead”: signed with an ed25519 key the human owns.
• A history of roles that survives employment changes.

Flow.

# One-off: generate the bundle from the personal workspace
syn identity export --out ~/me-romulo.synapse

# In every new workspace
cd ~/work/cliente-novo
syn init
syn identity import ~/me-romulo.synapse
# → creates person/romulo-febasi pre-populated
# → links attestations as inbound references (read-only)

The MCP server surfaces that person as immediately-available context: no re-typing.

Why SaaS structurally cannot copy.

v0.3 scope (prototype).

• syn identity export --out FILE: bundle generation from the workspace person that the manifest marks as self: true.
• syn identity import FILE: create / update the person in the current workspace; attestations attach as inbound read-only references.
• syn identity inspect FILE: clear-text dump for audit (no crypto required to inspect).
• Optional ed25519 in v0.3: bundles without a signature import as unverified; signed bundles verify against a pinned public key. Mandatory signing lands in v0.4.
• Workspace manifest gains identity.consumes: [bundle-path] to declare federation intent. Read-only.

Out of v0.3 (deferred).

• Attestation revocation (v0.4).
• Sigstore-style transparency log (v0.5+).
• Cross-bundle merge (multiple bundles federated).
• HTTP discovery of bundles (backlog).

Bet 2: Decision-trace frontmatter as a first-class entity field

Every accepted AI proposal stamps the resulting markdown with:

x-ai-source: mcp:capture_fact
x-decision-trace-id: 0193af-...-a4b7
x-prompt-hash: sha256:f8e2c1...
x-model: anthropic/claude-opus-4-7
x-accepted-at: 2026-05-25T15:30:00Z
x-accepted-by: romulo@febasi.com.br

• Becomes the EU AI Act Article 50 receipt and a queryable edge in the graph.
• SaaS audit logs are vendor-locked; Synapse’s is a git diff.
• Stamps respect a [provenance] inline = false flag to keep the markdown clean when the user prefers the audit log alone.

Bet 3: Cross-workspace “stale + uncommitted” advisory

$ syn audit stale --over 14d
Across 7 workspaces, you have 4 open commitments older than 14 days:

  [client-alfa]    task/migracao-pagamentos     21d  high risk: focal: maria-silva
  [work-brain]     project/refactor-auth        17d  medium risk: no recent linked notes
  [personal-brain] note/contratar-juniors       16d  low risk
  [client-beta]    api/webhooks-v2              14d  unknown: last contact unclear

• No SaaS sees across workspaces it does not own.
• Builds on federation + freshness primitives already shipped in v0.2.

Bet 4: Capability disclosure manifest at .synapse/server-card.json

Each workspace publishes what is readable cross-workspace and what is redacted:

{
  "name": "client-alfa",
  "exposes": ["project", "api", "person"],
  "redacts": { "tags": ["confidential"], "types": ["note"] },
  "federation_protocol": "synapse/v1"
}

• Aligns with MCP SEP-1649 trajectory, adds workspace-level capability scopes, a primitive no current MCP server has.
• Other Synapse instances negotiate the federation handshake reading this card.

Bet 5: syn pending replay <id>

Re-runs the original prompt against the original context snapshot stored alongside the proposal; shows the diff between the original output and the new one.

• Catches model drift, gives EU-AI-Act-grade reproducibility.
• SaaS cannot ship this: they do not keep the context snapshot client-side.
• Requires a new pending.context_snapshot column (added in SYN-114).

7. Ticket sketch (provisional IDs SYN-110..SYN-129)

These are sketches, not GitHub issues. Issues open only when the milestone is greenlit.

Total after cuts: 18 sketched tickets in v0.3 (SYN-119 and SYN-120 deferred). One ticket carried to v0.4 in parallel: SYN-130: syn-lsp LSP companion (completions for slugs / types / tags in any editor that speaks LSP). v0.4 milestone opened so the issue has a home.

Estimate 4-6 weeks of focused execution at the v0.2 pace if the 2026-08-02 deadline lock-in holds.

8. Risk register

9. Open decisions

All resolved on 2026-05-25:

The brief is accepted and actioned.

10. References

MCP ecosystem

• The 2026 MCP Roadmap: official roadmap blog.
• MCP 2026-07-28 release candidate: RC notes for the spec window v0.3 targets.
• MCP server discovery: .well-known/mcp.json 2026 guide (Ekamoira): SEP-1649 implementation walkthrough.
• SEP-1649: .well-known/mcp discovery (GitHub issue): spec discussion.
• MCP ecosystem v1.27: Context Studios: ecosystem state.

Auditability and regulation

• Glean: Audit trail compliance for sensitive data: enterprise audit benchmark.
• Notion audit log: what Notion captures.
• EU AI Act Article 50: transparency obligations (HSF Kramer, 2026-03): legal analysis.
• EU AI Act August 2026 (Bria): pragmatic enterprise checklist.
• Human-in-the-loop AI agents: approvals 2026 (getclaw): batch approval as the new sweet spot.

Knowledge graphs and context

• Glean knowledge graph: incumbent SaaS reference.
• Glean doubles ARR to $200M (Futurum): competitive scale.
• Backstage vs Cortex vs Port: developer portal comparison 2026: engineering knowledge graph landscape.
• Enterprise search for engineering teams (Onyx): orthogonal incumbent.
• Context graphs: Foundation Capital: investor framing.
• Gartner context graphs (Atlan summary): analyst framing.

Integrations and adoption

• CodeRabbit Slack Agent launch (BusinessWire, 2026-04): adjacent product launch and adoption signal.
• AI browser landscape 2026 (DigitalApplied): Arc successors and capture patterns.

Pain points and ergonomics

• Tana alternatives 2026 (Storyflow): competitor pain-point coverage.
• Context switching costs (WaymakerOS): quantitative reference for multi-context tax.