Olyder 0.5.0b1__tar.gz

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 (80) hide show
  1. olyder-0.5.0b1/CHANGELOG.md +40 -0
  2. olyder-0.5.0b1/LICENSE +202 -0
  3. olyder-0.5.0b1/MANIFEST.in +8 -0
  4. olyder-0.5.0b1/PKG-INFO +157 -0
  5. olyder-0.5.0b1/README.md +123 -0
  6. olyder-0.5.0b1/pyproject.toml +50 -0
  7. olyder-0.5.0b1/setup.cfg +4 -0
  8. olyder-0.5.0b1/src/Olyder.egg-info/PKG-INFO +157 -0
  9. olyder-0.5.0b1/src/Olyder.egg-info/SOURCES.txt +78 -0
  10. olyder-0.5.0b1/src/Olyder.egg-info/dependency_links.txt +1 -0
  11. olyder-0.5.0b1/src/Olyder.egg-info/entry_points.txt +2 -0
  12. olyder-0.5.0b1/src/Olyder.egg-info/requires.txt +10 -0
  13. olyder-0.5.0b1/src/Olyder.egg-info/top_level.txt +1 -0
  14. olyder-0.5.0b1/src/olyder/__init__.py +2 -0
  15. olyder-0.5.0b1/src/olyder/__main__.py +3 -0
  16. olyder-0.5.0b1/src/olyder/accounting.py +130 -0
  17. olyder-0.5.0b1/src/olyder/acp_bridge.py +157 -0
  18. olyder-0.5.0b1/src/olyder/adapters.py +142 -0
  19. olyder-0.5.0b1/src/olyder/agents.py +130 -0
  20. olyder-0.5.0b1/src/olyder/analysis.py +57 -0
  21. olyder-0.5.0b1/src/olyder/api.py +68 -0
  22. olyder-0.5.0b1/src/olyder/backends.py +82 -0
  23. olyder-0.5.0b1/src/olyder/benchmark.py +119 -0
  24. olyder-0.5.0b1/src/olyder/checks.py +232 -0
  25. olyder-0.5.0b1/src/olyder/cli.py +249 -0
  26. olyder-0.5.0b1/src/olyder/config.py +197 -0
  27. olyder-0.5.0b1/src/olyder/contracts.py +50 -0
  28. olyder-0.5.0b1/src/olyder/control.py +55 -0
  29. olyder-0.5.0b1/src/olyder/data/SKILL.md +21 -0
  30. olyder-0.5.0b1/src/olyder/demo.py +34 -0
  31. olyder-0.5.0b1/src/olyder/diagnostics.py +27 -0
  32. olyder-0.5.0b1/src/olyder/engine.py +319 -0
  33. olyder-0.5.0b1/src/olyder/execution.py +152 -0
  34. olyder-0.5.0b1/src/olyder/idea.py +32 -0
  35. olyder-0.5.0b1/src/olyder/impact.py +40 -0
  36. olyder-0.5.0b1/src/olyder/integrity.py +148 -0
  37. olyder-0.5.0b1/src/olyder/interfaces.py +60 -0
  38. olyder-0.5.0b1/src/olyder/ledger.py +159 -0
  39. olyder-0.5.0b1/src/olyder/mcp.py +114 -0
  40. olyder-0.5.0b1/src/olyder/models.py +127 -0
  41. olyder-0.5.0b1/src/olyder/plugins.py +63 -0
  42. olyder-0.5.0b1/src/olyder/policy.py +32 -0
  43. olyder-0.5.0b1/src/olyder/privacy.py +35 -0
  44. olyder-0.5.0b1/src/olyder/quota.py +74 -0
  45. olyder-0.5.0b1/src/olyder/report.py +56 -0
  46. olyder-0.5.0b1/src/olyder/research.py +59 -0
  47. olyder-0.5.0b1/src/olyder/sdk.py +482 -0
  48. olyder-0.5.0b1/src/olyder/skill_install.py +85 -0
  49. olyder-0.5.0b1/src/olyder/state.py +155 -0
  50. olyder-0.5.0b1/src/olyder/workspace.py +318 -0
  51. olyder-0.5.0b1/tests/test_99_scenarios.py +477 -0
  52. olyder-0.5.0b1/tests/test_acp_bridge.py +155 -0
  53. olyder-0.5.0b1/tests/test_analysis_budget.py +46 -0
  54. olyder-0.5.0b1/tests/test_benchmark.py +17 -0
  55. olyder-0.5.0b1/tests/test_core.py +247 -0
  56. olyder-0.5.0b1/tests/test_docker_live.py +51 -0
  57. olyder-0.5.0b1/tests/test_enhancement_probes.py +228 -0
  58. olyder-0.5.0b1/tests/test_execution_credentials.py +54 -0
  59. olyder-0.5.0b1/tests/test_first_run.py +73 -0
  60. olyder-0.5.0b1/tests/test_impact_recovery.py +69 -0
  61. olyder-0.5.0b1/tests/test_integrations.py +120 -0
  62. olyder-0.5.0b1/tests/test_interoperability_diagnostics.py +28 -0
  63. olyder-0.5.0b1/tests/test_live_browser.py +32 -0
  64. olyder-0.5.0b1/tests/test_mcp_hardening.py +81 -0
  65. olyder-0.5.0b1/tests/test_protected_workspace.py +73 -0
  66. olyder-0.5.0b1/tests/test_regressions_99.py +98 -0
  67. olyder-0.5.0b1/tests/test_release_metadata.py +37 -0
  68. olyder-0.5.0b1/tests/test_runtime_resources.py +70 -0
  69. olyder-0.5.0b1/tests/test_sdk.py +109 -0
  70. olyder-0.5.0b1/tests/test_skill_global_setup.py +84 -0
  71. olyder-0.5.0b1/tests/test_skill_quick_setup.py +53 -0
  72. olyder-0.5.0b1/tests/test_universal_adapters.py +57 -0
  73. olyder-0.5.0b1/tests/test_universal_review.py +98 -0
  74. olyder-0.5.0b1/tests/test_universal_review_followup.py +90 -0
  75. olyder-0.5.0b1/tests/test_universal_security.py +96 -0
  76. olyder-0.5.0b1/tests/test_v04.py +223 -0
  77. olyder-0.5.0b1/tests/test_v05_ledger.py +100 -0
  78. olyder-0.5.0b1/tests/test_v05_policy.py +39 -0
  79. olyder-0.5.0b1/tests/test_v05_verdict.py +163 -0
  80. olyder-0.5.0b1/tests/test_verified_harness.py +258 -0
@@ -0,0 +1,40 @@
1
+ # Changelog
2
+
3
+ ## 0.5.0b1 — first PyPI beta candidate (pending owner approval)
4
+
5
+ - Package metadata uses the public name **Olyder**. Install with `pip install olyder` after publication.
6
+ - Offline pass/fail demo with real verification reports, exercised from the built wheel.
7
+ - Antigravity setup guide and a GitHub Actions starter with verdict summaries
8
+ and downloadable acceptance evidence.
9
+ - Protected test inputs reject new conventional acceptance files and preserve root pytest configuration.
10
+ - Managed subprocesses and Chromium exclude Olyder's verifier and local API tokens.
11
+ - One-command editor skill setup, including project and global native skill
12
+ locations, conflict-safe repeated installs, and correct `description` metadata.
13
+ - GitHub Actions builds/checks wheel and sdist and clean-installs the wheel
14
+ across Windows, Ubuntu and macOS.
15
+ - Release-tag and version consistency validation, content/secret checks,
16
+ and PyPI Trusted Publishing through an approval-gated GitHub environment.
17
+ - All previously documented limitations remain: no real paid vendor benchmark,
18
+ no provider-enforced quota cap, and no complete ACP TCK. Experimental ACP
19
+ external-client support remains **unmerged** in a separate draft PR.
20
+ - First public upload requires the package owner's PyPI account and publisher
21
+ authorization; committing this candidate alone does not publish it.
22
+
23
+
24
+ ## Unreleased v0.5 foundations (not release-ready)
25
+
26
+ - Explicit schema-2 requirement coverage and subset/critic completion guards.
27
+ - Decimal ledger library and opt-in progress-aware retry modes.
28
+ - Conservative adapter flags and evidence in all report formats.
29
+ - Runtime monetary integration, detached harness, durable recovery and paired benchmarks remain outstanding.
30
+
31
+ ## Unreleased universal engine
32
+
33
+ - Versioned adapter/backend/model/verifier/event interfaces and protected SDK orchestration.
34
+ - Detached acceptance snapshots, source application checks and explicit plugin permissions.
35
+ - Runtime Decimal admission, verifier reserves, usage provenance, dated pricing and manual receipt reconciliation.
36
+ - Transactional run IDs/checkpoints, cancellation, restricted recovery and retention controls.
37
+ - Dependency-aware intermediate selection with mandatory final full verification; no result cache.
38
+ - CLI diagnostics/state/report/benchmark commands, SDK, server-granted local MCP execution and read-only loopback API.
39
+ - Windows/Ubuntu/macOS matrix, Docker SDK smoke, executable paired pilot and new adversarial tests.
40
+ - No production tag, hard quota, live paid-vendor benchmark or exhaustive-security claim.
olyder-0.5.0b1/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
@@ -0,0 +1,8 @@
1
+ include LICENSE
2
+ include README.md
3
+ include CHANGELOG.md
4
+ recursive-include src/olyder/data *.md
5
+ prune .github
6
+ prune .olyder
7
+ global-exclude __pycache__ *.py[cod] *.pyd *.so
8
+ global-exclude .env .env.* *.pem *.p12 *.pfx id_rsa id_ed25519
@@ -0,0 +1,157 @@
1
+ Metadata-Version: 2.4
2
+ Name: Olyder
3
+ Version: 0.5.0b1
4
+ Summary: Verification-driven execution, independent checks, and evidence for AI coding agents
5
+ Author: Olyder Contributors
6
+ License-Expression: Apache-2.0
7
+ Project-URL: Homepage, https://github.com/Ratnadeep-2007/Olyder
8
+ Project-URL: Repository, https://github.com/Ratnadeep-2007/Olyder
9
+ Project-URL: Issues, https://github.com/Ratnadeep-2007/Olyder/issues
10
+ Project-URL: Documentation, https://github.com/Ratnadeep-2007/Olyder/blob/main/docs/UNIVERSAL_GUIDE.md
11
+ Project-URL: Changelog, https://github.com/Ratnadeep-2007/Olyder/blob/main/CHANGELOG.md
12
+ Keywords: ai-agents,testing,verification,mcp,coding-agents,agent-skills
13
+ Classifier: Development Status :: 4 - Beta
14
+ Classifier: Environment :: Console
15
+ Classifier: Intended Audience :: Developers
16
+ Classifier: Operating System :: OS Independent
17
+ Classifier: Programming Language :: Python :: 3
18
+ Classifier: Programming Language :: Python :: 3.11
19
+ Classifier: Programming Language :: Python :: 3.12
20
+ Classifier: Programming Language :: Python :: 3.13
21
+ Classifier: Topic :: Software Development :: Quality Assurance
22
+ Classifier: Topic :: Software Development :: Testing
23
+ Requires-Python: >=3.11
24
+ Description-Content-Type: text/markdown
25
+ License-File: LICENSE
26
+ Provides-Extra: browser
27
+ Requires-Dist: playwright>=1.50; extra == "browser"
28
+ Provides-Extra: acp
29
+ Requires-Dist: agent-client-protocol<0.13,>=0.12; extra == "acp"
30
+ Provides-Extra: dev
31
+ Requires-Dist: pytest>=8; extra == "dev"
32
+ Requires-Dist: ruff>=0.9; extra == "dev"
33
+ Dynamic: license-file
34
+
35
+ # Olyder
36
+
37
+ **Test AI-generated code against acceptance criteria you define.**
38
+
39
+ Olyder turns an `olyder.json` acceptance specification into a reproducible verdict
40
+ and HTML, Markdown, and JSON evidence. Use it with Google Antigravity, Codex,
41
+ Claude Code, or OpenCode, or run it in GitHub Actions.
42
+ Deterministic verification works with Python 3.11+ and uses zero model tokens.
43
+ An optional reviewer can assess the observed evidence, and a repair loop can
44
+ send failing checks back to a configured builder.
45
+
46
+ [![CI](https://github.com/Ratnadeep-2007/Olyder/actions/workflows/ci.yml/badge.svg)](https://github.com/Ratnadeep-2007/Olyder/actions/workflows/ci.yml)
47
+ [Quick start](#quick-start) · [Antigravity skill](docs/ANTIGRAVITY.md) · [GitHub Actions](docs/GITHUB_ACTIONS.md) · [Contribute](CONTRIBUTING.md) · [Changelog](CHANGELOG.md)
48
+
49
+ ## Quick start
50
+
51
+ The first PyPI beta, `0.5.0b1`, is a release candidate. Install from the GitHub
52
+ source in a Python virtual environment while publication is pending. This
53
+ installation route requires Git and network access. Create an environment with
54
+ `python -m venv .venv` and activate it with `source .venv/bin/activate` on
55
+ macOS/Linux or `.venv\Scripts\Activate.ps1` in PowerShell.
56
+
57
+ ```sh
58
+ python -m pip install "git+https://github.com/Ratnadeep-2007/Olyder.git"
59
+ olyder demo
60
+ olyder demo --fail
61
+ ```
62
+
63
+ The demo uses two file checks in a temporary project. The first command exits
64
+ `0` and writes a report under `.olyder/demo/pass/`. The second deliberately fails
65
+ one assertion, exits `1`, and writes a separate report under `.olyder/demo/fail/`.
66
+ Open `report.html` or read `report.json` to see what ran and why the verdict
67
+ changed. Both runs work offline and use zero model tokens. If you already have
68
+ a reviewed wheel, install it without package-index access using
69
+ `python -m pip install --no-index "/path/to/olyder-0.5.0b1-py3-none-any.whl"`.
70
+
71
+ ## Verify your repository
72
+
73
+ Save this as `olyder.json` at your project root and replace the sample assertion
74
+ with a condition your change must satisfy.
75
+
76
+ ```json
77
+ {
78
+ "goal": "The README explains how to install the project",
79
+ "checks": [
80
+ {"id": "install-docs", "type": "file", "path": "README.md", "contains": "Install"}
81
+ ]
82
+ }
83
+ ```
84
+
85
+ ```sh
86
+ olyder plan
87
+ olyder verify
88
+ ```
89
+
90
+ Add a check object to the `checks` array to run your existing test suite.
91
+ This example assumes pytest is installed in the verification environment.
92
+
93
+ ```json
94
+ {"id": "unit-tests", "type": "command", "argv": ["python", "-m", "pytest", "-q"]}
95
+ ```
96
+
97
+ Review all configured commands before running `olyder verify --allow-exec`.
98
+ File checks need no execution grant.
99
+ HTTP and optional Playwright browser checks require `--allow-exec`, and
100
+ non-local URLs also require `--allow-network`. A blocked check leaves acceptance
101
+ unverified. See the [cart-pricing example](examples/demo-app/) for a checked-in
102
+ spec with a real unit test suite.
103
+
104
+ Use the same `olyder verify` command in CI and archive `.olyder/report.json` or
105
+ `report.html` when the contents are safe to share. Exit `0` means acceptance
106
+ passed. Exit `1` covers failed or unresolved acceptance, and `2` covers CLI
107
+ or configuration errors. The JSON verdict differentiates failed and blocked checks.
108
+ A configuration error leaves earlier reports in place. Use the exit code and
109
+ the report paths from the current command when collecting evidence. In CI, use
110
+ a fresh `--output` directory per run and archive reports for exits `0` or `1`.
111
+ Reports show selected checks and actual execution coverage. If you run
112
+ from another directory with `--spec`, the default report directory is relative
113
+ to the directory where you launched Olyder. Use `--output` to select it explicitly.
114
+
115
+ ## Choose how to use Olyder
116
+
117
+ | Use case | Entry point |
118
+ | --- | --- |
119
+ | Add local or CI verification | `olyder verify` and a checked-in `olyder.json`. Use the [GitHub Actions starter](docs/GITHUB_ACTIONS.md) for pull requests |
120
+ | Give an editor the Olyder skill | [`olyder setup antigravity`](docs/ANTIGRAVITY.md), `olyder setup codex`, `olyder setup opencode`, or `olyder setup claude`. Add `--global` for all projects |
121
+ | Integrate a tool or application | Python [SDK](docs/UNIVERSAL_GUIDE.md) or read-only-by-default stdio `olyder mcp` |
122
+ | Connect a compatible ACP editor | Optional [ACP v1 bridge](docs/ACP_BRIDGE.md) via `olyder[acp]` |
123
+ | Review evidence with another model | `olyder verify --ai` with a configured OpenAI-compatible endpoint |
124
+ | Run bounded correction attempts | Configured Codex, OpenCode, Claude, or executable adapter with explicit builder permissions and a reviewed [Docker sandbox](docs/UNIVERSAL_GUIDE.md) |
125
+
126
+ `olyder doctor` reports local capabilities. Skills can be installed repeatedly
127
+ and preserve customized files unless you pass `--force`.
128
+ See the [integration guide](docs/UNIVERSAL_GUIDE.md) for configuration, execution
129
+ permissions, resuming runs, and reports. The [scenario examples](docs/EXAMPLES.md)
130
+ cover browser, staging, and data workflows.
131
+
132
+ ## Trust and validation
133
+
134
+ - A successful verdict covers the declared checks in the recorded environment.
135
+ Optional model feedback gets a fresh request with requirements and bounded
136
+ test evidence. It cannot override a deterministic failure.
137
+ - Builder runs separate the proposed code from protected acceptance inputs.
138
+ Host mode has no OS isolation. Use separately enforced filesystem, credential,
139
+ and network restrictions for untrusted code.
140
+ - Olyder can track its own model calls and record supported builder telemetry.
141
+ Provider hard spending limits and subscription balances are outside its control.
142
+ - Reports may contain test output. Review them before saving to shared CI artifacts.
143
+ Browser traces are opt-in and can include sensitive data.
144
+
145
+ See [known limits](docs/KNOWN_LIMITATIONS.md), the [threat model](docs/THREAT_MODEL.md),
146
+ [release validation](docs/PYPI_RELEASE.md), and [beta readiness research](docs/BETA_READINESS.md).
147
+ CI covers Linux, Windows, and macOS.
148
+ The [historical verification benchmark](docs/BENCHMARK_V05.md) and
149
+ [99-scenario evidence](docs/QA_99.md) describe their fixtures and test boundaries.
150
+
151
+ ## Contribute
152
+
153
+ Fork the repository and run `python -m pip install -e ".[dev]"` followed by
154
+ `python -m pytest -q`. The [contributing guide](CONTRIBUTING.md) explains how to
155
+ report a reproducible verdict or onboarding problem.
156
+
157
+ Apache License 2.0.
@@ -0,0 +1,123 @@
1
+ # Olyder
2
+
3
+ **Test AI-generated code against acceptance criteria you define.**
4
+
5
+ Olyder turns an `olyder.json` acceptance specification into a reproducible verdict
6
+ and HTML, Markdown, and JSON evidence. Use it with Google Antigravity, Codex,
7
+ Claude Code, or OpenCode, or run it in GitHub Actions.
8
+ Deterministic verification works with Python 3.11+ and uses zero model tokens.
9
+ An optional reviewer can assess the observed evidence, and a repair loop can
10
+ send failing checks back to a configured builder.
11
+
12
+ [![CI](https://github.com/Ratnadeep-2007/Olyder/actions/workflows/ci.yml/badge.svg)](https://github.com/Ratnadeep-2007/Olyder/actions/workflows/ci.yml)
13
+ [Quick start](#quick-start) · [Antigravity skill](docs/ANTIGRAVITY.md) · [GitHub Actions](docs/GITHUB_ACTIONS.md) · [Contribute](CONTRIBUTING.md) · [Changelog](CHANGELOG.md)
14
+
15
+ ## Quick start
16
+
17
+ The first PyPI beta, `0.5.0b1`, is a release candidate. Install from the GitHub
18
+ source in a Python virtual environment while publication is pending. This
19
+ installation route requires Git and network access. Create an environment with
20
+ `python -m venv .venv` and activate it with `source .venv/bin/activate` on
21
+ macOS/Linux or `.venv\Scripts\Activate.ps1` in PowerShell.
22
+
23
+ ```sh
24
+ python -m pip install "git+https://github.com/Ratnadeep-2007/Olyder.git"
25
+ olyder demo
26
+ olyder demo --fail
27
+ ```
28
+
29
+ The demo uses two file checks in a temporary project. The first command exits
30
+ `0` and writes a report under `.olyder/demo/pass/`. The second deliberately fails
31
+ one assertion, exits `1`, and writes a separate report under `.olyder/demo/fail/`.
32
+ Open `report.html` or read `report.json` to see what ran and why the verdict
33
+ changed. Both runs work offline and use zero model tokens. If you already have
34
+ a reviewed wheel, install it without package-index access using
35
+ `python -m pip install --no-index "/path/to/olyder-0.5.0b1-py3-none-any.whl"`.
36
+
37
+ ## Verify your repository
38
+
39
+ Save this as `olyder.json` at your project root and replace the sample assertion
40
+ with a condition your change must satisfy.
41
+
42
+ ```json
43
+ {
44
+ "goal": "The README explains how to install the project",
45
+ "checks": [
46
+ {"id": "install-docs", "type": "file", "path": "README.md", "contains": "Install"}
47
+ ]
48
+ }
49
+ ```
50
+
51
+ ```sh
52
+ olyder plan
53
+ olyder verify
54
+ ```
55
+
56
+ Add a check object to the `checks` array to run your existing test suite.
57
+ This example assumes pytest is installed in the verification environment.
58
+
59
+ ```json
60
+ {"id": "unit-tests", "type": "command", "argv": ["python", "-m", "pytest", "-q"]}
61
+ ```
62
+
63
+ Review all configured commands before running `olyder verify --allow-exec`.
64
+ File checks need no execution grant.
65
+ HTTP and optional Playwright browser checks require `--allow-exec`, and
66
+ non-local URLs also require `--allow-network`. A blocked check leaves acceptance
67
+ unverified. See the [cart-pricing example](examples/demo-app/) for a checked-in
68
+ spec with a real unit test suite.
69
+
70
+ Use the same `olyder verify` command in CI and archive `.olyder/report.json` or
71
+ `report.html` when the contents are safe to share. Exit `0` means acceptance
72
+ passed. Exit `1` covers failed or unresolved acceptance, and `2` covers CLI
73
+ or configuration errors. The JSON verdict differentiates failed and blocked checks.
74
+ A configuration error leaves earlier reports in place. Use the exit code and
75
+ the report paths from the current command when collecting evidence. In CI, use
76
+ a fresh `--output` directory per run and archive reports for exits `0` or `1`.
77
+ Reports show selected checks and actual execution coverage. If you run
78
+ from another directory with `--spec`, the default report directory is relative
79
+ to the directory where you launched Olyder. Use `--output` to select it explicitly.
80
+
81
+ ## Choose how to use Olyder
82
+
83
+ | Use case | Entry point |
84
+ | --- | --- |
85
+ | Add local or CI verification | `olyder verify` and a checked-in `olyder.json`. Use the [GitHub Actions starter](docs/GITHUB_ACTIONS.md) for pull requests |
86
+ | Give an editor the Olyder skill | [`olyder setup antigravity`](docs/ANTIGRAVITY.md), `olyder setup codex`, `olyder setup opencode`, or `olyder setup claude`. Add `--global` for all projects |
87
+ | Integrate a tool or application | Python [SDK](docs/UNIVERSAL_GUIDE.md) or read-only-by-default stdio `olyder mcp` |
88
+ | Connect a compatible ACP editor | Optional [ACP v1 bridge](docs/ACP_BRIDGE.md) via `olyder[acp]` |
89
+ | Review evidence with another model | `olyder verify --ai` with a configured OpenAI-compatible endpoint |
90
+ | Run bounded correction attempts | Configured Codex, OpenCode, Claude, or executable adapter with explicit builder permissions and a reviewed [Docker sandbox](docs/UNIVERSAL_GUIDE.md) |
91
+
92
+ `olyder doctor` reports local capabilities. Skills can be installed repeatedly
93
+ and preserve customized files unless you pass `--force`.
94
+ See the [integration guide](docs/UNIVERSAL_GUIDE.md) for configuration, execution
95
+ permissions, resuming runs, and reports. The [scenario examples](docs/EXAMPLES.md)
96
+ cover browser, staging, and data workflows.
97
+
98
+ ## Trust and validation
99
+
100
+ - A successful verdict covers the declared checks in the recorded environment.
101
+ Optional model feedback gets a fresh request with requirements and bounded
102
+ test evidence. It cannot override a deterministic failure.
103
+ - Builder runs separate the proposed code from protected acceptance inputs.
104
+ Host mode has no OS isolation. Use separately enforced filesystem, credential,
105
+ and network restrictions for untrusted code.
106
+ - Olyder can track its own model calls and record supported builder telemetry.
107
+ Provider hard spending limits and subscription balances are outside its control.
108
+ - Reports may contain test output. Review them before saving to shared CI artifacts.
109
+ Browser traces are opt-in and can include sensitive data.
110
+
111
+ See [known limits](docs/KNOWN_LIMITATIONS.md), the [threat model](docs/THREAT_MODEL.md),
112
+ [release validation](docs/PYPI_RELEASE.md), and [beta readiness research](docs/BETA_READINESS.md).
113
+ CI covers Linux, Windows, and macOS.
114
+ The [historical verification benchmark](docs/BENCHMARK_V05.md) and
115
+ [99-scenario evidence](docs/QA_99.md) describe their fixtures and test boundaries.
116
+
117
+ ## Contribute
118
+
119
+ Fork the repository and run `python -m pip install -e ".[dev]"` followed by
120
+ `python -m pytest -q`. The [contributing guide](CONTRIBUTING.md) explains how to
121
+ report a reproducible verdict or onboarding problem.
122
+
123
+ Apache License 2.0.
@@ -0,0 +1,50 @@
1
+ [build-system]
2
+ requires = ["setuptools>=77.0.3"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "Olyder"
7
+ version = "0.5.0b1"
8
+ description = "Verification-driven execution, independent checks, and evidence for AI coding agents"
9
+ readme = "README.md"
10
+ requires-python = ">=3.11"
11
+ license = "Apache-2.0"
12
+ license-files = ["LICENSE"]
13
+ authors = [{name = "Olyder Contributors"}]
14
+ keywords = ["ai-agents", "testing", "verification", "mcp", "coding-agents", "agent-skills"]
15
+ classifiers = [
16
+ "Development Status :: 4 - Beta",
17
+ "Environment :: Console",
18
+ "Intended Audience :: Developers",
19
+ "Operating System :: OS Independent",
20
+ "Programming Language :: Python :: 3",
21
+ "Programming Language :: Python :: 3.11",
22
+ "Programming Language :: Python :: 3.12",
23
+ "Programming Language :: Python :: 3.13",
24
+ "Topic :: Software Development :: Quality Assurance",
25
+ "Topic :: Software Development :: Testing",
26
+ ]
27
+
28
+ [project.urls]
29
+ Homepage = "https://github.com/Ratnadeep-2007/Olyder"
30
+ Repository = "https://github.com/Ratnadeep-2007/Olyder"
31
+ Issues = "https://github.com/Ratnadeep-2007/Olyder/issues"
32
+ Documentation = "https://github.com/Ratnadeep-2007/Olyder/blob/main/docs/UNIVERSAL_GUIDE.md"
33
+ Changelog = "https://github.com/Ratnadeep-2007/Olyder/blob/main/CHANGELOG.md"
34
+
35
+ [project.optional-dependencies]
36
+ browser = ["playwright>=1.50"]
37
+ acp = ["agent-client-protocol>=0.12,<0.13"]
38
+ dev = ["pytest>=8", "ruff>=0.9"]
39
+
40
+ [project.scripts]
41
+ olyder = "olyder.cli:main"
42
+
43
+ [tool.setuptools.packages.find]
44
+ where = ["src"]
45
+
46
+ [tool.pytest.ini_options]
47
+ testpaths = ["tests"]
48
+
49
+ [tool.setuptools.package-data]
50
+ olyder = ["data/SKILL.md"]
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+