1. Purpose of This Document
This document describes the governance philosophy, current structure, and intended evolution of the Dillweed Namespace Project — a neutral, independently operated capability coordination namespace for AI agent systems. It is provided to inform prospective institutional partners, implementers, and contributors of the project's governance posture and founding stewardship principles.
2. Background and Founding Asset
Dillweed.com has been under continuous single-owner operation since 1997 — a 28-year provenance that establishes the domain as one of the longest-held independent namespace assets on the internet. This continuity of stewardship is foundational to the project's credibility and neutrality thesis.
The Dillweed Namespace Project encompasses three specification documents and two deployable reference implementations:
- Dillweed Namespace Standard (v0.4) — the core capability coordination namespace specification
- DillClaw Resolver Specification (v0.1) — resolver protocol and reference implementation (Node.js, port 7474)
- Dillweed Registry Specification (v0.1) — registry protocol and reference implementation (Node.js, port 7475, Ed25519 cryptographic signing)
Supporting domain assets include dillweed.ai, dill.ai, dillclaw.ai, dillclaw.com, dillforge.ai, dillforge.com, and approximately 230 defensively registered related domains. Trademark coverage spans Classes 35, 41, and 42 in the United States.
3. The Neutrality Thesis
The central strategic premise of the Dillweed Namespace Project is that a capability coordination namespace for AI agents derives its value precisely from its neutrality.
No major platform company can credibly operate a multi-party coordination namespace — any such namespace controlled by Google, Microsoft, Meta, Anthropic, or Amazon would be regarded with justified suspicion by the other participants.
This creates a structural opportunity for an independently held, long-provenance namespace to serve as the neutral coordination layer that platform participants cannot provide for themselves. The governance framework described in this document is designed to institutionalize that neutrality across time, independent of any single moment of stewardship.
4. Current Governance Structure — Founding Phase
4.1 Founding Steward
The project is currently governed by its founding steward, who has held the anchor domain asset since 1997 and developed the specification stack. During the founding phase, the founding steward retains full authority over:
- Specification evolution and versioning
- Domain and trademark asset management
- Partnership and institutional engagement decisions
- Reference implementation development and release
4.2 Founding Phase Duration
The founding phase is expected to conclude when one or more of the following conditions are met:
- A significant institutional partner or implementer has adopted the standard
- Multiple independent implementations exist
- Sufficient community interest exists to constitute a multi-stakeholder governance body
5. Intended Governance Evolution
As multi-party adoption develops, the project intends to formalize a multi-stakeholder governance model consistent with durable internet standards practice. The intended structure comprises three governance tiers, supported by explicit amendment and disclosure procedures.
5.1 Founding Steward Continuity Role
The founding steward retains a permanent continuity seat in all governance structures, recognizing custodianship of the foundational domain and trademark assets. This structure mirrors continuity roles commonly preserved in durable internet governance models, and ensures that the long-provenance thesis which underlies the neutrality argument is structurally protected across governance transitions.
In matters involving direct commercial arrangements that materially affect the founding asset base, the Technical Steering Committee may, by majority vote, request that the founding steward abstain from non-technical decisions in that specific matter. This conflict-of-interest provision is designed to strengthen institutional credibility without compromising continuity of stewardship.
5.2 Technical Steering Committee
A Technical Steering Committee (TSC) — initially three to five members, always an odd number — will govern specification evolution. Membership is earned through demonstrated technical contribution to the specification or reference implementations. The TSC operates by consensus, with the founding steward holding a permanent seat. In the event of a tied vote, the founding steward's position prevails.
5.3 Participant Council
Organizations that have adopted and implemented the Dillweed Namespace Standard in production systems will be eligible for representation on a Participant Council. The Participant Council holds the following defined authorities:
- May initiate formal review requests for proposed specification changes, which the TSC is obligated to consider within a defined response window
- May issue public implementation recommendations and compatibility guidance
- Provides advisory input on governance evolution and foundation structure decisions
The Participant Council does not hold authority over the core specification. No single participant organization may hold a controlling interest in the council's proceedings.
5.4 Succession and Continuity
The founding steward may designate a continuity trustee or controlled stewardship entity to preserve governance continuity in the event of incapacity or succession. Any such designation shall be documented and held by the Technical Steering Committee. This provision preserves governance continuity beyond individual stewardship and reinforces the institutional durability implied by the project's 28-year provenance.
In extraordinary circumstances where the continuity seat is vacant and no prior designation exists, the TSC may appoint an interim continuity trustee by unanimous vote pending formal succession. This provision ensures that no governance vacuum arises from the absence of a prior designation.
5.5 Foundation Structure
As multi-party adoption develops, the project intends to formalize foundation status — either as a 501(c)(6) trade association or under the stewardship of an established standards body such as the Linux Foundation. Any such arrangement will be structured as a licensing and stewardship agreement rather than a transfer of domain or trademark assets.
5.6 Amendment Process and Transparency
Amendments to this governance framework and any successor charter instruments require concurrence of the founding continuity seat and a majority of the Technical Steering Committee. Proposed amendments must be circulated to the Participant Council for review no fewer than 30 days prior to adoption.
Major governance transitions, continuity designations, and framework amendments will be publicly disclosed in a timely manner, consistent with the project's commitment to transparency and auditability. This disclosure principle applies equally to any successor charter instruments adopted in connection with foundation formation.
6. Asset Protection Principles
The following principles govern the relationship between the founding asset base and any governance structure:
- The domain assets (dillweed.com, dillclaw.com, dillweed.ai, dill.ai, and related domains) will not be transferred to any foundation, partner, or institutional entity outright.
- The specifications may be licensed to a foundation or standards body for stewardship purposes under terms that preserve the founding steward's continuity role.
- Trademark registrations (Classes 35, 41, 42) will be maintained by the founding steward or a wholly controlled entity.
- Any institutional partnership agreement must explicitly acknowledge the neutrality thesis and prohibit any arrangement that would give a single platform participant effective control over the namespace.
7. Institutional Partner Engagement
The project welcomes engagement from institutional partners in the following capacities:
- Implementer — organizations adopting the Dillweed Namespace Standard in their agent systems
- Technical contributor — organizations or individuals contributing to specification development
- Infrastructure partner — organizations providing hosting, resolver, or registry infrastructure
- Governance participant — organizations represented on the Participant Council upon qualifying adoption
The project does not accept engagement that would compromise the neutrality thesis, including exclusive arrangements, controlling equity or governance positions for any single platform participant, or any structure that would effectively transfer control of the namespace to a commercial entity.
8. Contact and Further Information
Specification documents are available at the following canonical URLs:
Inquiries regarding partnership, institutional engagement, or governance discussion may be directed through dillweed.com.