sembl-stack 0.1.0__tar.gz

sembl_stack-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,67 @@
+name: Publish to PyPI
+
+# Runs when you publish a GitHub Release (Releases -> Draft a new release ->
+# pick a tag like vX.Y.Z -> Publish). The release tag MUST match the version in
+# pyproject.toml and sembl_stack/__init__.py, or the build step fails.
+#
+# Publishing uses PyPI Trusted Publishing (OIDC): no API token is stored anywhere.
+# Before the first release, register this repo + workflow as a trusted publisher
+# for the `sembl-stack` project on PyPI (https://pypi.org/manage/account/publishing/).
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    name: Build distribution
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Verify release tag and all version surfaces agree
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          VER="$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")"
+          INIT="$(python -c "import re;print(re.search(r'__version__\s*=\s*\"([^\"]+)\"', open('sembl_stack/__init__.py').read()).group(1))")"
+          echo "release tag: $TAG | pyproject: $VER | __init__: $INIT"
+          if [ "$TAG" != "$VER" ] || [ "$VER" != "$INIT" ]; then
+            echo "::error::Version mismatch (tag '$TAG', pyproject '$VER', __init__ '$INIT'). They must all match."
+            exit 1
+          fi
+
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build
+
+      - name: Check distribution metadata
+        run: |
+          python -m pip install --upgrade twine
+          python -m twine check dist/*
+
+      - name: Upload built distribution
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write  # required for Trusted Publishing (OIDC); no token needed
+    steps:
+      - name: Download built distribution
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

sembl_stack-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+# Example target repos are git-inited locally for demos; don't nest their .git
+examples/**/repo/.git/
+# Local-only tests (kept off the repo by request)
+tests/local/
+# Run artifacts (the run store) are local-only
+.sembl/
+examples/**/repo/.sembl/
+__pycache__/
+*.egg-info/
+.pytest_cache/
+.test-tmp/
+build/
+dist/
+.venv/

sembl_stack-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Siddharth Totla (speedvibecode)
+
+   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.

sembl_stack-0.1.0/PKG-INFO

@@ -0,0 +1,165 @@
+Metadata-Version: 2.4
+Name: sembl-stack
+Version: 0.1.0
+Summary: A swappable, spec-driven software factory: task to bounds, an agent writes in a sandbox, the Sembl gate judges the diff, PASS merges, deploys, and a post-deploy gate confirms or rolls back. Every stage an adapter behind one typed contract.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.10
+Requires-Dist: click>=8.1
+Requires-Dist: langgraph>=0.2
+Requires-Dist: mcp>=1.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: sembl>=0.1.20
+Provides-Extra: all
+Requires-Dist: langfuse>=2.0; extra == 'all'
+Requires-Dist: langgraph>=0.2; extra == 'all'
+Requires-Dist: mcp>=1.0; extra == 'all'
+Requires-Dist: sembl>=0.1.20; extra == 'all'
+Requires-Dist: textual>=0.50; extra == 'all'
+Provides-Extra: gate
+Requires-Dist: sembl>=0.1.20; extra == 'gate'
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.0; extra == 'mcp'
+Provides-Extra: orchestrate
+Requires-Dist: langgraph>=0.2; extra == 'orchestrate'
+Provides-Extra: trace
+Requires-Dist: langfuse>=2.0; extra == 'trace'
+Provides-Extra: tui
+Requires-Dist: textual>=0.50; extra == 'tui'
+Description-Content-Type: text/markdown
+
+# sembl-stack
+
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Built around Sembl](https://img.shields.io/badge/gate-Sembl-ccff00.svg)](https://github.com/speedvibecode/sembl)
+
+**A swappable, spec-driven software factory.** A task becomes declared bounds, an
+agent writes the change inside a disposable sandbox, the **[Sembl](https://github.com/speedvibecode/sembl)
+gate** judges the real diff against those bounds, a PASS merges and deploys, and a
+post-deploy gate confirms it's healthy — or rolls it back. **Every stage is an
+interchangeable adapter behind one typed artifact contract, and every run is
+recorded.**
+
+We sell **process correctness** — the change did what the spec declared, stayed in
+bounds, is honestly evidenced, and reached production accountably — **never "the
+model writes better code."** The stack takes no side in the agent wars: swap the
+executor, the sandbox, or the deploy target with one line of config and the rest of
+the pipeline doesn't notice.
+
+[Website](https://sembl-stack.vercel.app) · [The gate (Sembl)](https://sembl.vercel.app) · [Architecture & plan](docs/PROCESS-ACTION-PLAN.md)
+
+```text
+task ─▶ bounds ─▶ execute ─▶ sandbox ─▶ SEMBL GATE ─▶ merge ─▶ deploy ─▶ verify-in-prod
+        (L2)       (L3)        (L4)       (L5)         (L6.5)    (L7)       (L8)
+                                          every arrow is a typed artifact on disk
+```
+
+## Quickstart
+
+```bash
+pip install sembl-stack sembl     # the stack + the gate it runs at its core
+sembl-stack init                  # scaffold sembl.stack.yaml + task.yaml from a preset
+sembl-stack doctor                # config-aware preflight
+sembl-stack loop task.yaml        # plan → execute → gate → retry-on-BLOCK
+sembl-stack runs [<id>]           # list / inspect runs
+sembl-stack apply <id>            # apply the accepted patch (a BLOCK is never applied)
+```
+
+**Presets** (`sembl-stack init --preset …`):
+
+| Preset | What runs | Needs |
+|--------|-----------|-------|
+| `just-gate` | gate any diff, nothing else | only `sembl` |
+| `gate+sandbox` | the whole loop with a mock executor | no API keys |
+| `full-loop` | real agent + sandbox + gate | an executor key |
+
+Swap any layer in `sembl.stack.yaml` — e.g. `execute: opencode`, `execute: aider` —
+with no code change.
+
+## The stage map (L0–L8)
+
+Each stage consumes and produces typed artifacts; that hand-off *is* the whole
+interface, which is what makes every stage swappable.
+
+| Stage | Does | Artifact flow | Who owns it |
+|-------|------|---------------|-------------|
+| **L0** Protocol & hub | one wire between stages | — | **we own** (the contract) |
+| **L1** Repo intel | code-graph context | `Task → Context` | adapter |
+| **L2** Spec → bounds | scope the change | `Task → Bounds` | **we own** (`sembl`) |
+| **L3** Execute | write the change | `Task + Bounds → Change` | adapter (claude / aider / opencode) |
+| **L4** Sandbox | contain a bad diff | `Change → Change` | adapter (disposable clone) |
+| **L5** Verify | gate the diff | `Change + Bounds → Verdict` | **the gate** (`sembl`) |
+| **L5.5** Review (advisory) | code-quality signal | `diff → findings` | adapter (`llm` — BYO agent-CLI reviewer; CodeRabbit optional) |
+| **L6** Orchestrate | loop, retry, trace | wiring + `* → Trace` | **we own** (LangGraph) |
+| **L6.5** Merge | gated merge | `Verdict(PASS) → MergeRecord` | **we own** |
+| **L7** Deploy | ship | `Verdict(PASS) → Delivery` | adapter |
+| **L8** Verify-in-prod | gate production | `Delivery → Verdict` | **the gate** (health + rollback) |
+
+We own exactly three things: the **artifact contract + stage Protocol**, the **gate
+(L5 + the post-deploy L8)**, and the **glue + layer-replacement protocol**.
+Everything else is deliberately a best-in-class tool behind an interface.
+
+## The accountable spine
+
+A verdict is bound to the change it judged — most agent pipelines stop at "the check
+passed"; this one guarantees a verdict can only ship the exact change it was issued
+for:
+
+- **Verdicts carry their subject.** Every verdict is stamped with the SHA-256 and
+  file set of the diff it judged. `apply` recomputes the patch hash and refuses a
+  verdict issued for a different patch; `merge` refuses if the merge would ship files
+  the verdict never saw.
+- **BLOCK means blocked.** A BLOCK verdict is never applied and never merged — the
+  loop retries the executor instead. Overrides (`--skip-binding-check`) exist but are
+  recorded permanently in the `MergeRecord`.
+- **Production is gated too.** After deploy, the L8 gate checks the live delivery
+  (health + payload, deterministically) and triggers a rollback when it fails.
+
+Every run leaves a complete paper trail in `.sembl/runs/<id>/`:
+
+```text
+.sembl/runs/2ca41f/
+├─ task.json          # what was asked
+├─ bounds.json        # the declared contract
+├─ change.json        # the actual diff
+├─ verdict.json       # the gate's judgement + subject binding
+├─ merge-record.json  # what shipped, and under whose PASS
+└─ trace.json         # the timeline
+```
+
+## The guided TUI (optional)
+
+`pip install "sembl-stack[tui]"` adds a Textual wizard. Run bare `sembl-stack` and
+press `r`: the stage rail runs the real loop under your configured profile,
+streaming per-stage status (pending/running/pass/fail) live and showing the final
+verdict — byte-identical to a headless `sembl-stack loop`, because it drives the
+same adapters.
+
+## The full picture
+
+**→ [`docs/PROCESS-ACTION-PLAN.md`](docs/PROCESS-ACTION-PLAN.md)** is the single
+source of truth: architecture, the L0–L8 stage map with build status, the eval
+metric, locked decisions, the guided-TUI vision, and the remaining-work plan.
+
+Reference: [`process-self-improvement.md`](docs/process-self-improvement.md)
+(north-star theory) · [`eval-metric-O3.md`](docs/eval-metric-O3.md) (the metric) ·
+[`memory-plane-hypothesis.md`](docs/memory-plane-hypothesis.md).
+
+## Local development
+
+```bash
+uv sync --extra all
+uv pip install -e ../sembl          # or: pip install sembl
+.venv/Scripts/python -m pytest -q   # run from the repo root (corpus paths are cwd-relative)
+```
+
+## Releasing
+
+Publishing uses GitHub Actions + PyPI Trusted Publishing (OIDC); no tokens are
+stored. `.github/workflows/release.yml` builds and publishes when you publish a
+GitHub Release whose tag (`vX.Y.Z`) matches `pyproject.toml` and
+`sembl_stack/__init__.py`.
+
+---
+
+Agents write the code. **sembl-stack makes the whole pipeline accountable.**

sembl_stack-0.1.0/README.md

@@ -0,0 +1,135 @@
+# sembl-stack
+
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Built around Sembl](https://img.shields.io/badge/gate-Sembl-ccff00.svg)](https://github.com/speedvibecode/sembl)
+
+**A swappable, spec-driven software factory.** A task becomes declared bounds, an
+agent writes the change inside a disposable sandbox, the **[Sembl](https://github.com/speedvibecode/sembl)
+gate** judges the real diff against those bounds, a PASS merges and deploys, and a
+post-deploy gate confirms it's healthy — or rolls it back. **Every stage is an
+interchangeable adapter behind one typed artifact contract, and every run is
+recorded.**
+
+We sell **process correctness** — the change did what the spec declared, stayed in
+bounds, is honestly evidenced, and reached production accountably — **never "the
+model writes better code."** The stack takes no side in the agent wars: swap the
+executor, the sandbox, or the deploy target with one line of config and the rest of
+the pipeline doesn't notice.
+
+[Website](https://sembl-stack.vercel.app) · [The gate (Sembl)](https://sembl.vercel.app) · [Architecture & plan](docs/PROCESS-ACTION-PLAN.md)
+
+```text
+task ─▶ bounds ─▶ execute ─▶ sandbox ─▶ SEMBL GATE ─▶ merge ─▶ deploy ─▶ verify-in-prod
+        (L2)       (L3)        (L4)       (L5)         (L6.5)    (L7)       (L8)
+                                          every arrow is a typed artifact on disk
+```
+
+## Quickstart
+
+```bash
+pip install sembl-stack sembl     # the stack + the gate it runs at its core
+sembl-stack init                  # scaffold sembl.stack.yaml + task.yaml from a preset
+sembl-stack doctor                # config-aware preflight
+sembl-stack loop task.yaml        # plan → execute → gate → retry-on-BLOCK
+sembl-stack runs [<id>]           # list / inspect runs
+sembl-stack apply <id>            # apply the accepted patch (a BLOCK is never applied)
+```
+
+**Presets** (`sembl-stack init --preset …`):
+
+| Preset | What runs | Needs |
+|--------|-----------|-------|
+| `just-gate` | gate any diff, nothing else | only `sembl` |
+| `gate+sandbox` | the whole loop with a mock executor | no API keys |
+| `full-loop` | real agent + sandbox + gate | an executor key |
+
+Swap any layer in `sembl.stack.yaml` — e.g. `execute: opencode`, `execute: aider` —
+with no code change.
+
+## The stage map (L0–L8)
+
+Each stage consumes and produces typed artifacts; that hand-off *is* the whole
+interface, which is what makes every stage swappable.
+
+| Stage | Does | Artifact flow | Who owns it |
+|-------|------|---------------|-------------|
+| **L0** Protocol & hub | one wire between stages | — | **we own** (the contract) |
+| **L1** Repo intel | code-graph context | `Task → Context` | adapter |
+| **L2** Spec → bounds | scope the change | `Task → Bounds` | **we own** (`sembl`) |
+| **L3** Execute | write the change | `Task + Bounds → Change` | adapter (claude / aider / opencode) |
+| **L4** Sandbox | contain a bad diff | `Change → Change` | adapter (disposable clone) |
+| **L5** Verify | gate the diff | `Change + Bounds → Verdict` | **the gate** (`sembl`) |
+| **L5.5** Review (advisory) | code-quality signal | `diff → findings` | adapter (`llm` — BYO agent-CLI reviewer; CodeRabbit optional) |
+| **L6** Orchestrate | loop, retry, trace | wiring + `* → Trace` | **we own** (LangGraph) |
+| **L6.5** Merge | gated merge | `Verdict(PASS) → MergeRecord` | **we own** |
+| **L7** Deploy | ship | `Verdict(PASS) → Delivery` | adapter |
+| **L8** Verify-in-prod | gate production | `Delivery → Verdict` | **the gate** (health + rollback) |
+
+We own exactly three things: the **artifact contract + stage Protocol**, the **gate
+(L5 + the post-deploy L8)**, and the **glue + layer-replacement protocol**.
+Everything else is deliberately a best-in-class tool behind an interface.
+
+## The accountable spine
+
+A verdict is bound to the change it judged — most agent pipelines stop at "the check
+passed"; this one guarantees a verdict can only ship the exact change it was issued
+for:
+
+- **Verdicts carry their subject.** Every verdict is stamped with the SHA-256 and
+  file set of the diff it judged. `apply` recomputes the patch hash and refuses a
+  verdict issued for a different patch; `merge` refuses if the merge would ship files
+  the verdict never saw.
+- **BLOCK means blocked.** A BLOCK verdict is never applied and never merged — the
+  loop retries the executor instead. Overrides (`--skip-binding-check`) exist but are
+  recorded permanently in the `MergeRecord`.
+- **Production is gated too.** After deploy, the L8 gate checks the live delivery
+  (health + payload, deterministically) and triggers a rollback when it fails.
+
+Every run leaves a complete paper trail in `.sembl/runs/<id>/`:
+
+```text
+.sembl/runs/2ca41f/
+├─ task.json          # what was asked
+├─ bounds.json        # the declared contract
+├─ change.json        # the actual diff
+├─ verdict.json       # the gate's judgement + subject binding
+├─ merge-record.json  # what shipped, and under whose PASS
+└─ trace.json         # the timeline
+```
+
+## The guided TUI (optional)
+
+`pip install "sembl-stack[tui]"` adds a Textual wizard. Run bare `sembl-stack` and
+press `r`: the stage rail runs the real loop under your configured profile,
+streaming per-stage status (pending/running/pass/fail) live and showing the final
+verdict — byte-identical to a headless `sembl-stack loop`, because it drives the
+same adapters.
+
+## The full picture
+
+**→ [`docs/PROCESS-ACTION-PLAN.md`](docs/PROCESS-ACTION-PLAN.md)** is the single
+source of truth: architecture, the L0–L8 stage map with build status, the eval
+metric, locked decisions, the guided-TUI vision, and the remaining-work plan.
+
+Reference: [`process-self-improvement.md`](docs/process-self-improvement.md)
+(north-star theory) · [`eval-metric-O3.md`](docs/eval-metric-O3.md) (the metric) ·
+[`memory-plane-hypothesis.md`](docs/memory-plane-hypothesis.md).
+
+## Local development
+
+```bash
+uv sync --extra all
+uv pip install -e ../sembl          # or: pip install sembl
+.venv/Scripts/python -m pytest -q   # run from the repo root (corpus paths are cwd-relative)
+```
+
+## Releasing
+
+Publishing uses GitHub Actions + PyPI Trusted Publishing (OIDC); no tokens are
+stored. `.github/workflows/release.yml` builds and publishes when you publish a
+GitHub Release whose tag (`vX.Y.Z`) matches `pyproject.toml` and
+`sembl_stack/__init__.py`.
+
+---
+
+Agents write the code. **sembl-stack makes the whole pipeline accountable.**