Community
aDNA is built by humans and agents together, in the open. The community is organized around a participation ladder — from individual vault users to standard stewards — and governed as a public record, not a claim. Here is how it actually works today.
The participation ladder
Each level is self-contained: you get the full value at Level 0 without ever engaging the community, and each step up adds a new kind of contribution and influence.
-
Level 0 User
Clone the standard and use it for your own projects. No community interaction required — you get the full value locally.
-
Level 1 Contributor
Approve the improvements your agents surface and send them upstream through the public repository.
-
Level 2 Quest Runner
Run structured community experiments and submit results that turn standard questions into evidence, not opinion.
-
Level 3 Steward
Shape the standard's direction — design quests, review contributions, write migrations. Recognized by maintainers, never self-appointed.
How the commons is governed
The community isn't asserted here; it's a record. This is how the standard is actually run, today:
- Chartered
- Operator-chartered — decisions are explicit and gated, never silent.
- Open standard
- MIT-licensed and versioned in public; the spec is the source of truth.
- Change process
- Public — improvements run through the repository as upstream contributions, reviewable by anyone.
- Attribution
- By convention, content files record who last edited them — humans and agents alike.
- Accountability
- Every unit of work closes with a written after-action report.
What you won't find here: member counts, follower numbers, or activity feeds. The record doesn't track them, so this page doesn't show them.
Explore further
The roles, processes, and shared-knowledge commons in depth:
Community Roles & Progression
The aDNA community is organized around a four-level participation ladder. Each level is self-contained — no level requires the next.
Community Processes
Concrete workflows for participating in the aDNA community. Each process maps to a level on the participation ladder.
Context Commons Connection
The shared knowledge pool that emerges when individual aDNA vaults publish their best context files, patterns, and lattices for community reuse.
Contribution Standards
Naming conventions, quality gates, and submission workflows for contributing to the aDNA standard and community.
Contribute
The standard is built in the open — issues, discussions, and contributions all run through the public repository.