holdout 0.1.0__tar.gz

holdout-0.1.0/.gitignore

@@ -0,0 +1,61 @@
+# Python
+__pycache__/
+*.py[cod]
+*.pyo
+*.pyd
+.Python
+*.egg
+*.egg-info/
+dist/
+build/
+eggs/
+parts/
+var/
+sdist/
+wheels/
+*.egg-link
+.installed.cfg
+MANIFEST
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+
+# Testing
+.pytest_cache/
+.coverage
+coverage.xml
+htmlcov/
+
+# Type checking
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Linting
+.ruff_cache/
+
+# Environment / secrets
+.env
+.env.*
+*.key
+
+# SQLite databases
+*.db
+*.sqlite
+*.sqlite3
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# macOS
+.DS_Store
+
+# Distribution
+*.tar.gz
+*.whl

holdout-0.1.0/CLAUDE.md

@@ -0,0 +1,153 @@
+# CLAUDE.md
+
+Steering for Claude Code working on **MAGI**. Read this fully before any task. It is
+deliberately short. When this file and a vibe disagree, this file wins.
+
+---
+
+## What MAGI is (one paragraph)
+
+MAGI takes a question that has **no verifiable answer** and puts it to N independently
+prompted agents, each committing a written rationale and a YES/NO vote **before seeing
+any peer**. It preserves every rationale — including the losing one — as a durable
+record, and on disagreement returns a **crux** instead of a forced answer. The output is
+an artifact, not a decision. MAGI makes **no accuracy claim** and has **no benchmark**.
+
+The full case lives in the design docs. You do not need them to build. You need this
+file, the build spec, and the testing strategy.
+
+---
+
+## The two invariants (do not violate, ever)
+
+These are the whole point of the project. Most "improvements" an agent is tempted to make
+violate one of them. If a change touches either, stop and re-read this section.
+
+### I. NO SYNTHESIS
+The system **never** merges the positions into a single answer. There is no "final
+answer," no "consensus summary," no "recommended decision" beyond the prevailing vote or
+the crux.
+- `Record` has **no field** that could hold a merged answer. Do not add one
+  (`synthesis`, `answer`, `final`, `summary`, `consensus`, `verdict_text`, etc.).
+- The terminal step builds a `Record` from `Position` objects + an `Outcome` (+ optional
+  crux, + optional concurrence flag). It produces **no free text that aggregates the
+  rationales**.
+- If a task seems to want a "summary of what the panel decided," the answer is the
+  `Record` itself, rendered faithfully. Not a synthesized paragraph.
+
+### II. BLIND COMMITMENT
+Each agent commits **without sight of any peer's output**.
+- The commitment function takes the question and **exactly one agent** — never the panel,
+  never a list of peer rationales. Do not add a parameter through which peer output could
+  pass.
+- The N commitment calls are dispatched **concurrently** and awaited together, so none can
+  depend on another's result.
+- A peer rationale must never appear in an agent's prompt. This is enforced by the
+  function boundary and **tested by surveillance** (sentinel tokens in scripted
+  rationales; assert no agent's prompt contains a peer's token). Never weaken that test.
+
+Both invariants are **encoded in the types and call graph**, not just in docs. Keep them
+there. A pre-merge gate fails if the no-synthesis field-absence test or the
+blind-commitment surveillance test is removed or skipped.
+
+---
+
+## Hard rules
+
+- **No agent framework.** No LangChain, CrewAI, LlamaIndex, AutoGen, or similar. They
+  impose the synthesis/coordination patterns MAGI rejects; importing one smuggles the
+  convergence bias back through a dependency. Talk to providers over plain async HTTP.
+- **Provider is an injected seam.** Everything depends on the one-method `Provider`
+  protocol, never a concrete provider. The default test double is `FakeProvider`. The
+  whole engine must be testable **offline, deterministically, with no API key**.
+- **The contract (`types.py`) is depended on by everything and depends on nothing.** Build
+  it first; change it rarely; never loosen its validators to make a test pass.
+- **Tests are structural where it matters.** For the two invariants, test the *property*
+  (can it happen at all?), not an *example* (did it happen this time?). See the testing
+  strategy.
+- **Don't test prompt quality in the unit suite.** Whether a crux is *wise* is a prompt
+  loop, not a test. Tests assert plumbing: prompt loads, fields populate, response parses.
+- **`async` throughout the protocol.** The fan-out is inherently parallel; modeling it
+  synchronously models it wrong.
+- **Keep the public API tiny.** `Agent`, `Position`, `Record`, `Vote`, `Tier`, `Outcome`,
+  and `Panel.deliberate`. Resist surface-area growth.
+
+---
+
+## Repo map
+
+```
+src/holdout/
+  __init__.py          public API (tiny)
+  types.py             THE CONTRACT — build first, change rarely
+  providers/
+    base.py            Provider protocol (one method)
+    openai_compat.py   the ONE real adapter (httpx) — the only live surface
+    fake.py            deterministic test double; also records prompts
+  protocol/
+    commit.py          blind commitment: parallel fan-out, one agent per call
+    tabulate.py        vote counting; threshold by tier
+    crux.py            consequence-anchored crux (LLM call)
+    concurrence.py     fragile-agreement detection (LLM call)
+    engine.py          orchestrates the steps -> Record
+  store/
+    schema.sql         the record schema, verbatim from the spec
+    sqlite.py          write, get-by-id, recent, similar
+  report/
+    template.html.j2   faithful, equal-weight render
+    render.py
+  cli.py               thin typer wrapper over the library
+prompts/               versioned prompt text, SEPARATE from logic
+tests/                 mirror the modules above
+```
+
+Module boundaries mirror the protocol steps on purpose: a task is usually "implement
+`<module>.py` so `tests/test_<module>.py` is green." Keep it that way.
+
+---
+
+## Build order (each step ends green before the next)
+
+1. `types.py` + `providers/base.py` + `providers/fake.py` — contract and test harness, no
+   behavior. (Reference contract already passes 21 checks; keep them green.)
+2. `protocol/commit.py` + `tabulate.py` — run a deliberation against the fake, get a
+   majority result. Blind-commitment tests (surveillance + concurrency + signature) land
+   here and are non-negotiable.
+3. `protocol/crux.py` + `concurrence.py` — split and fragile-agreement paths. Test wiring
+   and structural result only, not crux quality.
+4. `store/` — schema, write, get-by-id, recent, then similar. Faithful round-trip;
+   verbatim mandate (auditability).
+5. `report/` — faithful, equal-weight render; minority labelled on-record, never error.
+   Ties to the no-synthesis faithfulness test.
+6. Two-tier handling + caller-asserted tier at the entrypoint.
+7. `cli.py`; then `providers/openai_compat.py` (offline via respx; one opt-in live smoke
+   test).
+
+Don't jump ahead. Don't hold more than one module's complexity at once.
+
+---
+
+## Workflow expectations
+
+- **Run the gate before declaring done:** `ruff check`, `ruff format --check`,
+  `mypy --strict src`, `pytest` (excludes live by default).
+- **`mypy --strict` must stay clean on `src`.** The contract is typed; enforce it.
+- **Live tests are opt-in** (`-m live`, needs a key). Never make them gate ordinary work.
+- **Small, reviewable commits**, one module/concern each. The invariants must remain
+  visible in diffs — a change that touches synthesis or blind commitment should be
+  obvious to a reviewer.
+- **If a task tempts you to violate an invariant, surface it instead of doing it.** Say
+  which invariant and why the task seems to want it. The likely resolution is that the
+  task is misread, not that the invariant should bend.
+
+---
+
+## Quick self-check before any change
+
+- Does this add a field or path that could hold a merged answer? → **Stop (Invariant I).**
+- Could a peer rationale reach an agent's prompt after this? → **Stop (Invariant II).**
+- Am I adding a framework or a heavy dependency? → **Stop (hard rule).**
+- Am I testing whether a prompt is *good* rather than *wired*? → **Wrong layer.**
+- Did I loosen a `types.py` validator to pass a test? → **Fix the test, not the contract.**
+
+If all five are clear, proceed.

holdout-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

holdout-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,51 @@
+# Contributing
+
+## Set up
+
+```bash
+git clone https://github.com/mehrabr/holdout.git
+cd holdout
+uv pip install -e ".[dev]"   # or: pip install -e ".[dev]"
+```
+
+Requires Python 3.11+.
+
+## Run the gate
+
+All four must pass before a PR is ready:
+
+```bash
+ruff check src tests          # lint
+ruff format --check src tests # formatting
+mypy --strict src             # types (strict; src only)
+pytest                        # tests (live tests excluded by default)
+```
+
+Run them together:
+
+```bash
+ruff check src tests && ruff format --check src tests && mypy --strict src && pytest
+```
+
+Live tests hit a real provider endpoint and need an API key. They are opt-in and never
+gate ordinary work:
+
+```bash
+pytest -m live
+```
+
+## Before opening a PR
+
+- Keep commits small and focused on one module or concern.
+- Any change that touches synthesis prevention or blind commitment should be obviously
+  visible in the diff — reviewers look for this.
+- If a change seems to require loosening a validator in `types.py`, fix the change, not
+  the contract.
+- If a change seems to require merging agent positions or passing peer output between
+  agents, read `CLAUDE.md` — the two invariants explain why those paths are closed.
+
+## Project structure
+
+The repo map and build order are in `CLAUDE.md`. The two design invariants (no synthesis,
+blind commitment) are described there too; they are encoded in the types and call graph,
+not just in docs.

holdout-0.1.0/LICENSE

@@ -0,0 +1,189 @@
+                                 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 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, as submitted to the 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 designated in writing by the copyright owner as "Not a
+      Contribution."
+
+      "Contributor" shall mean Licensor and any Legal Entity on behalf of
+      whom a Contribution has been received by the Licensor and included
+      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 the 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 any
+      Contribution embodied 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, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, 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 in addition 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 license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the
+      Contribution, either on their own or together with this Work.
+
+   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 reproducing 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 exemplary 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 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 offer only
+      conditions consistent with this License, subject to any additional
+      terms You require or accept.
+
+   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 in question. It may be
+      appropriate to place the header in a source file's first section.
+
+   Copyright 2026 mehrabr
+
+   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.