Resources

Support and community

Where to go for each need.

Approved by the Board for implementation · 20 November 2026

Status

Routes marked new open with the hub. No forum or chat channel yet: we start with what we can look after.

Six needs, six routes

A developer who is stuck should know in one step where to go.

What do you need?the Support page asksA question about a specificationThe comment route on that specification’s pageA change you want to proposeThe contribution flowA partnership or deployment enquiryThe contact page, with a Developer hub subjectA security vulnerabilityThe security address, never a public threadA concern about a CRIS system or claimRequest an audit or make a complaint, on the Audit Suite pageHelp as a CIX contributorThe CIX door on the contact page, not the developer hub; contributor help opens with the pilot
Six needs, six routes: one place for each. A security vulnerability goes to the security address, never a public thread.

Response times marked proposal are for Systems Engineering to confirm.

How contributions work

Anyone can comment on a specification. A proposal is a written change with reasons. Systems Engineering reviews it in public and decides to accept, revise or decline, giving reasons either way. An accepted change becomes a new version, and the changelog credits the contributor by name if they wish.

1 Commenton a specification,from its page2 Proposala written change,with reasons3 Reviewby SystemsEngineering, in public4 Decisionaccept, revise ordecline; reasons given5 New versionthe changelogcredits younot accepted: the reason is published, and the thread stays openChanges to the Invariant, or to anything that weakens a gate, need Board approvalThe AI Constitution’s amendment rules apply, not this flow.
From a comment to a new version, with public reasons and credit. Specification contributors are credited, not paid; paid contribution happens on CIX, under its own rules.

One limit applies: a change to the Continuity Invariant, or anything that would weaken one of the two gates, is not decided in this flow. Under our proposed AI Constitution a change that would weaken the Invariant is an entrenched, mission-protected matter that needs every approval the bylaws and the certificate require (see who may change it); other changes to the gates go to our Board under its amendment rules.

At launch, comments and proposals are made from each specification’s page, with a public thread of replies. Whether we also open a public code repository for specifications and schemas is a decision for Systems Engineering; if we do, it becomes the place for proposals, and this page will link it. Contributors agree to short contributor terms first.

Community, honestly sized

CRIS has no developer community yet, and this page does not pretend otherwise: no forum with three posts, no chat channel nobody reads. We start with what we can look after: comment threads on specifications, answered by named Systems Engineering staff. A public forum or repository follows only when there is someone to look after it.

Developer programmes

None exists yet. We list programmes here only when they exist. Candidates for later, each a decision for the board or the Founder:

  • Continuity Learn courses for engineers, through the Academy of Philosophy-Engineering (planned; under a written agreement not yet recorded).
  • Research partnerships for universities working on the Invariant, verification or CTU metering, through Join the ecosystem.
  • An accredited auditor programme, for people and firms who want to audit CRIS proofs, once the audit kit opens.
  • Office hours with Systems Engineering, once the first specifications are published.

The Academy of Philosophy-Engineering. An organisation also led by our Founder. Any work with CRIS is under a separate written agreement on arm’s-length terms. Related organisations

News for developers

The changelog feed is the main channel. Larger moments, such as a specification reaching 1.0 or an interface opening, are also posted on News with a link back to the hub.

Owner: Systems EngineeringNext review: 2027-05-11