augmanitai

AUGMANITAI Maintainers

This file lists the current maintainers of the AUGMANITAI terminology project, their areas of responsibility, and their contact preferences.

Lead Maintainer (BDFL)

Andreas Ehstand

• Role: Project founder, Lead Maintainer, Final decision-making authority (per GOVERNANCE.md)
• ORCID: 0009-0006-3773-7796
• Contact: through GitHub issues, or the channels listed in SECURITY.md for private matters
• Responsibilities: All areas by default; term canonicalization; editorial review; release signing; dispute resolution
• Active since: Project inception (2025)

Domain Stewards

Domain stewards are responsible for reviewing proposals and maintaining quality within a specific subset of the terminology compendium. This role is aspirational as of v1.0; appointments will be announced on the project roadmap.

Domain	Steward	Terms in scope
Meta-Cognitive	(vacant)	SLE, RKE, SSP, CIR, SRTL, AIPS, CLR
Compound Cognition	(vacant)	CC, TI, TEA, TC, SM, LFMA
Multi-Agent / Swarm	(vacant)	CDC, Handoff Amnesia, Swarm Sycophancy, … (30 terms)
Collective Intelligence	(vacant)	Cognitive Mesh, Attribution Entropy, … (20 terms)
Prompt-Ontology Bridge	(vacant)	Intentional Compression Loss, Tokenization Fracture, … (24 terms)
Multilingual / Translation	(vacant)	EN/DE/ZH/HI/AR coverage
Infrastructure / Tooling	(vacant)	Python package, NPM, MCP server, APIs
Academic Pipeline	(vacant)	LaTeX, DOI, Zenodo deposit stewardship

Emeritus Maintainers

(none yet)

Per GOVERNANCE.md, maintainers who step down are honored here with gratitude for their past contributions.

How to Become a Maintainer

See the “Becoming a Maintainer” section of GOVERNANCE.md. In short: sustained, high-quality contributions over a minimum of 6 months, demonstrated understanding of ISO 704/1087/30042 terminology principles, and a nomination from an existing maintainer that is not blocked within the consensus period.

Maintainer Communication

• Public: GitHub Discussions, Issues, and Pull Requests
• Private (security, CoC violations, personnel): see SECURITY.md
• Async by default; no required meetings

Trust and Responsibility

Maintainers are expected to:

1. Uphold the Code of Conduct (CODE_OF_CONDUCT.md)
2. Respond to pull requests and issues in their domain within a reasonable time
3. Never merge their own non-trivial changes without second review once the team is larger than 2
4. Be transparent about conflicts of interest when reviewing proposals
5. Sign commits and releases (GPG or Sigstore) for supply-chain integrity

---

Bound by the Ethical Disclaimer §1–§20 (DISCLAIMER.md) and the repository licenses (LICENSE). Contact and provider: IMPRESSUM.md.

This site is open source. Improve this page.