latticerb 0.4.0-aarch64-linux

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (32) hide show
  1. checksums.yaml +7 -0
  2. data/LICENSE +176 -0
  3. data/README.md +163 -0
  4. data/exe/lattice +7 -0
  5. data/ext/lattice_native/rustfmt.toml +1 -0
  6. data/lib/lattice/3.2/lattice_native.so +0 -0
  7. data/lib/lattice/3.3/lattice_native.so +0 -0
  8. data/lib/lattice/3.4/lattice_native.so +0 -0
  9. data/lib/lattice/4.0/lattice_native.so +0 -0
  10. data/lib/lattice/agent.rb +204 -0
  11. data/lib/lattice/cli.rb +469 -0
  12. data/lib/lattice/constraints.rb +265 -0
  13. data/lib/lattice/formatters.rb +193 -0
  14. data/lib/lattice/ipog.rb +103 -0
  15. data/lib/lattice/model.rb +83 -0
  16. data/lib/lattice/native.rb +10 -0
  17. data/lib/lattice/parser.rb +427 -0
  18. data/lib/lattice/resources/claude/lattice-workflow/SKILL.md +144 -0
  19. data/lib/lattice/resources/claude/lattice-workflow/references/modeling-rules.md +52 -0
  20. data/lib/lattice/resources/claude/lattice-workflow/references/worked-examples.md +59 -0
  21. data/lib/lattice/resources/codex/lattice-workflow/SKILL.md +144 -0
  22. data/lib/lattice/resources/codex/lattice-workflow/agents/openai.yaml +7 -0
  23. data/lib/lattice/resources/codex/lattice-workflow/references/modeling-rules.md +52 -0
  24. data/lib/lattice/resources/codex/lattice-workflow/references/worked-examples.md +59 -0
  25. data/lib/lattice/resources/generic/lattice-workflow/SKILL.md +152 -0
  26. data/lib/lattice/resources/generic/lattice-workflow/references/modeling-rules.md +52 -0
  27. data/lib/lattice/resources/generic/lattice-workflow/references/worked-examples.md +59 -0
  28. data/lib/lattice/schema_text.rb +153 -0
  29. data/lib/lattice/version.rb +5 -0
  30. data/lib/lattice.rb +88 -0
  31. data/lib/latticerb.rb +4 -0
  32. metadata +99 -0
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: f760c7c8c0720ffbf602d4adc15e94ddef258f6c17d2edc3f56fa285f5853215
4
+ data.tar.gz: fd4ec065fc4ba82f36d6b2dcd7ae9c024775574786046e77167ffed3788d4ba8
5
+ SHA512:
6
+ metadata.gz: 1c0bebac121265f79fcf4a02246bd70af1b3838ba2c3cef7f10072e1280e54429ba105bfeb05e0566acff3f0fe9db6839ba378793f180d348d38a0ad19e8fad2
7
+ data.tar.gz: d412e640d3c4111ad0819ed0337af2eb392f3166d8b7d68eea3be17d22962aff4f58587a331bd04d6be639975f9cd71fa8ae7b87068139e2b469678b0d251e3c
data/LICENSE ADDED
@@ -0,0 +1,176 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
data/README.md ADDED
@@ -0,0 +1,163 @@
1
+ # Lattice (Ruby)
2
+
3
+ Deterministic combinatorial coverage for constrained variant surfaces — roles, permissions, feature flags, modes, providers, optional fields, component props, config matrices — as a Ruby library and CLI.
4
+
5
+ Lattice takes a schema of parameters, values, and constraints and generates a minimal covering array: the smallest practical set of scenarios in which every valid pair (or triple, at strength 3) of values appears at least once. Constraints are honored during generation, so no scenario is ever invalid.
6
+
7
+ This is the Ruby package of [Lattice](https://github.com/tylerklose/lattice) ([lattice-cli on PyPI](https://pypi.org/project/lattice-cli/)). Both packages generate scenarios with the same Rust engine, so they give **byte-identical output** for the same schema, seed and pool size. The test suite checks that by running both and comparing their output. Use whichever runtime your project already has.
8
+
9
+ ## Install
10
+
11
+ ```ruby
12
+ # Gemfile
13
+ gem "latticerb"
14
+ ```
15
+
16
+ or standalone:
17
+
18
+ ```bash
19
+ gem install latticerb
20
+ ```
21
+
22
+ The gem ships precompiled for macOS (Apple Silicon and Intel), Linux (x86-64 and ARM64, glibc and musl) and Windows (x86-64). On other platforms it compiles the engine on install, which needs a Rust toolchain. JRuby isn't supported, because it can't load native extensions. If your Gemfile.lock was created on a Mac and you deploy to Linux, add the platform once: `bundle lock --add-platform x86_64-linux`.
23
+
24
+ ## Library usage
25
+
26
+ The primary API is designed for test suites:
27
+
28
+ ```ruby
29
+ require "lattice"
30
+
31
+ run = Lattice.generate(file: "spec/fixtures/checkout.yaml")
32
+
33
+ run.scenarios.each do |scenario|
34
+ # { "payment_method" => "credit_card", "region" => "US", "card_type" => "visa", ... }
35
+ it "checks out with #{scenario.values.join(', ')}" do
36
+ # drive the flow with scenario values
37
+ end
38
+ end
39
+ ```
40
+
41
+ Schemas can also be inline Hashes or YAML/JSON strings:
42
+
43
+ ```ruby
44
+ run = Lattice.generate(
45
+ "parameters" => {
46
+ "role" => %w[admin member guest],
47
+ "plan" => %w[free pro enterprise],
48
+ "beta_flag" => %w[on off]
49
+ },
50
+ "constraints" => [
51
+ { "type" => "invalid_pair",
52
+ "if" => { "parameter" => "role", "value" => "guest" },
53
+ "then_not" => { "parameter" => "plan", "value" => "enterprise" } }
54
+ ]
55
+ )
56
+
57
+ run.scenarios # array of { name => value } hashes
58
+ run.coverage_curve # cumulative coverage per scenario
59
+ run.to_table # human-readable table (also: to_json_output, to_yaml_output, to_csv, to_summary)
60
+
61
+ Lattice.scenarios(file: "...") # shortcut straight to the hashes
62
+ Lattice.validate!(schema) # raises Lattice::ValidationError / Lattice::ConstraintError
63
+ ```
64
+
65
+ Generation options: `strength:` (default 2 = pairwise), `seed:` (default 42), `pool_size:` (candidate rows per step, default 16), `max_rows:`, `stop_after_coverage:`.
66
+
67
+ ## CLI usage
68
+
69
+ The gem installs a `lattice` executable mirroring the Python CLI:
70
+
71
+ ```bash
72
+ cat schema.yaml | lattice validate
73
+ cat schema.yaml | lattice generate # JSON by default
74
+ lattice generate schema.yaml --format table
75
+ lattice generate schema.yaml --format yaml # same content as JSON, for hand-edited files
76
+ lattice generate schema.yaml --strength 3 --seed 7
77
+ lattice agent instructions # coding-agent integration guidance
78
+ ```
79
+
80
+ ## Schema format
81
+
82
+ ```yaml
83
+ model_name: checkout
84
+ strength: 2
85
+ parameters:
86
+ payment_method: [credit_card, paypal, apple_pay]
87
+ region: [US, UK, DE]
88
+ browser:
89
+ values: [chrome, safari, firefox]
90
+ weights: [0.6, 0.3, 0.1]
91
+ constraints:
92
+ - type: invalid_pair
93
+ if: { parameter: payment_method, value: apple_pay }
94
+ then_not: { parameter: browser, value: firefox }
95
+ - type: conditional
96
+ parameter: card_type
97
+ values: [visa, mastercard]
98
+ parent: payment_method
99
+ applies_when: [credit_card]
100
+ ```
101
+
102
+ Constraint types: `invalid_pair`, `higher_order`, `forward_dep`, `bidirectional`, `conditional`, `forced`. Every constraint needs a `type` key. Run `lattice agent instructions` for an example of each type.
103
+
104
+ ### Values keep their text
105
+
106
+ Every value in a schema (the model name, parameter names and values, and constraint references) is used exactly as written. In YAML, unquoted `1.10`, `0x1F`, `.inf` or `2026-10-26T10:00:00Z` stay as typed rather than being turned into numbers or dates. The exceptions:
107
+
108
+ - Unquoted `yes`, `no`, `on`, `off`, `true` and `false` (lowercase, Capitalized or UPPERCASE) become `true` / `false`, and an empty value, `~` or `null` becomes `null`. Quote them (`"yes"`) to keep the word.
109
+ - JSON integers are written in plain decimal form (`-0` becomes `0`).
110
+
111
+ `strength` must be a whole number, and `weights` decimal numbers such as `0.7` or `1e-3`. Anchors, aliases and `<<` merge keys work; a key written twice, more than one YAML document, or a tag other than YAML's standard ones is an error.
112
+
113
+ Changed in 0.3.0: earlier versions converted unquoted numbers and dates, so `0x1F` became `31`, `1.10` became `1.1`, and some values (`.inf`, timestamps) came out differently in the Ruby and Python implementations.
114
+
115
+ ## Performance
116
+
117
+ Generation runs in a Rust engine (the `lattice-engine` crate), in two phases:
118
+
119
+ 1. **Build.** Rows are added greedily. Each row is the best of several candidates (`pool_size:`, default 16), and each candidate picks, value by value, whatever covers the most combinations still uncovered.
120
+ 2. **Shrink.** A row is removed and the gaps are repaired with tabu search, which changes values in the remaining rows without breaking any constraint or forced combination. This repeats while repairs succeed within a fixed step budget.
121
+
122
+ The budget is a number of steps, not a time limit, so the same schema and seed give the same rows on every machine. The rows come out ordered so each adds the most new coverage, which is why `max_rows:` and `stop_after_coverage:` cut the set short with as much coverage as possible.
123
+
124
+ Scenario counts against [PICT](https://github.com/microsoft/pict) 3.7, with default settings for both:
125
+
126
+ | Model | PICT | Lattice 0.4 | Lattice 0.3 |
127
+ |---|---|---|---|
128
+ | 13 parameters × 3 values | 20 | **15** (best known) | 22 |
129
+ | 100 × 2 | 16 | **10** (optimal) | over 60 s |
130
+ | 61 mixed (4^15 3^17 2^29) | 40 | **30** | over 60 s |
131
+ | 12 × 6 | 70 | **60** | 88 (32 s) |
132
+ | 30 × 5 | 66 | **55** | over 60 s |
133
+ | 20 × 10 | 218 | **192** | over 60 s |
134
+ | Strength 3, 10 × 4 | 158 | **140** | 176 (27 s) |
135
+
136
+ Each Lattice 0.4 run above takes 0.04–1.2 s on an Apple M-series laptop. PICT is faster (about 0.02 s) because it stops after the build phase.
137
+
138
+ Changed in 0.4.0: rows differ from 0.3.x for the same seed, and every example needs the same number of scenarios or fewer. `pool_size:` now sets the candidates per row; its default went from 50 to 16.
139
+
140
+ ## Parity with the Python implementation
141
+
142
+ Both packages parse schemas in their own language and hand the engine the same compiled constraints (`ConstraintEngine#engine_constraints` here, `lattice.ipog` in Python), so the engine gets identical input. `test/python_parity_test.rb` shells out to the Python implementation (checkout via `LATTICE_PYTHON_SRC`, or an installed `lattice-cli`) and asserts byte-equal output across formats, seeds, strengths and stopping rules; it skips when no Python implementation is available.
143
+
144
+ Schemas are read with Psych here and PyYAML in Python, but both implementations build values from the parsed text with the same rules (see "Values keep their text"), so a schema means the same thing in either. `test/fixtures/scalar_text.*` pins those rules for both.
145
+
146
+ ## Development
147
+
148
+ Building the extension needs a Rust toolchain (`rustup`); the engine comes from crates.io (`lattice-engine`).
149
+
150
+ ```bash
151
+ bundle install
152
+ bundle exec rake compile # builds lib/lattice/lattice_native
153
+ bundle exec rake test # unit, golden-parity, and live Python-parity suites (compiles first)
154
+ bundle exec mutant run # mutation testing (see docs/mutation-testing.md)
155
+ ```
156
+
157
+ Golden fixtures are authored by the reference Python implementation; regenerate
158
+ them with `ruby test/support/generate_goldens.rb` after intentional behavior
159
+ changes (requires the Python checkout, see the script header).
160
+
161
+ ## License
162
+
163
+ Apache-2.0
data/exe/lattice ADDED
@@ -0,0 +1,7 @@
1
+ #!/usr/bin/env ruby
2
+ # frozen_string_literal: true
3
+
4
+ require "lattice"
5
+ require "lattice/cli"
6
+
7
+ exit Lattice::CLI.main(ARGV)
@@ -0,0 +1 @@
1
+ max_width = 120
Binary file
Binary file
Binary file
Binary file
@@ -0,0 +1,204 @@
1
+ # frozen_string_literal: true
2
+
3
+ require "fileutils"
4
+
5
+ module Lattice
6
+ module Agent
7
+ SKILL_NAME = "lattice-workflow"
8
+
9
+ MEMORY_SNIPPET =
10
+ "Reach for Lattice when planning, testing, or reviewing a finite constrained surface " \
11
+ "with interacting states such as roles, permissions, feature flags, modes, providers, " \
12
+ "optional fields, component props, rendering branches, template variants, config " \
13
+ "matrices, lifecycle states, or cross-product edge cases. Extract a schema with " \
14
+ "parameters, values, and true constraints; run `lattice validate`; then run " \
15
+ "`lattice generate`; use the generated rows as the source of truth for plan review, " \
16
+ "rendered variants, fixtures, or missing tests instead of hand-enumerating pairwise " \
17
+ "combinations."
18
+
19
+ DEFAULT_PROMPT =
20
+ "Use $lattice-workflow. Inspect this feature, test surface, component variant space, " \
21
+ "template, or config matrix; extract a Lattice schema; validate it; generate pairwise " \
22
+ "rows; and use the rows to strengthen the plan, tests, fixtures, or visual review."
23
+
24
+ SCHEMA_REFERENCE = <<~REFERENCE
25
+
26
+ Schema format, with one example of each constraint type:
27
+
28
+ ```yaml
29
+ model_name: checkout
30
+ strength: 2
31
+ parameters:
32
+ user: [guest, member]
33
+ payment: [card, paypal, apple_pay, invoice]
34
+ device: [desktop, ios, android]
35
+ region: [us, eu]
36
+ currency: [usd, eur]
37
+ shipping: [standard, express, pickup]
38
+ constraints:
39
+ # invalid_pair: these two assignments never appear in the same row.
40
+ - type: invalid_pair
41
+ if: { parameter: payment, value: apple_pay }
42
+ then_not: { parameter: device, value: android }
43
+ # bidirectional: each assignment requires the other.
44
+ - type: bidirectional
45
+ pair:
46
+ - { parameter: region, value: eu }
47
+ - { parameter: currency, value: eur }
48
+ # forward_dep: the source requires the target; the target may appear elsewhere.
49
+ - type: forward_dep
50
+ source: { parameter: shipping, value: pickup }
51
+ target: { parameter: region, value: us }
52
+ # conditional: defines a child parameter that only applies for some parent values.
53
+ - type: conditional
54
+ parameter: card_type
55
+ values: [visa, mastercard]
56
+ parent: payment
57
+ applies_when: [card]
58
+ # forced: this combination must appear in at least one row.
59
+ - type: forced
60
+ assignments:
61
+ - { parameter: user, value: guest }
62
+ - { parameter: device, value: ios }
63
+ - { parameter: shipping, value: express }
64
+ # higher_order: the last assignment is excluded only when all of if_all hold.
65
+ - type: higher_order
66
+ if_all:
67
+ - { parameter: user, value: guest }
68
+ - { parameter: region, value: eu }
69
+ then_not: { parameter: shipping, value: pickup }
70
+ ```
71
+
72
+ Every constraint needs a `type` key. Each assignment is `{ parameter: <name>, value: <value> }`.
73
+ REFERENCE
74
+
75
+ GENERIC_AGENT_INSTRUCTIONS = <<~INSTRUCTIONS + SCHEMA_REFERENCE
76
+ # Lattice Agent Instructions
77
+
78
+ Lattice is harness-agnostic. Use these instructions in OpenClaw, Hermes, Codex, xAI-backed agents, Claude Code, or any agent that can run shell commands.
79
+
80
+ Memory:
81
+ #{MEMORY_SNIPPET}
82
+
83
+ Default prompt:
84
+ #{DEFAULT_PROMPT}
85
+
86
+ Workflow:
87
+ 1. Check whether `lattice --help` works.
88
+ 2. Extract one coherent schema with parameters, values, and true constraints.
89
+ 3. Encode nonsensical or impossible combinations as constraints. Do not strip constraints and mark invalid rows after generation. Lattice supports exclusion-style constraints such as `invalid_pair` and `higher_order`, not only `conditional` parameters.
90
+ 4. Run `lattice validate` before generation.
91
+ 5. Run `lattice generate` and treat the generated rows as the source of truth.
92
+ 6. Map rows to the active evaluator: plan review, tests, fixtures, rendered variants, screenshots, visual diffs, sandbox calls, or another harness-specific action.
93
+
94
+ Prefer JSON or YAML on stdin:
95
+
96
+ ```bash
97
+ cat schema.json | lattice validate
98
+ cat schema.json | lattice generate
99
+ ```
100
+ INSTRUCTIONS
101
+
102
+ AgentSetup = Data.define(:surface, :skill_name, :skill_path, :memory, :default_prompt) do
103
+ def to_json_payload
104
+ {
105
+ "surface" => surface,
106
+ "skill_name" => skill_name,
107
+ "skill_path" => skill_path.to_s,
108
+ "memory" => memory,
109
+ "default_prompt" => default_prompt
110
+ }
111
+ end
112
+ end
113
+
114
+ extend self
115
+
116
+ def default_codex_skill_path
117
+ codex_home = ENV.fetch("CODEX_HOME", nil)
118
+ base = codex_home && !codex_home.empty? ? File.expand_path(codex_home) : File.join(Dir.home, ".codex")
119
+ File.join(base, "skills", SKILL_NAME)
120
+ end
121
+
122
+ def default_claude_skill_path
123
+ File.join(Dir.home, ".claude", "skills", SKILL_NAME)
124
+ end
125
+
126
+ def codex_available?
127
+ !which("codex").nil? ||
128
+ File.exist?(File.join(Dir.home, ".codex")) ||
129
+ !ENV.fetch("CODEX_HOME", "").empty?
130
+ end
131
+
132
+ def claude_code_available?
133
+ !which("claude").nil? || File.exist?(File.join(Dir.home, ".claude"))
134
+ end
135
+
136
+ def install_codex_skill(target = nil)
137
+ destination = target ? File.expand_path(target) : default_codex_skill_path
138
+ copy_bundled_skill("codex", destination)
139
+ AgentSetup.new(
140
+ surface: "codex",
141
+ skill_name: SKILL_NAME,
142
+ skill_path: destination,
143
+ memory: MEMORY_SNIPPET,
144
+ default_prompt: DEFAULT_PROMPT
145
+ )
146
+ end
147
+
148
+ def install_generic_skill(target)
149
+ destination = File.expand_path(target)
150
+ copy_bundled_skill("generic", destination)
151
+ AgentSetup.new(
152
+ surface: "generic",
153
+ skill_name: SKILL_NAME,
154
+ skill_path: destination,
155
+ memory: MEMORY_SNIPPET,
156
+ default_prompt: DEFAULT_PROMPT
157
+ )
158
+ end
159
+
160
+ def install_claude_skill(target = nil, force: false)
161
+ if !force && !claude_code_available?
162
+ raise "Claude Code was not detected. Re-run with --force to install anyway."
163
+ end
164
+
165
+ destination = target ? File.expand_path(target) : default_claude_skill_path
166
+ copy_bundled_skill("claude", destination)
167
+ AgentSetup.new(
168
+ surface: "claude-code",
169
+ skill_name: SKILL_NAME,
170
+ skill_path: destination,
171
+ memory: MEMORY_SNIPPET,
172
+ default_prompt: DEFAULT_PROMPT
173
+ )
174
+ end
175
+
176
+ def codex_skill_installed?(target = nil)
177
+ destination = target ? File.expand_path(target) : default_codex_skill_path
178
+ File.file?(File.join(destination, "SKILL.md"))
179
+ end
180
+
181
+ def claude_skill_installed?(target = nil)
182
+ destination = target ? File.expand_path(target) : default_claude_skill_path
183
+ File.file?(File.join(destination, "SKILL.md"))
184
+ end
185
+
186
+ def copy_bundled_skill(resource_name, destination)
187
+ source = File.join(__dir__, "resources", resource_name, SKILL_NAME)
188
+ unless File.directory?(source)
189
+ raise "Bundled #{resource_name} skill `#{SKILL_NAME}` was not found."
190
+ end
191
+
192
+ FileUtils.mkdir_p(destination)
193
+ FileUtils.cp_r(File.join(source, "."), destination)
194
+ end
195
+
196
+ def which(command)
197
+ ENV.fetch("PATH", "").split(File::PATH_SEPARATOR).each do |directory|
198
+ candidate = File.join(directory, command)
199
+ return candidate if File.file?(candidate) && File.executable?(candidate)
200
+ end
201
+ nil
202
+ end
203
+ end
204
+ end