DevHeal Research / DH-ADOM

Contracts you can inspect directly.

Read the supplied JSON Schemas, delegation template, lifecycle models and API outline without unpacking the full release.

White paper 1.1 · Publication package 1.1.1 · 7 October 2026

DH-ADOM Agent

Required top-level fields: agent_id, name, type, parent_agent, feature, intent, permissions, autonomy.

Open JSON Schema →

DH-ADOM Audit Event

Required top-level fields: event_id, timestamp, actor, action, resource, result.

Open JSON Schema →

DH-ADOM Delegation Contract

Required top-level fields: apiVersion, kind, metadata, spec.

Open JSON Schema →

DH-ADOM Feature

Required top-level fields: feature_id, name, owner_agent, intent, scope.

Open JSON Schema →

Validation scope.

These schemas validate the supplied structural contract. Several nested objects remain permissive, and numeric budgets do not yet carry minimum constraints. Schema acceptance alone is not authorization or full conformance. Apply policy checks and runtime enforcement independently.

Delegation and lifecycle.

Delegation contract / YAML

API outline.

The OpenAPI document sketches agent registration, delegation and audit retrieval. It does not define complete request/response schemas, authentication or a running service.

OpenAPI 3.1 outline / YAML

Diagram

100%