Skip to content

Commit 91f9963

Browse files
Add project ethics, governance, and code of conduct
Establish TRAIL's ethical foundation with three new documents: - CODE_OF_CONDUCT.md: Contributor Covenant with AI-specific standards - ETHICS.md: Six core principles including dual-use awareness and anti-surveillance commitments - GOVERNANCE.md: Phased governance model (Founding -> Advisory -> Multi-Stakeholder) Update CONTRIBUTING.md and README.md to reference the new documents. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 21833db commit 91f9963

File tree

5 files changed

+352
-3
lines changed

5 files changed

+352
-3
lines changed

CODE_OF_CONDUCT.md

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
# Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and maintainers of the TRAIL Protocol pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
6+
7+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8+
9+
## Our Standards
10+
11+
Examples of behavior that contributes to a positive environment:
12+
13+
- Using welcoming and inclusive language
14+
- Being respectful of differing viewpoints and experiences
15+
- Giving and gracefully accepting constructive feedback
16+
- Focusing on what is best for the community and the protocol
17+
- Showing empathy toward other community members
18+
- Prioritizing technical merit and evidence-based reasoning in protocol discussions
19+
20+
Examples of unacceptable behavior:
21+
22+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
23+
- Trolling, insulting or derogatory comments, and personal or political attacks
24+
- Public or private harassment
25+
- Publishing others' private information without explicit permission
26+
- Misrepresenting your contributions, credentials, or affiliations
27+
- Using the project's reputation or community channels for commercial promotion unrelated to TRAIL
28+
- Other conduct which could reasonably be considered inappropriate in a professional setting
29+
30+
## AI-Specific Standards
31+
32+
Because TRAIL Protocol exists at the intersection of AI and identity, we hold ourselves to additional standards:
33+
34+
- **Transparency over obscurity.** We build infrastructure that makes AI systems more accountable, not less. This principle extends to how we work together.
35+
- **No surveillance by design.** We reject contributions that would enable mass surveillance, social scoring, or discriminatory profiling through AI identity infrastructure.
36+
- **Human agency first.** AI identity systems must enhance human oversight, not replace it. Contributions that undermine human control over AI systems will not be accepted.
37+
- **Honest about limitations.** We document what TRAIL can and cannot do. Overstating the protocol's capabilities - especially regarding regulatory compliance - is unacceptable.
38+
39+
## Scope
40+
41+
This Code of Conduct applies within all project spaces, including GitHub repositories, issue discussions, pull requests, W3C CCG mailing lists, DIF Discord channels, and any other space where the TRAIL Protocol community interacts.
42+
43+
It also applies when an individual is officially representing the project in public spaces, such as using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
44+
45+
## Enforcement
46+
47+
### Reporting
48+
49+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to:
50+
51+
- **Christian Hommrich** - conduct@trailprotocol.org
52+
53+
All complaints will be reviewed and investigated promptly and fairly. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
54+
55+
### Enforcement Guidelines
56+
57+
Project maintainers will follow these guidelines in determining consequences for any action they deem in violation of this Code of Conduct:
58+
59+
**1. Correction**
60+
- **Impact:** Minor, unintentional violation.
61+
- **Consequence:** A private written warning, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
62+
63+
**2. Warning**
64+
- **Impact:** A violation through a single incident or series of actions.
65+
- **Consequence:** A warning with consequences for continued behavior. No interaction with the people involved for a specified period. This includes avoiding interactions in community spaces as well as external channels. Violating these terms may lead to a temporary or permanent ban.
66+
67+
**3. Temporary Ban**
68+
- **Impact:** A serious violation of community standards, including sustained inappropriate behavior.
69+
- **Consequence:** A temporary ban from any sort of interaction or public communication with the community for a specified period. No public or private interaction with the people involved is allowed during this period. Violating these terms may lead to a permanent ban.
70+
71+
**4. Permanent Ban**
72+
- **Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
73+
- **Consequence:** A permanent ban from any sort of public interaction within the community.
74+
75+
## Relationship to Other Codes
76+
77+
This project participates in the [Decentralized Identity Foundation (DIF)](https://identity.foundation) and the [W3C Credentials Community Group (CCG)](https://www.w3.org/community/credentials/). When participating in those communities on behalf of TRAIL, their respective codes of conduct also apply.
78+
79+
## Attribution
80+
81+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1, with AI-specific extensions reflecting TRAIL Protocol's mission.
82+
83+
---
84+
85+
*Version 1.0 - April 2026*

CONTRIBUTING.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,9 +65,20 @@ For minor fixes (typos, formatting), direct PRs are welcome.
6565

6666
## Code of Conduct
6767

68-
This project adheres to the [DIF Code of Conduct](https://github.com/decentralized-identity/org/blob/master/code-of-conduct.md). By participating, you agree to uphold its principles of open, inclusive, and collaborative engagement.
68+
This project has its own [Code of Conduct](CODE_OF_CONDUCT.md) adapted from the Contributor Covenant with AI-specific extensions. By participating, you agree to uphold its principles.
6969

70-
In short: Be constructive. Technical disagreement is welcome; personal attacks are not. Assume good intent. If conflicts arise, follow the [DIF escalation process](https://github.com/decentralized-identity/org/blob/master/code-of-conduct.md#reporting-guidelines).
70+
In short: Be constructive. Technical disagreement is welcome; personal attacks are not. Assume good intent. Report violations to conduct@trailprotocol.org.
71+
72+
We also adhere to the [DIF Code of Conduct](https://github.com/decentralized-identity/org/blob/master/code-of-conduct.md) when participating in DIF community spaces.
73+
74+
## Ethics and Governance
75+
76+
TRAIL Protocol maintains explicit ethical principles and a governance model:
77+
78+
- **[ETHICS.md](ETHICS.md)** - The ethical principles that guide protocol design decisions
79+
- **[GOVERNANCE.md](GOVERNANCE.md)** - How decisions are made, roles, and dispute resolution
80+
81+
All contributions are evaluated against these principles. Please review them before submitting substantial proposals.
7182

7283
## Community
7384

ETHICS.md

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
# TRAIL Protocol - Ethical Principles
2+
3+
## Why This Document Exists
4+
5+
TRAIL Protocol builds identity infrastructure for AI systems. Infrastructure shapes behavior. The choices we make in protocol design determine what is easy, what is hard, and what is impossible for everyone who builds on top of TRAIL.
6+
7+
This document states the ethical principles that guide those choices. It is a commitment to our contributors, users, and the broader AI ecosystem.
8+
9+
## Core Principles
10+
11+
### 1. AI Must Serve Humans, Not the Other Way Around
12+
13+
TRAIL exists because AI systems are becoming autonomous actors in commerce, governance, and daily life. Identity infrastructure for AI must strengthen human oversight, not erode it.
14+
15+
**In practice, this means:**
16+
- Every AI identity in TRAIL is linked to a verifiable human or organizational controller
17+
- The protocol requires explicit disclosure of AI nature - no AI system should pass as human
18+
- Human override and revocation capabilities are non-negotiable protocol features
19+
- We design for human comprehension: trust signals must be interpretable by non-technical stakeholders
20+
21+
### 2. Transparency Is Non-Negotiable
22+
23+
Trust cannot be built on hidden mechanisms. TRAIL's trust model is based on verifiable, auditable, and publicly inspectable data.
24+
25+
**In practice, this means:**
26+
- Trust Score computation is fully documented and reproducible by any verifier
27+
- The specification is open (CC BY 4.0) and the reference implementation is open source (MIT)
28+
- We publicly document the limitations of our trust model, not just its strengths
29+
- Registry operations, governance decisions, and protocol changes are published with rationale
30+
31+
### 3. No Surveillance Infrastructure - and Dual-Use Awareness
32+
33+
AI identity infrastructure could be weaponized for mass surveillance, social scoring, or discriminatory profiling. We refuse to build that.
34+
35+
We also acknowledge that identity infrastructure is inherently dual-use. The same system that enables trust verification could be repurposed for state-controlled gatekeeping, systematic exclusion, or coercive compliance regimes. This is not a theoretical risk - it has happened with every major identity system in history. TRAIL is designed with active countermeasures against these failure modes.
36+
37+
**In practice, this means:**
38+
- TRAIL uses minimal disclosure: only the information necessary for trust verification is exposed
39+
- No behavioral tracking across contexts - a DID interaction with one verifier must not leak to another
40+
- GDPR compliance is a design constraint, not an afterthought
41+
- We actively reject feature requests or contributions that enable population-scale monitoring
42+
- Correlation risk analysis is a required part of any protocol extension review
43+
- TRAIL must never become a whitelist-only system where unregistered agents are blocked from operating. Tier 0 (self-signed) exists precisely to ensure that registration is a choice, not a precondition for existence
44+
- Protocol design is evaluated against misuse scenarios: "How could an authoritarian actor use this feature?" is a mandatory review question for every extension proposal
45+
46+
### 4. Honesty About What We Are and What We Are Not
47+
48+
TRAIL is a trust infrastructure protocol. It is not a regulatory compliance certificate, not a safety guarantee, and not a substitute for responsible AI development.
49+
50+
**In practice, this means:**
51+
- TRAIL registration does NOT constitute EU AI Act compliance - we say this explicitly in the spec
52+
- A high Trust Score indicates verifiable identity practices, not that an AI system is safe or ethical
53+
- We do not claim to solve AI alignment, bias, or safety - those are different problems
54+
- Marketing and communication about TRAIL must reflect these boundaries accurately
55+
- We support regulation like the EU AI Act not because it is mandated, but because we believe good regulation strengthens AI trust. Compliance-by-conviction, not compliance theater
56+
57+
### 5. Inclusive by Design
58+
59+
AI identity infrastructure will shape who can and who cannot deploy AI systems commercially. We design for broad access, not gatekeeping.
60+
61+
**In practice, this means:**
62+
- Tier 0 (self-issued) identities work offline and cost nothing - the barrier to entry is zero
63+
- The protocol is vendor-neutral: no single company controls who can operate a registry
64+
- Federation is a core architectural feature, preventing monopolistic control
65+
- We actively seek contributors from diverse geographies, industries, and technical backgrounds
66+
- Specification language is accessible: we explain jargon and provide examples
67+
- No protocol feature may require a specific vendor, jurisdiction, or commercial relationship to function at its base tier
68+
69+
### 6. Security as a Precondition for Trust
70+
71+
Identity infrastructure that can be forged, spoofed, or compromised destroys the trust it claims to provide. Security is not a feature - it is a precondition.
72+
73+
**In practice, this means:**
74+
- Cryptographic choices are conservative and well-studied (Ed25519, JCS)
75+
- Crypto agility is built in, with documented migration paths and deprecation windows
76+
- We actively invite security challenges and vulnerability reports
77+
- Key ceremony processes are documented and witnessed
78+
- We do not deploy features that have not undergone threat modeling
79+
80+
## Applying These Principles
81+
82+
### For Contributors
83+
84+
These principles guide what we accept into the protocol. If a proposed feature or change conflicts with these principles, it will be rejected - regardless of its technical elegance. When in doubt, open an issue to discuss the ethical implications before investing implementation effort.
85+
86+
### For Registry Operators
87+
88+
Organizations operating TRAIL registries commit to these principles by adopting the protocol. Registry operators who violate these principles - for example, by enabling surveillance use cases or misrepresenting trust guarantees - may have their operator credentials revoked through the governance process defined in `GOVERNANCE.md`.
89+
90+
### For AI Agent Deployers
91+
92+
Registering an AI agent with TRAIL is a statement that you take identity and accountability seriously. These principles set the baseline expectation. Deployers who misuse TRAIL identity to create false trust signals undermine the ecosystem for everyone.
93+
94+
## Evolution
95+
96+
These principles are not immutable. As the AI landscape evolves, our ethical understanding must evolve with it. Changes to this document require:
97+
98+
1. A public proposal (GitHub Issue with the `ethics` label)
99+
2. A minimum 30-day community review period
100+
3. Approval by the Governance Board (or Founding Maintainer in Phase 1)
101+
4. Publication of the rationale for any changes
102+
103+
We will never weaken these principles to accommodate commercial pressure. We may strengthen them as new risks emerge.
104+
105+
## Influences and Acknowledgments
106+
107+
These principles draw on:
108+
- [OECD AI Principles](https://oecd.ai/en/ai-principles) (2019)
109+
- [EU AI Act](https://eur-lex.europa.eu/eli/reg/2024/1689) - Articles 4a (AI literacy), 13 (transparency), 14 (human oversight)
110+
- [W3C Ethical Web Principles](https://www.w3.org/TR/ethical-web-principles/)
111+
- [Montreal Declaration for Responsible AI](https://montrealdeclaration-responsibleai.com/)
112+
- [DIF Code of Conduct](https://github.com/decentralized-identity/org/blob/master/code-of-conduct.md)
113+
114+
---
115+
116+
*Version 1.0 - April 2026*

0 commit comments

Comments
 (0)