Responsibility Infrastructure Governance Charter

1. Purpose

This Charter establishes the governance arrangements for the Responsibility Infrastructure publication set.

It defines how publications are proposed, drafted, reviewed, consulted upon, approved, amended, superseded, withdrawn, archived, interpreted, and preserved.

The purpose of publication governance is to ensure that Responsibility Infrastructure instruments remain identifiable, attributable, transparent, version-controlled, reconstructable, and capable of institutional reliance.

2. Scope

This Charter applies to publications issued within the following series:

• RI — foundational, definitional, informational, and analytical publications;
• RI-STD — operational standards and specifications;
• RI-GOV — governance instruments;
• RI-REG — registry frameworks and registry specifications; and
• RI-RAIL — responsibility lifecycle and interoperability instruments.

This Charter governs the publication set. It does not replace the constitutional arrangements of any independent verification, Recognition, Registry, accreditation, licensing, or adjudication body.

3. Governance Principles

3.1 Public Record

The publication set shall operate as a public and retrievable institutional record.

The identity, title, version, status, issue date, effective date, publisher, relationships, and lifecycle history of each publication shall remain capable of examination.

3.2 Clear Authority

Authority to draft, edit, publish, approve, amend, supersede, withdraw, or archive a publication shall be defined and attributable.

Editorial participation does not automatically create authority to verify claims, grant Recognition, publish Registry standing, or decide accountability outcomes.

3.3 Separation of Functions

The following functions shall remain distinguishable:

• drafting;
• editorial review;
• consultation;
• technical evaluation;
• publication approval;
• verification;
• Recognition;
• Registry publication; and
• accountability judgment.

One organisation may participate in more than one function where permitted, but the authority exercised at each stage shall not be treated as identical.

3.4 Evidence-Based Change

Substantive changes should be supported by a documented reason.

Reasons may include implementation evidence, identified ambiguity, technical failure, interoperability requirements, legal or regulatory change, consultation findings, safety concerns, institutional experience, or demonstrated structural gaps.

3.5 Transparency

Material decisions affecting publication status or normative meaning shall be recorded.

A publication shall not be materially changed without an attributable change record.

3.6 Reconstruction

The publication history shall remain reconstructable.

Earlier versions, corrections, consultation stages, supersession relationships, withdrawals, and archival decisions should remain retrievable where reasonably practicable.

3.7 Constitutional Restraint

Publication governance shall exercise only the authority necessary to maintain the integrity of the publication set.

A governance decision shall not be used to create unrecorded powers, alter independent determinations, interfere with Registry publication duties, or convert publication administration into commercial control over institutional judgment.

4. Publication Roles

4.1 Publisher

The publisher is responsible for administering publication, preserving the official text, maintaining publication records, and ensuring that the published status is accurately displayed.

4.2 Editor

An editor prepares, reviews, coordinates, or maintains publication content.

An editor shall not be treated as having independent verification, Recognition, Registry, or adjudicative authority merely because the editor prepared or maintained the publication.

4.3 Working Group

A working group may support research, drafting, technical review, implementation testing, consultation analysis, or amendment proposals.

Working group recommendations do not take effect until the applicable publication decision has been formally recorded.

4.4 Consultation Participants

Individuals, organisations, implementers, public bodies, experts, affected communities, and other interested parties may submit comments during an open consultation.

Participation in consultation does not create ownership, approval authority, endorsement, or a right to require adoption of a proposal.

4.5 Publication Decision

A publication decision records whether an instrument is issued, advanced, amended, maintained, superseded, withdrawn, or archived.

The decision shall be attributable and reflected in the publication lifecycle record.

5. Publication Statuses

5.1 Foundational Publication

A Foundational Publication establishes the conceptual, definitional, or architectural basis of the Responsibility Infrastructure category.

Foundational Publications may be referenced normatively by later instruments but do not necessarily operate as detailed conformance standards.

5.2 Public Working Draft

A Public Working Draft is an early publication released for open review.

It is non-normative and may undergo substantial revision. Implementation against a Public Working Draft is undertaken at the implementer's own risk.

5.3 Consultation Draft

A Consultation Draft is an instrument released for formal consultation during a defined review period.

Comments, objections, implementation evidence, and proposed changes may be received and recorded before advancement.

5.4 Issued

An Issued publication is the current version made publicly available by its publisher. Issuance does not, by itself, indicate independent approval, regulatory adoption, legal force, or category-wide binding authority.

5.5 Version Status

Each publication shall separately state whether its version is Current, Superseded, or Withdrawn. Superseded and Withdrawn publications remain preserved in the Publications Registry, and permanent identifiers shall not be reassigned.

6. Publication Lifecycle

A publication may pass through the following lifecycle:

1. proposal;
2. research and drafting;
3. editorial review;
4. Public Working Draft;
5. Consultation Draft;
6. consultation review and disposition;
7. Working Draft, where applicable;
8. formal publication decision;
9. Issued publication;
10. maintenance and amendment;
11. supersession or withdrawal; and
12. archival preservation.

Not every publication is required to pass through every stage. The lifecycle used shall be proportionate to the publication's function, authority, risk, and normative effect.

7. Proposal and Drafting

A proposal for a new publication or amendment should identify:

• the problem being addressed;
• the proposed publication series;
• the intended scope;
• the affected publications or implementations;
• the reason the change is required;
• known risks or conflicts;
• the evidence supporting the proposal; and
• whether consultation is recommended.

A proposal does not become authoritative merely because it has been submitted, discussed, drafted, or published as a working document.

8. Consultation

8.1 Consultation Notice

A formal consultation should identify the publication under review, the consultation period, the method for submitting comments, and the principal questions being considered.

8.2 Consultation Record

Material consultation responses should be preserved in a form that supports later review and reconstruction.

Personal, confidential, legally restricted, security-sensitive, or commercially sensitive information may be protected or redacted where necessary.

8.3 Disposition of Comments

Consultation comments may be accepted, accepted in part, deferred, rejected, or recorded without change.

The publication authority is not required to adopt every submission. Material decisions should, however, be capable of explanation.

8.4 Reconsultation

A draft should return to consultation where revisions materially alter its scope, requirements, authority, interoperability effect, or burden upon implementers.

9. Version Control

Every published instrument shall have an identifiable version.

Version changes should distinguish between:

• major revisions — changes to scope, architecture, authority, obligations, conformance requirements, or normative meaning;
• minor revisions — compatible clarifications, additions, or improvements that do not overturn the instrument's central requirements; and
• corrections — typographical, formatting, reference, metadata, or other non-substantive repairs.

A new version shall identify its issue date and, where applicable, its effective date and the version it supersedes.

10. Amendment and Change Control

10.1 Substantive Amendment

A substantive amendment changes normative meaning, scope, requirements, authority, status, conformance conditions, or institutional effect.

Substantive amendments require a new version and an attributable lifecycle entry. Consultation should be conducted where the amendment may materially affect reliance or implementation.

10.2 Editorial Correction

An editorial correction repairs an error without changing normative meaning.

Editorial corrections should be recorded where the correction could affect citation, interpretation, implementation, or reconstruction.

10.3 No Silent Replacement

A published instrument shall not be materially rewritten while continuing to present itself as the same unchanged version.

Earlier authoritative text shall not be silently erased where preservation is necessary to determine what requirements applied at an earlier time.

11. Urgent Corrections

An urgent correction may be issued where an error creates immediate risk of serious misunderstanding, unsafe implementation, legal conflict, security exposure, institutional harm, or loss of record integrity.

The reason, authority, date, affected text, and effect of the correction shall be recorded.

An urgent correction shall not be used to bypass ordinary consultation for a wider substantive policy change.

12. Conflicts of Interest and Recusal

A person participating in a publication decision should disclose any material interest that may reasonably call their independence into question.

A conflict may arise from:

• commercial benefit;
• ownership or licensing interests;
• employment or contractual relationships;
• involvement in the implementation under review;
• involvement in the underlying verification or Recognition decision;
• personal relationships; or
• another interest capable of affecting impartial judgment.

Where appropriate, the affected person shall recuse themselves from the relevant decision.

Recusal should be recorded where it affects the authority or integrity of the publication process.

13. Interpretation

13.1 Authoritative Text

The authoritative text of a publication is the version identified in the official Publications Registry.

Drafts, presentations, summaries, messages, interviews, training materials, and explanatory guidance do not amend the authoritative text unless formally incorporated through the publication process.

13.2 Interpretation by Function

Terms shall be interpreted according to their defined function within the Responsibility Infrastructure publication set.

Ordinary workflow, productivity, compliance, software, or commercial terminology shall not override an express definition in an authoritative publication.

13.3 Ambiguity

Where a material ambiguity is identified, the interpretation should:

• preserve the purpose of the publication;
• remain consistent with normative references;
• avoid creating unrecorded authority;
• protect the integrity of responsibility records;
• preserve separation between verification, Recognition, Registry publication, and accountability judgment; and
• be recorded where future reliance may be affected.

13.4 Interpretive Notices

An interpretive notice may explain how existing text applies without changing the publication's normative meaning.

Where the proposed interpretation would change normative meaning, a formal amendment is required.

14. Challenge and Review

A person or organisation may raise a documented challenge concerning:

• an error in the published text;
• an inconsistency between publications;
• an unclear requirement;
• a procedural failure;
• an undisclosed conflict of interest;
• an incorrect status or version record;
• an interoperability problem; or
• another matter affecting institutional reliance.

A challenge does not automatically suspend the publication.

The outcome may include no change, clarification, correction, amendment, consultation, suspension, supersession, withdrawal, or another recorded response.

15. Supersession, Withdrawal, and Archival

15.1 Supersession

A publication is superseded where a later publication or version formally replaces it.

The relationship between the earlier and later instruments shall be recorded.

15.2 Withdrawal

A publication may be withdrawn where it is materially defective, unsafe, obsolete, unlawful, misleading, incompatible with the architecture, or no longer capable of institutional reliance.

The withdrawal record should identify the reason, date, authority, and effect of withdrawal.

15.3 Archival Preservation

Superseded or withdrawn publications should remain retrievable as archived records unless lawful restriction, security risk, privacy protection, or another compelling reason requires limited access.

Archival preservation does not imply that the publication remains in force.

16. Publications Registry

The Publications Registry is the authoritative source for the published status of instruments within the publication set.

A publication entry should identify, where applicable:

• publication identifier;
• title;
• series;
• type;
• status;
• version;
• issue date;
• effective date;
• publisher and editors;
• normative references;
• related publications;
• supersession relationships;
• lifecycle history; and
• available publication files.

The Registry record shall not be altered merely to conceal an earlier publication state or decision.

17. Relationship to Verification, Recognition, and Registry Standing

Publication of a standard does not verify an implementation.

Conformance with a standard does not automatically establish Recognition.

Verification does not automatically create Registry standing.

Recognition and Registry publication shall occur only through their applicable authorised processes.

This separation protects the publication set from being used as a substitute for independent institutional determination.

18. Relationship to Other Publications

This Charter should be read alongside:

• RI-001 — Definition of the Responsibility Infrastructure Category.
• RI-002 — Principles of Provable Responsibility.
• RI-003 — Core Elements of Responsibility Infrastructure.
• RI-004 — The Responsibility Record Specification.
• RI-005 — Characteristics of Responsibility Infrastructure.
• RI-GLOSS-01 — Responsibility Infrastructure Glossary.
• RI-STD-01 — The Responsibility Chain.
• RI-STD-02 — Responsibility Evidence Requirements.
• RI-STD-03 — Responsibility Verification Requirements.
• RI-REG-01 — Responsibility Infrastructure Registry Framework.

19. Governance Statement

Responsibility Infrastructure publications shall be governed through attributable authority, transparent change control, preserved history, defined status, and constitutional restraint.

No unpublished statement, private instruction, commercial interest, or silent amendment shall override the authoritative publication record.

20. Keywords

Responsibility Infrastructure, Governance Charter, Publication Governance, Publication Lifecycle, Version Control, Consultation, Change Control, Amendment, Interpretation, Conflict of Interest, Recusal, Supersession, Withdrawal, Archival, Publications Registry