Guide / Contribution / Public review

Contribute records, not opinions.

A useful profile contribution brings source material, mapping decisions and review surfaces.

The goal is not to add more JSON. The goal is to make a public-rule machine profile inspectable enough for others to challenge.

01 / Contribution path

Seven steps to a reviewable profile.

A contribution should move from source to profile through visible artefacts.

Identify the public act.

Choose a specific reporting act, obligation or regulated workflow.

Pin official sources.

Name official artefacts and compute source hashes.

Create fragments.

Break source material into supportable units.

Map fields.

Derive machine-readable fields from source-supported needs.

Record judgement.

Mark assumptions, interpretation and review-required decisions.

Add test vectors.

Help implementers test without implying legal validity.

Submit for challenge.

Invite source, fragment, interpretation, currentness and overclaim review.

02 / Challenge types

A profile becomes stronger when it can be disputed.

Challenge templates make public review precise.

Source challenge

Wrong official source, missing artefact, or unsuitable source basis.

Fragment challenge

The fragment does not support the mapped field.

Interpretation challenge

The profile adds meaning not clearly present in the source.

Overclaim challenge

The profile implies compliance, approval or certainty.

Currentness challenge

Newer source material exists or old material was superseded.

Omission challenge

A source-supported requirement is absent from the profile.

03 / Contribution pack

Submit the review surface with the profile.

Good contributions include enough evidence for someone else to disagree intelligently.

FILE-01profile.json

Machine profile.

The derived operational profile and version identifiers.

FILE-02source_bundle

Official artefacts.

Source list, hashes and retrieval notes.

FILE-03mapper_report

Transformation record.

Fragments, decisions and traceability.

FILE-04tests

Reuse support.

Examples and expected outcomes for implementers.

04 / Boundary

A contribution is not a legal opinion.

It is a reviewable machine-profile proposal grounded in public source material.

This layer can show

official source artefacts named and hashed
field provenance, mapper notes and reproducibility
schema divergence against a public reference profile
where interpretation entered the machine profile

This layer cannot show

legal approval or supervisory acceptance
that a filing, firm or vendor is compliant
that a mapping is legally complete without review
that pinned sources are automatically the latest legal state