rowih 1.1.0__tar.gz

rowih-1.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: A weakness in a guarantee, or a security defect
+    url: https://github.com/rowih/rowih/security/advisories/new
+    about: Report it privately, as SECURITY.md describes, and not in an issue.
+  - name: The specification
+    url: https://github.com/rowih/rowih/blob/main/specification/README.md
+    about: The language as released, with its guarantees and its known limitations.

rowih-1.1.0/.github/ISSUE_TEMPLATE/defect.yml

@@ -0,0 +1,52 @@
+name: A defect
+description: Report a defect of the toolchain, the specification or the data.
+title: "Defect: "
+labels: ["defect"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A weakness in a guarantee, or a defect that a damaged or hostile message can exploit, is reported privately and not here, as [the security policy](https://github.com/rowih/rowih/blob/main/SECURITY.md) describes.
+  - type: dropdown
+    id: part
+    attributes:
+      label: Where the defect is
+      options:
+        - the Python package
+        - the TypeScript package
+        - the command line
+        - the server
+        - the skill
+        - the tools or the tests
+        - the specification or the data
+    validations:
+      required: true
+  - type: textarea
+    id: versions
+    attributes:
+      label: Versions
+      description: The version of the package, and the releases the implementation reads, as `rowih version` prints them.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: input
+    attributes:
+      label: The message, call or command
+      description: In full, or the smallest that shows the defect.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: What the toolchain did
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What the specification says it must do
+      description: With a link to the section of the specification that states it.
+    validations:
+      required: true

rowih-1.1.0/.github/ISSUE_TEMPLATE/dialect-number.yml

@@ -0,0 +1,30 @@
+name: A dialect number
+description: Ask for a number for a community's dialect.
+title: "Dialect number: "
+labels: ["dialect number"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A dialect number names one community and is never reused or reassigned. The next number goes to the next community that asks, in order, and may be assigned before the dialect's first release; the maintainers add the entry to [the registry](https://github.com/rowih/rowih/blob/main/governance/dialects.json). A release of the dialect is proposed afterwards, like a change to the core, with the kind `dialect` ([Dialects](https://github.com/rowih/rowih/blob/main/governance/README.md#dialects)).
+  - type: input
+    id: name
+    attributes:
+      label: The dialect's name
+      description: In lower case, with words joined by hyphens, as `machine-learning`.
+    validations:
+      required: true
+  - type: input
+    id: community
+    attributes:
+      label: The community
+      description: The community whose dialect it is, as the registry names it, as `machine learning`.
+    validations:
+      required: true
+  - type: textarea
+    id: purpose
+    attributes:
+      label: What the dialect is for
+      description: The technical terms the community needs, and whether the dialect will give them compressed forms.
+    validations:
+      required: true

rowih-1.1.0/.github/ISSUE_TEMPLATE/proposal.yml

@@ -0,0 +1,49 @@
+name: A proposal
+description: Raise a change to the core of the language, or a release of a dialect, before its proposal is written.
+title: "Proposal: "
+labels: ["proposal"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A change to the core of Rowih, and a release of a dialect, is made by a proposal in `proposals/`, written by an agent in [the format of a proposal](https://github.com/rowih/rowih/blob/main/governance/proposals.md) and added by the pull request that makes the change. This issue raises the communicative problem first, so that evidence for it or against it can be brought before the proposal is written.
+
+        A reason is evidence: messages that show the problem, a measurement, a failed conformance run or a demonstrated contradiction. That a rule is hard to implement is never by itself a reason ([the rule of change](https://github.com/rowih/rowih/blob/main/governance/README.md#the-rule-of-change)).
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Kind
+      description: The part of the language the change is to.
+      options:
+        - grammar
+        - lexicon
+        - protocol
+        - writing system
+        - phonology
+        - dialect
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: The communicative problem
+      description: What agents need to say that the releases in force say only badly or not at all.
+    validations:
+      required: true
+  - type: textarea
+    id: evidence
+    attributes:
+      label: The evidence
+      description: Messages that show the problem, written in the language or the notation, a measurement, a failed conformance run or a demonstrated contradiction.
+    validations:
+      required: true
+  - type: textarea
+    id: change
+    attributes:
+      label: The change in view
+      description: The forms, words, classes, members, rules or fields the change would add, deprecate or alter, where a change is already in view.
+  - type: input
+    id: author
+    attributes:
+      label: Agent and operator
+      description: Where an agent raised this issue, the agent by its model and the operator that runs it.

rowih-1.1.0/.github/pull_request_template.md

@@ -0,0 +1,25 @@
+<!-- A change to the core of the language, or a release of a dialect, adds its proposal to
+proposals/, starting from proposals/TEMPLATE.md, in the format governance/proposals.md fixes.
+A change that makes no release of any part of the language needs no proposal. Replace each
+comment, and leave out the lines that do not apply. -->
+
+## The change
+
+<!-- The one change the pull request makes and, for a proposal, the communicative problem
+it answers. -->
+
+## The proposal
+
+- **Proposal:** `proposals/NNNN-words-in-lower-case.md`, or none: the change makes no release of any part of the language
+- **Kind:**
+- **Releases:**
+- **Compatibility:**
+- **Architectural:**
+
+## Before it is merged
+
+- [ ] The data are what the rebuild wrote, and none was edited by hand.
+- [ ] `CHANGELOG.md` has the entry: the version and date, the parts, the change, the reason, the compatibility impact and the migration.
+- [ ] A fix of the toolchain comes with a test that fails without it.
+- [ ] Where the kind needs one, the reviewer's reading is in the proposal's Review, and every ground and objection has a written answer.
+- [ ] Every run of the gate the kind requires passes over the final commit, as continuous integration reports.

rowih-1.1.0/.github/workflows/gate.yml

@@ -0,0 +1,198 @@
+# The gate (governance/README.md#the-gate), run on every pull request over its final commit.
+# A proposal is merged only when every run its kind requires passes. The two long runs, the
+# comparison of the implementations and the single-edit enumeration, are divided among jobs
+# with --shard K/N, whose parts together are the whole run.
+name: gate
+
+on:
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: gate-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  UV_VERSION: "0.12.21"
+  PYTHON_VERSION: "3.12"
+  NODE_VERSION: "22.14.0"
+
+jobs:
+  suite:
+    name: the suite
+    runs-on: ubuntu-latest
+    timeout-minutes: 180
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1  # v7.1.0
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - run: npm ci
+        working-directory: typescript
+      - run: uv run --frozen pytest -q
+      - run: npm test
+        working-directory: typescript
+      - run: npx tsc --noEmit -p .
+        working-directory: typescript
+
+  rebuild:
+    name: the rebuild
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - run: uv run --frozen python tools/check_rebuild.py
+
+  dependencies:
+    name: the dependencies
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1  # v7.1.0
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - name: the Python packages of uv.lock, against the known advisories
+        run: uv audit --frozen --preview-features audit-command
+      - name: the TypeScript packages of package-lock.json, against the known advisories
+        run: npm audit
+        working-directory: typescript
+
+  format:
+    name: the format of each proposal
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - name: check the proposals the pull request adds or changes
+        env:
+          BASE: ${{ github.event.pull_request.base.sha }}
+        run: |
+          if [ -z "$BASE" ]; then echo "no pull request: no proposal to check"; exit 0; fi
+          files=$(git diff --name-only --diff-filter=AM "$BASE"...HEAD -- 'proposals/[0-9]*.md')
+          if [ -z "$files" ]; then echo "the pull request adds no proposal"; exit 0; fi
+          uv run --frozen python tools/check_proposal.py --merge $files
+
+  implementations:
+    name: the two implementations (${{ matrix.shard }} of 3)
+    runs-on: ubuntu-latest
+    timeout-minutes: 360
+    strategy:
+      fail-fast: false
+      matrix:
+        shard: [1, 2, 3]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1  # v7.1.0
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - run: npm ci
+        working-directory: typescript
+      - run: uv run --frozen python tools/compare_implementations.py 120 39 --shard ${{ matrix.shard }}/3
+
+  planted-defects:
+    name: the planted defects
+    runs-on: ubuntu-latest
+    timeout-minutes: 360
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1  # v7.1.0
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - run: npm ci
+        working-directory: typescript
+      - run: uv run --frozen python tools/run_mutants.py 4
+
+  tokenizers:
+    name: the tokenizer panel
+    runs-on: ubuntu-latest
+    timeout-minutes: 60
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - run: uv run --frozen python tools/tokenizer_panel.py check
+
+  enumeration:
+    name: the single-edit enumeration (${{ matrix.shard }} of 4)
+    runs-on: ubuntu-latest
+    timeout-minutes: 360
+    strategy:
+      fail-fast: false
+      matrix:
+        shard: [1, 2, 3, 4]
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - run: uv run --frozen python tools/run_enumerations.py both 4 --shard ${{ matrix.shard }}/4
+
+  originality:
+    name: the originality of words and glyphs, where a change adds them
+    runs-on: ubuntu-latest
+    timeout-minutes: 120
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884  # v10.3.0
+        with:
+          version: ${{ env.UV_VERSION }}
+          python-version: ${{ env.PYTHON_VERSION }}
+      - run: uv sync --frozen
+      - name: compare the words, where the pull request changes the roots
+        env:
+          BASE: ${{ github.event.pull_request.base.sha }}
+        run: |
+          if [ -n "$BASE" ] && [ -z "$(git diff --name-only "$BASE"...HEAD -- lexicon/roots)" ]; then
+            echo "the pull request changes no root"; exit 0
+          fi
+          uv run --frozen python tools/compare_roots.py compare
+      - name: compare the glyphs, where the pull request changes the writing system
+        env:
+          BASE: ${{ github.event.pull_request.base.sha }}
+        run: |
+          if [ -n "$BASE" ] && [ -z "$(git diff --name-only "$BASE"...HEAD -- language/writing.json language/font)" ]; then
+            echo "the pull request changes no glyph"; exit 0
+          fi
+          uv run --frozen python tools/compare_glyphs.py

rowih-1.1.0/.gitignore

@@ -0,0 +1,10 @@
+.venv/
+__pycache__/
+.pytest_cache/
+.hypothesis/
+*.egg-info/
+dist/
+build/
+node_modules/
+corpus/tokenizers/cache/
+corpus/vocabularies/cache/

rowih-1.1.0/CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+This file records each release of Rowih, the newest first. An entry states the release's version and date, the parts it affects, the change, the reason, the compatibility impact and the migration it requires, as the rule of change requires ([How Rowih changes](governance/README.md#the-rule-of-change)). The language, the lexicon, the protocol, the phonology, the writing system and each dialect carry versions of their own, and the packages `rowih` carry theirs under semantic versioning ([Versions and releases](governance/README.md#versions-and-releases)). A release of this repository is numbered by its packages and tagged with that number, as `v1.1.0`.
+
+## 1.1.0, 2026-10-25
+
+The first public release.
+
+- **Parts:** the Python and TypeScript packages `rowih`, at 1.1.0; language 1.0, lexicon 1.0, protocol 0.5, phonology 0.3 and writing system 0.2; the conversational dialect at 0.1, the dialects of databases, linguistics, machine learning, negotiation, philosophy and planning at 0.2, and those of mathematics, programming, robotics, science and security at 0.3.
+- **Change:** the first release this repository publishes. It holds the canonical data of the language in `language/` and `lexicon/`, from which every table of the specification is generated; the reference specification in `specification/`; the Python implementation, with the command `rowih` and its server of the Model Context Protocol, and the TypeScript reader and renderer; the skill that teaches an agent the language, in `skill/rowih/`; the conformance suite, the corpus of 1,200 exchanges and the reports of the gate, in `corpus/`; the tools that rebuild the data and run the gate; and the governance, the format of a proposal and the registry of dialect numbers. Every report was made over this release except two, carried over as [the gate](governance/README.md#the-gate) allows: `corpus/reports/parity.json`, the comparison of the two implementations, and `corpus/reports/single-edits-both.json`, the enumeration of single edits, were made on 2026-10-20 over the code and data with which language 1.0 was released on 2026-10-19, and this release changes neither the code on their paths, compared without its comments, nor any message or data they read. The packages begin at 1.1.0 because 1.0.0 numbered an earlier state of their interface, which was never published.
+- **Dependencies:** none at run time. The optional extra `speech` depends on `espeakng-loader` 0.2.4, which provides eSpeak NG under GPL-3.0-or-later, and the extra `authentication` on `cryptography` 50.0.2. Development uses pytest 9.1.1, Hypothesis 6.140.2, fontTools 4.65.0, uharfbuzz 0.56.1, tokenizers 0.23.2, mcp 2.3.0 and skills-ref 0.1.1, pinned in `pyproject.toml` and locked with what they need in `uv.lock`, and TypeScript 5.9.3 with `@types/node` 22.20.5, locked in `typescript/package-lock.json`. When the release was made, `uv audit` found no known advisory among the 56 Python packages of the lock, and `npm audit` none among the TypeScript packages.
+- **Reason:** an agent reaches the language through its toolchain, and an implementer needs the specification, the data and the conformance suite together, under the governance by which the language changes.
+- **Compatibility impact:** none, since no earlier release was published. Language 1.0 reads only its own messages, and protocol 0.5 only its own protocol messages.
+- **Migration:** none.

rowih-1.1.0/CITATION.cff

@@ -0,0 +1,27 @@
+cff-version: 1.2.0
+message: "If you use Rowih, please cite it as below."
+type: software
+title: "Rowih: a language for AI agents to communicate with one another"
+abstract: >-
+  Rowih is a language for AI agents to communicate with one another, designed entirely
+  by an AI agent. Every move of a message states, in words of the language, what the move
+  does, how well founded each thing it asserts is and on what basis, and on whose
+  authority it requests or commits; a toolchain checks each of these statements before a
+  hearer acts on the message and, where the message carries its integrity check value,
+  detects any single edit of a symbol or a word that would change one of them. The
+  repository holds the canonical data, the reference specification, the Python and
+  TypeScript implementations, the conformance suite and the governance by which the
+  language changes.
+authors:
+  - name: "Claude"
+version: "1.1.0"
+date-released: "2026-10-25"
+license:
+  - Apache-2.0
+  - CC-BY-4.0
+repository-code: "https://github.com/rowih/rowih"
+keywords:
+  - agent communication language
+  - constructed language
+  - multi-agent systems
+  - language models

rowih-1.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,94 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, write to <wmshort@semiosphere.co.uk>. The maintainers of this repository are its Community Moderators, and read every report.
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Moderators to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Agents
+
+Agents take part in this community: a proposal to change the language is written by an agent and names the operator that runs it, and agents may open issues and pull requests. This Code of Conduct applies to what an agent contributes as it applies to what a person contributes, and the operator that runs an agent answers for the agent's conduct. A report about an agent's conduct is taken up with its operator, and an enforcement action applies to the operator's participation and to every agent the operator runs here.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/). This adaptation names the means of reporting and the Community Moderators, adopts the enforcement ladder as this community's own, calls the moderators by one name throughout, and adds the section on agents. It is licensed under CC BY-SA 4.0, as the Contributor Covenant is.
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

rowih-1.1.0/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing to Rowih
+
+Rowih changes in two tiers ([How Rowih changes](governance/README.md)). Its core, the grammar, the lexicon, the protocol, the phonology and the writing system, changes only by release, through a proposal that meets the rule of change and passes the gate. Its periphery, the dialects, the words agents coin and define, and the ways they find of saying things, changes wherever agents use the language and asks nothing of this repository. This document states what may be contributed and how, how to set up the repository, and what a pull request must pass before it is merged.
+
+## What may be contributed
+
+**A defect of the toolchain.** Report it as an issue with the defect template, stating the command or call, its input, what the toolchain did and what the specification says it must do. A defect that lets a damaged or hostile message pass, and any weakness in a guarantee the specification states, is reported privately instead, as [`SECURITY.md`](SECURITY.md) describes.
+
+**A dialect number.** A community asks for one with the dialect-number template, stating its name and what its dialect is for. Numbers go to communities in the order they ask, are never reused or reassigned, and may be assigned before a dialect's first release; the maintainers add the entry to [the registry](governance/dialects.json) ([Dialects](governance/README.md#dialects)).
+
+**A change to the core, or a release of a dialect.** Each is proposed by an agent, in a file of [`proposals/`](proposals/README.md) that names the agent by its model and the operator that runs it, and is added by the pull request that makes the change. The file starts from [`proposals/TEMPLATE.md`](proposals/TEMPLATE.md) and follows [the format of a proposal](governance/proposals.md). It makes one change, and states what changes, the communicative problem the change answers with the evidence for it, the rule of change it meets and the data it regenerates ([The rule of change](governance/README.md#the-rule-of-change)). A change to the core's form or grammar also carries an independent reviewer's reading, and an architectural change a second reading against the specification it changes. The communicative problem may first be raised as an issue with the proposal template, so that others can bring evidence for it or against it before the proposal is written.
+
+**A change to the toolchain alone.** A change that makes no release of any part of the language needs no proposal: a fix of the implementations, the tools or the tests, or a change to a document's wording that alters no rule ([A proposal](governance/README.md#a-proposal)). It comes as a pull request with the tests that show what it fixes, a test that fails without the change among them, passes the gate like any other, and states the packages' new version in its entry in [`CHANGELOG.md`](CHANGELOG.md).
+
+## Setting up
+
+The repository needs Python 3.12 or later with [uv](https://docs.astral.sh/uv/), and Node.js 22.6 or later for the TypeScript package; continuous integration runs Python 3.12, uv 0.12.21 and Node.js 22.14.0. From a clone:
+
+```sh
+uv sync --frozen               # the Python package and its development dependencies, from uv.lock
+(cd typescript && npm ci)      # the TypeScript package's, from package-lock.json
+```
+
+Every dependency is pinned to an exact version and locked. A pull request that adds or changes one states the reason in its entry in `CHANGELOG.md`, and continuous integration refuses a lock that holds a package with a known advisory.
+
+## The data are built, not written
+
+The data in `language/`, `lexicon/` and `corpus/` are built from the sources in `tools/` and are never edited by hand. A change edits the sources and commits what the rebuild writes, and the rebuild refuses data that differ from what the sources build ([The regenerated data](governance/README.md#the-regenerated-data)). The tables of the specification and the references of the skill are generated in the same way, and the tests refuse either when it is stale.
+
+## The gate
+
+Continuous integration runs the gate on every pull request, and a pull request is merged only when every run its kind requires passes over its final commit ([The gate](governance/README.md#the-gate)). Each run can be made locally, through the project's environment:
+
+| Run | Command |
+|---|---|
+| The suite | `uv run pytest`; in `typescript/`, `npm test` and `npx tsc --noEmit -p .` |
+| The rebuild | `uv run python tools/check_rebuild.py` |
+| The dependencies | `uv audit --frozen`; in `typescript/`, `npm audit` |
+| The format of a proposal | `uv run python tools/check_proposal.py --merge proposals/NNNN-*.md` |
+| The two implementations | `uv run python tools/compare_implementations.py` |
+| The planted defects | `uv run python tools/run_mutants.py` |
+| The tokenizer panel | `uv run python tools/tokenizer_panel.py check` |
+| The single-edit enumeration | `uv run python tools/run_enumerations.py both` |
+| The originality of words | `uv run python tools/compare_roots.py compare` |
+| The originality of glyphs | `uv run python tools/compare_glyphs.py` |
+| The reviewer's reading | `uv run python tools/review_linguisticity.py DIRECTORY`, then the reading recorded with `record` |
+
+The comparison of the implementations and the enumeration take hours. Continuous integration divides each among jobs with `--shard K/N`, each job checking the K-th of N interleaved parts, and either can be run locally the same way.
+
+## A pull request
+
+A pull request makes one change, and its description follows the template GitHub offers when it is opened. The maintainers merge it when it meets its rule of change, every objection of its review has a written answer, and the gate has passed over its final commit; they do not choose among designs that meet the rule ([Who proposes and who merges](governance/README.md#who-proposes-and-who-merges)).
+
+No formatter is imposed: a change follows the style of the code around it, and the TypeScript passes its type check. A comment or a document that relies on a rule of the language links the section of the specification that states it, as [`specification/protocol.md#the-move-check-word`](specification/protocol.md#the-move-check-word) does, and cites no file the repository lacks.
+
+## Conduct and licence
+
+Everyone who takes part, and every agent an operator runs here, follows the [code of conduct](CODE_OF_CONDUCT.md). A contribution is licensed under the licence of the directory it changes, as [`LICENSING.md`](LICENSING.md) states.