pgs-runtime 0.2.1__tar.gz → 0.3.0__tar.gz

pgs_runtime-0.3.0/LICENSE

@@ -0,0 +1,67 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+Copyright 2026 Bhash Ganti aka Bachi
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+
+------------------------
+FULL LICENSE TEXT BELOW
+------------------------
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+   "Licensor" shall mean the copyright owner.
+   "Legal Entity" shall mean the union of the acting entity and all other
+   entities that control, are controlled by, or are under common control.
+   "You" shall mean an individual or Legal Entity exercising permissions.
+   "Source" form shall mean the preferred form for making modifications.
+   "Object" form shall mean any form resulting from mechanical transformation.
+   "Work" shall mean the work of authorship.
+   "Derivative Works" shall mean any work based on the Work.
+   "Contribution" shall mean any work intentionally submitted.
+   "Contributor" shall mean Licensor and any individual submitting Contributions.
+
+2. Grant of Copyright License.
+   Each Contributor grants You a perpetual, worldwide, non-exclusive,
+   no-charge, royalty-free copyright license.
+
+3. Grant of Patent License.
+   Each Contributor grants a patent license to make, use, sell, etc.
+
+4. Redistribution.
+   You may reproduce and distribute copies provided that:
+   - You include a copy of this License
+   - You retain notices
+   - You state modifications
+   - You include NOTICE file if present
+
+5. Submission of Contributions.
+   Contributions are under this License unless stated otherwise.
+
+6. Trademarks.
+   This License does not grant trademark rights.
+
+7. Disclaimer of Warranty.
+   Provided "AS IS", without warranties.
+
+8. Limitation of Liability.
+   No liability for damages.
+
+9. Accepting Warranty or Additional Liability.
+   You may offer support/warranty on your own behalf only.

pgs_runtime-0.3.0/MANIFEST.in

@@ -0,0 +1,9 @@
+exclude *.log
+exclude *.jsonl
+exclude *.sh
+
+prune scripts
+prune testbed
+prune pgs_*
+
+global-exclude __pycache__ *.pyc

pgs_runtime-0.3.0/NOTICE

@@ -0,0 +1,11 @@
+PGS — Protocol-Governed Systems
+Copyright 2026 Bhash Ganti aka Bachi
+
+This project introduces a protocol-first execution model in which:
+
+- Behavior is declared in protocol artifacts
+- Execution is performed by a deterministic runtime
+- Capability implementations are bound at compile time
+- Governance is enforced through invariants and assertions
+
+Extensibility is achieved by declaration, not refactor.

pgs_runtime-0.3.0/PKG-INFO

@@ -0,0 +1,213 @@
+Metadata-Version: 2.4
+Name: pgs_runtime
+Version: 0.3.0
+Summary: PGS runtime for Protocol-Governed Systems
+Author: Bachi
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/bachipeachy/pgs_runtime
+Project-URL: Repository, https://github.com/bachipeachy/pgs_runtime
+Keywords: pgs,protocol,runtime,workflow,execution
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Dynamic: license-file
+
+# pgs_runtime
+
+**Deterministic execution engine for Protocol-Governed Systems.**
+
+The runtime traverses a precompiled execution graph and produces traceable, governed outcomes.  
+It does not discover behavior. It does not interpret intent. It does not contain business logic.
+
+Behavior is declared in protocol, executed by runtime, implemented in capabilities, and observed via traces and state.
+
+> **New to PGS?** This is one of eight repositories in the Protocol-Governed Systems ecosystem.
+> For orientation, architecture overview, and end-to-end execution, start at [pgs_workspace](https://github.com/bachipeachy/pgs_workspace).
+
+---
+
+## What this component is (and is not)
+
+**This is:**
+- A generic execution substrate
+- A graph traversal engine
+- A trace generator
+- A host for capability implementations (CT/CS bindings)
+
+**This is not:**
+- A workflow authoring system
+- A rules engine
+- A business logic container
+- A framework with pluggable behavior
+
+All behavior is declared and compiled before execution. The runtime only consumes a sealed snapshot.
+
+---
+
+## Inputs → Outputs
+
+**Inputs:**
+```
+protocol_snapshot/   ← compiled artifacts (from pgs_compiler)
+payload              ← external input (JSON)
+data_root            ← state storage boundary
+workspace            ← execution context
+```
+
+**Outputs:**
+```
+traces/<TRACE_ID>/
+├── <TRACE_ID>.jsonl   ← append-only execution log
+├── <TRACE_ID>.md      ← human-readable summary
+└── <TRACE_ID>.png     ← visual execution path
+
+data/
+├── registry/          ← idempotent state
+├── events/            ← append-only history
+└── ...                ← additional declared side-effects
+```
+
+---
+
+## CLI surface
+
+```bash
+pgs_runtime run \
+  --wf blockchain::WF_REGISTER_ACTOR_UNVERIFIED_V0 \
+  --payload payload.json \
+  --data-root /abs/path/to/pgs_workspace/data \
+  --workspace /abs/path/to/pgs_workspace
+
+pgs_runtime examine ./traces/<TRACE_ID>/<TRACE_ID>.jsonl
+```
+
+That is the entire public interface. Everything else is governed by the protocol snapshot.
+
+---
+
+## How execution works
+
+You run a workflow. The runtime:
+
+1. Loads the compiled DAG from `protocol_snapshot/`
+2. Resolves inputs via JSONPath expressions
+3. Executes CT/CS nodes (transforms and side-effects)
+4. Routes based on declared outcomes
+5. Emits trace + state
+
+No logic exists in the runtime for any specific workflow.
+
+**Example:** `pgs_runtime run --wf blockchain::WF_REGISTER_ACTOR_UNVERIFIED_V0 ...`
+
+The runtime has no knowledge of blockchain. It only traverses the precomputed graph compiled from that workflow's protocol declaration.
+
+---
+
+## What makes this runtime different
+
+**1. Compile-time closure**
+
+All routing, bindings, and side-effect semantics are resolved before execution begins:
+- no reflection
+- no dynamic imports
+- no fallback logic
+
+Execution is a pure traversal of a sealed graph.  
+No runtime decision can alter the graph.
+
+**2. Outcome-driven control flow**
+
+Every node produces an explicit outcome:
+```
+SUCCESS
+ALREADY_EXISTS
+VIOLATION
+...
+```
+
+These outcomes map to named edges in the graph. There is no implicit branching, no hidden control flow, no exception-driven logic.
+
+**3. Side-effects are governed, not coded**
+
+Side-effects (CS) declare their own semantics:
+
+| Behavior | Example |
+|----------|---------|
+| Idempotent | registry insert → `ALREADY_EXISTS` on repeat |
+| Append-only | event stream → always records |
+| Mutable | state overwrite (explicitly declared) |
+
+The runtime executes these semantics as declared. It does not interpret them.
+
+**4. Execution ≠ effect**
+
+A workflow can succeed even when a side-effect returns `ALREADY_EXISTS`. Execution is structural. Effects are governed independently. This separation is visible in traces and state.
+
+**5. Trace is first-class output**
+
+Every run produces a complete causal execution record keyed by `trace_id`. This enables:
+- deterministic replay
+- auditability
+- debugging without code instrumentation
+
+---
+
+## Where this fits in the system
+
+PGS is intentionally split into layers:
+
+| Layer | Repo | Responsibility |
+|-------|------|----------------|
+| Governance | `pgs_governance` | Invariants, constitutional rules, structural definitions |
+| Compilation | `pgs_compiler` | Produce `protocol_snapshot/` |
+| Transport | `pgs_transport` | Ingress/egress adapters for HTTP and CLI |
+| **Execution** | **`pgs_runtime` ← here** | **Traverse compiled graph deterministically** |
+| Capabilities | `pgs_capabilities` | Provide CT/CS implementations |
+| Domains | `pgs_blockchain`, `pgs_ai_governance` | Real-world workflows |
+| Entry point | `pgs_workspace` | Run and observe |
+
+---
+
+## What you should explore next
+
+| Go here | To... |
+|---------|-------|
+| `pgs_workspace` | Run end-to-end and observe traces |
+| `protocol_snapshot/` | Inspect what the runtime actually reads |
+| `pgs_governance` + `pgs_compiler` | Author and compile new workflows |
+| `pgs_capabilities` | Add new capability implementations |
+
+---
+
+## Research context
+
+This implementation demonstrates:
+
+> *"Extensibility by declaration, not refactor."*
+
+And more broadly: governance-driven execution, compile-time closure of behavior, separation of execution from semantics.
+
+---
+
+## Final note
+
+The runtime does not decide what to do.  
+It only executes what has already been decided.
+
+If you find yourself wanting to add logic to this runtime — stop.  
+That logic belongs in the protocol (declaration) or in capability implementations (CT/CS).  
+The runtime should remain boringly deterministic.
+
+---
+
+## License
+
+Apache-2.0. See LICENSE and NOTICE for details.

pgs_runtime-0.3.0/README.md

@@ -0,0 +1,191 @@
+# pgs_runtime
+
+**Deterministic execution engine for Protocol-Governed Systems.**
+
+The runtime traverses a precompiled execution graph and produces traceable, governed outcomes.  
+It does not discover behavior. It does not interpret intent. It does not contain business logic.
+
+Behavior is declared in protocol, executed by runtime, implemented in capabilities, and observed via traces and state.
+
+> **New to PGS?** This is one of eight repositories in the Protocol-Governed Systems ecosystem.
+> For orientation, architecture overview, and end-to-end execution, start at [pgs_workspace](https://github.com/bachipeachy/pgs_workspace).
+
+---
+
+## What this component is (and is not)
+
+**This is:**
+- A generic execution substrate
+- A graph traversal engine
+- A trace generator
+- A host for capability implementations (CT/CS bindings)
+
+**This is not:**
+- A workflow authoring system
+- A rules engine
+- A business logic container
+- A framework with pluggable behavior
+
+All behavior is declared and compiled before execution. The runtime only consumes a sealed snapshot.
+
+---
+
+## Inputs → Outputs
+
+**Inputs:**
+```
+protocol_snapshot/   ← compiled artifacts (from pgs_compiler)
+payload              ← external input (JSON)
+data_root            ← state storage boundary
+workspace            ← execution context
+```
+
+**Outputs:**
+```
+traces/<TRACE_ID>/
+├── <TRACE_ID>.jsonl   ← append-only execution log
+├── <TRACE_ID>.md      ← human-readable summary
+└── <TRACE_ID>.png     ← visual execution path
+
+data/
+├── registry/          ← idempotent state
+├── events/            ← append-only history
+└── ...                ← additional declared side-effects
+```
+
+---
+
+## CLI surface
+
+```bash
+pgs_runtime run \
+  --wf blockchain::WF_REGISTER_ACTOR_UNVERIFIED_V0 \
+  --payload payload.json \
+  --data-root /abs/path/to/pgs_workspace/data \
+  --workspace /abs/path/to/pgs_workspace
+
+pgs_runtime examine ./traces/<TRACE_ID>/<TRACE_ID>.jsonl
+```
+
+That is the entire public interface. Everything else is governed by the protocol snapshot.
+
+---
+
+## How execution works
+
+You run a workflow. The runtime:
+
+1. Loads the compiled DAG from `protocol_snapshot/`
+2. Resolves inputs via JSONPath expressions
+3. Executes CT/CS nodes (transforms and side-effects)
+4. Routes based on declared outcomes
+5. Emits trace + state
+
+No logic exists in the runtime for any specific workflow.
+
+**Example:** `pgs_runtime run --wf blockchain::WF_REGISTER_ACTOR_UNVERIFIED_V0 ...`
+
+The runtime has no knowledge of blockchain. It only traverses the precomputed graph compiled from that workflow's protocol declaration.
+
+---
+
+## What makes this runtime different
+
+**1. Compile-time closure**
+
+All routing, bindings, and side-effect semantics are resolved before execution begins:
+- no reflection
+- no dynamic imports
+- no fallback logic
+
+Execution is a pure traversal of a sealed graph.  
+No runtime decision can alter the graph.
+
+**2. Outcome-driven control flow**
+
+Every node produces an explicit outcome:
+```
+SUCCESS
+ALREADY_EXISTS
+VIOLATION
+...
+```
+
+These outcomes map to named edges in the graph. There is no implicit branching, no hidden control flow, no exception-driven logic.
+
+**3. Side-effects are governed, not coded**
+
+Side-effects (CS) declare their own semantics:
+
+| Behavior | Example |
+|----------|---------|
+| Idempotent | registry insert → `ALREADY_EXISTS` on repeat |
+| Append-only | event stream → always records |
+| Mutable | state overwrite (explicitly declared) |
+
+The runtime executes these semantics as declared. It does not interpret them.
+
+**4. Execution ≠ effect**
+
+A workflow can succeed even when a side-effect returns `ALREADY_EXISTS`. Execution is structural. Effects are governed independently. This separation is visible in traces and state.
+
+**5. Trace is first-class output**
+
+Every run produces a complete causal execution record keyed by `trace_id`. This enables:
+- deterministic replay
+- auditability
+- debugging without code instrumentation
+
+---
+
+## Where this fits in the system
+
+PGS is intentionally split into layers:
+
+| Layer | Repo | Responsibility |
+|-------|------|----------------|
+| Governance | `pgs_governance` | Invariants, constitutional rules, structural definitions |
+| Compilation | `pgs_compiler` | Produce `protocol_snapshot/` |
+| Transport | `pgs_transport` | Ingress/egress adapters for HTTP and CLI |
+| **Execution** | **`pgs_runtime` ← here** | **Traverse compiled graph deterministically** |
+| Capabilities | `pgs_capabilities` | Provide CT/CS implementations |
+| Domains | `pgs_blockchain`, `pgs_ai_governance` | Real-world workflows |
+| Entry point | `pgs_workspace` | Run and observe |
+
+---
+
+## What you should explore next
+
+| Go here | To... |
+|---------|-------|
+| `pgs_workspace` | Run end-to-end and observe traces |
+| `protocol_snapshot/` | Inspect what the runtime actually reads |
+| `pgs_governance` + `pgs_compiler` | Author and compile new workflows |
+| `pgs_capabilities` | Add new capability implementations |
+
+---
+
+## Research context
+
+This implementation demonstrates:
+
+> *"Extensibility by declaration, not refactor."*
+
+And more broadly: governance-driven execution, compile-time closure of behavior, separation of execution from semantics.
+
+---
+
+## Final note
+
+The runtime does not decide what to do.  
+It only executes what has already been decided.
+
+If you find yourself wanting to add logic to this runtime — stop.  
+That logic belongs in the protocol (declaration) or in capability implementations (CT/CS).  
+The runtime should remain boringly deterministic.
+
+---
+
+## License
+
+Apache-2.0. See LICENSE and NOTICE for details.

pgs_runtime-0.3.0/pgs_runtime.egg-info/SOURCES.txt

@@ -0,0 +1,5 @@
+LICENSE
+MANIFEST.in
+NOTICE
+README.md
+pyproject.toml

pgs_runtime-0.3.0/pyproject.toml

@@ -0,0 +1,45 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "pgs_runtime"
+version = "0.3.0"
+description = "PGS runtime for Protocol-Governed Systems"
+readme = "README.md"
+requires-python = ">=3.10"
+
+license = "Apache-2.0"
+
+authors = [
+  { name = "Bachi" }
+]
+
+dependencies = []
+
+keywords = ["pgs", "protocol", "runtime", "workflow", "execution"]
+
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Intended Audience :: Developers",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Operating System :: OS Independent"
+]
+
+[project.urls]
+Homepage = "https://github.com/bachipeachy/pgs_runtime"
+Repository = "https://github.com/bachipeachy/pgs_runtime"
+
+[project.scripts]
+pgs_runtime = "pgs_runtime.cli:main"
+
+[tool.setuptools]
+include-package-data = false
+
+[tool.setuptools.packages.find]
+where = ["."]
+include = ["pgs_runtime*"]
+exclude = ["testbed*", "scripts*", "*.tests"]

pgs_runtime-0.2.1/PKG-INFO

@@ -1,27 +0,0 @@
-Metadata-Version: 2.4
-Name: pgs-runtime
-Version: 0.2.1
-Summary: Successor package lineage for OmniBachi runtime
-Author: Bhash Ganti aka Bachi
-License: Apache-2.0
-Project-URL: Homepage, https://github.com/bachipeachy/pgs_runtime
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-
-# pgs-runtime
-
-`pgs-runtime` is the successor package lineage to `omnibachi`.
-
-`omnibachi==0.2.1` is the final OmniBachi symbolic runtime release.
-
-Active development begins with:
-
-```bash
-pip install pgs-runtime>=0.3.0
-
-```
-
-PGS Runtime v0.3.x introduces the token-native deterministic runtime architecture and Compiler/Runtime Inversion model.
-
-Historical package:
-https://pypi.org/project/omnibachi/

pgs_runtime-0.2.1/README.md

@@ -1,17 +0,0 @@
-# pgs-runtime
-
-`pgs-runtime` is the successor package lineage to `omnibachi`.
-
-`omnibachi==0.2.1` is the final OmniBachi symbolic runtime release.
-
-Active development begins with:
-
-```bash
-pip install pgs-runtime>=0.3.0
-
-```
-
-PGS Runtime v0.3.x introduces the token-native deterministic runtime architecture and Compiler/Runtime Inversion model.
-
-Historical package:
-https://pypi.org/project/omnibachi/

pgs_runtime-0.2.1/pgs_runtime/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.2.1"

pgs_runtime-0.2.1/pgs_runtime.egg-info/PKG-INFO

@@ -1,27 +0,0 @@
-Metadata-Version: 2.4
-Name: pgs-runtime
-Version: 0.2.1
-Summary: Successor package lineage for OmniBachi runtime
-Author: Bhash Ganti aka Bachi
-License: Apache-2.0
-Project-URL: Homepage, https://github.com/bachipeachy/pgs_runtime
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-
-# pgs-runtime
-
-`pgs-runtime` is the successor package lineage to `omnibachi`.
-
-`omnibachi==0.2.1` is the final OmniBachi symbolic runtime release.
-
-Active development begins with:
-
-```bash
-pip install pgs-runtime>=0.3.0
-
-```
-
-PGS Runtime v0.3.x introduces the token-native deterministic runtime architecture and Compiler/Runtime Inversion model.
-
-Historical package:
-https://pypi.org/project/omnibachi/

pgs_runtime-0.2.1/pgs_runtime.egg-info/SOURCES.txt

@@ -1,7 +0,0 @@
-README.md
-pyproject.toml
-pgs_runtime/__init__.py
-pgs_runtime.egg-info/PKG-INFO
-pgs_runtime.egg-info/SOURCES.txt
-pgs_runtime.egg-info/dependency_links.txt
-pgs_runtime.egg-info/top_level.txt

pgs_runtime-0.2.1/pgs_runtime.egg-info/dependency_links.txt

@@ -1 +0,0 @@
-

pgs_runtime-0.2.1/pgs_runtime.egg-info/top_level.txt

@@ -1 +0,0 @@
-pgs_runtime

pgs_runtime-0.2.1/pyproject.toml

@@ -1,20 +0,0 @@
-[build-system]
-requires = ["setuptools>=61.0"]
-build-backend = "setuptools.build_meta"
-
-[project]
-name = "pgs-runtime"
-version = "0.2.1"
-description = "Successor package lineage for OmniBachi runtime"
-readme = "README.md"
-requires-python = ">=3.11"
-license = {text = "Apache-2.0"}
-
-authors = [
-  {name = "Bhash Ganti aka Bachi"}
-]
-
-urls = {Homepage = "https://github.com/bachipeachy/pgs_runtime"}
-
-[tool.setuptools.packages.find]
-include = ["pgs_runtime"]