b3-prosaic-harness-postgres 0.2.1__tar.gz

b3_prosaic_harness_postgres-0.2.1/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_postgres-0.2.1/MANIFEST.in

@@ -0,0 +1,2 @@
+include LICENSE NOTICE README.md
+recursive-include tests *.py

b3_prosaic_harness_postgres-0.2.1/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_postgres-0.2.1/PKG-INFO

@@ -0,0 +1,222 @@
+Metadata-Version: 2.4
+Name: b3-prosaic-harness-postgres
+Version: 0.2.1
+Summary: Explicit PostgreSQL run storage for Prosaic Harness
+License-Expression: Apache-2.0
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: b3-prosaic-harness<0.8,>=0.7
+Requires-Dist: psycopg[binary]<4,>=3.2.3
+Requires-Dist: psycopg-pool<4,>=3.2
+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
+
+# PostgreSQL persistence for Prosaic Harness
+
+Run on worker A, inspect/resume on worker B, without a shared writable run
+directory. Core remains database-free; install this separate adapter only when
+you need shared durable state. The API is synchronous; a private I/O thread
+bounds network waits. Model execution holds no database connection/transaction.
+The current candidate is `b3-prosaic-harness-postgres` **0.2.0**, selecting
+`b3-prosaic-harness>=0.7,<0.8`. The adapter is maintained in this repository but
+installed and versioned separately, keeping PostgreSQL drivers optional for
+Harness users. Imports and CLI names remain unchanged. Final qualification and
+publication of the b3 release train are pending. The historical
+[Harness v0.6.1 release](https://github.com/B3Cognition/prosaic-harness/releases/tag/v0.6.1)
+retains its original 0.6.1/0.1.1 package names and receipts.
+
+## 1. Install and supply an existing database
+
+Python 3.11+, PostgreSQL 16 or 18 on a writable primary, and libpq 17+ are
+required. `psycopg[binary]` supplies libpq; older libpq is rejected.
+From the exact candidate Harness checkout, use a new environment and a curated
+wheelhouse containing only the manifest-selected b3 candidate wheels:
+
+```sh
+python3 -m venv .venv-postgres
+.venv-postgres/bin/python -m pip install --find-links /absolute/path/to/curated-wheelhouse . ./adapters/postgres
+export PATH="$PWD/.venv-postgres/bin:$PATH"
+prosaic --version
+prosaic-harness-postgres --help
+```
+
+ALWAYS migrate using a fresh environment or image; NEVER install legacy and b3
+distributions together because they own the same import paths. See
+[package migration](../../docs/package-migration.md). The Runtime 0.8 candidate
+must be available before this installation can resolve.
+
+Harness does **not** provision PostgreSQL, create databases/users, start a
+service, or fall back to files. Your operator supplies two DSNs through a secret
+manager: `HARNESS_MIGRATION_DSN` (schema owner with database CREATE permission)
+and `HARNESS_RUNTIME_DSN` (restricted runtime role). Never put DSNs in Markdown,
+YAML, argv, logs or Git. For a local terminal:
+
+```sh
+export HARNESS_MIGRATION_DSN="$(python -c 'import getpass; print(getpass.getpass("Migration DSN: "))')"
+export HARNESS_RUNTIME_DSN="$(python -c 'import getpass; print(getpass.getpass("Runtime DSN: "))')"
+```
+
+Preserve operator TLS/authentication settings, e.g. `sslmode=verify-full` and
+certificate roots. The adapter adds `target_session_attrs=read-write` for primary
+routing; it never weakens TLS.
+
+## 2. Initialize once, then grant runtime access
+
+```sh
+prosaic-harness-postgres init --dsn-env HARNESS_MIGRATION_DSN
+```
+
+Initialization is explicit, transactional, repeatable and concurrency-safe.
+It creates schema/version 1, not your database. It refuses unknown versions,
+foreign-owned, partial or damaged schemas; it does not repair or downgrade them.
+
+As schema owner, apply these grants, replacing `harness_runtime` with your
+existing runtime role (role/password creation belongs to your operator):
+
+```sql
+GRANT USAGE ON SCHEMA prosaic_harness TO harness_runtime;
+GRANT SELECT ON prosaic_harness.schema_version, prosaic_harness.leases,
+    prosaic_harness.runs, prosaic_harness.receipts TO harness_runtime;
+GRANT INSERT, UPDATE ON prosaic_harness.leases, prosaic_harness.runs TO harness_runtime;
+GRANT INSERT ON prosaic_harness.receipts TO harness_runtime;
+```
+
+Do **not** grant runtime schema CREATE, schema-version UPDATE, receipt UPDATE,
+or table DELETE. Check using the actual application's credentials:
+
+```sh
+prosaic-harness-postgres doctor --dsn-env HARNESS_RUNTIME_DSN
+```
+
+Default doctor reads only catalogs/settings/privileges: no rows, model calls or
+migrations. For an explicit write-and-cleanup test, use migration or dedicated
+diagnostic credentials with DELETE on the three data tables:
+
+```sh
+prosaic-harness-postgres doctor --dsn-env HARNESS_MIGRATION_DSN --check-write
+```
+
+This exercises guarded create/CAS/receipt/read/release operations in a fresh
+`prosaic-diagnostic-<uuid>` namespace. Reserve this prefix; applications must not
+use it. Cleanup deletes only its exact receipt/run/lease identities, in that
+order, after release. It never deletes production lease generations. Cleanup,
+interruption and commit-ack failures fail the command. Its error includes the
+diagnostic namespace for reconciliation: inspect exact rows before manual
+cleanup/retry, never blindly delete by prefix.
+
+## 3. Embed the single Harness engine
+
+```python
+from prosaic_harness import Harness, Workflow
+from prosaic_harness_postgres import PostgresRunStore
+
+workflow = Workflow.load('/srv/workflows/approval/pause.yml')
+# Construct after fork; keep one long-lived store per bounded trusted namespace.
+with PostgresRunStore.from_env('HARNESS_RUNTIME_DSN', namespace='my-app') as store:
+    store.check_ready()  # startup gate; no implicit init
+    h = Harness(workflow, store=store, run_id='0123456789abcdef0123456789abcdef')
+    h.run({'task': 'example'})  # use a NEW UUID for each new run
+    snapshot = h.status()     # read-only .state and opaque .revision
+    h.resume(choice='approve', expected_revision=snapshot.revision)
+```
+
+Worker B reconstructs the same Workflow/namespace/run ID and calls status/resume,
+not run. Human choices, structured responses and explicit interrupted-call retry
+require the current revision. A stale approval cannot approve a later same-named
+pause. Never silently fetch a fresh revision to bypass rejection: show current
+state and require a new decision. See the [runnable example](../../examples/postgres/README.md).
+
+`load_run` returns an independent RunSnapshot; create/save return revisions.
+Receipt absence is None, corruption is an error. Writes require this store/run's
+active lease. Tokens are run/namespace scoped, not lease owner/fencing tokens.
+Receipts are immutable; identical repeats need live ownership. Sealed finite
+JSON is limited to 8 MiB per document including UTF-8 bytes. Public APIs return
+no driver objects. The legacy `Harness(workflow, run_dir)` and filesystem CLI
+remain supported; the adapter adds no new workflow interpreter.
+
+## Deployment and safety
+
+- All reads/writes use the authoritative writable primary, never replicas/caches.
+  Tables must be permanent/logged; fsync/full_page_writes must be on, effective
+  synchronous_commit on or remote_apply. Existing remote_apply is preserved.
+  Primary/WAL guards run on every operation/reconnection.
+- Mount immutable workflow, prose, schema, evidence and reviewed tool assets at
+  identical absolute paths across workers. Keep executables, validator versions
+  and Runtime configuration identical. Drift fails before dispatch. PostgreSQL
+  moves run state, not assets or private tool scratch.
+- Synchronize worker/database clocks and avoid abrupt clock steps. Expiry uses
+  fresh clock_timestamp() after the lease-row lock; local ownership uses a
+  conservative monotonic deadline starting before the request, not at reply.
+- Default lease/renewal 60s/15s. Duration >=15s; renewal >=1s and <=duration/3;
+  renewal + operation budget + 1s must be less than duration. Default total I/O
+  budget 10s, pool/connect 5s, row lock 1s, statement 5s. Deadlines cover pool,
+  network and COMMIT waits. Stalled connections are quarantined; unresolved
+  operations retain capacity and prevent unsafe close.
+- Default lazy pool bounds per store/process: 8 ordinary + 4 renewal connections,
+  maximum 4 active leases. Renewal has reserved capacity. Multiply capacity
+  across replicas/namespaces; do not create a pool per HTTP request. Applications
+  still own scheduling, model concurrency and quotas.
+- Construct after fork; do not share across processes. Drain executions before
+  close/context exit. Threads can share a store; use a separate Harness per run.
+- Namespaces are trusted isolation keys, **not authorization or DB row-level
+  security**. A shared DB role can directly access other namespaces. Derive
+  namespace/run ownership from authenticated server state, never browser/model
+  input. Applications own tenant authorization and admission policies.
+- Raw status state contains private inputs, evidence, responses and history.
+  Products must expose a filtered authorized view, not the operator demo JSON.
+- Prose frontmatter requests tools; Runtime/workflow permissions authorize them.
+  Neither grants database permissions. No HTTP service, queue, PostgreSQL server
+  or historical file importer is included.
+- Fencing stops stale DB mutations, not external tool/model effects. Use
+  application-owned idempotency keys. Pending calls without receipts require
+  explicit fresh retry consent, not automatic redispatch. Unknown token usage
+  may still prevent a token-budgeted retry; abandoned calls retain their budget.
+- Acknowledged WAL durability is not zero-loss asynchronous failover. A lagging
+  promoted primary or older backup can lose receipts/generations. Require
+  operator replication guarantees where needed; do not promise exactly-once
+  external effects from this adapter.
+
+## Errors and recovery
+
+| Code | Action |
+| --- | --- |
+| store_uninitialized | Operator runs init, applies grants, then doctor. |
+| store_incompatible | Check role/version/primary/WAL settings and intact logged schema; no automatic repair. |
+| store_unavailable | Restore primary connectivity and reload status. outcome_unknown means a commit may have succeeded; never blindly repeat writes/effects. |
+| run_busy | Another worker owns execution; back off without launching another call. |
+| lease_lost | Stop dispatch/admission/writes, discard late output; acquire fresh execution and reconcile durable state. |
+| revision_conflict | Show the user's current pause and require a new explicit decision. |
+| store_busy | Drain active/queued/renewal work; construct a new store after fork. |
+| receipt_conflict / store_corrupt | Stop; investigate evidence without overwriting it. |
+
+## Development verification
+
+Core tests need no database/driver. Adapter tests use disposable databases and
+synthetic inference, never TokenProxy. Required mode fails rather than skips
+missing infrastructure. Select Podman/Docker explicitly for crash/standby gates:
+
+```sh
+python -m pip install -e '.[test]' -e './adapters/postgres[test]'
+python adapters/postgres/tests/support/local_cluster.py start --engine podman --version 16
+# Retain the printed ownership.json path as FIXTURE_MANIFEST.
+python adapters/postgres/tests/support/local_cluster.py test --manifest "$FIXTURE_MANIFEST"
+python adapters/postgres/tests/support/local_cluster.py stop --manifest "$FIXTURE_MANIFEST"
+```
+
+Repeat with version 18. Stop validates exact IDs/names/ownership labels before
+removing only owned containers/volumes/network. Generated fixture networks and
+loopback ports use synthetic trust authentication, never production defaults.
+# Lease registration candidate
+
+The adapter transfers acquisition capacity into registered
+session capacity atomically under the existing store mutex. A registering lease
+can no longer be counted twice while maintenance is scheduled. The database
+storage/fencing contract is unchanged. A unit scheduling-boundary regression and
+an owned PostgreSQL 16/18 race regression cover the transition.

b3_prosaic_harness_postgres-0.2.1/README.md

@@ -0,0 +1,202 @@
+# PostgreSQL persistence for Prosaic Harness
+
+Run on worker A, inspect/resume on worker B, without a shared writable run
+directory. Core remains database-free; install this separate adapter only when
+you need shared durable state. The API is synchronous; a private I/O thread
+bounds network waits. Model execution holds no database connection/transaction.
+The current candidate is `b3-prosaic-harness-postgres` **0.2.0**, selecting
+`b3-prosaic-harness>=0.7,<0.8`. The adapter is maintained in this repository but
+installed and versioned separately, keeping PostgreSQL drivers optional for
+Harness users. Imports and CLI names remain unchanged. Final qualification and
+publication of the b3 release train are pending. The historical
+[Harness v0.6.1 release](https://github.com/B3Cognition/prosaic-harness/releases/tag/v0.6.1)
+retains its original 0.6.1/0.1.1 package names and receipts.
+
+## 1. Install and supply an existing database
+
+Python 3.11+, PostgreSQL 16 or 18 on a writable primary, and libpq 17+ are
+required. `psycopg[binary]` supplies libpq; older libpq is rejected.
+From the exact candidate Harness checkout, use a new environment and a curated
+wheelhouse containing only the manifest-selected b3 candidate wheels:
+
+```sh
+python3 -m venv .venv-postgres
+.venv-postgres/bin/python -m pip install --find-links /absolute/path/to/curated-wheelhouse . ./adapters/postgres
+export PATH="$PWD/.venv-postgres/bin:$PATH"
+prosaic --version
+prosaic-harness-postgres --help
+```
+
+ALWAYS migrate using a fresh environment or image; NEVER install legacy and b3
+distributions together because they own the same import paths. See
+[package migration](../../docs/package-migration.md). The Runtime 0.8 candidate
+must be available before this installation can resolve.
+
+Harness does **not** provision PostgreSQL, create databases/users, start a
+service, or fall back to files. Your operator supplies two DSNs through a secret
+manager: `HARNESS_MIGRATION_DSN` (schema owner with database CREATE permission)
+and `HARNESS_RUNTIME_DSN` (restricted runtime role). Never put DSNs in Markdown,
+YAML, argv, logs or Git. For a local terminal:
+
+```sh
+export HARNESS_MIGRATION_DSN="$(python -c 'import getpass; print(getpass.getpass("Migration DSN: "))')"
+export HARNESS_RUNTIME_DSN="$(python -c 'import getpass; print(getpass.getpass("Runtime DSN: "))')"
+```
+
+Preserve operator TLS/authentication settings, e.g. `sslmode=verify-full` and
+certificate roots. The adapter adds `target_session_attrs=read-write` for primary
+routing; it never weakens TLS.
+
+## 2. Initialize once, then grant runtime access
+
+```sh
+prosaic-harness-postgres init --dsn-env HARNESS_MIGRATION_DSN
+```
+
+Initialization is explicit, transactional, repeatable and concurrency-safe.
+It creates schema/version 1, not your database. It refuses unknown versions,
+foreign-owned, partial or damaged schemas; it does not repair or downgrade them.
+
+As schema owner, apply these grants, replacing `harness_runtime` with your
+existing runtime role (role/password creation belongs to your operator):
+
+```sql
+GRANT USAGE ON SCHEMA prosaic_harness TO harness_runtime;
+GRANT SELECT ON prosaic_harness.schema_version, prosaic_harness.leases,
+    prosaic_harness.runs, prosaic_harness.receipts TO harness_runtime;
+GRANT INSERT, UPDATE ON prosaic_harness.leases, prosaic_harness.runs TO harness_runtime;
+GRANT INSERT ON prosaic_harness.receipts TO harness_runtime;
+```
+
+Do **not** grant runtime schema CREATE, schema-version UPDATE, receipt UPDATE,
+or table DELETE. Check using the actual application's credentials:
+
+```sh
+prosaic-harness-postgres doctor --dsn-env HARNESS_RUNTIME_DSN
+```
+
+Default doctor reads only catalogs/settings/privileges: no rows, model calls or
+migrations. For an explicit write-and-cleanup test, use migration or dedicated
+diagnostic credentials with DELETE on the three data tables:
+
+```sh
+prosaic-harness-postgres doctor --dsn-env HARNESS_MIGRATION_DSN --check-write
+```
+
+This exercises guarded create/CAS/receipt/read/release operations in a fresh
+`prosaic-diagnostic-<uuid>` namespace. Reserve this prefix; applications must not
+use it. Cleanup deletes only its exact receipt/run/lease identities, in that
+order, after release. It never deletes production lease generations. Cleanup,
+interruption and commit-ack failures fail the command. Its error includes the
+diagnostic namespace for reconciliation: inspect exact rows before manual
+cleanup/retry, never blindly delete by prefix.
+
+## 3. Embed the single Harness engine
+
+```python
+from prosaic_harness import Harness, Workflow
+from prosaic_harness_postgres import PostgresRunStore
+
+workflow = Workflow.load('/srv/workflows/approval/pause.yml')
+# Construct after fork; keep one long-lived store per bounded trusted namespace.
+with PostgresRunStore.from_env('HARNESS_RUNTIME_DSN', namespace='my-app') as store:
+    store.check_ready()  # startup gate; no implicit init
+    h = Harness(workflow, store=store, run_id='0123456789abcdef0123456789abcdef')
+    h.run({'task': 'example'})  # use a NEW UUID for each new run
+    snapshot = h.status()     # read-only .state and opaque .revision
+    h.resume(choice='approve', expected_revision=snapshot.revision)
+```
+
+Worker B reconstructs the same Workflow/namespace/run ID and calls status/resume,
+not run. Human choices, structured responses and explicit interrupted-call retry
+require the current revision. A stale approval cannot approve a later same-named
+pause. Never silently fetch a fresh revision to bypass rejection: show current
+state and require a new decision. See the [runnable example](../../examples/postgres/README.md).
+
+`load_run` returns an independent RunSnapshot; create/save return revisions.
+Receipt absence is None, corruption is an error. Writes require this store/run's
+active lease. Tokens are run/namespace scoped, not lease owner/fencing tokens.
+Receipts are immutable; identical repeats need live ownership. Sealed finite
+JSON is limited to 8 MiB per document including UTF-8 bytes. Public APIs return
+no driver objects. The legacy `Harness(workflow, run_dir)` and filesystem CLI
+remain supported; the adapter adds no new workflow interpreter.
+
+## Deployment and safety
+
+- All reads/writes use the authoritative writable primary, never replicas/caches.
+  Tables must be permanent/logged; fsync/full_page_writes must be on, effective
+  synchronous_commit on or remote_apply. Existing remote_apply is preserved.
+  Primary/WAL guards run on every operation/reconnection.
+- Mount immutable workflow, prose, schema, evidence and reviewed tool assets at
+  identical absolute paths across workers. Keep executables, validator versions
+  and Runtime configuration identical. Drift fails before dispatch. PostgreSQL
+  moves run state, not assets or private tool scratch.
+- Synchronize worker/database clocks and avoid abrupt clock steps. Expiry uses
+  fresh clock_timestamp() after the lease-row lock; local ownership uses a
+  conservative monotonic deadline starting before the request, not at reply.
+- Default lease/renewal 60s/15s. Duration >=15s; renewal >=1s and <=duration/3;
+  renewal + operation budget + 1s must be less than duration. Default total I/O
+  budget 10s, pool/connect 5s, row lock 1s, statement 5s. Deadlines cover pool,
+  network and COMMIT waits. Stalled connections are quarantined; unresolved
+  operations retain capacity and prevent unsafe close.
+- Default lazy pool bounds per store/process: 8 ordinary + 4 renewal connections,
+  maximum 4 active leases. Renewal has reserved capacity. Multiply capacity
+  across replicas/namespaces; do not create a pool per HTTP request. Applications
+  still own scheduling, model concurrency and quotas.
+- Construct after fork; do not share across processes. Drain executions before
+  close/context exit. Threads can share a store; use a separate Harness per run.
+- Namespaces are trusted isolation keys, **not authorization or DB row-level
+  security**. A shared DB role can directly access other namespaces. Derive
+  namespace/run ownership from authenticated server state, never browser/model
+  input. Applications own tenant authorization and admission policies.
+- Raw status state contains private inputs, evidence, responses and history.
+  Products must expose a filtered authorized view, not the operator demo JSON.
+- Prose frontmatter requests tools; Runtime/workflow permissions authorize them.
+  Neither grants database permissions. No HTTP service, queue, PostgreSQL server
+  or historical file importer is included.
+- Fencing stops stale DB mutations, not external tool/model effects. Use
+  application-owned idempotency keys. Pending calls without receipts require
+  explicit fresh retry consent, not automatic redispatch. Unknown token usage
+  may still prevent a token-budgeted retry; abandoned calls retain their budget.
+- Acknowledged WAL durability is not zero-loss asynchronous failover. A lagging
+  promoted primary or older backup can lose receipts/generations. Require
+  operator replication guarantees where needed; do not promise exactly-once
+  external effects from this adapter.
+
+## Errors and recovery
+
+| Code | Action |
+| --- | --- |
+| store_uninitialized | Operator runs init, applies grants, then doctor. |
+| store_incompatible | Check role/version/primary/WAL settings and intact logged schema; no automatic repair. |
+| store_unavailable | Restore primary connectivity and reload status. outcome_unknown means a commit may have succeeded; never blindly repeat writes/effects. |
+| run_busy | Another worker owns execution; back off without launching another call. |
+| lease_lost | Stop dispatch/admission/writes, discard late output; acquire fresh execution and reconcile durable state. |
+| revision_conflict | Show the user's current pause and require a new explicit decision. |
+| store_busy | Drain active/queued/renewal work; construct a new store after fork. |
+| receipt_conflict / store_corrupt | Stop; investigate evidence without overwriting it. |
+
+## Development verification
+
+Core tests need no database/driver. Adapter tests use disposable databases and
+synthetic inference, never TokenProxy. Required mode fails rather than skips
+missing infrastructure. Select Podman/Docker explicitly for crash/standby gates:
+
+```sh
+python -m pip install -e '.[test]' -e './adapters/postgres[test]'
+python adapters/postgres/tests/support/local_cluster.py start --engine podman --version 16
+# Retain the printed ownership.json path as FIXTURE_MANIFEST.
+python adapters/postgres/tests/support/local_cluster.py test --manifest "$FIXTURE_MANIFEST"
+python adapters/postgres/tests/support/local_cluster.py stop --manifest "$FIXTURE_MANIFEST"
+```
+
+Repeat with version 18. Stop validates exact IDs/names/ownership labels before
+removing only owned containers/volumes/network. Generated fixture networks and
+loopback ports use synthetic trust authentication, never production defaults.
+# Lease registration candidate
+
+The adapter transfers acquisition capacity into registered
+session capacity atomically under the existing store mutex. A registering lease
+can no longer be counted twice while maintenance is scheduled. The database
+storage/fencing contract is unchanged. A unit scheduling-boundary regression and
+an owned PostgreSQL 16/18 race regression cover the transition.

b3_prosaic_harness_postgres-0.2.1/pyproject.toml

@@ -0,0 +1,22 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "b3-prosaic-harness-postgres"
+version = "0.2.1"
+description = "Explicit PostgreSQL run storage for Prosaic Harness"
+requires-python = ">=3.11"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+dependencies = ["b3-prosaic-harness>=0.7,<0.8", "psycopg[binary]>=3.2.3,<4", "psycopg-pool>=3.2,<4"]
+
+[project.optional-dependencies]
+test = ["pytest>=8", "build>=1", "setuptools>=77", "wheel", "packaging"]
+
+[project.scripts]
+prosaic-harness-postgres = "prosaic_harness_postgres.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]

b3_prosaic_harness_postgres-0.2.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+