Working group

How a change to the standard is made

A specification with no route for an objection is a publication, not a standard. This is the route.

9Decision recordsall published

3Process documents

Step 1

Open an issue

State the defect against a specific pointer in a specific release. A finding without a pointer is an opinion.

Step 2

Bring a fixture

A change to the profile arrives with the fixture that fails before it and passes after. The corpus is the argument.

Step 3

Record the decision

Anything architectural lands as an ADR with the alternatives it beat and the conditions it carries.

Setup

Run the gates before you open anything

Every change passes the same checks the repository runs in CI.

shell

git clone https://github.com/verastd/vera
cd vera
uv venv .venv --python 3.11
uv pip install --python .venv/bin/python -e packages/ver-validator
# the conformance corpus is the contract
PYTHONPATH=packages/ver-validator/src .venv/bin/python \
    -m pytest tests/ -q

The thesis test is tests/test_cpnp_determinism.py: strip every byte of descriptive metadata from a photograph and its content hash changes while its pixel hash, perceptual hash and embedding do not. If it fails, nothing else about the repository matters.

Repository Contributing guide

Process

The documents that govern the track

10 sections

Governance

Roles, how a change is proposed, how a decision is recorded, and how an objection is heard.

8 sections

Contributing

Development setup, the gates every change passes, and the standards-track rules.

5 sections

Security policy

How to report a vulnerability, which versions are supported, and what the prototype does not defend.

Security

Report a vulnerability privately

The runnable stack is an experimental prototype. Do not deploy it where untrusted input, an untrusted network or an untrusted operator can reach it.

Security policy