lattice-cli 0.1.0__tar.gz

lattice_cli-0.1.0/LICENSE

@@ -0,0 +1,176 @@
+                                 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

lattice_cli-0.1.0/PKG-INFO

@@ -0,0 +1,229 @@
+Metadata-Version: 2.4
+Name: lattice-cli
+Version: 0.1.0
+Summary: Deterministic combinatorial coverage for agent workflows and constrained variant surfaces.
+Author-email: Tyler Klose <tylerklose@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/tylerklose/lattice
+Project-URL: Repository, https://github.com/tylerklose/lattice
+Project-URL: Issues, https://github.com/tylerklose/lattice/issues
+Keywords: coding-agents,combinatorial-testing,component-variants,pairwise-testing,test-generation,visual-testing,coverage
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: PyYAML<7,>=6
+Provides-Extra: solver
+Requires-Dist: ortools<10,>=9.10; extra == "solver"
+Dynamic: license-file
+
+# Lattice
+
+Say you're testing a checkout flow. Users are signed in or guest. They have a coupon or not. The cart is empty, single-item, or multi-item. Shipping is standard, express, or pickup. Payment is card, Apple Pay, or PayPal. The site renders in light or dark mode.
+
+Six knobs, a few settings each — 216 combinations. Real product surfaces have dozens of knobs and hundreds of thousands of combinations. And most production bugs are *interaction* bugs: the one where dark mode plus Apple Pay plus the new coupon breaks the order page, even though each piece works fine alone.
+
+Nobody writes tests for 216 combinations. Nobody can write tests for 200,000. So humans and coding agents alike pick a handful of cases by gut feel, and the interaction bug ships.
+
+Lattice is the way out. You list the knobs, the settings, and any rules ("Apple Pay isn't allowed for pickup orders"). Lattice gives back a short, deterministic list of scenarios that hits every *pair* of settings at least once. The six-knob example above collapses from 216 cases to about a dozen — enough to catch the overwhelming majority of interaction bugs without writing the universe.
+
+The math behind this is old. It's what Hexawise and similar tools have been selling for years. What's new here is the packaging: schema in on stdin, rows out on stdout, deterministic, built for a coding agent to call while planning a feature or writing tests. The agent describes the surface, Lattice does the combinatorics, the agent turns each row into a test, a rendered screenshot, a fixture, or a step of plan review.
+
+## What this unlocks
+
+**Pre-code planning.** An agent given a feature spec writes a plan that looks careful and treats interactions as an afterthought. Modeling the surface as a Lattice schema first — parameters, values, constraints — changes the plan. The agent isn't picking edges by gut feel; it has a deterministic list of combinations the design has to handle. Spec gaps surface during modeling, when they're still cheap to address, instead of during the first incident.
+
+**Writing tests.** The failure mode isn't undertesting. Agents will happily generate fifty tests — overmocked, all hitting the same happy path, and on the next run, silently rewritten when one fails. An [empirical study](https://arxiv.org/abs/2602.00409) of 1.2M commits found agents add mocks at nearly 1.4x the human rate and reach almost exclusively for the basic `mock` primitive where humans spread across fakes, spies, and stubs. The rewrite-instead-of-fix instinct shows up in the [Claude Code issue tracker](https://github.com/anthropics/claude-code/issues/51856) under the name *fix-fail-propose-new-fix*: a fix breaks the live app, the unit suite still passes, so the agent files the symptoms as new bugs and proposes more fixes instead of reverting. The pattern is structural — it follows from handing an agent unilateral write access to the assertion it has to pass — not a quirk of any specific model.
+
+Lattice doesn't solve the temptation; it removes the choice. The schema dictates the matrix. The rows dictate the assertions. An unsatisfied row is a case the design has to answer for — not a test to delete.
+
+Same loop in both places: the agent describes the surface, Lattice does the combinatorics, the agent reasons over the rows. The schema is cheap. The coverage is defensible.
+
+## How it goes
+
+1. The agent writes a small JSON or YAML schema: parameters, values, constraints.
+2. Pipe it to `lattice generate`.
+3. Lattice returns the covering rows. Same schema and seed always produce the same rows.
+4. The agent maps each row to whatever it's evaluating — a test, a render, a fixture, a sandbox call.
+
+The schema is the contract between agent and engine. The rows are the product. Lattice does not care whether the surface is a backend feature, an API, a state machine, a Rails partial, a design-system component, an email template, a config matrix, or a data-model slice — if it has dimensions, values, rules, and an evaluator, Lattice can cover it.
+
+Project status: experimental `0.1`. The CLI and agent skill bootstrap path work; the schema contract may still evolve as the project finds its first users.
+
+## Install For Agents
+
+Start with [docs/install.md](docs/install.md) when you want any coding agent or harness to adopt Lattice.
+
+That page covers:
+
+- installing the `lattice` CLI with `pipx`, `uvx`, or `pip`
+- printing universal instructions with `lattice agent instructions`
+- installing a generic `lattice-workflow` skill into any harness directory with `lattice agent install-skill <target>`
+- installing Codex and Claude Code convenience skills with `lattice agent bootstrap`
+- adding an agent memory for when to reach for Lattice
+- running a smoke test over stdin
+
+## Why This Shape
+
+Lattice is split into three small modules on purpose:
+
+- `parser.py`: the schema contract between a harness and the engine
+- `constraints.py`: deterministic feasibility and constraint reasoning
+- `ipog.py`: covering-array generation and coverage accounting
+
+That keeps the math isolated from OpenClaw, Hermes, Codex, xAI-backed agents, Claude Code, or any other harness wrapper.
+
+## CLI
+
+```bash
+# stdin-first, harness-friendly
+cat schema.json | lattice validate
+cat schema.json | lattice generate
+
+# file input is optional and useful for debugging
+lattice validate schema.yaml --format text
+lattice generate schema.yaml --strength 3 --format table
+lattice generate schema.yaml --strength 4 --progress --progress-every 25 > scenarios.json
+lattice generate schema.yaml --strength 4 --stop-after-coverage 84 > prefix.json
+
+# explicit machine-readable validation
+lattice validate schema.json --format json
+```
+
+Supported output formats:
+
+- `json`
+- `table`
+- `csv`
+- `summary`
+
+`generate` defaults to JSON because the primary consumer is usually a coding harness. File-based schemas are supported, but the schema file is transport, not the product surface.
+
+For long higher-strength runs, use `--progress` to stream coverage progress to
+stderr while keeping stdout clean for JSON, CSV, table, or summary output.
+`--progress-every N` controls how many generated scenarios pass between
+updates.
+
+Use `--stop-after-coverage PCT` for prefix runs that stop after the first
+generated scenario reaching that cumulative coverage percentage. Use
+`--max-rows N` for a fixed-size prefix. If both are set, generation stops at
+whichever limit is reached first. `--stop-after-coverage 100` is treated as a
+full run so rounded `100.0%` coverage near the tail does not skip final rows.
+
+## Model Features
+
+Lattice currently supports:
+
+- pairwise and t-way generation
+- JSON and YAML schema transport
+- `invalid_pair`
+- `bidirectional`
+- `forward_dep`
+- `conditional`
+- `forced`
+- `higher_order`
+- inline parameter `weights`
+- deterministic generation via `--seed`
+
+Model true impossibilities as constraints before generation. Do not strip
+constraints and mark impossible rows downstream: that changes the coverage
+surface from valid interactions to an unconstrained cross-product. Use
+`invalid_pair` for two assignments that cannot coexist and `higher_order` when
+the invalid rule needs multiple antecedents.
+
+`conditional` parameters are first-class schema features. The parser expands them into concrete parameter domains and the constraint engine enforces `N/A` semantics automatically.
+
+## Solver Notes
+
+The current engine is deterministic and self-contained. If `ortools` is installed via the `solver` extra, Lattice can use CP-SAT feasibility checks for partial assignments; otherwise it falls back to the built-in backtracking solver.
+
+Install in editable mode while developing:
+
+```bash
+python3 -m pip install -e /path/to/lattice
+```
+
+Install with the optional solver backend:
+
+```bash
+python3 -m pip install -e "/path/to/lattice[solver]"
+```
+
+## Using In Other Projects
+
+The normal workflow in another repo is:
+
+1. install Lattice once into the Python environment your harness uses
+2. have the harness emit a schema on stdin
+3. call `lattice validate`
+4. call `lattice generate`
+5. consume the JSON output inside the harness
+
+Example:
+
+```bash
+cat schema.json | lattice validate
+cat schema.json | lattice generate
+```
+
+If you want an agent such as OpenClaw, Hermes, Codex, an xAI-backed harness, Claude Code, or a custom local agent to use the same workflow in another repo, start with [docs/install.md](docs/install.md), then see [docs/using-in-other-projects.md](docs/using-in-other-projects.md).
+
+Scope each schema to the thing being worked on: the feature, service, workflow, component, rendering surface, template family, config matrix, or behavior slice under active design or test work.
+
+The shortest agent adoption path after install is:
+
+```bash
+lattice agent instructions
+lattice agent bootstrap
+lattice agent doctor
+```
+
+`instructions` works for any agent. `bootstrap` installs convenience skills only for known harnesses detected on the machine.
+
+## Harness Contract
+
+Lattice is intentionally narrow. A harness owns extraction and interpretation; Lattice owns schema validation and deterministic row generation.
+
+- plan synthesis: harness extracts schema from a plan, Lattice generates scenarios, harness strengthens the plan
+- test synthesis: harness extracts schema from code/tests, Lattice generates scenarios, harness writes missing tests
+- variant coverage: harness extracts component, template, or design-system variants, Lattice generates rows, harness renders screenshots, a contact sheet, or visual diffs
+- evaluator coverage: harness extracts a config or sandbox matrix, Lattice generates rows, harness runs each row through the relevant evaluator
+
+See [docs/agent-handoff.md](docs/agent-handoff.md) for the repository-level handoff shape.
+See [docs/workflows.md](docs/workflows.md) for concrete agent usage patterns.
+See [docs/case-studies.md](docs/case-studies.md) for public audit examples and the standard for how to write them up.
+See [docs/using-in-other-projects.md](docs/using-in-other-projects.md) for portable installation and adoption.
+See [docs/lattice-on-lattice.md](docs/lattice-on-lattice.md) for a worked example of Lattice testing its own agent bootstrap surface.
+
+## Skill
+
+This repo includes a repo-local Codex skill at `.codex/skills/lattice-workflow/`, bundled Codex and Claude Code skill resources, and a generic skill resource for any harness that accepts a `SKILL.md` directory.
+
+Use it when you want a coding harness to:
+
+- extract a schema from code, a spec, or a variant surface
+- validate the schema before generation
+- run Lattice deterministically
+- interpret the rows as design review scenarios, rendered variants, fixtures, or test cases
+
+## Examples
+
+The `examples/` directory contains eight end-to-end examples:
+
+- `plan-mode-saved-search`: plan -> schema -> generated scenarios
+- `test-mode-checkout`: code/test surface -> schema -> generated scenarios
+- `three-way-notifications`: strength-3 schema -> generated scenarios
+- `lattice-self-test`: Lattice generates a matrix for testing Lattice itself
+- `agent-bootstrap-matrix`: Lattice generates a matrix for testing agent skill bootstrap behavior
+- `schema-guidance-matrix`: Lattice generates a matrix for testing Lattice's schema discoverability guidance
+- `component-variant-matrix`: component/rendering surface -> schema -> generated visual review variants
+- `httpx-query-param-merge`: OSS audit example for a real HTTPX query-parameter interaction issue

lattice_cli-0.1.0/README.md

@@ -0,0 +1,201 @@
+# Lattice
+
+Say you're testing a checkout flow. Users are signed in or guest. They have a coupon or not. The cart is empty, single-item, or multi-item. Shipping is standard, express, or pickup. Payment is card, Apple Pay, or PayPal. The site renders in light or dark mode.
+
+Six knobs, a few settings each — 216 combinations. Real product surfaces have dozens of knobs and hundreds of thousands of combinations. And most production bugs are *interaction* bugs: the one where dark mode plus Apple Pay plus the new coupon breaks the order page, even though each piece works fine alone.
+
+Nobody writes tests for 216 combinations. Nobody can write tests for 200,000. So humans and coding agents alike pick a handful of cases by gut feel, and the interaction bug ships.
+
+Lattice is the way out. You list the knobs, the settings, and any rules ("Apple Pay isn't allowed for pickup orders"). Lattice gives back a short, deterministic list of scenarios that hits every *pair* of settings at least once. The six-knob example above collapses from 216 cases to about a dozen — enough to catch the overwhelming majority of interaction bugs without writing the universe.
+
+The math behind this is old. It's what Hexawise and similar tools have been selling for years. What's new here is the packaging: schema in on stdin, rows out on stdout, deterministic, built for a coding agent to call while planning a feature or writing tests. The agent describes the surface, Lattice does the combinatorics, the agent turns each row into a test, a rendered screenshot, a fixture, or a step of plan review.
+
+## What this unlocks
+
+**Pre-code planning.** An agent given a feature spec writes a plan that looks careful and treats interactions as an afterthought. Modeling the surface as a Lattice schema first — parameters, values, constraints — changes the plan. The agent isn't picking edges by gut feel; it has a deterministic list of combinations the design has to handle. Spec gaps surface during modeling, when they're still cheap to address, instead of during the first incident.
+
+**Writing tests.** The failure mode isn't undertesting. Agents will happily generate fifty tests — overmocked, all hitting the same happy path, and on the next run, silently rewritten when one fails. An [empirical study](https://arxiv.org/abs/2602.00409) of 1.2M commits found agents add mocks at nearly 1.4x the human rate and reach almost exclusively for the basic `mock` primitive where humans spread across fakes, spies, and stubs. The rewrite-instead-of-fix instinct shows up in the [Claude Code issue tracker](https://github.com/anthropics/claude-code/issues/51856) under the name *fix-fail-propose-new-fix*: a fix breaks the live app, the unit suite still passes, so the agent files the symptoms as new bugs and proposes more fixes instead of reverting. The pattern is structural — it follows from handing an agent unilateral write access to the assertion it has to pass — not a quirk of any specific model.
+
+Lattice doesn't solve the temptation; it removes the choice. The schema dictates the matrix. The rows dictate the assertions. An unsatisfied row is a case the design has to answer for — not a test to delete.
+
+Same loop in both places: the agent describes the surface, Lattice does the combinatorics, the agent reasons over the rows. The schema is cheap. The coverage is defensible.
+
+## How it goes
+
+1. The agent writes a small JSON or YAML schema: parameters, values, constraints.
+2. Pipe it to `lattice generate`.
+3. Lattice returns the covering rows. Same schema and seed always produce the same rows.
+4. The agent maps each row to whatever it's evaluating — a test, a render, a fixture, a sandbox call.
+
+The schema is the contract between agent and engine. The rows are the product. Lattice does not care whether the surface is a backend feature, an API, a state machine, a Rails partial, a design-system component, an email template, a config matrix, or a data-model slice — if it has dimensions, values, rules, and an evaluator, Lattice can cover it.
+
+Project status: experimental `0.1`. The CLI and agent skill bootstrap path work; the schema contract may still evolve as the project finds its first users.
+
+## Install For Agents
+
+Start with [docs/install.md](docs/install.md) when you want any coding agent or harness to adopt Lattice.
+
+That page covers:
+
+- installing the `lattice` CLI with `pipx`, `uvx`, or `pip`
+- printing universal instructions with `lattice agent instructions`
+- installing a generic `lattice-workflow` skill into any harness directory with `lattice agent install-skill <target>`
+- installing Codex and Claude Code convenience skills with `lattice agent bootstrap`
+- adding an agent memory for when to reach for Lattice
+- running a smoke test over stdin
+
+## Why This Shape
+
+Lattice is split into three small modules on purpose:
+
+- `parser.py`: the schema contract between a harness and the engine
+- `constraints.py`: deterministic feasibility and constraint reasoning
+- `ipog.py`: covering-array generation and coverage accounting
+
+That keeps the math isolated from OpenClaw, Hermes, Codex, xAI-backed agents, Claude Code, or any other harness wrapper.
+
+## CLI
+
+```bash
+# stdin-first, harness-friendly
+cat schema.json | lattice validate
+cat schema.json | lattice generate
+
+# file input is optional and useful for debugging
+lattice validate schema.yaml --format text
+lattice generate schema.yaml --strength 3 --format table
+lattice generate schema.yaml --strength 4 --progress --progress-every 25 > scenarios.json
+lattice generate schema.yaml --strength 4 --stop-after-coverage 84 > prefix.json
+
+# explicit machine-readable validation
+lattice validate schema.json --format json
+```
+
+Supported output formats:
+
+- `json`
+- `table`
+- `csv`
+- `summary`
+
+`generate` defaults to JSON because the primary consumer is usually a coding harness. File-based schemas are supported, but the schema file is transport, not the product surface.
+
+For long higher-strength runs, use `--progress` to stream coverage progress to
+stderr while keeping stdout clean for JSON, CSV, table, or summary output.
+`--progress-every N` controls how many generated scenarios pass between
+updates.
+
+Use `--stop-after-coverage PCT` for prefix runs that stop after the first
+generated scenario reaching that cumulative coverage percentage. Use
+`--max-rows N` for a fixed-size prefix. If both are set, generation stops at
+whichever limit is reached first. `--stop-after-coverage 100` is treated as a
+full run so rounded `100.0%` coverage near the tail does not skip final rows.
+
+## Model Features
+
+Lattice currently supports:
+
+- pairwise and t-way generation
+- JSON and YAML schema transport
+- `invalid_pair`
+- `bidirectional`
+- `forward_dep`
+- `conditional`
+- `forced`
+- `higher_order`
+- inline parameter `weights`
+- deterministic generation via `--seed`
+
+Model true impossibilities as constraints before generation. Do not strip
+constraints and mark impossible rows downstream: that changes the coverage
+surface from valid interactions to an unconstrained cross-product. Use
+`invalid_pair` for two assignments that cannot coexist and `higher_order` when
+the invalid rule needs multiple antecedents.
+
+`conditional` parameters are first-class schema features. The parser expands them into concrete parameter domains and the constraint engine enforces `N/A` semantics automatically.
+
+## Solver Notes
+
+The current engine is deterministic and self-contained. If `ortools` is installed via the `solver` extra, Lattice can use CP-SAT feasibility checks for partial assignments; otherwise it falls back to the built-in backtracking solver.
+
+Install in editable mode while developing:
+
+```bash
+python3 -m pip install -e /path/to/lattice
+```
+
+Install with the optional solver backend:
+
+```bash
+python3 -m pip install -e "/path/to/lattice[solver]"
+```
+
+## Using In Other Projects
+
+The normal workflow in another repo is:
+
+1. install Lattice once into the Python environment your harness uses
+2. have the harness emit a schema on stdin
+3. call `lattice validate`
+4. call `lattice generate`
+5. consume the JSON output inside the harness
+
+Example:
+
+```bash
+cat schema.json | lattice validate
+cat schema.json | lattice generate
+```
+
+If you want an agent such as OpenClaw, Hermes, Codex, an xAI-backed harness, Claude Code, or a custom local agent to use the same workflow in another repo, start with [docs/install.md](docs/install.md), then see [docs/using-in-other-projects.md](docs/using-in-other-projects.md).
+
+Scope each schema to the thing being worked on: the feature, service, workflow, component, rendering surface, template family, config matrix, or behavior slice under active design or test work.
+
+The shortest agent adoption path after install is:
+
+```bash
+lattice agent instructions
+lattice agent bootstrap
+lattice agent doctor
+```
+
+`instructions` works for any agent. `bootstrap` installs convenience skills only for known harnesses detected on the machine.
+
+## Harness Contract
+
+Lattice is intentionally narrow. A harness owns extraction and interpretation; Lattice owns schema validation and deterministic row generation.
+
+- plan synthesis: harness extracts schema from a plan, Lattice generates scenarios, harness strengthens the plan
+- test synthesis: harness extracts schema from code/tests, Lattice generates scenarios, harness writes missing tests
+- variant coverage: harness extracts component, template, or design-system variants, Lattice generates rows, harness renders screenshots, a contact sheet, or visual diffs
+- evaluator coverage: harness extracts a config or sandbox matrix, Lattice generates rows, harness runs each row through the relevant evaluator
+
+See [docs/agent-handoff.md](docs/agent-handoff.md) for the repository-level handoff shape.
+See [docs/workflows.md](docs/workflows.md) for concrete agent usage patterns.
+See [docs/case-studies.md](docs/case-studies.md) for public audit examples and the standard for how to write them up.
+See [docs/using-in-other-projects.md](docs/using-in-other-projects.md) for portable installation and adoption.
+See [docs/lattice-on-lattice.md](docs/lattice-on-lattice.md) for a worked example of Lattice testing its own agent bootstrap surface.
+
+## Skill
+
+This repo includes a repo-local Codex skill at `.codex/skills/lattice-workflow/`, bundled Codex and Claude Code skill resources, and a generic skill resource for any harness that accepts a `SKILL.md` directory.
+
+Use it when you want a coding harness to:
+
+- extract a schema from code, a spec, or a variant surface
+- validate the schema before generation
+- run Lattice deterministically
+- interpret the rows as design review scenarios, rendered variants, fixtures, or test cases
+
+## Examples
+
+The `examples/` directory contains eight end-to-end examples:
+
+- `plan-mode-saved-search`: plan -> schema -> generated scenarios
+- `test-mode-checkout`: code/test surface -> schema -> generated scenarios
+- `three-way-notifications`: strength-3 schema -> generated scenarios
+- `lattice-self-test`: Lattice generates a matrix for testing Lattice itself
+- `agent-bootstrap-matrix`: Lattice generates a matrix for testing agent skill bootstrap behavior
+- `schema-guidance-matrix`: Lattice generates a matrix for testing Lattice's schema discoverability guidance
+- `component-variant-matrix`: component/rendering surface -> schema -> generated visual review variants
+- `httpx-query-param-merge`: OSS audit example for a real HTTPX query-parameter interaction issue