Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
#
# The spec is the source of truth for the protocol. All changes are
# reviewed by stewards; substantive and breaking changes additionally
# follow the comment-period process in GOVERNANCE.md.

* @fuax16
23 changes: 21 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,32 @@ See [§4 of the spec](concept-and-spec.md#4-reference-implementation-plan) for t

## Contributing

See [CONTRIBUTING.md](https://github.com/openagp/.github/blob/main/CONTRIBUTING.md) and [GOVERNANCE.md](https://github.com/openagp/.github/blob/main/GOVERNANCE.md) at the org level.
See [CONTRIBUTING.md](https://github.com/openagp/.github/blob/main/CONTRIBUTING.md) and [GOVERNANCE.md](https://github.com/openagp/.github/blob/main/GOVERNANCE.md) at the org level. For routing — questions vs. bugs vs. spec changes — see [SUPPORT.md](https://github.com/openagp/.github/blob/main/SUPPORT.md).

For spec changes:
1. Open an issue describing the change and rationale.
1. Open a [Spec change issue](https://github.com/openagp/spec/issues/new?template=spec_change.yml) describing the change and rationale.
2. PR adds a decision record in `decisions/`.
3. Substantive changes have a 2-week comment period; breaking changes have 4 weeks.

### Local checks before opening a PR

```bash
# Validate every event fixture against schemas/event.json (same script CI runs)
pip install "jsonschema>=4.21.0" "referencing>=0.34.0"
# see .github/workflows/validate.yml for the exact validator

# Run the cross-language test vectors against an SDK
cd ../sdk-python && pytest tests/test_interop.py
cd ../sdk-typescript && npm test -- interop
cd ../cts && make vectors
```

If you're changing a schema or a test vector, **the SDKs and `agp-cts` must all stay green** — they share these inputs.

### Questions

Use [GitHub Discussions on this repo](https://github.com/openagp/spec/discussions) for design conversations and "how do I model X?" questions.

## License

[CC BY 4.0](LICENSE) — you may share and adapt the spec for any purpose, including commercially, with attribution.
Loading