OPCP v0.3.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.3.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 the results for a hypothetical bank, open opcp-example-report-0.3.0.html (the full report) and opcp-example-readout-0.3.0.html (the two-page sponsor pack).

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

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

What's new in 0.3.0

Supplier portability becomes something you can test, not just assess.

• Swap drill. A portable, pass-or-fail test that a capability can move from an incumbent supplier to a candidate without changing the business's process, context lease or authority policy. The candidate runs in shadow on the same contract and business-owned regression cases, and passes only if all six gates hold. Gates are never averaged. A proven time-to-swap must carry the drill date. Specification: spec/SWAP-DRILL.md; schema: schema/swap-drill.schema.json.
• Swap-drill tools. opcp swap-drill <evidence.json> evaluates a drill record; opcp swap-demo runs one between two simulated suppliers.
• Sponsor readout. opcp scorecard readout answers.json -o readout.html writes a two-page pack for the decision meeting: where each process stands, the decisions to take in order of urgency, and each renewing contract's last day to give notice.
• OCEL 2.0 export. opcp ocel events.jsonl -o events.ocel.json converts the runtime's event log for process-mining tools. Checked with PM4Py's OCEL 2.0 reader.
• Example process pack for SME credit origination, with a matching drill record. The process-pack format is provisional.
• Fix: the control plane uses the event log it is given, even when that log is empty.

Everything from 0.2.0 is still here: the Exit-Readiness Scorecard and offline form, the 22-question bank with evidence levels, 74 clause-level references to 15 regulations and standards, 20 verified research sources, the DORA register export, the pilot playbook, and the reference runtime with conformance checks.

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, swap-drill format, process-pack format 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.

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.