Skip to content

RaC Conformance v1.0 evidence and maturity programme #38

Description

@edithatogo

Objective

Bring RaC Conformance from a hardened evidence-first 0.x programme to a defensible v1.0 through stable compatibility commitments, cross-domain process evidence, platform portability, engineering hardening, and independent implementation.

Release principle

More internally authored examples do not establish maturity. v1.0 requires:

  • a frozen and versioned normative contract surface;
  • a platform-neutral process profile;
  • evidence from materially different process and rules domains;
  • an optional Camunda portability implementation;
  • hostile-input, compatibility, performance, reproducibility, SBOM, and provenance evidence;
  • at least three maintained consumers across two domain classes; and
  • at least one independently controlled implementation and independently verifiable result.

Authority and safety boundaries

  • Regulators, HTA bodies, payers, service-funding bodies, and post-market authorities remain distinct.
  • Medsafe/Pharmac, TGA/PBAC-PBS/MSAC-MBS, MHRA/NICE, and FDA/payer-specific US processes are not treated as equivalent authorities.
  • No runtime AI makes legal, clinical, disclosure, market-authorisation, reimbursement, or patient-access decisions.
  • Only public or appropriately licensed sources and synthetic health cases may enter committed fixtures.

Child tracks

Native subissues mirror the nine local Conductor tracks. Local specs and plans remain authoritative.

Completion criteria

  • Foundation, process profile, health demonstrators, Camunda adapter, and hardening tracks are reviewed and complete.
  • Independent implementation gate passes under the published independence criteria.
  • All compatibility, security, release, external, and human gates have current evidence.
  • v1.0 artifacts are authorized, published, independently install-verified, and reflected in Project 19.

Local roadmap: https://github.com/edithatogo/rac-conformance/blob/main/conductor/V1_ROADMAP.md

Successor programme to the repo-local completion work tracked in #20; existing external adoption #23, papers #24, FOI governance #30, and citation/Zenodo #33 remain separate source-of-truth gates.

Track issues

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    github-projectGitHub Issues/Projects synchronization.releaseProgram release orchestration and certification.roadmap-nextgenNext-generation rules/process roadmap work.v1-roadmapRaC Conformance v1.0 maturity and release programme

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions