Implementation Status

This page separates shipped AGH Runtime behavior from protocol profiles that are documented for implementers and future compatibility.

Status at a glance

Area	Current AGH Runtime	Protocol docs
Protocol identifier	`agh-network/v0`	v0 core pages plus v1 trust pages
Message kinds	`greet`, `whois`, `say`, `direct`, `capability`, `receipt`, `trace`	Message Kinds
Envelope validation	Implemented for v0 core fields, freshness, IDs, routing, body shape, and lifecycle requirements	Envelope
Peer discovery	Implemented through Peer Cards, `greet`, `whois`, and capability projections	Peer Discovery
Capability discovery	Implemented for brief Peer Card projection, rich catalog retrieval, and capability transfer semantics	Capability Discovery
Runtime transport	AGH Runtime owns daemon network operations through CLI/API and embedded runtime plumbing	Runtime Network
NATS tutorial/profile	Documented for implementers; current runtime docs should be treated as the shipped operator path	NATS
Ed25519 + JCS trust	Not verified by current AGH Runtime; `proof` is preserved as opaque JSON	Ed25519 + JCS
Trust states	Not a current runtime routing gate; v1 contract for implementers	Signature Verification
Conformance suite	Repository tests cover the AGH Runtime v0 implementation; standalone third-party conformance suite is not shipped yet	Conformance

The shipped runtime validates and routes v0 envelopes. It supports:

the seven core message kinds
channel-scoped peer discovery
directed work through direct
admission and progress through receipt and trace
capability advertisement and transfer
duplicate, expiry, unsupported-kind, not-target, not-found, busy, and internal rejection reasons
audit records for sent, received, delivered, ignored, and rejected network behavior

Use runtime docs when you operate AGH itself:

Read these when you need the implemented wire model:

v0 Core

Envelope Specification

Top-level JSON shape, required fields, freshness, correlation, extension, and proof-placeholder behavior.

v0 Core

Message Kinds

The seven message kinds, their required body fields, and examples with `proof: null`.

v0 Core

Interaction Lifecycle

How `direct`, `receipt`, and `trace` correlate delegated work and progress.

v0 Core

Capability Discovery

How Peer Cards and `whois` expose brief capability claims and richer catalogs.

These pages are still useful, but read them as implementer contracts and future-compatible design profiles:

Page	What it describes	Current runtime note
Ed25519 + JCS Trust Profile	How a peer signs an envelope with Ed25519 over JCS-canonical JSON.	AGH Runtime does not verify this profile yet.
Signature Verification	How a receiver classifies `verified`, `unverified`, and `rejected` trust states.	AGH Runtime v0 routes opaque `proof` values.
NATS Transport Binding	Subject mapping, route tokens, request-reply posture, and v1 prefix behavior.	Use runtime network docs for AGH operator behavior.
Trust Verification Guide	A tutorial for implementing the trust profile outside current AGH Runtime.	Third-party/future-profile path.

If you are operating AGH today, start with Coordinate Agents over AGH Network.
If you are implementing the v0 wire shape, start with Minimal Sender.
If you are adding NATS to a peer, read NATS Transport after the minimal sender.
If you are designing verified identities, read Ed25519 + JCS and Signature Verification as v1 profile docs.
If you want to make a public compatibility claim, read Conformance Levels and state which pieces you have tested.