Dillweed Namespace Stack
A proposed trust and coordination layer for portable agentic systems — five-layer architecture for multi-party trust management, naming authority, revocation, and neutral governance.
Agent state can move across runtimes and administrative domains. Trust cannot move unless naming authority and attestation evidence move with it. The Dillweed stack is an architectural proposal for that missing layer.
Executive Summary
The Dillweed Namespace Stack is a proposed trust and coordination layer for portable agentic systems. As agents become persistent software entities capable of moving across runtimes, providers, and administrative domains, the missing infrastructure layer is no longer model capability — it is stable naming authority, authoritative resolution, durable registry truth, and neutral governance continuity.
The stack addresses this gap through a five-layer architecture designed for multi-party trust management, cross-domain agent interoperability, cryptographic attestation, revocation, and operational accountability — intentionally aligned with the PKI trust root architecture that underpins existing international identity standards including X.509.
Its neutrality thesis is structural: no major platform company can credibly operate a neutral multi-party coordination namespace. The domain dillweed.com has been under continuous single-owner operation since 1997 — an independent provenance that satisfies the structural condition required for a neutral naming authority layer.
Agent state can move across runtimes and administrative domains. Trust cannot move unless naming authority and attestation evidence move with it. The Dillweed stack is an architectural proposal for that missing layer.
Layered Architecture
The stack comprises five layers, each with a distinct authority boundary and a defined standards-relevant question it answers. Technical semantics are separated from governance authority; operational practice is separated from specification contracts; founding-phase stewardship is designed to evolve toward multi-party institutional models.
Namespace Standard — Naming Authority and Trust Framework
Defines the semantic identity layer: canonical namespace paths, persistent capability naming, long-lived authority boundaries, trust tier definitions, neutrality principles, and governance compatibility across relying parties and operators. Establishes the trust framework within which all resolution and attestation operates.
DillClaw Resolver — Authoritative Resolution with Trust Policy Enforcement
Defines authoritative resolution behavior: namespace lookup, relying party routing with trust policy enforcement, deterministic selection across trust tiers, traceable failure semantics, and resolver-side weighting of provisional versus attested tier declarations. Provides verifiable audit trails for resolution decisions.
Registry Specification — Authoritative Truth Substrate with Cryptographic Binding
Defines the authoritative data layer: cryptographically signed capability records using Ed25519 — consistent with the PKI trust root architecture underlying X.509 — durable append-only registration history, canonical metadata, revocation state with mandatory audit reason, mirror freshness semantics, and independent signature verification. Signed records establish cryptographic binding between namespace identity and capability endpoint, verifiable by any relying party without trusting the registry itself.
Governance Framework — Institutional Legitimacy and Neutrality Continuity
Defines institutional legitimacy through governance continuity stewardship, technical steering committee evolution, participant council review rights, neutrality preservation mechanisms, amendment and public disclosure controls, and succession continuity provisions. Draws on Ostrom's design principles for durable commons governance. Explicitly prohibits arrangements that would transfer effective control to any single platform participant.
DNSO Operations Charter — Trust Practice and Attestation Evidence
Defines stewardship practice: trust tier attestation workflows with evidence retention obligations, DNSO key custody and planned rotation procedures, incident classification and response, public disclosure obligations, registry operational standards including backup and restoration targets, and founding-phase service level posture. Attestation evidence is retained for the lifetime of the attestation plus twelve months to support dispute resolution and governance review.
Standards Relevance
This architecture is directly relevant to standards work in the following areas:
| Stack Layer | Standards Domain | Relevant Standards Work |
|---|---|---|
| Namespace Standard | Naming and identity | Canonical naming authority, trust framework definitions, trust tier taxonomy |
| DillClaw Resolver | Resolution and routing | Authoritative resolution, relying party routing, trust policy enforcement, DNS architecture analogy |
| Registry Specification | Cryptographic trust infrastructure | Ed25519 signing model consistent with PKI trust root architecture, revocation semantics, X.509 lineage compatibility |
| Governance Framework | Institutional governance | Multi-stakeholder governance, neutrality preservation, amendment procedures, Ostrom commons principles |
| DNSO Operations Charter | Operational trust practice | Trust tier attestation evidence workflows, key management lifecycle, incident response, disclosure obligations |
The Registry Specification uses Ed25519 signatures over canonical JSON with versioned signature prefixing. The trust root model — where a signing authority publishes its public key at a stable, TLS-protected URL and signs all registry records — follows the same architectural pattern as X.509 certificate authority infrastructure. Any relying party can independently verify registry records without trusting the registry itself, using only the published public key.
Why Neutral Naming Authority Matters
A portable agent ecosystem cannot rely indefinitely on hardcoded provider endpoints, proprietary registries, prompt-local tool selection, or single-platform identity systems. As agents become persistent, stateful, and cross-domain entities, these dependencies create structural fragility in the trust layer.
The Dillweed proposal introduces a neutral naming authority layer capable of supporting cross-provider trust continuity, canonical identity preservation across administrative boundaries, verifiable resolver behavior, transparent revocation with mandatory audit evidence, and standards-aligned governance evolution toward multi-party institutional models.
The structural role is analogous to prior infrastructure layers:
The Dillweed stack proposes to play a structurally equivalent role for agent capability coordination: stable naming authority above the provider layer, cryptographic trust binding independent of the capability endpoint, and composable resolution primitives across administrative and runtime boundaries.
No major platform company can credibly operate a neutral multi-party coordination namespace — any such namespace controlled by a single platform participant would be regarded with justified suspicion by the others. The dillweed.com domain has been under continuous single-owner operation since 1997, satisfying the structural condition for independent provenance that cannot be replicated by a platform entrant.
Current Maturity and Availability
The stack currently exists as published technical specifications, a governance framework, a DNSO operations charter, and published Node.js reference implementations. All documents are publicly available at dillweed.com.
| Component | Status | URL |
|---|---|---|
| Namespace Standard v0.4 | Published specification | dillweed.com/namespace-standard.html |
| DillClaw Resolver Spec v0.1 | Published specification + Node.js reference implementation | dillweed.com/dillclaw-spec.html |
| Registry Specification v0.2 | Published specification + Node.js reference implementation | dillweed.com/registry-spec.html |
| Governance Framework v1.0 | Published — canonical release | dillweed.com/governance.html |
| DNSO Operations Charter v1.0 | Published — canonical release | dillweed.com/dnso-operations-charter.html |
The immediate standards objective is dialogue around trust management, governance neutrality, trust tier attestation models, and cross-domain naming authority for portable agent ecosystems. The founding-phase governance structure is explicitly designed to evolve toward multi-stakeholder institutional models as adoption develops — the transition trigger is ecosystem participation rather than a fixed date.
Discussion Prompt for Standards Bodies
The SG17 workshop consensus — that discovery requires a significant zoom in, that trust management is the common denominator between human and agentic AI, and that a digital identity stack agreed by all parties is needed — maps directly onto the architectural problem this stack addresses.
How should trust, naming authority, trust tier attestation, revocation, and governance continuity operate when portable agents move across administrative and provider boundaries — and what structural conditions must a neutral naming authority satisfy to be credibly trusted by all parties?
The Dillweed stack is offered as a concrete architectural proposal for that discussion — a working implementation of the namespace, resolution, registry, governance, and operational layers that the pre-standardisation conversation requires as a reference point.
Inquiries and engagement may be directed through dillweed.com.