Specification

Protocol & Tier Details

A closer look at the structured protocol definition, tiered requirements and compliance invariants that underpin every FemtoClaw implementation【254469092789682†L3-L29】.

Protocol

Structured JSON Tool Calls

The FemtoClaw protocol defines a strict JSON schema for tool calls. The authority layer never interprets free‑form natural language; instead, generative inference must produce explicit tool call objects that specify the tool name and its arguments【254469092789682†L3-L18】.

{
  "tool_call": {
    "tool": "shell",
    "args": {
      "bin": "ls",
      "argv": ["-la"]
    }
  }
}
          
Tiers

Enterprise vs Reference

FemtoClaw defines two normative tiers. The Enterprise tier (SPEC 1–40) outlines the core safety and deterministic runtime requirements for production deployments, while the Reference tier (SPEC 41–60) specifies distributed clustering, gossip synchronization and high availability models【254469092789682†L19-L23】.

  • Enterprise: Deterministic execution, strict capability gating, WAL durability and observability.
  • Reference: Distributed node clustering, gossip synchronization, hierarchical state replication and failover strategies.
Invariants

Compliance Requirements

To earn compliance certification, a FemtoClaw implementation must conform to the strict JSON gate: no natural language execution is permitted in the authority layer. All tool calls are validated against the specification and no unspecified behaviour is allowed【254469092789682†L25-L29】.

These invariants ensure that every deployment remains predictable, auditable and safe, regardless of the underlying inference model or infrastructure.【254469092789682†L25-L29】.