# Code of Conduct

## Purpose

**Telemt exists to solve technical problems.**
- Telemt is open to contributors who want to learn, improve and build meaningful systems together.
- It is a place for building, testing, reasoning, documenting, and improving systems.
- Discussions that advance this work are in scope, discussions that divert it are not.
- Technology has consequences, responsibility is inherent.

> **Absicht bestimmt die Form**

> Design follows intent

---

## Principles

* **Technical over emotional**
  - Arguments are grounded in data, logs, reproducible cases, or clear reasoning.

* **Clarity over noise**
  - Communication is structured, concise, and relevant.

* **Openness with standards**
  - Participation is open. The work remains disciplined.

* **Independence of judgment**
  - Claims are evaluated on technical merit, not affiliation or posture.

* **Responsibility over capability**
  - Capability does not justify careless use.

* **Cooperation over friction**
  - Progress depends on coordination, mutual support, and honest review.

* **Good intent, rigorous method**
  - Assume good intent, but require rigor.

> **Aussagen gelten nach ihrer Begründung.**

> Claims are weighed by evidence.

---

## Expected Behavior

Participants are expected to:

* Communicate directly and respectfully
* Support claims with evidence
* Stay within technical scope
* Accept critique and provide it constructively
* Reduce noise, duplication, and ambiguity
* Help others reach correct and reproducible outcomes
* Act in a way that improves the system as a whole

Precision is learned.

- New contributors are welcome
- They are expected to grow into these standards
- Existing contributors are expected to make that growth possible

> **Wer behauptet, belegt.**

> Whoever claims, proves.

---

## Unacceptable Behavior

The following is not allowed:

* Personal attacks, insults, harassment, or intimidation
* Repeatedly derailing discussion away from Telemt’s purpose
* Spam, flooding, or repeated low-quality input
* Misinformation presented as fact
* Attempts to degrade, destabilize, or exhaust Telemt or its participants
* Use of Telemt or its spaces to enable harm

Telemt is not a venue for disputes that displace technical work.
Such discussions may be closed, removed, or redirected.

> **Störung ist kein Beitrag.**

> Disruption is not contribution.

---

## Security and Misuse

Telemt is intended for responsible use.

* Do not use it to plan, coordinate, or execute harm
* Do not publish vulnerabilities without responsible disclosure
* Report security issues privately where possible

Security is both technical and behavioral.

> **Verantwortung endet nicht am Code.**

> Responsibility does not end at the code.

---

## Openness

Telemt is open to contributors of different backgrounds, experience levels, and working styles.

- Standards are public, legible, and applied to the work itself.
- Questions are welcome. Careful disagreement is welcome. Honest correction is welcome.
- Gatekeeping by obscurity, status signaling, or hostility is not.

---

## Scope

This Code of Conduct applies to all official spaces:

* Source repositories (issues, pull requests, discussions)
* Documentation
* Communication channels associated with Telemt

---

## Maintainer Stewardship

Maintainers are responsible for final decisions in matters of conduct, scope, and direction.

This responsibility is stewardship: 
- preserving continuity, 
- protecting signal, 
- maintaining standards, 
- keeping Telemt workable for others.

Judgment should be exercised with restraint, consistency, and institutional responsibility.
- Not every decision requires extended debate.
- Not every intervention requires public explanation.

All decisions are expected to serve the durability, clarity, and integrity of Telemt.

> **Klarheit vor Zustimmung - Bestand vor Beifall**

> Clarity above approval - substantiality before success
---

## Enforcement

Maintainers may act to preserve the integrity of Telemt, including by:

* Removing content
* Locking discussions
* Rejecting contributions
* Restricting or banning participants

Actions are taken to maintain function, continuity, and signal quality.
- Where possible, correction is preferred to exclusion.
- Where necessary, exclusion is preferred to decay.

---

## Final

**Telemt is built on discipline, structure, and shared intent**
- Signal over noise
- Facts over opinion
- Systems over rhetoric
- Work is collective
- Outcomes are shared
- Responsibility is distributed
- Precision is learned
- Rigor is expected
- Help is part of the work

> **Ordnung ist Voraussetzung der Freiheit**

- If you contribute — contribute with care
- If you speak — speak with substance
- If you engage — engage constructively

---

## After All

Systems outlive intentions
- What is built will be used
- What is released will propagate
- What is maintained will define the future state

There is no neutral infrastructure, only infrastructure shaped well or poorly

> **Ordnung → Umsetzung → Ergebnis**

> Order → Implementation → Result

- Stability requires discipline
- Freedom requires structure
- Trust requires honesty

In the end: the system reflects its contributors

