Ekur — one stack beneath everything we build.

Deployable edge nodes

Ruggedised, self-contained units — compute, local model serving, sensor ingestion, and the trust harness in one enclosure — sized in tiers.

Mesh & reachback fabric

Neighbouring nodes exchange observations peer-to-peer over a self-healing mesh, so the picture survives the loss of any node or link.

Adaptive sensor ingestion

One common pipeline connects to the feeds your environment already has, through versioned, signed connectors. Sources are authenticated on arrival, normalised, and tagged.

Explainable, actionable outputs

Every indicator an operator sees carries what was detected, which sources contributed, and a confidence score computed from a signed, hash-linked chain of custody.

Anshar

What you believe is happening vs. what is

The core dysfunction in most organisations is the gap between documented intent and measurable reality — and when things go wrong, no way to tell whether the failure was policy, operations, reporting, or structure. Anshar closes that gap by treating the boundary conditions between units of work — the points where responsibility is handed off — as the primary design objects.

A zone is a bounded operational space with one goal and two boundary conditions. The exit condition of one zone becomes the entry stake of the next, forming a chain of contractual handoffs; a message formally signals each crossing. You cannot manage what you cannot measure, and you cannot measure what you have not defined — Anshar makes your operations definable.

Zones bound. Policies govern. Conops delivers. Reporting measures.

A small set of patterns scales to a whole enterprise

Kittu

Calibrated trust, not maximal trust

The goal is reliance matched to a system's actual, demonstrated trustworthiness — because over-reliance and under-reliance are both failures. A dependable system nobody can interpret invites under-reliance; a polished interface over an undependable system invites dangerous over-reliance. Kittu is built to deliver, and to demonstrate, both sides: objective dependability and the affordances that let you perceive it accurately.

Every trust claim is an assurance case — claim, argument, evidence — bound to exactly one policy with an explicit threshold and owner. A claim is satisfied only when the measured outcome meets the threshold and the evidence chain validates: every signature verifies, no hash link is broken, no evidence has expired. Never on a passing number alone.

Nine components of trustworthiness

Each carries its own policy, claim, measurable outcomes, and evidence chain — and each maps to the NIST AI RMF trustworthiness characteristics, so the dossier cross-walks to recognised governance.

The Trust Harness: never trust, always verify

The same claims, policies, and provenance move to inference time. The harness is a reference monitor for trust: nothing an agent produces — plans, messages, tool calls, outputs — is trusted by default. A checkpoint sits at every boundary, and delegated authority can never exceed the authority that delegated it.

Nusku

Declare centrally. Reconcile locally. Report by exception.

A distributed intelligence fabric succeeds or fails on a problem that is neither sensing nor inference: operating the fleet. Hundreds to thousands of edge nodes — carried by teams, mounted on vehicles, embedded in autonomous platforms, or bolted to poles — must be enrolled, configured, kept healthy, updated, and recovered when they fail, across intermittent, contested, and bandwidth-poor links. Doing this by hand does not scale past a handful of nodes; doing it with a conventional cloud device-management service violates the sovereignty, classification, and disconnection constraints these fabrics live under.

Nusku is Enkidu's answer: a sovereign, self-hosted control plane, and the third foundational framework of the stack. To the established premise — determinism where it matters, reasoning where it helps — Nusku adds its own corollary: declaration where it scales. Fleet state is declared, signed, and reconciled by pull, so a node that has been dark for a day converges to the same state as a node that never lost its link.

One component at every tier

Nusku rides the same bearers as the data plane — with its own, strictly smaller traffic class. The hub is the unit of autonomy: a cluster cut off from the centre continues to reconcile, monitor, and remediate locally. And distribution follows the fabric: a 2 GB model update to a 40-node cluster costs the reachback link one transfer, not forty.

Nusku's authoritative record of every managed node — identity, hardware tier, installed versions, bound policies, current health, desired state. The twin is what the fleet operator sees; the node is what exists in the field. Operators and the event engine reason over twins, never ad-hoc queries to the field.

Six load-bearing invariants

They hold everywhere Nusku runs — because the control plane must be as disciplined as the fabric it operates.

Shedu

Not a future problem. A present recording problem.

Every promise the Enkidu stack makes rests, in the end, on cryptography: Kittu's chain of custody is signatures, Nusku's artifact admission is signatures, every mesh link and reachback spoke is a key exchange. Against a cryptanalytically relevant quantum computer, today's public-key primitives break outright — and the harvest now, decrypt later attack means traffic recorded off a link today can be read retroactively the day such a machine exists. For a fabric carrying Protected B data with multi-decade sensitivity, the adversary needs no quantum computer now — only patience and storage.

The urgency is asymmetric: a signature forged in the future does not falsify the past, but a key exchange broken in the future retroactively exposes everything it protected. That is why Shedu's first wave is hybrid key establishment on links — and why the mandate horizon is not the quantum computer's arrival date, but the recording adversary's patience, subtracted from your data's lifetime.

One primary, one reserve — per function

Finalised NIST standards, deployed in hybrid constructions, with a designated backup on different mathematics behind every primary — so a cryptanalytic surprise is a policy flip, not a crisis program.

Four binding points, zero new components

Shedu is a substitution of cryptographic substance, not an addition of moving parts. It changes what every existing handshake, signature, and boot check is made of.