invara 0.1.0__tar.gz

invara-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

invara-0.1.0/NOTICE

@@ -0,0 +1,7 @@
+INVARA
+Copyright 2026 MIGARYOS (미가리오스)
+
+Licensed under the Apache License, Version 2.0. See LICENSE.
+
+This product includes no third-party code. At runtime it imports only the
+Python standard library.

invara-0.1.0/PKG-INFO

@@ -0,0 +1,281 @@
+Metadata-Version: 2.4
+Name: invara
+Version: 0.1.0
+Summary: Independent verification that a change kept the constraints it declared
+Author: MIGARYOS
+License-Expression: Apache-2.0
+Keywords: verification,ai-agents,provenance,ci,evidence
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Dynamic: license-file
+
+<!-- mcp-name: io.github.jujitae/invara -->
+# INVARA
+
+**Engineering invariants for AI-built software.**
+
+> **INVARA upgrades vibe-coded software into verifiable, engineering-grade
+> software.**
+
+You asked an agent to do a piece of work. It says it is done. INVARA decides
+that independently, from exit codes and file bytes, and writes the verdict into
+a hash chain so the answer cannot be quietly revised later.
+
+**The agent's own report is not an input.** There is no field in a contract
+where anything can assert that the work is finished.
+
+```text
+Founder intent
+    ↓
+Sealed specification and constraints
+    ↓
+Builder agent (Claude Code / Codex / another agent)
+    ↓
+Code, files, database changes, commands, runtime effects
+    ↓
+Independent INVARA verifier
+    ↓
+Observable evidence and provenance
+    ↓
+BLOCK / UNVERIFIABLE / HUMAN_REVIEW / PASS
+    ↓
+Human or policy-controlled authority
+```
+
+Status: **v0.1 / Alpha.** It is dogfooded daily and has not been sold. It is
+not autonomous authorization and not an enterprise compliance control.
+
+---
+
+## What this is not
+
+Read this part before the install line. It is short on purpose, and the word
+that carries the promise above is *verifiable* — not *correct*.
+
+> **INVARA does not prove software correctness.**
+> **It verifies declared constraints against observable evidence.**
+
+Specifically:
+
+- **It does not inspect your codebase.** It never asks whether the code is
+  good, whether the architecture holds, or whether the tests are the right
+  tests. Stack a new floor on junk and, if this floor was built to the
+  declared spec, the verdict is `PASS`.
+- **It does not find bugs.** A completion check that runs your suite is only as
+  strong as your suite. INVARA reports the exit code; it does not have an
+  opinion about coverage.
+- **It does not decide what should have been promised.** You write the
+  contract. A weak contract earns a weak `PASS`, and the contract is stored
+  verbatim so anyone can see how weak it was.
+- **It is not a sandbox.** Completion checks are commands and they run with
+  your permissions. Do not seal a contract you have not read.
+- **It does not judge intent.** `intent` is prose; nothing checks that the
+  work matched it. The checks are what bind.
+- **It is not an AI code generator and not an LLM code-review bot.** There is
+  no model anywhere in the verdict path.
+
+The narrow claim, which is what the machine actually does:
+
+> **It decides, independently, whether this change kept the promises it made.**
+
+---
+
+## Install and first verdict, in five minutes
+
+Nothing to configure. No API key, no service, no account. Python 3.12+.
+
+```bash
+uvx --from git+https://github.com/Jujitae/invara invara list
+```
+
+or, to keep it:
+
+```bash
+pip install "invara @ git+https://github.com/Jujitae/invara"
+```
+
+The package declares **zero runtime dependencies**, so this pulls only the
+standard library.
+
+From a checkout it is the same program, but install it first — the source
+lives under `src/`, so a bare `python -m invara` in the repository root
+finds nothing to run:
+
+```bash
+pip install -e .
+python -m invara list
+```
+
+### 1. Write the contract *before* the work
+
+`task.json`, next to the repository you are about to change:
+
+```json
+{
+  "task_id": "2026-08-17-tidy-the-parser",
+  "intent": "Speed up the CSV parser without changing what it accepts",
+  "constraints": [
+    {
+      "kind": "paths_unchanged",
+      "paths": ["tests/test_parser.py"],
+      "reason": "a speedup that edits its own test is not a speedup"
+    }
+  ],
+  "done_when": [
+    {
+      "id": "suite",
+      "command": ["python", "-m", "pytest", "-q"],
+      "expect_exit": 0,
+      "reason": "the whole suite"
+    }
+  ]
+}
+```
+
+```bash
+invara seal task.json
+```
+
+Sealing takes the digests of the protected paths **now**, before anyone knows
+what the verdict will be. That ordering is the entire guarantee.
+
+### 2. Do the work.
+
+### 3. Judge
+
+```bash
+invara judge 2026-08-17-tidy-the-parser            # dry run
+invara judge 2026-08-17-tidy-the-parser --commit   # record it
+```
+
+```
+  BLOCK: 1 protected path(s) changed: tests/test_parser.py: changed
+         (a speedup that edits its own test is not a speedup)
+  decided by: constraint_breaks
+```
+
+That is the first verdict. Everything below is detail.
+
+---
+
+## The four verdicts
+
+| Verdict | Meaning | Exit |
+|---|---|---|
+| `BLOCK` | A protected path changed, or a completion check failed | 1 |
+| `UNVERIFIABLE` | A check could not be run at all. **Unchecked is not passed** | 2 |
+| `HUMAN_REVIEW` | Machine checks passed; something was declared as needing eyes | 0 |
+| `PASS` | Every check returned what it promised, every protected path is byte-identical | 0 |
+
+Constraint breaks outrank everything. A run that touched what it promised not
+to touch is not partially fine.
+
+`BLOCK` is two rules wearing one word — a protected path that changed and a
+check that came back wrong are not the same accusation. So the verdict also
+records which rule decided it, named after the evidence it decided on
+(`constraint_breaks`, `failed`, `unrunnable`, `needs_human`, `passed`), and
+`judge` and `log` print it. Verdicts recorded before this existed do not have
+one, and do not get one fitted after the fact.
+
+## Sealing refuses more than it accepts
+
+`seal` will not write a contract that cannot fail the work. It refuses a task
+with no completion condition, a condition with no command to check it, a
+contract with no protected paths ("a task allowed to change anything cannot be
+said to have respected anything"), a duplicate check id, a protected path that
+does not exist, and — the one that matters most — a contract where **every**
+condition defers to a person.
+
+That last one is why this is not a rubber stamp: if the only evidence is
+somebody saying yes, there is no contract.
+
+## Other commands
+
+```
+invara list             sealed tasks and their latest verdict
+invara log   <task_id>  every verdict this task has ever had
+invara show  <task_id>  the contract, exactly as sealed
+invara chain            rebuild both hash chains
+```
+
+Verdicts live in `.runtime/verify.db` (`--db` to move it). A contract is sealed
+once and judged many times; the history is append-only and chained.
+
+---
+
+## Determinism
+
+Same repository state, same contract, same environment → same verdict. The
+verdict is a function of file digests and command exit codes, and nothing else;
+there is no model in the path and no clock in the decision.
+
+Measured rather than asserted, 2026-08-17: contract
+`2026-08-17-route-discovery` was judged twice, four minutes apart, against an
+unchanged tree — 7 checks each including a 2,021-test suite. Both runs returned
+the same status and the same reason string, and both rows are in the chain:
+
+```
+$ invara log 2026-08-17-route-discovery
+2026-08-17 09:17 UTC  PASS
+    7 check(s) passed and 6 protected path(s) are unchanged
+2026-08-17 09:21 UTC  PASS
+    7 check(s) passed and 6 protected path(s) are unchanged
+```
+
+Run that yourself on your own contract before you trust it on ours.
+
+The word doing work there is **environment**. See the first failure story
+below: a contract that passed locally and failed in CI was not
+non-deterministic — it was two different environments, and INVARA reported
+each one correctly. If you want the verdict to be reproducible, make the
+completion commands reproducible.
+
+---
+
+## Failure stories
+
+These are real, from building and using this tool. They are here because a
+verification tool that only shows its successes is asking to be trusted on
+exactly the grounds it tells you not to trust anything.
+
+**Environment contamination.** A contract passed on the machine that wrote it
+and failed in CI. The tree was clean; the *environment* was not.
+`PYTHONIOENCODING` was set in the shell, child processes inherited it, and the
+completion command only worked because of it. Verification runs now use
+`env -u PYTHONIOENCODING`. Clean tree is not clean environment.
+
+**A seal that broke itself.** A fresh clone rewrote a sealed ontology file to
+CRLF on checkout, so its SHA-256 no longer matched. The file whose entire job
+was to prove nothing had changed failed its own seal. Fixed in
+`.gitattributes`, not in the digest rule — the digest was right.
+
+**The first verdict was `UNVERIFIABLE`, and it was correct.** A completion
+command could not be found, because `subprocess` does not use `cwd` to resolve
+the executable. The verdict was right and the tool was useless. Both facts are
+recorded; only one of them was a bug.
+
+**It did not pass the work that built it.** The first contract INVARA ever
+sealed was the task of building it. It returned `UNVERIFIABLE`, then
+`PASS`, then `PASS`. All three are still in `.runtime/verify.db`, and
+`invara log` prints them.
+
+---
+
+## Where it came from
+
+The shape is lifted from a sibling engine in the same private repository:
+seal the contract
+before the evidence exists, refuse to create anything you cannot kill, score
+only observed records, and chain the result. Change "world claim" to "agent's
+work" and the same machine applies.
+
+INVARA was built and is dogfooded inside a private working repository (WIE);
+see [`PROVENANCE.md`](PROVENANCE.md) for what that means for this source.