invairiant 0.2.3__tar.gz

invairiant-0.2.3/.gitignore

@@ -0,0 +1,50 @@
+# macOS
+.DS_Store
+.AppleDouble
+.LSOverride
+Icon?
+
+# Editors / IDEs
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+
+# Local agent-harness state (machine-specific; install the skill per skill/README.md)
+.claude/
+
+# Python (validation tooling)
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+.mypy_cache/
+.pytest_cache/
+
+# Node (potential future product tooling)
+node_modules/
+npm-debug.log*
+dist/
+build/
+
+# invAIriant local audit output (projects using the framework may commit
+# their own audits; this repo does not carry generated reports)
+/audits-local/
+*.audit.local.md
+
+# Scratch / temp
+scratchpad/
+tmp/
+*.tmp
+
+# Stray spreadsheets dropped into the working dir (not part of the framework)
+*.xlsx
+
+# Python build/install artifacts
+*.egg-info/
+
+# Audit memory: commit ONLY the sanitized history/. Raw evidence bundles
+# (invairiant collect) and any local agent transcripts stay local.
+.invairiant/*
+!.invairiant/history/

invairiant-0.2.3/CHANGELOG.md

@@ -0,0 +1,272 @@
+# Changelog
+
+All notable changes to invAIriant are documented here. The format loosely
+follows Keep a Changelog; versions track the protocol.
+
+## [Unreleased]
+
+_Nothing yet._
+
+## [0.2.3] — 2026-07-04
+
+### Changed
+
+- **README quickstart split into two independent tracks** — *enable the skill*
+  (the product) and *install the CLI helper* (optional infrastructure) — leading
+  with the skill and framing `pip install` as the seatbelt the skill shells out
+  to, not "installing invAIriant". The two install independently.
+- **`pip install` is now production-grade.** The wheel and sdist bundle the
+  framework data the CLI reads at runtime (schemas, examples, lens ids) under
+  `invairiant_framework/`, and `framework_root()` falls back to it — so a plain
+  `pip install invairiant` works **outside a checkout**, no `INVAIRIANT_HOME`
+  needed. Before, a non-editable install shipped only the module and any real
+  command died with `schema not found`. The build backend moved to hatchling
+  (`force-include` maps the repo-root dirs into the distribution without moving
+  or duplicating them — the checkout stays the single source of truth). A CI
+  **packaging smoke** installs the wheel in a clean venv and runs a command from
+  outside the checkout, so this can't silently regress.
+
+### Added
+
+- **GitHub Action understands the bounded scopes.** The Action's optional
+  `collect` step gains `scope` / `pr` / `commit` / `path` / `narrow` inputs
+  (`range` kept), so CI can gather a bundle for a PR, module, ADR, or
+  refactoring proposal — not just a range. Inputs pass via env; the step builds
+  only the flags that are set, so it stays a bounded gather.
+
+### Fixed
+
+- **PR scope warns when the head isn't checked out.** `collect --scope pr` now
+  records `head_checked_out` in `resolved_scope` and prints a NOTICE (pointing
+  at `gh pr checkout <N>`, or auditing in CI where the PR head is the checkout)
+  when the PR head is not the working tree — because content-level grep signals
+  are then sparse. The diff, file set, and mass stay correct from git regardless.
+
+## [0.2.2] — 2026-07-04
+
+### Added
+
+- **`--scope pr` — first-class PR resolver (the main entrypoint, now backed).**
+  `invairiant collect --scope pr --pr <N>` pins a pull request **by number** and
+  resolves it to an ordinary bounded `base...head` range — so `audit-pr <N>` is
+  finally real, not just a promise in the command signature. It is an **optional
+  resolver adapter**: every other scope is pure-local git, and **only** `--scope
+  pr` may reach the remote — via `gh` if present, else the `pull/<n>/head` ref.
+  If the PR can't be reached (no remote, offline, non-GitHub remote) it **fails
+  closed and suggests `--range`**, never widening to the repo. `resolved_scope`
+  records `base`, `head`, and `resolver` (`gh`/`git`). Content-level signals read
+  the working tree, so check out the PR (or run in CI) for full fidelity; the
+  diff, file set, and mass are correct from git regardless. Documented across the
+  skill, `docs/methodology.md` §4.1, `docs/cli.md`, the schema, and the adapters;
+  6 hermetic tests (fail-closed cases + pull-ref resolution against a bare remote
+  carrying `refs/pull/1/head`, no gh/network). 82 tests total.
+
+## [0.2.1] — 2026-07-04
+
+### Added
+
+- **`audit-rp` — refactoring-proposal scope.** A sixth bounded scope kind
+  (`collect --scope rp --path <proposal.md>`) and skill command `audit-rp`. An
+  RP is the mirror image of an ADR: an ADR is a *made* decision (audit for
+  drift — does the code still match?), an RP is a *proposed* change (audit for
+  risk — would applying it break an invariant the code holds now?). It resolves
+  the proposal to the tracked code it references, snapshots that code, and
+  reuses the same fail-closed bounding as `adr` (no refs / too broad → exit 2,
+  `--narrow` to tighten). Documented across the skill, `docs/methodology.md`
+  §4.1 (seven scope kinds; adr = decision drift, rp = invariant risk),
+  `docs/cli.md`, the schema enum, and the cross-agent adapters. **No new
+  lenses**; the CLI still performs no judgment.
+
+### Changed
+
+- **README positioning.** Lead with the one-line promise — *invAIriant keeps
+  architectural invariants from drifting under AI-assisted change* — with the
+  slogan **No evidence. No finding.** as the brand stamp; the
+  "mindicator & silicon bags quartet" credit moves off the very top (it still
+  stands in Contributing and the License). The product row lists the bounded
+  targets, and "What it is not" states the discipline outright: **invAIriant
+  audits bounded engineering scopes, not vibes** — a scope it cannot bound is
+  refused, not widened.
+
+## [0.2.0] — 2026-07-04
+
+### Added
+
+- **Scope resolvers — the audit target beyond PRs.** `invairiant collect` now
+  takes `--scope {working,range,commit,module,adr,repo}` and resolves the pin to
+  a **bounded file set**; the entire evidence bundle (tree, language stats, grep
+  signals, generated mass) is computed over that set only — scoped gathering, not
+  a whole-repo scan. It **fails closed** (exit 2) when a scope can't be bounded —
+  a missing `--range`, an unknown `--path`/`--commit`, or an ADR whose references
+  don't resolve or resolve too broadly (unless `--narrow` tightens them) — and
+  never silently widens; `repo` is the one opt-in unbounded scope. Every bundle
+  now carries a **`resolved_scope`** block (documented in the evidence-bundle
+  schema) making the boundary explicit and auditable.
+- **`adr` scope** — `collect --scope adr --path <ADR.md>` pins an
+  **ADR ↔ code** audit: the ADR text joins the canonical docs and its referenced
+  paths/symbols resolve to the tracked files in scope, so decision-vs-code drift
+  is first-class evidence.
+- **Skill commands `audit-range`, `audit-commit`, `audit-module`, `audit-adr`**
+  ([`skill/SKILL.md`](skill/SKILL.md)) — thin scope-selectors over the **same**
+  four-stage pipeline, plus the unifying **audit target** concept
+  (`pinned scope + evidence bundle + selected lenses + report type`) in the skill
+  and [`docs/methodology.md`](docs/methodology.md) §4.1. **No new lenses** — a
+  wider set of things to point the audit at, not new judgment. Cross-agent
+  adapters (`AGENTS.md`, Cursor rule) updated to match.
+- **14 scope tests** (`tests/test_scope.py`): per-kind resolution, fail-closed
+  exit-2 cases, the `resolved_scope` shape, ADR reference/identifier resolution
+  with `--narrow`, and an end-to-end proof that a module scan stays inside its
+  subtree. 69 tests total.
+
+### Non-goal reaffirmed
+
+- invAIriant audits **bounded engineering scopes** — PRs, ranges, commits,
+  modules, ADR↔code drift, the repo by explicit choice. It does **not** perform
+  general repository search or brainstorming; an unbounded scope is refused, not
+  widened ([`docs/methodology.md`](docs/methodology.md) §7).
+
+## [0.1.2] — 2026-07-04
+
+### Added
+
+- **Two real (redacted) case studies** (`case-studies/`): `low-latency-runtime`
+  — a **full-scale** audit scoring the whole core lens block + Lamport, where a
+  ~7 average and a *pass* verdict still surface a real correctness finding
+  (anti-averaging on real code); and `social-autopost` — a focused PR audit of
+  raw model output auto-published with no content gate. Both from private
+  codebases with names and specifics withheld. The case set now spans the
+  depth × source × status range (see `case-studies/README.md`).
+- **GitHub Action** ([`action.yml`](action.yml)) — a composite action that
+  validates an audit report (schema + semantic), renders it into the job
+  summary, and **gates CI on open S0/S1** findings. Use it as
+  `uses: mindicator/invairiant@v0.1.2`. Docs:
+  [`docs/github-action.md`](docs/github-action.md).
+- **Unit-test suite** (`tests/`, 55 tests) for the CLI — parser dispatch,
+  `validate-report` semantic-linter rules, secret redaction, `record`
+  idempotency + sanitization, claim-key matching, `history` trends, repo-root
+  memory resolution, and the bounded `collect` scan. CI runs `pytest`. (Closes
+  self-audit finding CLOSE-003.)
+- **Roadmap for v0.2** ([`ROADMAP.md`](ROADMAP.md)) — hardening and reach, **no
+  new lenses**.
+- A **60-second Quickstart** at the top of the README and a demo PR-comment
+  visual ([`assets/pr-comment.svg`](assets/pr-comment.svg)).
+
+### Changed
+
+- **Origin narrative** reframed (README / NOTICE): invAIriant was forged in
+  AI-assisted development of complex, high-load systems — that is its story.
+- **`pyproject.toml` version bumped to 0.1.2** for this release.
+
+### Fixed
+
+- **Memory & `collect` hardening on large repos** (from self-audit #2):
+  - `record` / `history` / the memory-aware linter now resolve
+    `.invairiant/history/` from the **repo root**, not the current directory,
+    so running the CLI from a subdirectory no longer silently misses committed
+    audit memory (**CLOSE-001**).
+  - `collect` bounds its scan — skips large (>512 KB) and binary files, caps the
+    file count, does a single O(files) pass, and reports `limits` in the bundle
+    (no silent truncation) (**CLOSE-002**).
+  - `record` secret redaction hardened: full PEM blocks (not just the header),
+    AWS/GitHub/Slack tokens, and `Authorization` / `Bearer` values.
+
+## [0.1.1] — 2026-07-03
+
+### Added
+
+- **Cross-agent adapters** — the skill now runs beyond Claude Code. A portable
+  root [`AGENTS.md`](AGENTS.md) (Codex and any AGENTS.md-aware agent) and
+  [`.cursor/rules/invairiant.mdc`](.cursor/rules/invairiant.mdc) (Cursor) reach
+  the same protocol, both pointing to the canonical `skill/SKILL.md` instead of
+  duplicating it. Per-agent install in `skill/README.md`; README badges link
+  each.
+
+## [0.1.0] — 2026-07-03
+
+First public release. A reusable, evidence-first, multi-lens architecture-audit
+protocol for AI-era codebases, distilled from real-world auditing of AI-assisted
+development on complex, high-load systems. One rule underneath all of it: **no
+evidence, no finding.**
+
+### Protocol & lenses
+
+- **Docs** (`docs/`): methodology, evidence rules, severity model, audit
+  workflow, lens taxonomy, related work, CLI spec.
+- **Lens library** (`lenses/`): 28 lenses across 7 packs — core, systems,
+  implementation, correctness, security-safety, ai-generated-code, domain —
+  each with purpose, scope, core questions, good-state examples, red flags,
+  required evidence, a 0–10 rubric, finding examples, and an AI prompt block.
+  New lenses include Turing, von Neumann, Ritchie, Kernighan, Hoare, Lamport,
+  Liskov, Saltzer–Schroeder, and Leveson.
+- **Schemas** (`schemas/`): finding, audit-report, lens, config, and
+  evidence-bundle (JSON Schema draft 2020-12) — the stable contract for tooling.
+- **Templates** (`templates/`): audit-report, finding, pr-comment,
+  phase-transition-audit, event-triggered-audit.
+- **Prompt pack** (`prompts/`): lens-auditor, evidence-verifier,
+  severity-classifier, report-synthesizer — the four pipeline stages.
+
+### Skill — the primary product
+
+- **`/invairiant`** (`skill/`): an LLM coding agent runs the audit. Commands:
+  `audit-pr`, `full-audit`, `verify-findings`, `classify-severity`,
+  `synthesize-report`, `closure-verification`; a `--lenses a,b` override; and a
+  concrete `audit-pr` runbook (collect → lens passes → verify → classify → PR
+  comment). Other skills and tools attach as **evidence adapters**.
+
+### CLI — the narrow helper (serves the audit, never performs one)
+
+- **`invairiant`** (`cli/invairiant.py`, `pyproject.toml`, spec in
+  `docs/cli.md`): `init`, `collect`, `validate-config`, `validate-report`,
+  `render-report`, `render-comment`, `ci-gate`, `record`, `history`
+  (+ `collect-evidence` alias). Installs as the `invairiant` command; no
+  lenses, findings, or scores.
+- **`collect`** builds a deterministic evidence bundle (diff scope, tree,
+  language stats, grep signals, import hints, generated mass, known-rejected) —
+  candidate pointers only.
+- **`validate-report`** runs schema validation **plus a semantic pass**:
+  verdict↔severity consistency (open S0 → fail; open S1 → not pass), S0/S1
+  confidence, referential integrity, and a kept-`hypotheses` check.
+  `--schema-only` / `--md`.
+- **`render-comment`** turns a report into a paste-ready PR comment;
+  **`ci-gate`** exits non-zero on open S0/S1.
+- **Audit memory** (`record` / `history`): committed, **sanitized**
+  `.invairiant/history/` (rejected hypotheses, finding registry, lens-score
+  trends) — never raw evidence; secrets redacted; idempotent by audit label.
+  Raw bundles and transcripts stay gitignored under `.invairiant/cache/`.
+
+### Examples, case studies & dogfood
+
+- **Examples** (`examples/`): minimal-webapp, infra-service, ai-agent-system
+  configs + a worked infra-service report.
+- **Case studies** (`case-studies/`): four illustrative worked audits
+  (`persistent-mesh-transport`, `ai-agent-refund-bot`,
+  `generated-typescript-api`, `p2p-network-transport-change`) — each with the
+  diff, selected lenses, candidate/rejected/verified findings, a schema-valid
+  report, and a
+  side-by-side of **what a normal AI reviewer missed**.
+- **Two self-audits** of the framework recorded to audit memory, so
+  `invairiant history` shows a real per-lens trend.
+
+### Quality gates
+
+- **CI** (`.github/workflows/validate.yml`): validates schemas, examples, and
+  lens structure, and smoke-tests every CLI command (including a negative test
+  that the semantic linter fails an inconsistent report).
+- **Local authorship gate** (`commit-msg` hook): rejects AI co-author trailers
+  — commits are authored by the maintainer alone.
+
+### Principles enforced
+
+- No evidence, no finding.
+- A high average score never cancels an S0/S1 finding.
+- Observations and hypotheses stay separate from verified findings.
+- Default audits use 4–6 lenses, not 20.
+
+[Unreleased]: https://github.com/mindicator/invairiant/compare/v0.2.3...HEAD
+[0.2.3]: https://github.com/mindicator/invairiant/releases/tag/v0.2.3
+[0.2.2]: https://github.com/mindicator/invairiant/releases/tag/v0.2.2
+[0.2.1]: https://github.com/mindicator/invairiant/releases/tag/v0.2.1
+[0.2.0]: https://github.com/mindicator/invairiant/releases/tag/v0.2.0
+[0.1.2]: https://github.com/mindicator/invairiant/releases/tag/v0.1.2
+[0.1.1]: https://github.com/mindicator/invairiant/releases/tag/v0.1.1
+[0.1.0]: https://github.com/mindicator/invairiant/releases/tag/v0.1.0

invairiant-0.2.3/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 mindicator & silicon bags quartet
+
+   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.

invairiant-0.2.3/NOTICE

@@ -0,0 +1,12 @@
+invAIriant — evidence-based multi-lens architecture audits for AI-era codebases
+Copyright 2026 mindicator & silicon bags quartet
+
+Licensed under the Apache License, Version 2.0 (see LICENSE).
+
+This work distills a body of architecture-audit practice (the audit types, the
+0–10 lens scale, the score-to-severity mapping, the anti-averaging rules, and
+the network-persistence domain lens) developed while auditing AI-assisted
+development of complex, high-load systems.
+Lens names (Cormen, Parnas, Turing, Lamport, Leveson, and others) are used as
+mnemonic devices for schools of engineering questioning and imply no
+endorsement by the individuals named.

invairiant-0.2.3/PKG-INFO

@@ -0,0 +1,56 @@
+Metadata-Version: 2.4
+Name: invairiant
+Version: 0.2.3
+Summary: Helper CLI for the invAIriant agentic audit protocol — it serves the audit, it does not audit.
+Project-URL: Homepage, https://github.com/mindicator/invairiant
+Project-URL: Documentation, https://github.com/mindicator/invairiant/blob/main/docs/cli.md
+Author: mindicator & silicon bags quartet
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: architecture,audit,code-review,evidence,llm
+Requires-Python: >=3.9
+Requires-Dist: jsonschema>=4.18
+Requires-Dist: pyyaml>=6
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# `invairiant` CLI
+
+Infrastructure around the agentic audit — **not an architecture auditor.** No
+lenses, no findings, no scores. All judgment lives in the
+[`/invairiant` skill](../skill/SKILL.md); this CLI scaffolds, validates,
+collects evidence, renders, and gates.
+
+Full spec and rationale: [`docs/cli.md`](../docs/cli.md).
+
+## Install
+
+```bash
+pip install -e .     # or: pipx install -e .  → gives the `invairiant` command
+```
+
+(No install? Run `python3 cli/invairiant.py <command>` directly.) Python 3.9+;
+`jsonschema` + `pyyaml` are pulled in as dependencies.
+
+## Commands
+
+| Command | Purpose |
+|---|---|
+| `init [--type T]` | scaffold `invairiant.config.yml` |
+| `collect [--range A..B] [--out F]` | build a deterministic evidence bundle (candidate pointers only) |
+| `validate-config [paths…]` | schema-check configs + cross-check lens ids |
+| `validate-report <paths…> [--schema-only] [--md]` | schema **+ semantic** checks on a report |
+| `render-report <report.json> [--out F]` | report JSON → Markdown |
+| `render-comment <report.json> [--out F]` | report JSON → paste-ready PR comment |
+| `ci-gate <report.json> [--max-severity S0\|S1]` | exit non-zero on open S0/S1 |
+| `record <report.json> [--force]` | append distilled, **sanitized** memory to `.invairiant/history/` |
+| `history [--lens L]` | lens-score trends + recurring findings |
+
+`collect-evidence` is a thin alias for the adapter-only subset of `collect`.
+
+Full spec: [`docs/cli.md`](../docs/cli.md). Worked flow:
+[`docs/demo.md`](../docs/demo.md). Resolves the framework via
+`$INVAIRIANT_HOME`, the repo layout, or by searching upward from the current
+directory.