OPCP v0.2.0

Open Process Control Plane (OPCP) is an open framework that lets a business keep its process logic, context and authority, while renting capabilities from any supplier. This is a draft for comment.

Try it without installing anything

Download opcp-exit-readiness-form-0.2.0.html, open it in any browser, and answer the questions for one critical process. It works offline; nothing you type leaves your device. To see what the resulting report looks like, open opcp-example-report-0.2.0.html (a hypothetical bank).

To turn your answers into a report, install the package (Python 3.10+):

pip install opcp-0.2.0-py3-none-any.whl
opcp scorecard run answers.json -o report.html

What's in 0.2.0

• Exit-Readiness Scorecard. It rates how dependent each critical process is on its supplier: logic ownership, context, authority, lock-in, contract exit terms, time-to-swap, fallback, and concentration across processes.
• Standard question bank. 22 questions with stable IDs, anchored options, a named respondent role for each, triage and consistency checks.
• Evidence levels. Every answer is Declared, Documented or Tested, and every measure shows its weakest evidence.
• 74 clause-level references to 15 regulations, guidelines and standards: DORA and its RTS, the EU Data Act, EBA, APRA CPS 230, MAS, PRA, FSB, the Basel Committee, IOSCO, NIST and CSA.
• 20 verified research sources explaining why each measure matters (docs/EVIDENCE.md).
• Specification for capability archetypes, the standard envelope, two-stage routing and an authority gate based on Reversibility Classes R0-R4.
• Reference runtime with adapter and runtime conformance checks.
• DORA register export. opcp scorecard export answers.json -o dora.csv suggests EU DORA register of information values from your answers, with the reasoning for each. These are suggestions to review, not a filing.
• Pilot playbook and swap-drill guide. How to run the scorecard across three processes in six weeks, and how to rehearse a supplier swap safely.

Status and limits

• Self-assessment, not certification. Reports are a self-assessment against a published method, not a certification, and references show relevance, not compliance.
• Check locators first. Confirm every locator against the official text before relying on it; docs/REFERENCES.md records how each source was checked.
• Expect change. The specification and question bank will change based on feedback.

Licensed under Apache 2.0. Contributions are welcome under the DCO (see CONTRIBUTING.md). Contact: hello@twomuchlabs.com.