b3-prosaic-harness 0.7.1__py3-none-any.whl

b3_prosaic_harness-0.7.1.dist-info/METADATA

@@ -0,0 +1,389 @@
+Metadata-Version: 2.4
+Name: b3-prosaic-harness
+Version: 0.7.1
+Summary: Small durable workflows and validation around neutral Prosaic agents
+Author: B3 Cognition
+License-Expression: Apache-2.0
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: b3-prosaic-runtime<0.9,>=0.8
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: jsonschema>=4.23
+Requires-Dist: referencing>=0.28.4
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Requires-Dist: build>=1; extra == "test"
+Requires-Dist: setuptools>=77; extra == "test"
+Requires-Dist: wheel; extra == "test"
+Requires-Dist: packaging; extra == "test"
+Dynamic: license-file
+
+# Prosaic Harness
+
+Version **0.7.1** is the candidate `b3-prosaic-harness` index distribution, with
+`b3-prosaic-runtime>=0.8,<0.9` and optional `b3-prosaic-harness-postgres` **0.2.1**.
+Imports (`prosaic_harness`) and CLI commands (`prosaic-harness`) remain unchanged.
+The five-package release train is pending final qualification and publication;
+see [package migration](docs/package-migration.md) for fresh-environment installs.
+
+Version **0.6.2** added a [validated in-memory workflow factory](docs/workflow-factory.md)
+for approved agents, native tool registries and client-generated graphs. The host
+supplies policy and private bindings; proposals need no filesystem directory.
+Admission, schema bounds and durable failure recovery are enforced before execution.
+
+Optional [customer accounting context](docs/accounting.md) preserves attribution
+through workflow retries and resume. Existing callers and saved runs remain supported;
+durable usage recording is explicitly enabled through Prosaic Runtime.
+
+Version **0.6.1** fixes lease-registration admission in the separately installed PostgreSQL adapter
+(**0.1.1**) for cross-worker durable workflows. Core remains database-free; filesystem constructors/CLI remain supported.
+See [explicit database setup/grants](adapters/postgres/README.md) and the
+[zero-model-call two-worker example](examples/postgres/README.md). Prose tools
+do not grant database access; applications retain tenant authorization and
+filter private run state.
+
+The [RunStore ruling register](docs/decisions/2026-10-08-run-store-postgres-rulings.md)
+preserves implementation/review decisions, reasons and risks with stable IDs.
+
+Version 0.5.0 adds schema-validated human responses at durable workflow pauses,
+with trusted validators and retained feedback for downstream agents and checks.
+It pins Runtime v0.5.3 and automatically installs Python Prosaic v0.3.1.
+Installation and CI no longer require Node.js or npm.
+
+Version 0.4.0 adds [manifest-defined CLI tools](examples/README.md#custom-command-line-tools)
+through the normal workflow CLI, with offline availability checks and required
+native execution evidence. Current candidates select the compatible Runtime 0.8 series.
+
+## CLI permissions and sandboxing
+
+Harness **0.7.1** retains CLI sandbox policy enforcement and selects Runtime
+**0.8.x**, which provides `cli_sandbox_v1`. Follow the
+[sandboxed workflow walkthrough](examples/README.md#sandboxed-cli-workflow-harness-042)
+for installation, offline validation and live execution.
+The complete blueprint is [cli-tool-sandboxed.yml](examples/cli-tool-sandboxed.yml).
+
+Permissions are operator-owned, not granted by prose:
+
+| Location | Setting | Meaning |
+| --- | --- | --- |
+| Agent Markdown | `tools: [analyze_spec]` | Request the tool; not authorization |
+| Runtime YAML | `allowed_tools: [analyze_spec]` and reviewed `tool_directories` | Allow the tool and trust its manifest/executable |
+| Workflow agent step | `tools: [analyze_spec]`, `read_roots: [evidence]` | Grant that step the tool and narrow readable inputs |
+| Runtime YAML | `cli_sandbox: {mode: required}` | Enforce OS isolation for CLI execution and probes |
+| Workflow agent step | `require_tools: [analyze_spec]` | Require observed successful execution; grants nothing extra |
+
+All tool permission layers must agree. `validate` loads the workflow and runs
+offline CLI preflight; it does not contact a model or need an endpoint key.
+The sandbox is off by default. Required mode fails closed if unavailable;
+Linux needs Bubblewrap >= 0.12.0 and permitted user namespaces, while macOS needs
+Seatbelt's `sandbox-exec`. See [Runtime's setup](https://github.com/B3Cognition/prosaic-runtime/blob/main/docs/cli-tools.md).
+
+Sandboxed CLIs can read granted evidence and write private scratch, but cannot
+write the workspace or reach the host IP network. Keep host Unix sockets outside
+granted directories. Extra dependencies need narrow `runtime_roots`, not HOME or
+`/`. This does not sandbox Python callbacks, validators or native coding providers;
+builtin read tools retain their existing path checks. Harness itself still writes
+durable run state on the host. Required-mode policy is sealed into workflow
+identity: changes invalidate existing approvals/resume, and injected adapters
+cannot silently downgrade it. Use a fresh run directory when changing policy.
+
+## Overview
+
+The [custom-tool embedding example](examples/README.md#host-registered-custom-tools)
+adds catalogue lookup, version-bound native execution evidence, deterministic
+answer admission and a human pause. It requires Harness v0.4.0+ / Runtime v0.5.0+.
+
+A small Python harness for durable workflows built from neutral Prosaic agents.
+Define a graph in YAML, execute agents through Prosaic Runtime, validate their
+JSON outputs, and resume from local checkpoints. Apache-2.0.
+
+| Component | Owns |
+| --- | --- |
+| [Prosaic](https://github.com/B3Cognition/prosaic) | Markdown agents and resource inspection |
+| [Prosaic Runtime](https://github.com/B3Cognition/prosaic-runtime) | One model invocation, model tiers, tools, streaming, permissions |
+| Prosaic Harness | Steps, validation, transitions, review loops, human pauses, run evidence |
+
+The initial release supports Linux and macOS with Python 3.11+. It needs an
+existing OpenAI-compatible endpoint and the Python Prosaic CLI. Windows
+users can use WSL. The library imports no Echelon code.
+
+Version 0.2.0 adds versioned approvals, trusted checks and final-output validation,
+and hash-bound read provenance. Version 0.3.0 pins Prosaic Runtime 0.4.0, adding
+opt-in acquisition, strict initial-tool enforcement, admission-time resource
+checks and larger incident-review examples. State format is
+version 2; existing 0.1 runs must start afresh. See
+[hardening setup and contracts](docs/hardening.md).
+
+## First run
+
+Install Git and Python 3.11+ before starting. Use an explicit Python
+environment so another application's older runtime cannot be picked up by accident.
+
+```sh
+git clone https://github.com/B3Cognition/prosaic-harness.git
+cd prosaic-harness
+git checkout <exact-candidate-commit>
+python3 -m venv .venv
+.venv/bin/python -m pip install --find-links /absolute/path/to/curated-wheelhouse .
+
+export PATH="$PWD/.venv/bin:$PATH"
+prosaic --help
+.venv/bin/prosaic-harness --help
+```
+
+ALWAYS use a fresh clone/environment for migration; NEVER reuse an environment
+containing legacy distributions. In a future terminal, return to the repository and add its `.venv/bin` to PATH
+again. Node.js and npm are not required. Candidate dependency metadata selects
+`b3-prosaic-runtime` 0.8.x, `b3-prosaic` 0.4.x, PyYAML, jsonschema and referencing.
+Use only the manifest-selected b3 wheels in the curated wheelhouse. Candidate
+installation requires the Runtime 0.8 producer; it is not yet a published index install.
+No sibling checkout or manual Prosaic installation is needed. Older Harness
+tags retain their historical installation docs.
+
+### Configure an endpoint
+
+Edit `examples/runtime.yml`: replace the localhost URL and `your-model` with your
+operator's values. Each profile names an endpoint, model, credential environment
+variable, and optional transport features. Prose `model_tier` selects a profile
+through `routes`. Set the key without putting it into YAML:
+
+```sh
+export LOCAL_LLM_API_KEY="$(.venv/bin/python -c 'import getpass; print(getpass.getpass("Endpoint key: "))')"
+```
+
+An unauthenticated endpoint may omit `api_key_env`. If your endpoint rejects
+streaming usage reporting, set `stream_options: false`. Diagnostics do not
+generate text unless you explicitly request inference:
+
+```sh
+.venv/bin/prosaic-runtime doctor --config examples/runtime.yml --output text
+```
+
+For the private TokenProxy demo, `examples/tokenproxy.yml` supplies the four model
+profiles. `examples/tokenproxy-single.yml` and `examples/tokenproxy-review.yml`
+select that configuration. They require access to `10.16.81.27:8080`:
+
+```sh
+source ~/.zshrc
+export TOKENPROXY_KEY
+.venv/bin/prosaic-runtime doctor --config examples/tokenproxy.yml --output text
+```
+
+### Run one agent with validation
+
+```sh
+.venv/bin/prosaic-harness validate examples/single.yml --checks examples/checks.py
+.venv/bin/prosaic-harness run examples/single.yml \
+  --checks examples/checks.py --input examples/request.json --run-dir runs/first-note
+.venv/bin/prosaic-harness status --run-dir runs/first-note
+```
+
+For TokenProxy, substitute `examples/tokenproxy-single.yml`. This makes a real
+model request. The briefer must return JSON matching `examples/schemas/brief.json`;
+invalid output triggers bounded retries with validation feedback. Completion
+prints the accepted object. Use a fresh run directory for another input.
+
+### Run a review and repair workflow
+
+```sh
+.venv/bin/prosaic-harness run examples/tokenproxy-review.yml \
+  --checks examples/checks.py --input examples/request.json --run-dir runs/launch-review
+```
+
+This exercises four tiers: Ornith briefs the request, Qwen drafts a recommendation,
+DeepSeek reviews it, and Nemotron creates a final decision. A gate routes an
+unapproved review back to the author. The author receives the previous review
+as an identified input artifact. The actual final decision gets its own model
+review and deterministic evidence check before pausing for human approval:
+
+```sh
+.venv/bin/prosaic-harness resume examples/tokenproxy-review.yml \
+  --checks examples/checks.py --run-dir runs/launch-review --choice approve
+```
+
+Choose `reject` to finish with a rejected outcome. Approval records a decision;
+it does not publish files or send messages. Use `examples/review.yml` for your
+own configured endpoint. See [examples/README.md](examples/README.md) for the
+graph, contracts, tool example, and a complete Python embedding program.
+
+## Workflow format
+
+All paths in a workflow are relative to its directory and confined to it. The
+workflow can be launched from any working directory. Schema references are
+internal to their document. Arbitrary expressions and remote schema fetching
+are not supported.
+
+```yaml
+version: 1
+source: .prosaic
+runtime: runtime.yml
+start: draft
+limits:
+  max_calls: 8
+  max_visits: 3
+  timeout_s: 180
+steps:
+  draft:
+    kind: agent
+    agent: subagents/author.md
+    schema: schemas/draft.json
+    optional_inputs: [review]
+    max_attempts: 2
+    next: review
+  review:
+    kind: agent
+    agent: subagents/reviewer.md
+    schema: schemas/review.json
+    inputs: [draft]
+    next: gate
+  gate:
+    kind: gate
+    from: review
+    field: [approved]
+    equals: true
+    pass: done
+    fail: draft
+  done:
+    kind: finish
+```
+
+Agent `arguments` are a JSON object with `request` (the run input), `artifacts`
+(selected prior accepted outputs, keyed by step ID), and `validation_feedback`
+(the last validation error, if any). `inputs` are required; `optional_inputs`
+include an output only when it exists, allowing first-pass review loops.
+Outputs replace a step's latest accepted value on revisits, while every attempt
+is retained in receipts and approvals bind to exact required-input versions.
+Optional inputs can carry stale feedback, not required approval dependencies.
+Arguments also include `artifact_bindings` and declared file `sources`.
+Raw transport stdout must be one JSON value; a single
+JSON Markdown fence is also accepted. Schema failures do not advance the graph.
+
+| Step kind | Fields and behavior |
+| --- | --- |
+| `agent` | `agent`, `schema`, `next`; optional `acquisition` prose ID, input IDs, tools/read roots, required successful tools, attempts, visits |
+| `gate` | `from`, `field` (list of keys), `equals`, `pass`, `fail`; missing data blocks |
+| `check` | `from`, trusted `validators`, `pass`, `fail`; no model call |
+| `pause` | `question`, `choices` mapping named answers to next steps |
+| `finish` | Optional `outcome: completed` or `rejected` |
+
+A pause can optionally declare `response_schema: schemas/feedback.json` and
+host-registered `validators`. Submit `resume(choice="refine", response={"text": "..."})`
+or CLI `resume ... --choice refine --response feedback.json`. The schema validates
+the payload; trusted pause validators receive `{"choice": ..., "response": ...}`
+with the original request and accepted artifacts in their check context. Applications
+can verify dynamic candidate membership there without encoding product IDs into the
+workflow graph. Invalid responses leave the pause untouched. Accepted responses are
+sealed into history and subsequent agent arguments include `human_responses`, keyed
+by pause step with its latest `choice` and `response`. They are user data, never tool
+permissions. Existing choice-only pauses retain their original behavior and reject
+payloads. A completed response cannot be submitted again.
+Trusted downstream validators also receive these accepted values through
+`CheckContext.human_responses`; they can enforce that a proposal matches the user's
+selection rather than trusting a model's account of that selection.
+
+`max_run_s` includes human waiting. Interactive applications should use an explicit
+human expiry for a decision workflow and a separate bounded workflow for each model
+turn; do not reuse a short model request timeout as a human response deadline.
+
+Each step may override `max_visits`. Agent attempts bound validation/transport
+retries within a visit; visits bound graph loops; `max_calls` bounds invocations
+across the whole run, including authorized interrupted retries. `timeout_s` is
+per invocation. Optional `max_tokens` counts all reported tokens and blocks on
+unknown usage; `max_run_s` persists a whole-run deadline including human waiting.
+There is no monetary guarantee. Finite graph visits also bound
+non-agent loops. There is no automatic model escalation.
+
+## Permissions and evidence
+
+Default agent permissions are empty. A workflow step may declare read tools and
+explicit `read_roots`; the runtime also intersects those with the prose's tools
+and runtime configuration grants. Optional `require_tools: [read_file]` rejects
+an output unless the invocation produced a successful tool event for that name;
+it does not prove which file was read or whether the answer interpreted it correctly.
+Declare `evidence` and `require_reads` for hash-bound complete-file read evidence.
+Development-only `acquisition: subagents/evidence-acquisition.md` sends a short
+Prosaic artifact before the full agent assignment. It requires `require_reads`
+and Runtime `acquisition_v1`; both prose digests are part of the sealed workflow
+fingerprint. One Runtime invocation owns both phases, their shared deadline,
+usage and tool budget. Failed acquisition blocks without automatic repair or
+fallback. Final JSON/schema/source checks still apply after successful reads.
+Acquisition gets no final arguments; its own prose specifies the evidence path.
+For model-independent acquisition, explicitly choose the no-tool
+`preloaded-evidence.yml` blueprint instead: the controller supplies immutable
+evidence text in `sources`. This is snapshot evidence, not a native tool receipt.
+See the [step-by-step examples](examples/README.md#staged-acquisition-and-no-tool-preloading).
+The [direct-read problem and staged-acquisition resolution](examples/tool-acquisition.md)
+show how to keep a detailed answer contract out of the initial read phase and
+verify the native receipt before analysis.
+Trusted checks are explicitly supplied by the host through `validators=` or CLI
+`--checks`. They execute Python with host permissions and are not sandboxed.
+V0.2 has no shell checks, agent file writes,
+publication effects, remote workers, or recursive agent dispatch. Application
+integrations can be added through an explicit boundary in a later release.
+
+Run evidence is local:
+
+```text
+runs/launch-review/
+  run.json                 # sole durable state authority, accepted outputs, history
+  run.lock                 # OS-backed lock prevents concurrent writers
+  attempts/<id>.json       # arguments, raw result, token usage, model/tool events
+```
+
+`--events` emits JSONL events and a final status report to stdout. Normal mode
+prints status and a five-second heartbeat to stderr and accepted results to stdout.
+Credentials remain in environment/secret files; run evidence contains supplied
+inputs and model output, so give its directory the same protection as the inputs.
+The harness does not redact arbitrary sensitive information supplied by users.
+
+## Resume and interruption
+
+```sh
+.venv/bin/prosaic-harness resume examples/review.yml --checks examples/checks.py --run-dir runs/launch-review
+```
+
+The harness saves a pending invocation before contacting the runtime, then saves
+its receipt before committing the accepted output and transition. If a receipt
+survived, resume adopts it without making another request. If no receipt survived,
+the run blocks with `interrupted_call`: the endpoint may already have processed
+the request. Explicitly authorize another billable call with:
+
+```sh
+.venv/bin/prosaic-harness resume examples/review.yml \
+  --checks examples/checks.py --run-dir runs/launch-review --retry-interrupted
+```
+
+This consumes another call slot. There is no exactly-once guarantee for model
+calls or their tool activity. Definitions, schemas, inspected prose, and runtime
+configuration and validator versions are fingerprinted; changes require a new
+run. Declared evidence changes also reject resume. Credential rotation
+through the same environment-variable name does not change the fingerprint.
+Limit-exhausted runs remain blocked; start a new run with revised limits rather
+than modifying stored state. State assumes trusted local storage, not adversarial
+tampering. Checksums and structural checks detect corruption, not coordinated
+forgery. New checkpoints are version 2; old runs need a new directory.
+CLI exit codes: 0 completed/waiting, 1 blocked/rejected, 2 configuration
+or usage error, 130 interrupted. Waiting is explicit, not final acceptance.
+
+## Development
+
+```sh
+.venv/bin/python -m pip install -e '.[test]'
+.venv/bin/python -m pytest
+.venv/bin/python -m build
+```
+
+Tests cover schema retries, branching/repair, human choices, bounds, interrupted
+calls, receipt recovery, definition changes, locking, tool scope, and transport
+integration. Live runs are opt-in examples, not part of the offline suite.
+
+## Structured JSON tools
+
+This revision pins Prosaic Runtime 0.7.1, which supplies `StructuredToolLoop` for
+explicit JSON tool-request transport. Product adapters can yield one Runtime
+turn per Harness invocation while retaining application-owned result validators.
+Register the same `CustomTool` descriptors with the workflow and adapter so
+Harness fingerprints and checks their contracts. Harness retains routing and
+checkpoint ownership; Runtime owns parsing, dispatch, bounds and repeat detection.

b3_prosaic_harness-0.7.1.dist-info/RECORD

@@ -0,0 +1,26 @@
+b3_prosaic_harness-0.7.1.dist-info/licenses/LICENSE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+b3_prosaic_harness-0.7.1.dist-info/licenses/NOTICE,sha256=ElUIgB9aqeWDj68Un0FliVam9tItd9kKPum77UrCD8s,258
+prosaic_harness/__init__.py,sha256=bhMi273a_Wf9aAJvlTiYGQ1vl2_utfFvEWC13l5oZkI,1384
+prosaic_harness/admission_data.py,sha256=Yc5SVJ7xQhF4LPLgdgtiJMJ2oQVHiY2iXExz3sDVDYg,7093
+prosaic_harness/bundles.py,sha256=YV_HQ9MRlzkryEgInv2ghX6seYIZOCQoZg_yoQgzZvw,5249
+prosaic_harness/cli.py,sha256=xWK46mBeX_6sReQRwQ51qlUzfqC6nq0UbHDZuWLDq0k,4905
+prosaic_harness/contracts.py,sha256=xA7BP4QM7lrbCDWquoCGEwuQRsr0sPr1I9_e53y2i9s,10116
+prosaic_harness/discovery.py,sha256=mTIYQdYfzMS-KjZwmc_Uhv7CeiXDfN2xFgJygv8a714,10316
+prosaic_harness/engine.py,sha256=YeErdW5LBRLaM4C60vP5UmfX8on5ZW858JCgIQGlBWY,51292
+prosaic_harness/errors.py,sha256=5EGZeUsGp2lesttJe2Wx4YqsnHLlzQbts1Q9-iY9Kx0,4681
+prosaic_harness/factory.py,sha256=KpVVn_Yo9Rqgp5hcKWeI_0ht0lABCZtgQKsqFyfiFZs,37478
+prosaic_harness/file_store.py,sha256=OhcViBkJ7-Rn-YwD6glUE6GKKqvC5-E4WusHPVbmJrM,6233
+prosaic_harness/graph_admission.py,sha256=ueY5sd7xwByPhRTZDdYsXk_vRQpUB3vQU7FmcT0jmlU,11492
+prosaic_harness/interaction.py,sha256=hyZwZ5pSRXrv5vjqM2sd_CPb4Ph9c9FoapfiTVUq98g,3471
+prosaic_harness/observations.py,sha256=AaJgq4Rh93xLSCvhJm0PGCyv_5X9qgOHIKStCvw951o,1917
+prosaic_harness/run_store.py,sha256=d7PhDkZRLtByhLW-8ULB9c-zG12h1amj7dtb9Z2ke2I,4023
+prosaic_harness/schema_validation.py,sha256=jjmUe6Qv9OgN15LjpfCwqDYvT_Af8MAiL93IuUZGOxg,10025
+prosaic_harness/store.py,sha256=w66w9nH4nYILfmSubEvLBuXDTt02epjEEulUKmhqa7k,3868
+prosaic_harness/testing.py,sha256=dX7Oxn__WmypWxyBAsD9I4w1ard3ZqKBUwYpHlV5CT8,1510
+prosaic_harness/validation.py,sha256=O5B4umfq5mEslxM6FU_SOQx-RBuk-AWf_S1ALQVbUiw,1304
+prosaic_harness/workflow.py,sha256=nVU97lIRTnm2tEvIcTQJSObRBQWTWqU6hdo4tIiC54Y,16888
+b3_prosaic_harness-0.7.1.dist-info/METADATA,sha256=wWPgDlTCP083MlpOw6KKXloRZr3HFbw9-y3mVQbEw4w,19450
+b3_prosaic_harness-0.7.1.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+b3_prosaic_harness-0.7.1.dist-info/entry_points.txt,sha256=CR2CL_4Kb9YKSK1SrSzHqJECPy63kbE7a9srlpzxmbI,61
+b3_prosaic_harness-0.7.1.dist-info/top_level.txt,sha256=2SMWGxeYTQhYbvdWcYrRmdgqh2yq2ew4wUHlGgjC0jE,16
+b3_prosaic_harness-0.7.1.dist-info/RECORD,,

b3_prosaic_harness-0.7.1.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

b3_prosaic_harness-0.7.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+prosaic-harness = prosaic_harness.cli:main

b3_prosaic_harness-0.7.1.dist-info/licenses/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   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 or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.

b3_prosaic_harness-0.7.1.dist-info/licenses/NOTICE

@@ -0,0 +1,5 @@
+Prosaic Harness
+
+This project is distributed under the Apache License, Version 2.0; see LICENSE.
+Third-party dependencies retain their own licenses and attribution notices.
+Previously published versions and tags retain the license notices shipped with them.

b3_prosaic_harness-0.7.1.dist-info/top_level.txt

@@ -0,0 +1 @@
+prosaic_harness

prosaic_harness/__init__.py

@@ -0,0 +1,22 @@
+"""Durable, validated execution around Prosaic Runtime."""
+__version__ = '0.7.1'
+
+from .engine import Harness
+from .workflow import Workflow
+from .factory import WorkflowCatalog, WorkflowBindings, WorkflowPolicy, WorkflowFactory
+from .bundles import WorkflowBundle, WorkflowReference, PreparedWorkflow
+from .errors import WorkflowAdmissionError, HumanResponseError
+from .interaction import PendingInteraction
+from .validation import Validator, CheckContext
+from .file_store import FileRunStore
+from .run_store import (RunStore, RunSnapshot, LeaseSession, StoreError, StoreUninitialized,
+                        StoreIncompatible, StoreUnavailable, StoreBusy, RunBusy, LeaseLost,
+                        RevisionConflict, ReceiptConflict, RunNotFound, RunAlreadyExists, StoreCorrupt)
+
+__all__ = ['Harness', 'Workflow', 'Validator', 'CheckContext', 'FileRunStore', 'RunStore',
+           'RunSnapshot', 'LeaseSession', 'StoreError', 'StoreUninitialized', 'StoreIncompatible',
+           'StoreUnavailable', 'StoreBusy', 'RunBusy', 'LeaseLost', 'RevisionConflict',
+           'ReceiptConflict', 'RunNotFound', 'RunAlreadyExists', 'StoreCorrupt']
+__all__ += ['WorkflowCatalog', 'WorkflowBindings', 'WorkflowPolicy', 'WorkflowFactory',
+            'WorkflowAdmissionError', 'HumanResponseError', 'PendingInteraction']
+__all__ += ['WorkflowBundle', 'WorkflowReference', 'PreparedWorkflow']