Publish JSON Schemas for the decision record and audit chain, dialect recordings and receipts as consumed, so the record-shape catalog covers them
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- json, python
- Domain
- backend-api-design, testing
Research direction
Read the existing schemas, vectors, and record-shape catalog to identify the three format families and their current shapes. Add schemas under the stated namespace, then run tools/record_shapes.py record to generate a change record for each addition. Add tests validating every vector in each family; done means the tests pass and the catalog includes all three schemas.
Written by the indexing model from the issue text.
Description
#285 (#256) added the record-shape catalog and fingerprints every JSON Schema the specification defines. Three record formats #256 names have no schema in this repository: the decision record and audit chain, the dialect recordings, and receipts as consumed. Their shapes live in prose, verifier code and vectors only, so the catalog cannot fingerprint them and they have no format-status record.
To close this, publish a schema for each format under the https://judgmentpack.org/schema/ namespace. The catalog then picks them up automatically, with a change record per addition, generated by tools/record_shapes.py record. Each schema must agree with the existing vectors; add a test that validates every vector of the family.
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 98
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Judgment-Pack/judgment-pack-spec
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Judgment-Pack/judgment-pack-spec#282 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Judgment-Pack/judgment-pack-spec#275 ·
Maintainers usually reply within 1 day
-
Cover a rule's or an exception's reference list written without its array, or with a repeated entryOpengood first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
Judgment-Pack/judgment-pack-spec#158 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
Judgment-Pack/judgment-pack-spec#287 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Judgment-Pack/judgment-pack-spec#284 ·
Maintainers usually reply within 1 day
All issues in Judgment-Pack/judgment-pack-spec
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-samples/sample-per-model-bedrock#795 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Pretalx reports older version to be the latest release than what is actually installed and availableOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
micropython/micropython#19906 ·
Maintainers usually reply within 1 day