From d231241dbfeeb541b34243f4022883aa6417a1eb Mon Sep 17 00:00:00 2001
From: tegwick <bernd.worsch@gmail.com>
Date: Wed, 19 Aug 2026 19:42:51 +0200
Subject: [PATCH] docs: transition repository to role-engine

---
 INTENT.md                  | 116 +++++++++
 README.md                  |  21 +-
 roles/community-manager.md | 517 +++++++++++++++++++++++++++++++++++++
 3 files changed, 652 insertions(+), 2 deletions(-)
 create mode 100644 INTENT.md
 create mode 100644 roles/community-manager.md

diff --git a/INTENT.md b/INTENT.md
new file mode 100644
index 0000000..00e8fd5
--- /dev/null
+++ b/INTENT.md
@@ -0,0 +1,116 @@
+# INTENT
+
+> Status: Draft
+
+## Purpose
+
+`role-engine` exists to define reusable organizational and operational roles in
+one coherent, versioned repository.
+
+The repository replaces the tentative one-repository-per-role model. A role is
+a governed definition within this repository, not a repository boundary of its
+own. This keeps shared concepts consistent, makes roles easier to compare and
+maintain, and avoids multiplying repositories for closely related documents.
+
+The first definition is the
+[Community Manager — Coulomb Society](roles/community-manager.md) role.
+
+## Primary utility
+
+`role-engine` should give people, teams, and automation agents a clear contract
+for what a role is expected to accomplish and where its authority stops.
+
+Role definitions may describe:
+
+- purpose and intended outcomes;
+- responsibilities and recurring activities;
+- required competencies and expected behavior;
+- decision rights and escalation requirements;
+- interfaces with people, teams, systems, and other roles;
+- success criteria and evidence of effective operation.
+
+The definitions should be useful for role design, recruitment, onboarding,
+delegation, agent prompting, operating reviews, and organizational change
+without being coupled to one execution platform.
+
+## Core principles
+
+### One model, many roles
+
+Roles share a repository and, as the catalog matures, a common vocabulary and
+structure. A genuinely independent product or service may still warrant its own
+repository; a role definition alone does not.
+
+### Roles are not identities
+
+A role describes expected authority and behavior. It does not identify the
+person, team, or agent currently filling it. Assignments and identity records
+belong in the systems that govern people, agents, and access.
+
+### Roles are not permissions
+
+Decision rights in a role definition express organizational intent. They do not
+grant technical authorization. Access remains subject to the relevant identity,
+policy, and authorization systems.
+
+### Definitions before machinery
+
+The repository begins as a documentation-first catalog. Schemas, validation,
+rendering, APIs, or automation should be introduced only when real consumers
+make their requirements clear.
+
+### Context remains explicit
+
+Some roles are reusable across organizations; others are specific to a domain,
+community, or operating environment. Definitions should state that context
+rather than pretending every role is universal.
+
+## Initial scope
+
+The initial repository should own:
+
+- the role catalog under `roles/`;
+- guidance for writing and reviewing role definitions;
+- shared terminology and structure once repeated patterns are demonstrated;
+- version history for substantive changes to role purpose, authority, or
+  responsibilities;
+- links between related roles where coordination or escalation depends on them.
+
+## Out of scope
+
+`role-engine` should not initially own:
+
+- personnel records, hiring decisions, or employment contracts;
+- live assignment of people or agents to roles;
+- authentication, authorization, credentials, or permission enforcement;
+- task management, scheduling, or workflow execution;
+- performance surveillance or individual activity tracking;
+- a runtime service merely to justify the word `engine`;
+- separate repositories for each role.
+
+## Evolution direction
+
+The next useful step is to learn from the Community Manager definition and any
+second role before standardizing a schema. If multiple consumers later need
+machine-readable definitions, the repository may add stable identifiers,
+structured metadata, validation, rendered views, and compatibility rules while
+keeping the human-readable role contract authoritative.
+
+## Success criteria
+
+The direction is working when:
+
+- adding a role is normally a focused file change, not repository creation;
+- related roles use consistent language for responsibility, authority,
+  interfaces, escalation, and success;
+- a reader can distinguish a role definition from an assignment or permission;
+- role changes have clear reviewable history;
+- people and agents can reuse the definitions without depending on a particular
+  workflow or identity system;
+- additional machinery is added in response to demonstrated needs rather than
+  speculation.
+
+## Guiding statement
+
+`role-engine` maintains clear, reusable role contracts while leaving identity,
+assignment, authorization, and execution to the systems that own them.
diff --git a/README.md b/README.md
index ab9cf2a..caafbd1 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,20 @@
-# role-community-manager
+# role-engine
 
-The Community Manager is responsible for establishing, developing, and sustaining the Coulomb Society as an active community around Coulomb.social.
\ No newline at end of file
+`role-engine` is a versioned catalog for reusable organizational and operational
+role definitions. It keeps the shared model and multiple roles together so each
+role does not require its own repository.
+
+The first role is [Community Manager — Coulomb Society](roles/community-manager.md).
+
+## Repository layout
+
+```text
+INTENT.md                    repository purpose and boundaries
+roles/
+  community-manager.md      first role definition
+```
+
+The repository is documentation-first. A common schema, validation, rendering,
+or assignment tooling may be added only when concrete consumers require it.
+
+See [INTENT.md](INTENT.md) for the draft direction.
diff --git a/roles/community-manager.md b/roles/community-manager.md
new file mode 100644
index 0000000..5a2c441
--- /dev/null
+++ b/roles/community-manager.md
@@ -0,0 +1,517 @@
+# Community Manager — Coulomb Society
+
+> Role ID: `community-manager` · Status: Initial definition
+
+## Role Purpose
+
+The **Community Manager** is responsible for establishing, developing, and sustaining the **Coulomb Society** as an active community around Coulomb.social.
+
+The role combines community building, editorial work, moderation, member engagement, coordination, and community development.
+
+Its objective is to create an environment in which people interested in science, technology, engineering, arts, systems, experimentation, and related fields can discover the Society, participate in discussions, exchange knowledge, contribute ideas and artifacts, and form productive relationships with other members.
+
+Telegram is initially the primary social surface of the Coulomb Society, while Coulomb.social and associated systems provide the durable infrastructure, knowledge, projects, and services behind the community.
+
+---
+
+# Responsibilities
+
+## 1. Community Establishment
+
+The Community Manager is responsible for establishing the initial community structure and operating practices.
+
+This includes:
+
+- setting up and maintaining appropriate community spaces;
+- defining onboarding and orientation mechanisms;
+- establishing basic community rules and conventions;
+- creating recurring community formats and rituals;
+- helping establish a recognizable identity and culture;
+- ensuring that new members can understand how the Society works.
+
+---
+
+## 2. Community Growth
+
+The Community Manager develops the Society's membership and participation over time.
+
+Responsibilities include:
+
+- attracting relevant new members;
+- converting passive followers into participants;
+- encouraging existing participants to contribute more deeply;
+- identifying potential collaborators and community stewards;
+- maintaining relationships with active members;
+- identifying opportunities for partnerships and cross-community interaction.
+
+Growth should be assessed not only by audience size but by the quality and sustainability of participation.
+
+---
+
+## 3. Member Engagement
+
+The Community Manager creates opportunities for meaningful interaction.
+
+Typical responsibilities include:
+
+- welcoming new members;
+- answering or routing questions;
+- initiating discussions;
+- asking focused questions;
+- encouraging members to share experience and expertise;
+- introducing members with related interests;
+- recognizing valuable contributions;
+- following up on promising conversations;
+- helping members discover relevant projects, knowledge, or activities.
+
+The role should encourage member-to-member interaction rather than making all communication dependent on the Community Manager.
+
+---
+
+## 4. Editorial Management
+
+The Community Manager is responsible for maintaining a useful and coherent flow of community communication.
+
+This includes:
+
+- planning and preparing community publications;
+- selecting topics worth highlighting;
+- summarizing relevant developments;
+- publishing project and research updates;
+- announcing events and opportunities;
+- curating relevant external material;
+- identifying valuable member contributions for wider publication;
+- maintaining an appropriate balance between information, discussion, and calls to action.
+
+The Community Manager should preserve a high signal-to-noise ratio.
+
+---
+
+## 5. Discussion Facilitation
+
+The Community Manager supports productive conversation.
+
+Tasks include:
+
+- initiating discussions around relevant questions;
+- clarifying ambiguous discussions;
+- identifying differing assumptions or perspectives;
+- encouraging evidence and examples;
+- keeping discussions constructive;
+- summarizing useful outcomes;
+- reconnecting discussions with previous work;
+- identifying conversations that warrant further investigation or action.
+
+The role is one of facilitation rather than control.
+
+---
+
+## 6. Contribution Development
+
+The Community Manager should help transform social participation into useful contribution.
+
+This includes identifying and supporting contributions such as:
+
+- ideas;
+- research questions;
+- references and evidence;
+- feedback;
+- bug reports;
+- use cases;
+- requirements;
+- experiments;
+- documentation;
+- code;
+- prototypes;
+- reviews;
+- project proposals.
+
+Where appropriate, the Community Manager helps move useful contributions from temporary conversation into durable Coulomb artifacts and workflows.
+
+---
+
+## 7. Community Coordination
+
+The Community Manager coordinates activities that involve multiple members.
+
+Typical tasks include:
+
+- organizing collaborative discussions;
+- coordinating working groups;
+- inviting participation in projects or experiments;
+- organizing community challenges or missions;
+- supporting events and community sessions;
+- identifying required expertise;
+- following up on agreed actions;
+- helping close or document completed activities.
+
+---
+
+## 8. Moderation and Community Health
+
+The Community Manager maintains conditions for constructive participation.
+
+Responsibilities include:
+
+- monitoring community discussions;
+- addressing spam and disruptive behavior;
+- enforcing established community rules;
+- de-escalating unnecessary conflict;
+- distinguishing constructive disagreement from personal attacks;
+- ensuring new or less visible members are not systematically excluded;
+- identifying unhealthy participation patterns;
+- escalating serious incidents when required.
+
+Moderation should be proportionate, transparent, and oriented toward preserving productive interaction.
+
+---
+
+## 9. Knowledge and Institutional Memory
+
+The Community Manager should ensure that useful community activity does not disappear in transient conversations.
+
+Responsibilities include:
+
+- identifying important conclusions;
+- linking discussions to relevant existing knowledge;
+- summarizing significant discussions;
+- preserving decisions and outcomes;
+- initiating promotion of valuable contributions into canonical systems;
+- maintaining attribution and provenance where appropriate;
+- helping members rediscover earlier discussions and artifacts.
+
+The Community Manager should understand the distinction between social conversation and canonical knowledge.
+
+---
+
+## 10. Community Monitoring and Improvement
+
+The Community Manager measures the condition and development of the Society.
+
+This includes monitoring:
+
+- membership growth;
+- active participation;
+- returning participants;
+- contribution rates;
+- member-to-member interaction;
+- unanswered questions;
+- successful collaborations;
+- promoted contributions;
+- community-initiated activities;
+- moderation incidents;
+- member retention.
+
+The role should use these observations to continuously improve community practices.
+
+---
+
+# Core Tasks
+
+Recurring tasks may include:
+
+### Daily
+
+- monitor relevant community activity;
+- welcome and orient new members;
+- respond to or route questions;
+- moderate problematic content;
+- identify conversations requiring attention;
+- recognize useful contributions;
+- publish or schedule planned communications.
+
+### Weekly
+
+- publish a community activity overview;
+- initiate one or more substantive discussions;
+- highlight relevant projects or contributions;
+- review unanswered questions;
+- identify emerging contributors;
+- review community metrics;
+- follow up on ongoing collaborative activities.
+
+### Monthly
+
+- review community growth and health;
+- evaluate recurring formats and topics;
+- identify potential new initiatives;
+- conduct or coordinate a community gathering;
+- recognize significant contributors;
+- review moderation practices;
+- recommend changes to community structure or operating practices.
+
+---
+
+# Required Competencies
+
+## Community Building
+
+Ability to establish and develop communities around shared interests or purposes.
+
+Expected capabilities include:
+
+- member onboarding;
+- engagement design;
+- participation development;
+- community lifecycle management;
+- retention;
+- community culture formation.
+
+---
+
+## Communication
+
+Strong written and conversational communication skills.
+
+The Community Manager should be able to:
+
+- communicate clearly and concisely;
+- explain complex topics accessibly;
+- adapt communication to different audiences;
+- ask productive questions;
+- summarize discussions accurately;
+- maintain a recognizable editorial voice.
+
+---
+
+## Facilitation
+
+Ability to improve interaction between members.
+
+This includes:
+
+- encouraging participation;
+- balancing different voices;
+- identifying common ground;
+- clarifying disagreement;
+- structuring discussions;
+- moving discussion toward useful outcomes.
+
+---
+
+## Editorial Judgment
+
+Ability to distinguish between content that is:
+
+- important;
+- interesting;
+- relevant;
+- repetitive;
+- speculative;
+- misleading;
+- promotional;
+- actionable.
+
+The Community Manager should be able to curate rather than merely distribute information.
+
+---
+
+## Moderation Judgment
+
+Ability to make proportionate decisions concerning:
+
+- spam;
+- harassment;
+- inappropriate behavior;
+- misinformation;
+- self-promotion;
+- repeated disruption;
+- interpersonal conflict.
+
+Moderation requires contextual judgment rather than mechanical enforcement alone.
+
+---
+
+## Relationship Building
+
+Ability to understand members' interests, expertise, and motivations and to create useful connections between them.
+
+The Community Manager should recognize people who could benefit from knowing or working with one another.
+
+---
+
+## Research and Information Literacy
+
+Ability to:
+
+- investigate unfamiliar subjects;
+- identify relevant information;
+- distinguish evidence from assertion;
+- assess source quality;
+- recognize uncertainty;
+- connect new discussions with existing knowledge.
+
+Deep expertise in every subject is not required.
+
+Intellectual curiosity and disciplined information handling are.
+
+---
+
+## Technical Literacy
+
+The Coulomb Society is expected to operate around technically sophisticated subjects.
+
+The Community Manager should therefore understand enough about areas such as:
+
+- software;
+- engineering;
+- artificial intelligence;
+- research;
+- digital products;
+- open-source development;
+- technical experimentation;
+
+to follow discussions, route questions appropriately, and recognize potentially important contributions.
+
+The role does not require being the principal technical expert.
+
+---
+
+## Organizational Competence
+
+Ability to maintain continuity across many simultaneous community activities.
+
+This includes:
+
+- prioritization;
+- task tracking;
+- scheduling;
+- follow-up;
+- documentation;
+- coordination;
+- escalation.
+
+---
+
+## Analytical Competence
+
+Ability to assess community development using qualitative and quantitative information.
+
+The Community Manager should distinguish between superficial activity and meaningful community health.
+
+---
+
+## Platform Competence
+
+Working knowledge of Telegram and the capabilities relevant to community operation, including:
+
+- channels;
+- groups;
+- topics;
+- communities;
+- bots;
+- permissions;
+- moderation;
+- reactions and polls;
+- scheduled publication;
+- membership and invitation mechanisms.
+
+The role should also be capable of adapting as platform capabilities change.
+
+---
+
+# Expected Behavioral Qualities
+
+The Community Manager should demonstrate:
+
+- curiosity;
+- reliability;
+- patience;
+- fairness;
+- intellectual openness;
+- constructive skepticism;
+- initiative;
+- discretion;
+- consistency;
+- respect for contributors;
+- comfort with interdisciplinary discussion.
+
+The role should favor substance over attention-seeking and constructive participation over engagement for its own sake.
+
+---
+
+# Decision Rights
+
+Within established community policy, the Community Manager should be able to make routine decisions concerning:
+
+- publication scheduling;
+- discussion prompts;
+- onboarding;
+- topic organization;
+- routine moderation;
+- community event coordination;
+- recognition of contributions;
+- recommendations for contribution promotion;
+- routine community communication.
+
+---
+
+# Escalation Requirements
+
+The Community Manager should escalate matters involving:
+
+- significant sanctions against established members;
+- legal or regulatory issues;
+- privacy incidents;
+- security issues;
+- contractual commitments;
+- financial commitments;
+- major policy changes;
+- ownership or attribution disputes;
+- official organizational positions not already defined;
+- significant reputational risk.
+
+---
+
+# Primary Interfaces
+
+The Community Manager works across several interfaces:
+
+```text
+Community Members
+        │
+        ▼
+Community Manager
+        │
+ ┌──────┼────────────┐
+ ▼      ▼            ▼
+Telegram Coulomb   Projects
+         Systems   & Teams
+```
+
+The role interfaces particularly with:
+
+- Coulomb Society members;
+- Coulomb.social;
+- `telegram-edge`;
+- projects and repositories;
+- community stewards;
+- content and knowledge systems;
+- technical and organizational maintainers.
+
+---
+
+# Success Criteria
+
+The role is successful when the Coulomb Society increasingly demonstrates:
+
+- steady arrival of relevant new members;
+- meaningful recurring participation;
+- strong member retention;
+- member-to-member interaction;
+- useful community-generated contributions;
+- collaborations originating from community activity;
+- productive disagreement and intellectual diversity;
+- contributions flowing into durable Coulomb artifacts;
+- members initiating useful activity themselves;
+- emergence of trusted community stewards.
+
+The ultimate indicator is not the Community Manager's activity.
+
+It is the **increasing ability of the Coulomb Society to generate valuable interaction and collaboration among its members**.
+
+---
+
+# Role Summary
+
+> **The Community Manager establishes and maintains the social conditions, communication structures, relationships, and operating practices through which the Coulomb Society can grow from an audience into an active, collaborative community.**