MatKaiOS Master Map

What the company appears to be: MatKaiOS Master Map is a self-reported diagnostic tool for inspecting the structure of a local-first operating and coordination platform for governed AI agents called MatKaiOS. It is described as an external, zero-write, evidence-based system that maps MatKaiOS without executing or modifying it.

What changed: The author states that this project emerged from long-term experimentation with AI agents and their governance within a local development environment. A previous version (v1) was replaced by v2, which is described as an external diagnostic tool built around principles such as physical separation between the tool and target system, zero-write verification, and bounded capture of Git snapshots.

Single most important open question: Is there any evidence that MatKaiOS has been adopted or used beyond the author's own development environment?

The description states that MatKaiOS Master Map is an external, zero-write, evidence-based diagnostic system for inspecting the structure of MatKaiOS. It is described as a tool that builds a verifiable view of the system from a controlled Git snapshot and the evidence found inside the repository.

It includes five primary foundations:

• External Zero-Write Foundation
• Facts & Evidence Foundation
• Source Authority Foundation
• Structural Anatomy Foundation
• Static Module Resolution Foundation

The author describes it as not being all of MatKaiOS, but rather a diagnostic instrument developed to understand, verify, and make better decisions about the evolution of MatKaiOS.

The description states that MatKaiOS Master Map was created to help observe and understand the system without modifying the system it is trying to explain. It evolved from an internal tool (v1) that became increasingly difficult to maintain as a reproducible and trustworthy representation of the current system.

The author notes that the goal is not to pretend that powerful agents are harmless, but rather to make capability, risk, authority, and responsibility visible so the human can make an informed decision. The project evolved from using natural language instructions to structured formats like Markdown and JSON, eventually leading to a runtime where identity, sessions, tools, providers, policies, memory, evidence, autonomy, and security boundaries are real parts of the system.

Not evidenced. The description does not specify target customers or ideal customer profiles beyond the author's own use case.

Not evidenced. There is no mention of pricing, revenue models, or commercial arrangements in the provided description.

The project was built using:

• ai-agents
• codex
• developer-tools
• git
• github
• github-actions
• javascript
• json
• markdown
• node.js
• npm
• ollama
• openai
• sqlite
• static-analysis

It uses OpenAI Codex for inspection, implementation, refactoring, testing, and static analysis. The author mentions using GPT-5.6 Sol for studying architecture and characterizing limitations.

The system follows principles such as:

• physical separation between the tool, target, store, and vault;
• bounded capture of Git targets;
• zero-write and no-drift verification;
• facts linked to evidence;
• deny-by-default policies;
• provenance and producer identity;
• deterministic manifests and receipts;
• derived structural anatomy without retaining raw source-code bytes;
• static reference resolution;
• explicit terminal states;
• fail-closed behavior;
• precise documentation of boundaries and non-claims.

Not evidenced. The description does not contain any data on revenue, customers, adoption rates, or usage metrics. It describes the project as a long-term effort built through experimentation and iterations, but provides no evidence of traction or market validation.

Not evidenced. There is no mention of competitors or competitive landscape in the provided description.

• The entire description is self-reported and unverified.
• No evidence of revenue, customers, or adoption beyond the author's own development environment.
• The project appears to be a personal experiment rather than a commercial product.
• The author states that the system being inspected (MatKaiOS) was not created in one week for this event, suggesting it is a long-term project with no clear commercialization path.
• The description mentions challenges such as maintaining AI-agent work sessions without losing intent or control of scope, indicating potential instability or complexity issues.

1. What specific problems does MatKaiOS solve for users beyond the author's own development environment?
2. How is the system currently being used or tested outside of the author's personal development setup?
3. Are there any existing users, partners, or customers who have provided feedback on the platform?
4. What are the plans for monetization or commercialization of MatKaiOS or Master Map?
5. Can you provide evidence of the system's performance or reliability in real-world scenarios?
6. How does the project plan to scale beyond a single developer's environment?