DEVELOPER MAP

A small core with explicit trust boundaries.

The TypeScript monorepo keeps framework-independent protocol packages separate from applications. Public product claims follow the same reviewed implementation frontier.

Strict TypeScript · ESM · Node.js 22+

START LOCALLY

pnpm install
pnpm test
pnpm --filter @verimand/cloudops-demo dev

SEMANTIC PIPELINE

01MANDATE → ATTENUATE
02GRAPH → DISCOVER → VALIDATE
03RESOLVE → RESERVE → BIND
04DERIVE → VERIFY
05APPLICATION → EXECUTED | BLOCKED

IMPLEMENTATION STATUS

01Monotonic attenuation

Independently reviewed

02Authority Graph, discovery, validation, RESOLVE

Independently reviewed

03Stateful reservations + hierarchical budgets

Independently reviewed

04Revocation, binding, DERIVE, semantic Grant, VERIFY

Built · review pending

05CloudOps end-to-end application

Proof of Value

06Signed grants, Receipts, persistence, MCP/A2A

Planned

PACKAGE BOUNDARIES

Applications may depend on packages. Packages may not depend on applications.

Protocol, schemas, attenuation, Authority Graph, reservations, decisions, grants and verifier code remain framework independent. The website describes the architecture; it is not a source of authority semantics.

Every security feature requires tests. Every semantic change requires an ADR.

INTEGRATION DIRECTION

TODAY

Local semantic reference

Deterministic TypeScript APIs, JSON Schema contracts, conformance suites and in-memory state for the Proof of Value.

Repository implementation

PLANNED

Portable enterprise integration

Cryptographic grants, persistent state, identity integrations, MCP/A2A bindings and cloud adapters.

No provider selected