AI tool comparison
ArcKit vs SMF (Semantic Memory Filesystem)
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
ArcKit
68 AI commands that turn architecture governance from chaos into system
50%
Panel ship
—
Community
Free
Entry
ArcKit is an open-source toolkit that applies AI to enterprise architecture governance — the notoriously painful process of getting technology decisions documented, approved, and traceable across large organizations. It ships 68 commands organized around the full governance lifecycle: business case development, requirements capture, vendor evaluation, design review, and compliance documentation for frameworks including the UK Technology Code of Practice and EU AI Act. The toolkit distributes across every major AI coding platform: Claude Code (the primary target, with all 68 commands plus 10 autonomous research agents, 5 hooks, and bundled MCP servers for AWS, Microsoft Learn, and Google docs), Gemini CLI, GitHub Copilot, and OpenCode. Every generated document includes citation markers ("[DOC-CN]") for traceability, and the research agents can autonomously pull documentation from cloud provider APIs. What makes ArcKit stand out from generic prompt libraries is specificity. The UK public sector commands are built around actual HM Treasury Green Book and Orange Book frameworks, and the project has 11+ public demonstration repositories across NHS, government, and financial services scenarios. For organizations that spend weeks on Architecture Design Review documentation, having a structured AI-assisted workflow that produces auditable, traceable artifacts is genuinely valuable. It's trending on GitHub with 1.3k stars and actively maintained at v4.8.0.
Developer Tools
SMF (Semantic Memory Filesystem)
Your filesystem IS the vector database for AI agents
75%
Panel ship
—
Community
Paid
Entry
SMF (Semantic Memory Filesystem) is an open-source Python library that treats the POSIX filesystem as the native memory infrastructure for AI agents. The core bet: instead of standing up a vector database, embedding service, and retrieval pipeline, you model your agent's memory as ordinary directories, files, and symlinks — then use the OS's own tools for retrieval. Entities are directories, relationships are symlinks, metadata is file attributes, and search is built on grep and find. The appeal is radical simplicity. Every developer already understands the filesystem. Memory built on top of it is inspectable with any editor, versionable with git, and portable across machines with rsync. There's no new query language to learn, no vector index to maintain, and no external service to keep running. Dynamis-Labs argues that for many agent memory use cases, semantic similarity search is overkill — you need entity graphs and efficient lookup, which the filesystem already provides. With only 7 stars and created yesterday (April 14), SMF is in very early stages. But the approach has attracted immediate discussion from developers frustrated with the operational overhead of vector databases for relatively structured memory tasks. It's a contrarian bet that's worth watching.
Reviewer scorecard
“68 commands with citation traceability and MCP servers for cloud docs is a serious toolkit, not a prompt dump. The Claude Code integration with autonomous research agents that can pull actual AWS/Azure documentation is the kind of thing I'd spend weeks building from scratch. For anyone doing ADRs at scale, this is a significant time saver.”
“I've been burned too many times by embedding pipelines that drift when models update and vector indexes that mysteriously degrade. Filesystem-native memory is zero-dependency, trivially inspectable, and you can version it with git. For structured agent memory this is genuinely compelling.”
“Enterprise architecture governance is already bureaucracy-heavy, and AI-generated documents with '[COMMUNITY]' warnings baked in are not going to pass muster in regulated environments without significant human review. The UK-specific framing means international relevance is limited, and the steep learning curve makes this a niche tool even within its target audience.”
“The filesystem approach breaks down the moment you need fuzzy semantic matching — 'find memories related to customer churn' doesn't map to a grep. For anything beyond exact lookup, you're going to bolt on a vector DB anyway and now you have two systems. This is clever for toy agents, not production.”
“Structured AI assistance for governance workflows points toward a future where compliance and documentation aren't bottlenecks but nearly instant byproducts of design work. ArcKit is early and rough, but it's exploring the right problem: bringing AI into the unglamorous but critical middle layers of large organizations.”
“The insight that the filesystem is a perfectly good entity-relationship store is underappreciated. As agents move toward local-first architectures, having memory that's portable, inspectable, and git-versionable becomes a serious advantage over cloud-hosted vector DBs.”
“This is firmly in the enterprise-technical domain — not much here for content or design workflows. The Wardley Map and Mermaid diagram generation is interesting for visual architecture communication, but the tool requires deep domain knowledge to get value from. Admire the ambition, but it's not for me.”
“I love tools that demystify AI plumbing. The idea that agent memory could just be files I can open in a text editor makes the whole system feel less like a black box. This is the kind of transparency that builds trust.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.