SYMBIOCLAW™ · KHAICLAW, LLC · DEMONSTRATION ENVIRONMENT · v0.3 · BROOMFIELD CO · U.S.-OWNED · U.S.-OPERATEDBUILD kc23ref · 2026-07-01
SymbioClawSymbioClawagentic, stack-agnostic Micro-Factory Operating System (MFOS)

SYMBIOCLAW™ · AGENTIC, STACK-AGNOSTIC MICRO-FACTORY OPERATING SYSTEM (MFOS)

The U.S. cannot surge additive production across distributed suppliers because evidence does not travel.

KhaiClaw makes additive manufacturing evidence portable, signed, and verifier-ready across defense supplier networks.

A single prime can print a part. A supplier network cannot prove it. Build records sit in MES, PLM, QMS, and ERP systems that do not reconcile, do not sign, and do not survive a stack change, supplier transition, air-gapped review, or CDRL handoff. SymbioClaw™ gives the defense industrial base a portable, signed Build Dossier layer that travels with the part.

Live demo available on request. Synthetic part KC-DEMO-001.
Real Ed25519 verifier. Real tamper test. Real chain check.

MFOS, a SymbioClaw™ platform product.

BUILD DOSSIERexported · portable · signedNANOCLAWbounded edge agent · execution-onlySYMBIOCLAW™governance plane · deployedshared foundation: khaiclaw-protocol

2 components · 1 protocol · 1 portable artifact

SymbioClaw™
governance plane deployed
NanoClaw
bounded edge agent deployed
Build Dossier
signed export portable

A part is not a proof.

The proof is a Build Dossier - signed, hash-linked, verifier-ready, portable across stacks.

PROBLEM 01

Surge production breaks supplier networks

When DoW needs to surge an additive part across multiple suppliers, every supplier's evidence ends up in a different MES, PLM, QMS, ERP, or hand-built spreadsheet. The prime spends weeks reconciling. The program office takes months to qualify. The asset is late to the fleet.

Today: weeks of reconciliation per part. Months to qualify across vendors.

PROBLEM 02

Evidence does not survive boundaries

Build records bound to one stack do not move. They do not survive a supplier transition, a stack migration, air-gapped review at a depot or shipyard, or CDRL handoff to a program office. The evidence is trapped in the tool that captured it.

Today: every stack change is an evidence-loss event.

> SymbioClaw™ is the layer that makes evidence portable.

BASIS OF NEED

Six gaps SymbioClaw™ closes for the U.S. defense industrial base

Each gap maps to a SymbioClaw™ surface. Cards auto-expand one at a time on scroll and stay independently expandable when clicked.

SymbioClaw™'s Security Evidence Closure assembles CycloneDX SBOM, AIBOM, SLSA provenance, dual-FIDO2 receipts, DDIL proof, red-team artifacts, DFARS clause map, EAR/ITAR triage, MITRE ATLAS, ATT&CK for ICS, and NIST 800-218A evidence. Built to support SPRS, NIST 800-171, DFARS 252.204-7012, and CMMC L2 assessment — a statement of posture, not a claim of certification against those frameworks.

MFOS SURFACE → Security Evidence Closure (MOC-0003)

> Six gaps. One protocol. One portable dossier.

ARCHITECTURE

One protocol. Two deployed components. One portable artifact.

BUILD DOSSIERsigned · hash-linked · verifier-checkable · stack-neutral
exported · portable · signed
NANOCLAWbounded edge agent - execution-only, signed receipts
deployed at supplier sites
SYMBIOCLAW™governance plane - knowledge to KMAPs to receipts to audit
deployed as governance plane

shared foundation library: khaiclaw-protocol (schemas · signing · identity · receipts)

MFOS gives Foundry, AIP, ShipOS, Warp Speed, primes, and suppliers a portable signed Build Dossier layer for distributed manufacturing evidence, additive production provenance, QA receipts, MOC history, and acceptance artifacts that survive stack changes, supplier transitions, air-gapped review, and CDRL handoff.

THE CLAW MEMORY SPINE

How the claws remember - and where memory is not allowed to go

SymbioClaw™ treats memory as a governed boundary, not a convenience. Agent memory that could reconstruct customer data, facility telemetry, process traces, or CUI stays local to the site that produced it: encrypted at rest, per-tenant, governed-egress-only.

CLASS 01 · EDGE-BOUND

MFOS platform memory stays at the edge

Any MFOS memory that references or could reconstruct customer data lives at the site where the data originated. Encrypted at rest with keys KhaiClaw does not hold. Per-tenant isolation. Only approved, sanitized extracts leave through governed egress.

per-tenant · encrypted · governed egress only

CLASS 02 · REFERENCE

NanoClaw reference clones do not remember

The bounded edge agent carries no memory subsystem, no runtime binding, and no customer-data access. It executes a signed envelope and emits signed receipts. Nothing accumulates.

no memory · no bindings · no write access

CLASS 03 · SUBSTRATE

One database per site, coordinated by message

The edge substrate is local-first: one governed store per tenant/site, with agents coordinating through structured, signed message-passing rather than shared state. The dossier, not the database, is what travels.

local-first · signed message-passing · no shared pool

Public boundary: this page describes memory doctrine, not implementation. Substrate internals, key custody, schemas, and adapter source stay in controlled-access repositories.

SOFTWARE IN ACTION

How the MFOS Dashboard functions in the demo

The Dashboard is the inspection surface for the working MFOS loop, not the governed evidence authority. It shows synthetic part KC-DEMO-001 moving from controlled intent to signed receipt chain, verifier result, tamper test, and Build Dossier export.

01 · INGEST

Approved work becomes a KMAP

The demo starts with governed work instructions and an evidence plan that MFOS can dispatch without giving an agent release authority.

02 · DISPATCH

MFOS issues a bounded envelope

Scope, interlocks, authority limits, and required evidence travel together as a signed task envelope.

03 · WITNESS

NanoClaw emits receipts

The edge witness records action receipts, hashes them into sequence, and keeps execution separated from approval.

04 · VERIFY

The verifier checks the chain

The Dashboard exposes verifier status and a deliberate tamper failure so evaluators can see the math break when evidence mutates.

05 · EXPORT

Build Dossier leaves the stack

The export profile packages the evidence into a portable dossier for a prime, program office, offline reviewer, or future stack.

HEADLINE CAPABILITY

Agentic Dossier Enablement

The Dossier-to-Agent Converter turns conventional manufacturing knowledge into governed KMAPs that MFOS dispatches and NanoClaw executes. Knowledge in. Receipts out. Dossier exported.

STEP 01 - INGEST

Operator knowledge becomes a deterministic KMAP.

Source documents are ingested, hashed, and converted into a KMAP, task graph, skill map, and evidence plan. Blocking gaps stay visible until human approval or override.

Source hashed. KMAP drafted.

STEP 02 - DISPATCH

MFOS dispatches bounded work envelopes.

MFOS issues a bounded envelope to a skill or device. Scope, evidence requirements, autonomy level, interlocks, and authority limits are part of the envelope.

Envelope signed. Dispatched.

STEP 03 - VERIFY

Every action emits a signed receipt.

NanoClaw and supervised devices emit signed Ed25519 receipts. Each receipt is bound to the previous through canonical JSON hashing. The dossier verifies offline.

Receipt chain verified.

> Agents propose. Humans release.

Named platforms are referenced as export and profile targets only. No partnership, integration, certification, or endorsement is implied unless expressly stated.

WHO WE SERVE

SymbioClaw™ sits in three workflows

DEFENSE PRIMES

Stack-neutral dossier handoff

Foundry, AIP, ShipOS, and Warp Speed primes need an evidence layer that survives stack changes and supplier transitions.

Foundry · AIP · ShipOS · Warp Speed

SUPPLIERS AND DEPOTS

Audit-ready evidence at the edge

Qualified suppliers, awardees, shipyards, and depot AM cells need to produce evidence the prime and program office can accept.

Navy AM COE · DLA JAMA · AFWERX · Depot AM cells

VERIFIER INTEGRATORS

Protocol consumers and reviewer tooling

Independent reviewers, ATO assessors, program evaluators, and offline verifier integrations consume the dossier without operating MFOS.

khaiclaw-protocol · offline verifier · reviewer tooling

POSTURE & PROOF

Technical claims you can verify in a briefing

Every line below is a working claim in the demonstration environment, exportable as a dossier artifact, and described in SymbioClaw™ technical documentation. Designed to support assessment frameworks, not certified against them unless explicitly noted.

CRYPTO · ED25519Real Ed25519 signing on every action receipt. Not stubbed.
CRYPTO · ECDSA-P256ECDSA-P256 signatures on Build Dossier DD-BD-000002.
HASH · CANONICAL JSONJCS canonicalization. Reproducible bytes across stacks.
HASH · MERKLE20-leaf Merkle root over dossier evidence classes.
VERIFY · 29/29 CHECKSverify.py runs 29 of 29 checks against the v0.4 dossier.
VERIFY · TAMPER TESTtamper_test.sh demonstrates verifier failure on mutated chain.
EVIDENCE · SBOM 1.6Full SBOM in CycloneDX 1.6 format.
EVIDENCE · AIBOMAIBOM declared for AI-bearing components.
EVIDENCE · SLSASLSA in-toto provenance attestations bound to dossier.
IDENTITY · DUAL FIDO2Dual-FIDO2 receipts for high-consequence approvals.
OPS · DDIL 26 HOURDDIL-2026-Q2-03: 26 hours offline operation proven.
RED TEAM · RTX-Q2Independent red team artifacts included in dossier.
ATO · cATO MEMOATO Path Memo with cATO posture. Designed to support, not certified.
COMPLY · NIST 800-171Mapped to NIST 800-171 controls. Assessment-supporting.
COMPLY · 800-218ASecure software development practices applied.
COMPLY · DFARS MAPDFARS 252.204-7012 clause map included.
COMPLY · EAR/ITARExport control triage applied to dossier contents.
THREAT · MITRE ATLASAdversarial ML threats mapped.
THREAT · ATT&CK ICSOT/ICS threats mapped.
CDRL · INDEXCDRL index bound to evidence classes.
FOCI · U.S.-OWNEDU.S.-owned; no foreign ownership, control, or influence. FCL-eligible; SF-328 available on request.
DEMO · KC-DEMO-001Synthetic part KC-DEMO-001 runs the full loop in demonstration environment.

Each claim is runnable. Request a briefing to run it.

COMPLIANCE & POSTURE

KhaiClaw LLC is a U.S.-owned, U.S.-operated company with no foreign ownership, control, or influence. SymbioClaw™ is FCL-eligible; a current SF-328 is available to qualified reviewers on request. Compliance items are stated as posture, not certification - assessment-supporting unless explicitly noted.

U.S.-ownedU.S.-operatedno FOCIFCL-eligibleSF-328 on requestNIST 800-171 mappedDFARS 252.204-7012EAR/ITAR triage
IP & PATENTS

SI-RaaS is the subject of U.S. Provisional Patent Application No. 64/042,646 (filed 2026-04-17; patent pending), covering a memory-spine architecture for embodied AI: persistent context that travels with the agent across robots, edge devices, and micro-factory nodes, with cross-embodiment continuity and reviewable behavioral data products. A foreign filing license was granted 2026-06-16, preserving the global filing path subject to export-control review.

SI-RaaS provisionalApp. 64/042,646patent pendingforeign filing license grantedSymbioClaw™ USPTO 99774292

Launch the demonstration environment

Walk through MFOS v0.3 against the synthetic part KC-DEMO-001. Eleven dashboard modules. Real signing. Real verifier. Real tamper test. Notional data; intended for evaluation.

MFOS demo shell v0.3 · Build Dossier schema v0.4 · synthetic part KC-DEMO-001.

Open demo.khaiclaw.com

Demo access is included in every technical briefing.

Founder

Eric Hammond, Founder of KhaiClaw LLC

Eric Hammond

Founder, KhaiClaw LLC

Eric Hammond is the founder of KhaiClaw LLC and the architect of SymbioClaw™, the agentic Micro-Factory Operating System (MFOS). He is a chemical and systems engineer with more than twenty years in engineering, procurement, and construction (EPC) and midstream energy — including engineering-management and senior-process-engineering roles on capital projects up to $120M, plus international field engineering.

That work was built on the same primitives SymbioClaw™ makes portable: signed evidence, audit trails, management-of-change history, and acceptance artifacts that have to survive handoffs and scrutiny. KhaiClaw is an engineer-to-systems-engineer pivot — turning EPC-scale evidence discipline into a governed, stack-neutral Build Dossier layer for the U.S. defense industrial base.

He holds an MSc in Sustainable Business Leadership (University of Leeds) and a BS in Chemical Engineering (Montana State University). KhaiClaw is a solo-founded, U.S.-owned and U.S.-operated company with no foreign ownership, control, or influence.

Connect on LinkedIn →

Contact

Request a technical briefing

SymbioClaw™ briefings are scoped to qualified defense and advanced-manufacturing reviewers. Reach the founder directly to schedule a technical walkthrough of the MFOS governance plane, NanoClaw edge agent, and the signed Build Dossier.

Email eric@khaiclaw.com

Do not submit CUI, classified information, or ITAR/EAR-controlled technical data through this site or by email. Public demonstrations use synthetic, notional data only.