Governance Framework
Authority structure, neutrality preservation, and the intended evolution of the Dillweed Namespace toward multi-stakeholder governance.
A namespace operated by a major platform participant would face an unavoidable neutrality challenge. This framework is designed to institutionalize the neutrality that makes the namespace valuable — across time, independent of any single moment of stewardship.
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.
In summary: founding provenance anchors neutrality now; multi-stakeholder governance earns legitimacy later; asset protections prevent platform capture during the transition. This framework defines how that progression is institutionalized.
This revision integrates substantive feedback received on v1.1.2 across multiple rounds of review. Tone, framing, and taxonomy: the §01 cover thesis, §03 neutrality discussion, §03 platform-participants sentence, and §06 Asset Protection callout are all rewritten from advocacy to analytical formulation, aligning with parallel work on the Standards-Facing Overview and About page. The §02 specification stack taxonomy is restructured to align with the Standards Overview's "five core specifications, one cross-cutting document, one governance support protocol" framing while preserving the GSP-as-distinct-category structure that has architectural meaning beyond the Standards Overview's flatter grouping. The §02 cross-reference to the DNSO Operations Charter is normalized to major.minor granularity, and a §02 explanatory note is added disclosing that cross-document version references in this and other Dillweed specifications are shown at major.minor granularity by deliberate convention. Detailed revision history for prior versions has been moved to Appendix B.
Governance mechanics and status disclosure: the §5.1 founding-steward continuity seat language is reframed from "permanent in all governance structures" to a structural protection bounded by need; the residual "permanent seat" reference in §5.2 is harmonized via cross-reference to §5.1. The §5.6 amendment-concurrence requirement gains explicit scope-bounding language clarifying that it operates as asset-protection and neutrality-preservation logic rather than personal control. The §5.7 conflict-resolution precedence is extended to address GSP-01's role in succession, key custody, and continuity matters. A three-clause synthesis statement is added to §01 capturing the framework's institutional posture. A new Governance Status callout is added at §04 disclosing that multi-stakeholder bodies described in §04 and §05 are intended transition structures and are not yet constituted. No substantive governance authorities or neutrality commitments are altered by this revision; the changes refine institutional posture and clarify already-existing protections.
Conformance Terminology
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in BCP 14 [RFC 2119] [RFC 8174] when, and only when, they appear in all capitals, as shown here. Most of this framework is descriptive prose about governance philosophy and institutional intent; normative language is used sparingly in the asset-protection principles (§6), the amendment process (§5.6), and the conflict-resolution precedence order (§5.7).
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 five core governance-and-resolution specifications, one cross-cutting observability document, a standards-facing overview, one governance support protocol for continuity, and three deployable reference implementations.
Cross-document version references in this and other Dillweed specifications are shown at major.minor granularity (e.g., v0.4 rather than v0.4.1) by deliberate convention, to keep architectural cross-references stable across patch releases. Exact current versions of each document are tracked in the Standards Overview's maturity table.
Core Specifications
- 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)
- Governance Framework (v1.1.3) — authority structure, neutrality preservation, and governance evolution
- DNSO Operations Charter (v1.0) — operational procedures, attestation, key management, and service posture
Cross-Cutting Document
- Dillweed Anthill Observability Plane Specification (v0.1) — distributed signal aggregation, anomaly detection, and ecosystem health monitoring for the DNSO; reference implementation (Node.js)
Standards-Facing Overview
- Standards Overview — integrated standards-facing reference to the specification stack
Governance Support Protocols
- DNSO Continuity and Stewardship Transition Protocol (GSP-01 v1.0) — succession mechanics, key custody transfer, and governance continuity procedures for the DNSO
Supporting domain assets include dillweed.ai, dill.ai, dillclaw.ai, dillclaw.com, dillforge.ai, dillforge.com, and approximately 200 defensively registered related domains. Trademark coverage spans Classes 35, 41, and 42 in the United States.
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.
A namespace operated by a major platform participant would face an unavoidable neutrality challenge — a namespace controlled by Google, Microsoft, Meta, Anthropic, or Amazon would face the structural problem that the operator simultaneously occupies two roles: provider of competing services and arbiter of discovery and trust policy among them. The coordination function the namespace is designed to provide depends on those roles being structurally separable.
This creates a structural opportunity for an independently held, long-provenance namespace to serve as the neutral coordination layer that platform participants would struggle to provide credibly for themselves. The governance framework described in this document is designed to institutionalize that neutrality across time, independent of any single moment of stewardship.
Current Governance Structure — Founding Phase
The project is in founding-phase governance. The Technical Steering Committee, Participant Council, and other multi-stakeholder bodies described in this document and in §05 are intended transition structures and are not yet constituted. Sections describing those bodies represent governance design rather than current operational state.
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 (subject to the amendment process described in §5.6)
- 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
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 continuity seat in governance structures for matters affecting the structural neutrality of the namespace and the integrity of the founding asset base. The seat exists as a structural protection rather than a personal privilege: its function is to preserve the provenance-anchored neutrality argument that underlies the namespace's value, and it persists as long as that structural property remains at risk from governance evolution that could compromise it. This structure mirrors continuity roles commonly preserved in durable internet governance models, with the explicit understanding that the seat may evolve or be retired as multi-stakeholder governance matures and institutionalizes neutrality protections through other mechanisms.
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 the continuity seat described in §5.1. In the event of a tied vote, the founding steward's position prevails.
Where the founding steward has abstained from a specific matter pursuant to §5.1, the tie-break provision does not apply to that matter. In such cases, the TSC MUST reach a decision through majority of its remaining voting members, or defer the decision to a subsequent session. This constraint ensures that the abstention requested under §5.1 cannot be reversed in effect by tie-break operation, preserving the integrity of the conflict-of-interest mechanism.
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 30 calendar days of receipt
- 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. The precise definition of "controlling interest" in a council setting — whether through vote share, committee chair concentration, agenda-setting authority, or other mechanisms — will be refined when the council is constituted in practice; see Appendix A.
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. The operational procedures for succession, key custody transfer, and transition of stewardship obligations are specified in the DNSO Continuity and Stewardship Transition Protocol (GSP-01). 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. The specific legal structure is a matter for future decision and is tracked in Appendix A. 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. This concurrence requirement is limited to governance-framework and asset-continuity amendments and is intended to prevent changes that would compromise the neutrality thesis or transfer effective control of the founding asset base. 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 MUST be publicly disclosed in a timely manner, consistent with the project's commitment to transparency and auditability. The specific disclosure windows for governance-triggered events are specified in the DNSO Operations Charter §7. This disclosure principle applies equally to any successor charter instruments adopted in connection with foundation formation.
5.7 Document Authority and Conflict Resolution
The Dillweed specification stack comprises seven documents with distinct authority domains, supplemented by governance support protocols. In the event of a conflict between this Governance Framework and any operational or technical specification, governance authority over institutional structure, succession, amendment rights, and continuity shall prevail, while technical semantics remain governed by the applicable specification document. The precedence order for conflict resolution is: Governance Framework, then Namespace Standard, then Registry Specification, then DillClaw Resolver Specification, then DNSO Operations Charter, then Dillweed Anthill Observability Plane Specification. For matters of stewardship succession, key custody transfer, or continuity transition, GSP-01 (Continuity Protocol) controls within the scope delegated to it by this Governance Framework.
The Standards Overview is a meta-document providing an integrated standards-facing reference to the specification stack and does not participate in normative conflict resolution. Governance Support Protocols — including the DNSO Continuity and Stewardship Transition Protocol (GSP-01) — sit alongside the specification stack and are interpreted consistent with, but do not supersede, the core specifications. Conflicts between documents SHOULD be logged as amendment candidates for the affected document rather than resolved through informal interpretation.
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) MUST 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) MUST 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.
The domain assets are licensed, not transferred. No partnership, foundation formation, or institutional arrangement changes the founding steward's ownership of the underlying namespace infrastructure. This is a structural neutrality condition that a platform participant would struggle to replicate credibly.
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.
Contact and Further Information
Inquiries regarding partnership, institutional engagement, or governance discussion may be directed through dillweed.com.
must be earned through adoption, not granted through declaration.
Future Work (Non-Normative)
This appendix records items intended for a future revision of the Governance Framework. It is non-normative: nothing in this appendix imposes conformance requirements on current implementations or institutional participants. It is included to disclose the anticipated direction of the framework so that prospective partners, contributors, and stakeholders can plan for forthcoming refinements.
A.1 Foundation Structure Selection
The current framework notes that foundation formation may proceed as a 501(c)(6) trade association or under the stewardship of an established standards body such as the Linux Foundation (§5.5). The specific legal structure is a future decision that depends on the scale, composition, and geographic distribution of institutional partners at the point of formation. A future revision of this framework is expected to record the chosen structure, the rationale for the choice, and the licensing and stewardship terms negotiated with the receiving entity. This change will affect §5.5 and §6.
A.2 Controlling Interest Definition for the Participant Council
The current framework prohibits any single participant organization from holding a controlling interest in the Participant Council's proceedings (§5.3) but does not define "controlling interest" precisely. This is deliberate: the appropriate definition depends on the size, composition, and working practices of the council once constituted. A future revision is expected to refine this provision with specific limits on voting share, committee chair concentration, agenda-setting authority, and any proxy or bloc-voting arrangements. This change will affect §5.3.
A.3 Machine-Readable Governance Instruments
The governance instruments described in this framework are currently expressed in natural-language prose across this document, the DNSO Operations Charter, and the Continuity Protocol. A future revision is expected to publish machine-readable governance instruments — signed policy documents, amendment rules expressed as executable validation logic, and disclosure obligations expressed as testable predicates — so that the rules governing the namespace are enforceable by code rather than solely by document interpretation. This is aligned with the corresponding future-work item in the Namespace Standard Appendix A.3 and will affect §5.6 and §5.7.
A.4 Governance Observability Integration
The Anthill Observability Plane (v0.1) specifies a signal taxonomy and aggregation model oriented toward namespace ecosystem monitoring. A future revision is expected to extend Anthill's signal classes to cover governance events — TSC vote records, Participant Council review outcomes, amendment progressions, and continuity designations — so that governance activity benefits from the same observability and auditability discipline that the technical infrastructure does. This change will affect §5.6 and the Anthill Observability Plane specification.
Revision History (Non-Normative)
This appendix records the revision history of the Governance Framework prior to v1.1.3. Detailed notes for the current revision are at the top of this document. The entries below are preserved as institutional record of the document's evolution.
B.1 v1.1.2 (May 2026)
Corrected the §02 project inventory framing sentence to reflect the current document count and the addition of a third deployable reference implementation (Anthill Observability Plane); added a reference-implementation note to the Anthill specification bullet for parallelism with DillClaw and Registry; normalized the DNSO Operations Charter cross-reference to major.minor granularity for consistency with other cross-document references in the §02 list; made the Appendix A.2 controlling-interest deferral timeless rather than pinned to a specific revision; applied a stack-wide system-flow navigation panel style update at the document footer. No substantive governance provisions, authority structures, or neutrality commitments were altered.
B.2 v1.1.1 (April 2026)
Aligned the specification stack inventory with the v0.1 Registry Specification version; aligned the domain-asset portfolio reference with the Namespace Standard v0.4; added RFC 2119 conformance terminology; clarified the interaction between the §5.1 abstention mechanism and the §5.2 tie-break mechanism; introduced Appendix A for future work; corrected a structural footer defect carried forward from v1.1.
B.3 v1.1 (April 2026)
Updated the specification stack inventory to reflect the two specifications added in April 2026 (the Dillweed Anthill Observability Plane Specification v0.1 and the Standards Overview), and the first Governance Support Protocol (GSP-01 DNSO Continuity and Stewardship Transition Protocol v1.0). Extended the conflict-resolution precedence order in §5.7 correspondingly.