Firelock Labs.
The current Kin stack starts with the local semantic substrate, then moves up into hosted collaboration. The old editor and agent forks are retired from the active stack. The public story is Kin, KinDB, kin-vfs, Kin Editor, and KinLab.
Pre-registered determinism
26 / 26
Kin runs were bit-identical across all 26 tasks; the lexical baseline was bit-identical on 3 of 26.
Agent integration
60+ tools
Kin exposes semantic operations over MCP so any compatible agent can use the graph directly.
Public repo sync
GitHub-backed
Version badges use live GitHub metadata during deploys, with visibly labeled, date-verified fallbacks for offline builds.
Benchmark figures are scoped to one pre-registered 26-task Go suite on one model and runtime. They measure retrieval and localization, not patch success.Read the public proof summary.
Layer 1: Local Semantic Substrate
Lead with the local open-source stack: semantic truth in kin, graph storage in kin-db, transparent file projection inkin-vfs, and editor UX through kin-editor.
Kin
Semantic system of record
The open-source semantic VCS built in Rust. The entity graph is the truth; files, diffs, and review flows become compatibility projections on top.
Pre-registered n=26 evaluation: Kin leads symbol, span, and line F1; file F1 is a statistical tie.
KinDB
Graph database engine
The graph, indexing, and retrieval substrate below Kin. Purpose-built in Rust for code-aware tools, with static types, full-text search, and vector search.
kin-vfs
Transparent file projection
The virtual filesystem layer that makes any editor or tool see normal files while the backing truth stays semantic and blob-backed. No editor fork required.
This is the replacement for editor-fork thinking: the projection layer is generic.
Kin Editor
VS Code extension
The lightweight VS Code extension for entity browsing, semantic search, trace, review, rename, and graph-backed navigation. MCP-first, CLI fallback.
The extension plus kin-vfs is the current editor story.
Coming Soon
Newly public supporting repos that are part of the wider Kin ecosystem story, but not yet presented here as full flagship product surfaces.
kin-infer
Pure-Rust transformer inference
Universal transformer inference in pure Rust, spanning encoder and decoder architectures for local model execution inside the Kin ecosystem.
kin-blobs
Content-addressable blob store
The SHA-256 blob store behind Kin content, with Git-style sharding and ownership of the canonical Hash256 type used across the stack.
kin-search
Lightweight BM25 text search
Code-aware text search and ranking primitives for the ecosystem. A smaller public surface today, but a useful emerging building block alongside the core stack.
No Forks Required
The current Kin story is intentionally cleaner than the older material. Any MCP-compatible agent connects through Kin's built-in MCP server. Any editor can read projected files through kin-vfs. VS Code gets a focused extension for graph-native commands and navigation. The graph stays central; the surfaces stay replaceable.
Current access points
Layer 2: Hosted Collaboration
KinLab is the proprietary layer above Kin. It should be described as the collaboration and control plane above the local semantic substrate, not as a full GitHub replacement today.
KinLab
Hosted collaboration layer
The private product surface above Kin for shared semantic review, org-wide search, domain browsing, activity, and control-plane workflows. Functional and improving, not a GitHub replacement yet.
Open / proprietary boundary
Everything on the developer machine stays Apache-2.0. KinLab is the commercial hosted layer. Local semantic truth is the adoption wedge. Hosted collaboration is the business.
Layer 3: Secondary Systems Track
Longer-horizon research comes last. It matters, but it should never displace the active local substrate plus hosted collaboration story.
Kin Kernel
Trusted semantic control plane
Research into what process management, policy, and inter-actor coordination look like when semantic scopes are first-class instead of bolted on to file descriptors and PIDs.
Kin OS
Semantic-first runtime model
Long-horizon operating-system research for a world where semantic truth, not the filesystem, is the native substrate for software and automation.
Kin Hardware
Capability-aware hardware boundary
Exploration of hardware that self-describes capabilities and participates in semantic coordination, rather than flattening everything into generic byte streams.
Browse the public repos
The public Kin repos live under firelock-ai. This page is aligned to the current public topology and GitHub tag state rather than the older fork-era product map.