Responsibility Pathway Runtime

Govern external actions without losing evidence, recovery, or the human decision point.

Responsibility Pathway Runtime (RPR) is an MIT-licensed Python runtime for applications that need to place an explicit responsibility pathway in front of consequential external actions. It helps a host application preserve actor and authority declarations, execution-attempt continuity, readback evidence, fail-closed ambiguity handling, repair routes, and Human Gate decisions.

Public alpha source and live demo — 0.1.0a2
Freeze ID: RPR-CF-2026-08-02-01
Tested final rehearsal profile: Linux, Python 3.11
The repository, product site, and browser demo are public. A final tag, GitHub Release, and package-registry distribution have not yet been published.
RPR is not a legal-responsibility engine, identity provider, secret manager, production gateway, or guarantee of exactly-once effects across arbitrary remote systems.

Product site · Live browser demo · 日本語の入口 · Quick Start · Product documentation · Report an issue

Why RPR

AI agents and automation can execute faster than people can reconstruct what happened. RPR provides a bounded runtime layer where an integrating application can:

• declare actors, authority, and the proposed action;
• evaluate and retain an explicit pathway state;
• bind operations, attempts, and idempotency identity;
• require independent readback before completion;
• stop ambiguous writes as write_status_unknown instead of false success;
• retain Human Gate, repair, resume, reconciliation, and evidence continuity;
• survive restart without silently repeating unresolved effects.

Verified in the frozen alpha candidate

• pathway registration and authorized state transitions;
• persistent pathway and execution-attempt stores;
• Human Gate, repair, resume, and reconciliation boundaries;
• local-file, allow-listed HTTP, durable outbound-message, and real MCP subprocess paths;
• HTTP and MCP fault injection;
• crash/restart continuity and duplicate-dispatch prevention;
• backup, restore, diagnostics, uninstall, package/CLI residue checks, and customer-data retention;
• clean wheel and source-distribution installation;
• two independent byte-for-byte reproducible builds;
• English-primary and Japanese-parallel product documentation;
• Lean 4 verification of selected published state-machine invariants;
• Chromium and Pyodide execution of the CI-built RPR wheel in the public browser demo.

We need field-test reports for

RPR is public so real users can report reproducible environment and integration findings. Please open an Issue for:

• Windows, macOS, other Linux distributions, containers, and Python environments beyond the final Linux/Python 3.11 rehearsal;
• proxy, TLS, enterprise identity, credential handling, remote MCP, and service-specific connectivity;
• framework, agent, CI/CD, RPA, batch, and application integrations;
• installation, upgrade, backup/restore, removal, and operational usability;
• confusing states, missing examples, documentation gaps, and unsupported assumptions.

A user report is field evidence for that environment. It does not imply universal production readiness.

Quick Start

Until a package-registry distribution or GitHub Release is published, install from the public repository in a disposable environment:

git clone https://github.com/YutoriKomeiji/responsibility-pathway-runtime.git
cd responsibility-pathway-runtime
python3.11 -m venv .venv
. .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e .
rpr --help

To inspect the runtime without installing it locally, use the live browser demo. The demo runs the CI-built RPR wheel in Pyodide with SQLite; only the external payment provider is simulated.

The verified candidate artifact hashes are recorded in release-evidence/replacement-freeze-2026-08-02.json. Those candidate artifacts are not yet a general package distribution.

Integration boundary

The host application remains responsible for authentication, credential isolation, network controls, bypass prevention, domain-specific authorization, and the independent readback source. RPE integration is optional; RPE absence, malformed output, or unsupported results must not become implicit permission.

Documentation

• Product, scope, and architecture
• Installation, operations, and recovery
• Security, limitations, integration, and API
• Verification, known issues, release notes, and UAT
• Support and field testing
• Security reporting
• Contributing

License

RPR is released under the MIT License. Copyright © 2026 Akihisa Ono.