agenticreplay 0.0.0-stage → 0.1.0

package/.dockerignore

@@ -0,0 +1,11 @@
+.git
+node_modules
+**/node_modules
+**/dist
+**/*.tsbuildinfo
+**/__pycache__
+**/build
+**/.venv
+.agenticreplay
+prompt
+companion-kiokuko-dsh.patch

package/.gitattributes

@@ -0,0 +1,19 @@
+# A trace is evidence, and its integrity is a byte hash over the file. Git's newline conversion
+# rewrites those bytes on a Windows checkout, so a freshly cloned example fails its own integrity
+# check for a reason that has nothing to do with the reader. Before this file existed, every trace
+# under examples/ arrived with CRLF on Windows and `verify_integrity()` returned False on a run
+# that was intact in the repository — the failure mode this project exists to rule out.
+
+# Normalise to LF in the index and check out LF everywhere. The tooling, the tests and the trace
+# format all assume LF; nothing here wants CRLF.
+* text=auto eol=lf
+
+# Content-addressed. Never rewritten, in either direction.
+examples/traces/** -text
+packages/*/fixtures/** -text
+packages/*/test/fixtures/** -text
+
+*.png binary
+*.jpg binary
+*.gz binary
+*.zip binary

package/.github/workflows/ci.yml

@@ -0,0 +1,146 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  check:
+    name: check (node ${{ matrix.node }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        node: ['24', '26']
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node }}
+          cache: npm
+      - uses: actions/setup-python@v5
+        with: { python-version: '3.12' }
+      - run: npm ci
+      - run: npm run fmt:check
+      - run: npx tsc --build
+      - run: npx vitest run --reporter=verbose
+
+  conformance:
+    name: trace format conformance
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: '24', cache: npm }
+      - run: npm ci
+      - run: npx tsc --build
+      # Every example trace shipped in the repo must validate against the normative schema.
+      # This is what makes the format a format rather than whatever the writer happens to emit.
+      - run: node scripts/conformance.mjs
+      # "Replay is reliable" as a number that regresses visibly rather than as a sentence. The
+      # budgets live beside the corpus in the script; a change that costs fidelity fails here.
+      - run: node scripts/fidelity.mjs --check
+
+  integrations:
+    name: framework integrations
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '24'
+          cache: 'npm'
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - run: npm ci
+      - run: npx tsc --build
+      # The frameworks this speaks for. A check whose package is missing is skipped rather than
+      # failed, so a contributor can run the suite without all of them.
+      - run: >
+          pip install openai anthropic litellm langgraph langchain-openai browser-use haystack-ai
+          crewai openai-agents openhands-sdk llama-index-core llama-index-llms-openai
+      # Mastra is the one framework here that is JS, and it is 130 MB — more than this repo's whole
+      # dependency tree. `--no-save` keeps it out of package.json so it costs this job and nothing
+      # else: no npm ci anywhere else gets slower, and a contributor who has not run this line gets
+      # a skip rather than a failure, exactly as the pip line above behaves.
+      - run: npm install --no-save @mastra/core @ai-sdk/openai ai
+      # From the tree, not PyPI: the `openai-agents-handoff` and `langgraph-nodes` checks exist to
+      # prove the adapters in *this* commit work, and installing a published copy would test the
+      # last release instead.
+      - run: pip install -e python-openai-agents
+      - run: pip install -e python-langgraph
+      # `--require-all`, because installing them above was never what enforced it. Two checks were
+      # added without a line here and CI stayed green on the skips, while the README said "in CI"
+      # about both. A skip is now a failure on this runner, so forgetting the line above fails
+      # loudly instead of quietly making a claim untrue.
+      - run: node test/integrations/run.mjs --require-all
+      # Not part of the matrix: this records nothing and replays nothing. It asks CrewAI which model
+      # names it resolves and fails if the answer has drifted from what `docs/integrations.md` says.
+      # It exists because that claim was wrong once — the measurement behind it used a model name no
+      # known-model list contains, and read the refusal as being about the prefix.
+      - run: python test/integrations/agents/crewai_model_names.py
+        working-directory: .
+        env:
+          OPENAI_API_KEY: unused-but-crewai-wants-one
+      # Same shape, same reason: LlamaIndex refuses any model name outside a list compiled into it,
+      # before a request is made. That is a real limit on pointing it at a gateway, `docs/integrations.md`
+      # now says so, and this is what fails when it stops being true.
+      - run: python test/integrations/agents/llama_index_model_names.py
+        working-directory: .
+
+  python-sdk:
+    name: python sdk
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: '3.11' }
+      # The SDK itself has no runtime dependencies and is meant to keep it that way, but the test
+      # runner is not the SDK: setup-python provides a clean interpreter with no pytest on it.
+      # Installing the package rather than running pytest against the source tree also checks that
+      # `pip install agenticreplay-trace` actually works, which is how anyone will really get it.
+      - run: pip install ./python[dev]
+      - run: python -m pytest python/ -q
+      # The second Python distribution in this tree. It was added with tests and with a `pip install
+      # -e` in the integrations job, and nothing ran them — the same shape as the skipped checks
+      # that job now fails on, one layer out. Its `[dev]` extra brings the Agents SDK, because two
+      # of its tests are about how `install()` registers with it.
+      - run: pip install ./python-openai-agents[dev]
+      - run: python -m pytest python-openai-agents/ -q
+      # The third. Its `[dev]` extra brings langgraph and langchain-core, because the half of its
+      # suite that matters builds real graphs and invokes them — the unit tests assert what
+      # langchain-core is believed to pass, and only a real graph keeps that belief honest.
+      - run: pip install ./python-langgraph[dev]
+      - run: python -m pytest python-langgraph/ -q
+
+  plugin-api-neutrality:
+    name: plugin API neutrality
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: '24', cache: npm }
+      - run: npm ci
+      # A vendor plugin must reach AgenticReplay only through the published interface.
+      # If this ever fails, a plugin has grown a privileged path into the core.
+      - run: node scripts/check-neutrality.mjs
+
+  distributions:
+    name: installed npm packages and Docker
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: '24', cache: npm }
+      - run: npm ci
+      - run: npm run build
+      - run: node scripts/installed-smoke.mjs
+      - run: docker build -t agenticreplay-local .
+      - run: docker run --rm --entrypoint agenticreplay agenticreplay-local --version

package/.grok-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "name": "agenticreplay",
+  "version": "0.2.2",
+  "description": "Record, inspect, replay and fork coding-agent runs: read what an agent actually did from the evidence of its run, offline.",
+  "author": {
+    "name": "Continuum AI Corp",
+    "url": "https://github.com/Continuum-AI-Corp"
+  },
+  "repository": "https://github.com/askdkc/AgenticReplay",
+  "license": "Apache-2.0",
+  "keywords": ["agenticreplay", "agent run replay", "agent trace", "record agent run"]
+}

package/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "agenticreplay": {
+      "command": "npx",
+      "args": ["-y", "agenticreplay", "mcp"]
+    }
+  }
+}

package/.prettierignore

@@ -0,0 +1,4 @@
+dist/
+node_modules/
+*.md
+examples/

package/.prettierrc.json

@@ -0,0 +1 @@
+{ "singleQuote": true, "printWidth": 100, "semi": true, "trailingComma": "all" }

package/CONTRIBUTING.md

@@ -0,0 +1,106 @@
+# Contributing to AgenticReplay
+
+## The five-minute dev loop
+
+```console
+git clone https://github.com/askdkc/AgenticReplay
+cd AgenticReplay
+npm install
+npm run check     # format check + typecheck + tests
+```
+
+`npm run check` is the fast loop — format check, typecheck, tests — and it is the first CI job, but
+it is not all of CI. Three more jobs run commands `check` does not:
+
+```console
+node scripts/conformance.mjs      # the shipped example traces and a freshly written one both
+                                  # validate against the normative schema
+node scripts/check-neutrality.mjs # no vendor plugin reaches past @agenticreplay/plugin-api
+pip install ./python[dev] && python -m pytest python/ -q   # the Python SDK
+```
+
+`conformance.mjs` reads `packages/*/dist`, so run it after a build — `npm run check` has already
+done one by the time you get there.
+
+Run those four on Node 24 and Node 26; CI exercises both runtime lines.
+
+The published CLI and the development toolchain both require Node 24 or newer. The root
+`package.json` declares `>=24.0.0`, so `npm ci` reports an unsupported runtime immediately.
+
+Working on one package:
+
+```console
+npx vitest run packages/core      # one package
+npx vitest                        # watch mode, everything
+npx tsc --build                   # typecheck the project graph
+```
+
+If that took longer than five minutes on a clean machine, that is a bug — please open an issue
+saying where it stalled. Time-to-first-contribution is a metric we actually track.
+
+## Tests come first
+
+This project is built test-first, and not as a slogan: the payload schema, the checkpoint snapping
+rules and the redactor all had real bugs caught by a test written before the implementation.
+
+Write the failing test, run it, confirm it fails **for the reason you expect**, then implement.
+A test that has never been red has not proven anything.
+
+## What we are looking for
+
+The highest-value contributions, in order:
+
+1. **Adapters** — support for an agent harness we do not cover. `packages/adapters/` has the
+   pattern; the interface is two methods.
+2. **Providers** — a model API we cannot fork onto. `packages/providers/` has two examples.
+3. **Redaction rules** — a secret shape we fail to catch. These are small, self-contained, and
+   they protect everyone.
+4. **Trace analyzers** — anything that reads a trace and finds something useful. The loop detector
+   in `packages/viewer/src/render.ts` is the model: about forty lines, no privileged access.
+
+## Rules of the road
+
+- **No new runtime dependencies** without discussion. The CLI has none beyond a JSON Schema
+  validator, and a debugger you install to diagnose a broken environment should not drag in a
+  hundred packages. `devDependencies` are easier, but still argue for them.
+- **The spec is normative.** `spec/agenticreplay-trace-v0.md` and the JSON Schema come first; TypeScript
+  types are verified against them. If you need a format change, change the spec in the same PR and
+  bump the schema version. Adding an event type is a MINOR bump; changing one is MAJOR.
+- **Readers skip what they do not understand.** Never make an unknown event type an error.
+- **Replay never silently approximates.** If a match is inexact, emit a `divergence` event. A
+  debugger that quietly guesses is worse than no debugger, because you will believe it.
+- **Secrets never reach disk or a TTY.** Redaction lives in the write path. If you add a new sink,
+  it goes through the redactor. If it *cannot* — anything written by the agent's own process, or by
+  a child of it, is on disk before agenticreplay sees it — then ask one question first: **does anything read
+  this file after the run?**
+  - No: it is a transport, not part of the trace. Keep it out of the run directory, write an
+    allow-list of the fields something actually reads rather than whatever the payload holds, and
+    delete it once it has been read. `shell-frames.jsonl` and the agent-spans file are both this.
+  - Yes: it stays, and it is unredacted material in a directory people share. Say so in
+    SECURITY.md, and make sure `agenticreplay scrub` at least *searches* it — a scrubber that reports
+    "nothing matched" over a file it never opened is the one failure mode SECURITY.md says it must
+    not have. `mcp-frames.jsonl` is this: a replay answers from it, and rewriting a frame changes
+    the key it is looked up by, so a scrub that edited it would make the replay serve a different
+    recorded response rather than fail.
+- **A new field is a new sink.** The redactor works on payloads derived from the incoming request,
+  so a value sourced from anywhere else — configuration, a flag, an environment variable — arrives
+  having bypassed it. Adding an attribute, ask where its value comes from and whether that source
+  can carry a credential; `agenticreplay setup --gateway` accepts any URL, and `https://user:pw@gw` and
+  `https://gw?key=…` are both ordinary ways to configure a gateway. This was learned the hard way:
+  a field naming the origin that answered each call was verified four ways, all of them asking
+  whether the value was *correct* and none asking what else could be in it. Review caught it.
+  `packages/cli/test/no-credential-in-attrs.test.ts` is the part that cannot be forgotten — it
+  walks every attribute of every event and fails on the shape, whatever the field is called.
+
+## Sign your commits
+
+We use the [Developer Certificate of Origin](https://developercertificate.org/). Add a `Signed-off-by`
+line with `git commit -s`. There is no CLA and no copyright assignment.
+
+**This one is honour-system.** No CI job checks for the trailer and no bot will ask you for it, so a
+PR without one is not blocked — we would rather tell you that than have you discover it from a
+green tick. If we ever start enforcing it, it will be a check you can see, not a surprise on merge.
+
+## Code of conduct
+
+By participating you agree to the [Contributor Covenant](CODE_OF_CONDUCT.md).

package/Dockerfile

@@ -0,0 +1,30 @@
+# Ships only the MCP server, not the recorder.
+#
+# Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git
+# index. None of that survives a container boundary, so `agenticreplay record` inside here would watch an
+# empty namespace. What does travel is the read side: the six MCP tools serve runs that already
+# exist on disk, so a client mounts its `.agenticreplay` directory and reads it.
+#
+#   docker run -i --rm -v "$PWD/.agenticreplay:/work/.agenticreplay:ro" agenticreplay
+#
+# Read-only is deliberate. `agenticreplay replay` and `agenticreplay compare` execute a real agent and can spend
+# money, so a container that only ever reads is the honest default; drop `:ro` if you mean to
+# fork from in here.
+FROM node:24-alpine AS build
+WORKDIR /src
+COPY . .
+RUN npm ci && npm run build \
+    && mkdir /artifacts \
+    && npm pack --workspaces --pack-destination /artifacts
+
+FROM node:24-alpine
+
+ENV NODE_ENV=production
+WORKDIR /work
+
+# Install every matching workspace tarball from this checkout, including unpublished renamed packages.
+COPY --from=build /artifacts /artifacts
+RUN npm install -g --omit=dev /artifacts/*.tgz && rm -rf /artifacts
+
+# stdio transport — the client owns stdin/stdout, so no port is exposed.
+ENTRYPOINT ["agenticreplay", "mcp"]

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/MAINTAINERS.md

@@ -0,0 +1,24 @@
+# Maintainers
+
+| Area | Maintainer |
+|---|---|
+| Trace format & core | @Continuum-AI-Corp |
+| Proxy & replay | @Continuum-AI-Corp |
+| Adapters & providers | @Continuum-AI-Corp |
+| Viewer | @Continuum-AI-Corp |
+
+## Governance
+
+Today this is maintainer-led: the people above merge changes and cut releases.
+
+**The path out of that is written down on purpose.** Once three maintainers from outside the
+founding organisation are active, we form a technical steering committee with a published charter,
+and format changes require its consent rather than ours. Ambiguity about who controls an open
+format is a reason not to build on it, so we would rather commit to the trigger now than be asked
+about it later.
+
+## Becoming a maintainer
+
+Sustained, high-quality contribution in an area, plus the judgement to say no to changes that widen
+the surface. Adapters and providers are the usual route in. Ask — we would rather have the
+conversation early than have you guess.