Skip to content

README: Obsidian / Semantica / Graphier comparison table - #13

Merged
Joshuaakaspace merged 1 commit into
mainfrom
claude/semantica-repo-evaluation-essnux
Aug 16, 2026
Merged

Joshuaakaspace merged 1 commit into
mainfrom
claude/semantica-repo-evaluation-essnux

Conversation

@Joshuaakaspace

Copy link
Copy Markdown
Collaborator

Documentation-only PR following the merged #12. Adds a "Where Graphier sits" section positioning the project against the two things it inevitably gets compared to: Obsidian (the workspace it feels like) and Semantica (the engine room it borrows from).

Thirteen dimensions in one table — what each is, who uses it, how the graph gets made, semantics, reasoning, contradiction handling, provenance, time, sources, queries, AI involvement, deployment, and what each is best at — with honest entries in every column (Obsidian wins writing/ecosystem/polish; Semantica wins enterprise agent infrastructure).

Closes with the one-line relationship summary: Obsidian is where Graphier gets its philosophy, Semantica is where it gets three engine parts, and the product in between — the self-building, self-explaining, self-programmable vault — is Graphier.

No code changes; 51 tests untouched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QVbxD1gd3gsC6zXKE6L3ya


Generated by Claude Code

A 'Where Graphier sits' section positioning the project against the two
things it gets compared to: Obsidian (the workspace it feels like) and
Semantica (the engine room it borrows from). Thirteen dimensions —
graph construction, semantics, reasoning, provenance, time, sources,
queries, AI involvement — plus the one-line relationship summary.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QVbxD1gd3gsC6zXKE6L3ya
@Joshuaakaspace
Joshuaakaspace merged commit fc8718d into main Aug 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants