MIND SYSTEM

Your knowledge,
as a synced filesystem.

Files you own. Zones you control. Versioned for teams. Synced everywhere — without the database lock-in.

v1.4 · macOS · Windows · Linux

synap.app/acme-studio
MEMORY
architecture.md
product-roadmap.md
team-rituals.md
vendor-contracts.md
01 — ARCHITECTURE

System overview

Service boundaries, data ownership and the contracts each module exposes to the rest of the system.

3ZONESpersonal · team · workspace
1FILESYSTEMfiles you can read in any editor
0VENDOR LOCK-INopen Markdown, always
100%OFFLINE-CAPABLEedit anywhere, sync later
01 · ZONES

Three places.
One mind.

Personal drafts, team knowledge, working drafts — clearly separated.

PERSONAL

Solo thinking

Your private drafts and notes. Never leave your device unless you say so.

TEAM

Shared knowledge

Architecture docs, decisions, playbooks. Versioned, searchable, governed.

WORKSPACE

Open drafts

Your in-flight changes to team memory. Land via change requests.

02 · SYNC

Sync that respects
your offline life.

Open your mind on a flight. Edit in coffee shops with no wifi. Land at home and watch every change merge cleanly across all your devices.

macbook · pablo
iphone
studio · acme
VS THE DATABASE WAY

Files. Not rows.

Why a synced filesystem beats a proprietary database for thinking work.

TODAY · NOTION-LIKE

Locked in a database

Schema you can't change without migration
Closed format — pay forever to keep access
Search engine ignores your edit history
AI gets shown a database row, not the doc
WITH SYNAP · FILES

Files Claude can actually read

Plain Markdown. Open in any editor.
Versioned with git-style change history
Local search across every word, every revision
AI sees the actual file the way you wrote it
03 · CHANGE REQUESTS

Team memory
has approvals.

PR-style review for knowledge changes. Server-authoritative merge.

01 · OPEN A CR

PR-style review
for your knowledge.

Bundle your edits to team memory. Reviewers see a markdown diff. Server merges authoritatively. No git CLI required.

02 · REVIEW

Approve or request changes.

Markdown comments. Diff lines. Just like code review.

03 · MERGE

Server-authoritative.

Once approved, the merge is canonical. No client-side races.

MIND SURFACE

One area.
Five places to think.

Notes, canonical memory, the relationship graph, change requests, and the trash — under one Mind.

NOTES

Daily writing

Free-form thinking in plain Markdown — your living scratchpad.

MEMORY

Canonical knowledge

The team's source of truth. Reviewed before it lands.

GRAPH

How it connects

Relationships across notes, decisions, and findings — at a glance.

CHANGES (CR)

Pending edits

Track open change requests and their review status from here.

TRASH

Recoverable history

Nothing is gone until you say so. Restore from any device.

A mind worth
living in.

Free. macOS, Windows, Linux. Bring your own Claude or just keep your knowledge.

Free · No credit card · No telemetry