TalvikInfrastructure for portable, governed AI context.
Talvik builds infrastructure around MAK4I, an open protocol for portable, governed and reusable AI context across AI tools and agents. A working reference implementation now exists.
The protocol for not rebuilding what your AI already built.
- Open protocol
- MIT licensed
- Working reference implementation
- Developer Preview
Current Status
Developer Preview
MAK4I is under active development with a working reference implementation covering the core protocol workflow. Here's exactly where each part stands.
- Protocol specification
- Active development
- Defines portable context structures, lifecycle behavior, provenance, versioning and interoperability requirements.
- Reference implementation
- Working MVP
- A functional MAK4I reference implementation exists and is being tested against the evolving specification.
- MCP integration
- Working in the MVP
- MAK4I can be accessed through MCP as part of the reference implementation today. Broader interoperability work is ongoing.
- Developer validation
- Beginning
- Talvik is preparing MAK4I for testing by developers, AI implementation teams and early design partners.
Why Talvik?
Infrastructure for AI context that travels
Talvik is building infrastructure that lets AI systems reuse knowledge, preserve context, and carry decisions across tools, agents and environments — with governance over how that context is used.
MAK4I is the open protocol at the center of that work. Talvik develops the protocol in the open and builds commercial infrastructure and services on top of it.
The Problem
Knowledge doesn't travel with you
As teams adopt more AI tools, the same work gets regenerated again and again.
AI tools retain knowledge differently, with no shared standard.
Context becomes trapped inside individual platforms.
Teams repeatedly regenerate artifacts instead of reusing them.
Knowledge continuity is difficult to maintain across tools.
Existing workflows rarely encourage reuse before regeneration.
Why Now?
Fragmentation is still the default
AI adoption is accelerating, but knowledge remains fragmented across tools. Teams repeatedly recreate context, decisions, workflows, and artifacts because each platform generates and retains them differently. MAK4I is an open protocol for portable, governed reuse — and a working reference implementation now exists to prove the approach.
Meet MAK4I
Reusable AI Artifacts
MAK4I standardizes reusable AI knowledge. Memory is only one supported artifact type — MAK4I covers far more.
Core Principle
Check Before Create
MAK4I promotes reuse before regeneration — search first, adapt when possible, and create only as a last resort.
- 1
Need something
- 2
Search existing artifacts
- 3
Reuse
- 4
Adapt
- 5
Only create when nothing suitable exists
What Talvik Builds
Commercial infrastructure around an open protocol
Talvik is developing commercial infrastructure around MAK4I for organizations that need portable and governed AI context across tools, agents and environments. The items below are planned or in development — not yet generally available.
Managed MAK4I infrastructure
A hosted runtime for teams that don't want to operate the protocol themselves.
Context governance
Policy, access control and approval workflows over shared AI context.
Administration & policy management
Central controls for how context is created, reused and retired across an organization.
Observability & audit
Visibility into what context was retrieved, by which client, and why.
Storage integrations
Customer-controlled storage, or Talvik-managed storage options.
Deployment & support
Private, hybrid and self-managed deployment support, plus implementation services.
No product revenue, production integrations or enterprise deployments exist today. These are the intended commercial direction, not shipping products.
How It Works
Open protocol. Commercial infrastructure.
The protocol and the company are deliberately separate.
Open protocol
MAK4I
An open interoperability protocol defining how AI context is represented, exchanged, versioned, governed and reused across systems. MIT licensed and independently implementable — Talvik's implementation is not the definition of the protocol.
Commercial infrastructure
Talvik
The company developing enterprise infrastructure, managed services and tooling around MAK4I — and the current steward of the protocol's development.
High-Level Architecture
Deployment-neutral and storage-independent
A common layer that AI tools read from and write to. MAK4I does not require any specific cloud, orchestration platform, database or storage technology.
AI Tools & Agents
MAK4I Protocol
Represents, governs, versions and resolves reusable AI context on behalf of connected AI tools.
Portable AI Context
Decisions, architecture, workflows, history and more — in a standard, portable form.
Storage adapters
Where context is persisted — pluggable and storage-independent, not tied to any database or vendor.
Potential deployment models
- Talvik-hosted runtime with customer-controlled storage
- Fully Talvik-managed cloud deployment
- Customer-managed cloud deployment
- Private / on-premises deployment
- Hybrid deployment
- Fully self-managed MAK4I implementation
These are architectural and commercial deployment models, not a list of currently available products. Integrations shown above are illustrative of the target architecture; see the roadmap for what is built versus planned.
Where MAK4I Fits
Complementary to MCP and agent protocols
MAK4I is an open protocol — a proposed interoperability layer — that sits alongside connectivity standards rather than competing with them.
MCP
Connects AI systems to tools and data.
Agent-to-agent protocols
Connect agents to other agents.
MAK4I
Provides a portable context layer so AI systems can reuse what has already been learned, approved or produced.
In the current reference implementation, MAK4I is reachable through MCP — one integration path among several.
Roadmap Preview
Where MAK4I is headed
- 1
Phase 0 — Foundation
- 2
Phase 1 — Protocol Specification
- 3
Phase 2 — Reference Implementation
- 4
Phase 3 — Reusable Artifacts
- 5
Phase 4 — Hosted Registry
- 6
Phase 5 — MCP Integration
Open Source
Open protocol, commercial infrastructure
MAK4I is an open protocol with a working reference implementation. Talvik builds commercial infrastructure and services on top of it.
Open protocol
MAK4I's specification is developed in the open and is independently implementable.
MIT licensed
Free to use, adapt, and build on without restrictive licensing terms.
Community driven
Direction is shaped by feedback from the developers who use it.
Developer Preview
Interested in testing MAK4I?
Talvik is beginning developer and early-adopter validation of the MAK4I reference implementation. Public source access will follow when it's release-ready — until then, get in touch.