Library Guides

Operate a Predictable Agent Team (Engineers)

Set Up Persistent Memory and Metrics

Give your agent team persistent memory and real signal detection — wiki-backed state, XmR control charts, and evidence that agents act on changes, not noise.

Send a Memo or Update a Storyboard

Communicate across your agent team and keep storyboards current — without managing the wiki infrastructure yourself.

Chart a Metric and Check Variation

Know whether a metric has actually changed or just varied — natural process limits and Wheeler's detection rules separate signal from noise.

Bridge Conversations to the Agent Team (Builders)

Bridge a Threaded Channel to the Agent Team

Threaded-channel adapters share an intake skeleton, callback registry, durable thread state, and resume-trigger contract — one library, every channel.

Enable Agents on Every Surface (Builders)

Give Agents and Humans the Same Interface

Capabilities that work on every surface — one presenter, one contract, and one formatter shared between CLI and web, with no separate integrations.

Add a Capability to Both Surfaces

Ship a feature to terminal and browser at once — one presenter, one registration, both surfaces.

Ground Agents in Context (Builders)

Give Agents Typed, Retrievable Knowledge

Agents that can answer relationship questions, look up context, and find related content — backed by typed knowledge infrastructure with no external engines.

Query a Knowledge Graph

Answer relationship questions from an RDF graph index — triple patterns and type-filtered listings, no join logic or SPARQL endpoint.

Look Up Context Fast

Retrieve exactly the context you need from a JSONL-backed index — prefix, limit, and token-budget filters without loading everything into memory.

Resolve a Resource

Give agents rich, typed context from a resource identifier — provenance, access control, and RDF content instead of raw files.

Search Semantically

Find related content by meaning, not keywords — ranked results from a vector index without standing up a vector database.

Integrate with the Engineering Standard (Builders)

Turn Standard Definitions into Queryable Data

Engineering standard YAML becomes queryable data — derive skill matrices, behaviour profiles, and agent configurations programmatically from a single load.

Derive a Skill Matrix or Agent Profile

Go from discipline, level, and track to a complete skill matrix or agent profile — without parsing YAML by hand.

Keep Service Contracts Typed (Builders)

Keep Types Synced with Proto Definitions

Proto changes flow through to JavaScript types, MCP tools, and service endpoints automatically — one source of truth from definition to runtime.

Expose a Proto Method as an Agent Tool

A new gRPC method becomes an agent tool with one config entry — no glue code, no hand-written schema.

Ship a Service Endpoint

Ship a gRPC service with typed contracts, authentication, retries, and health checks — without reimplementing transport.

Run a Predictable Platform (Builders)

Manage Service Lifecycle from One Interface

Services that stay running and problems that surface before they escalate — supervision and observability from one interface.

Start, Stop, or Check a Service

Start, stop, restart, check status, and read logs through one interface — without remembering each service's specific incantation.

Add Observability

Structured, machine-readable logs and traces without configuring a logging framework — drop in a log line or trace span and it works.