disensor 0.14.0__tar.gz → 0.16.0__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 (70) hide show
  1. {disensor-0.14.0/src/disensor.egg-info → disensor-0.16.0}/PKG-INFO +146 -14
  2. {disensor-0.14.0 → disensor-0.16.0}/README.md +145 -13
  3. {disensor-0.14.0 → disensor-0.16.0}/pyproject.toml +1 -1
  4. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/GUIDE.es.md +17 -3
  5. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/GUIDE.md +16 -2
  6. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/__init__.py +1 -1
  7. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/brief.py +22 -2
  8. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/cli.py +27 -2
  9. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/gate.py +70 -21
  10. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/gitctx.py +55 -3
  11. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/init.py +30 -8
  12. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/pack.py +109 -15
  13. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/prompts/architecture.md +5 -3
  14. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/prompts/diff.md +5 -3
  15. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/prompts/plan.md +5 -3
  16. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/report.html +17 -6
  17. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/report.py +78 -13
  18. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/reviewers.py +305 -33
  19. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/round.py +305 -25
  20. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/template.py +98 -6
  21. {disensor-0.14.0 → disensor-0.16.0/src/disensor.egg-info}/PKG-INFO +146 -14
  22. {disensor-0.14.0 → disensor-0.16.0}/src/disensor.egg-info/SOURCES.txt +1 -0
  23. {disensor-0.14.0 → disensor-0.16.0}/tests/test_brief.py +55 -4
  24. {disensor-0.14.0 → disensor-0.16.0}/tests/test_cli_errors.py +68 -0
  25. disensor-0.16.0/tests/test_degraded_mode.py +238 -0
  26. {disensor-0.14.0 → disensor-0.16.0}/tests/test_docs.py +341 -0
  27. {disensor-0.14.0 → disensor-0.16.0}/tests/test_gate.py +208 -10
  28. {disensor-0.14.0 → disensor-0.16.0}/tests/test_hardening.py +31 -3
  29. {disensor-0.14.0 → disensor-0.16.0}/tests/test_init.py +21 -0
  30. {disensor-0.14.0 → disensor-0.16.0}/tests/test_new_round.py +76 -1
  31. {disensor-0.14.0 → disensor-0.16.0}/tests/test_pack.py +124 -2
  32. {disensor-0.14.0 → disensor-0.16.0}/tests/test_report.py +104 -2
  33. {disensor-0.14.0 → disensor-0.16.0}/tests/test_reviewers.py +251 -1
  34. {disensor-0.14.0 → disensor-0.16.0}/tests/test_round.py +517 -11
  35. {disensor-0.14.0 → disensor-0.16.0}/tests/test_upgrade.py +25 -0
  36. {disensor-0.14.0 → disensor-0.16.0}/LICENSE +0 -0
  37. {disensor-0.14.0 → disensor-0.16.0}/setup.cfg +0 -0
  38. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/__main__.py +0 -0
  39. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/branch.py +0 -0
  40. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/codex_home.py +0 -0
  41. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/guide.py +0 -0
  42. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/pin.py +0 -0
  43. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/programs.py +0 -0
  44. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/prompts/_common.md +0 -0
  45. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/render.py +0 -0
  46. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/residue.schema.json +0 -0
  47. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/residue.schema.v0.2.json +0 -0
  48. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/residue.schema.v0.3.json +0 -0
  49. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/residue.schema.v0.4.json +0 -0
  50. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/rules.py +0 -0
  51. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/scope.py +0 -0
  52. {disensor-0.14.0 → disensor-0.16.0}/src/disensor/vectors.py +0 -0
  53. {disensor-0.14.0 → disensor-0.16.0}/src/disensor.egg-info/dependency_links.txt +0 -0
  54. {disensor-0.14.0 → disensor-0.16.0}/src/disensor.egg-info/entry_points.txt +0 -0
  55. {disensor-0.14.0 → disensor-0.16.0}/src/disensor.egg-info/requires.txt +0 -0
  56. {disensor-0.14.0 → disensor-0.16.0}/src/disensor.egg-info/top_level.txt +0 -0
  57. {disensor-0.14.0 → disensor-0.16.0}/tests/test_branch.py +0 -0
  58. {disensor-0.14.0 → disensor-0.16.0}/tests/test_codex_home.py +0 -0
  59. {disensor-0.14.0 → disensor-0.16.0}/tests/test_docs_sync.py +0 -0
  60. {disensor-0.14.0 → disensor-0.16.0}/tests/test_guide.py +0 -0
  61. {disensor-0.14.0 → disensor-0.16.0}/tests/test_lectura_publica.py +0 -0
  62. {disensor-0.14.0 → disensor-0.16.0}/tests/test_pin.py +0 -0
  63. {disensor-0.14.0 → disensor-0.16.0}/tests/test_programs.py +0 -0
  64. {disensor-0.14.0 → disensor-0.16.0}/tests/test_render.py +0 -0
  65. {disensor-0.14.0 → disensor-0.16.0}/tests/test_requirement.py +0 -0
  66. {disensor-0.14.0 → disensor-0.16.0}/tests/test_rule_coverage.py +0 -0
  67. {disensor-0.14.0 → disensor-0.16.0}/tests/test_rules.py +0 -0
  68. {disensor-0.14.0 → disensor-0.16.0}/tests/test_scope.py +0 -0
  69. {disensor-0.14.0 → disensor-0.16.0}/tests/test_v04.py +0 -0
  70. {disensor-0.14.0 → disensor-0.16.0}/tests/test_vectors.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: disensor
3
- Version: 0.14.0
3
+ Version: 0.16.0
4
4
  Summary: A versioned record of what an AI code review could not establish: a CLI and a CI gate that validate the residue declaration a cross-model adversarial review leaves in the repository.
5
5
  Author-email: Nicolas Rocchia <nicolasrocchia@gmail.com>
6
6
  License: MIT
@@ -47,6 +47,55 @@ scrutiny instead of reading as a seal of quality. A CLI validates it, and a CI
47
47
  gate stops the pull request when the change calls for a record and the record
48
48
  is missing, generic, or does not match the change the pull request makes.
49
49
 
50
+ The limit, said once: the machine checks the shape and the coherence of the
51
+ record, not whether it is true. A made-up declaration with the right shape
52
+ passes, and human sampling is the only thing that catches it.
53
+
54
+ ## Quick start
55
+
56
+ One path, from nothing to the report. It needs a git repository with a branch
57
+ to review and a second assistant on this machine: the example registers Codex,
58
+ and `disensor reviewer suggest` lists what yours has.
59
+
60
+ ```bash
61
+ pip install disensor
62
+ disensor init --no-workflow # config, CLAUDE.md and skill; nothing under .github/
63
+ git add .claude .gitignore CLAUDE.md disensor.config.json && git commit -m disensor-init
64
+
65
+ disensor reviewer add codex --model <model> --yes # once per machine, with a model your account runs
66
+ disensor reviewer login codex # once: the isolated home of the reviewer signs in
67
+ disensor reviewer consent codex # once per repository, as its owner: the material may leave the machine
68
+
69
+ disensor round --gate diff --generator-family anthropic --generator-model <your-model> --base main --head HEAD --result ../result.json
70
+ disensor new --gate diff --level B --round ../result.json
71
+ # fill in what the template left as FILL_IN; `disensor guide` says how
72
+ disensor validate .residue/<id>.json
73
+ git add .residue && git commit -m residue-declaration
74
+ disensor gate --no-comment --base main --head HEAD # what CI will run; green writes the report
75
+ disensor report --open
76
+ ```
77
+
78
+ The two commits are part of the path: the round reviews commits and asks for a
79
+ clean tree, and the gate reads the declaration from a commit, not from the
80
+ working tree. The last command opens the residue report in the browser, with
81
+ what the round left open first and the coverage in grey. Driving the round by
82
+ hand, the hashes and the rest of the commands are in
83
+ [Command reference](#command-reference). This repository carries its own
84
+ declarations, so `disensor report --open` on a clone of it shows a real report,
85
+ and [disensor.dev/demo](https://disensor.dev/demo/) walks through a finished
86
+ round without installing anything.
87
+
88
+ Three things here can be checked instead of believed. This repository goes
89
+ through its own gate: its pull requests carry their declarations under
90
+ [`.residue/`](https://github.com/NicolasRocchia/disensor/tree/main/.residue), and [CI](https://github.com/NicolasRocchia/disensor/blob/main/.github/workflows/ci.yml) runs this Action on them. An external
91
+ reader cloned the v0.9.4 tag and ran both implementations cold, 89 vectors and
92
+ 28 ordinality cases with zero divergences
93
+ ([message of 31 August 2026 on the W3C public-agent-conformance list](https://lists.w3.org/Archives/Public/public-agent-conformance/2026Aug/0006.html));
94
+ that is one reader's run, not an endorsement by the group. And the method is
95
+ published with a DOI, [10.5281/zenodo.21633495](https://doi.org/10.5281/zenodo.21633495).
96
+
97
+ ## The method
98
+
50
99
  The method behind it is **controlled disagreement**: one model generates, a
51
100
  model from another family attacks, the generator verifies every finding, and
52
101
  the cycle ends when each finding has been resolved, refuted with evidence, or
@@ -194,9 +243,11 @@ field-by-field guide is `disensor guide`.
194
243
  - `docs/integracion-claude-code.md` (Spanish only): how the real flow (Claude Code plus a reviewer from another family) emits the artifact at the close of each event.
195
244
  - `docs/antecedentes.md` (Spanish only): where the method sits relative to the literature (residual doubt and defeaters, design rationale and its capture bottleneck, multi-agent adversarial review, governance runtimes, supply chain provenance), with the verification status of each reference.
196
245
 
197
- ## Quick start
246
+ ## Command reference
198
247
 
199
- The package is installed once (globally); each repository is initialised once:
248
+ Every command in one place, with both ways of running the round: orchestrated
249
+ (`round`, then `new --round`) and by hand (`prompt` or `pack`, then `new`). The
250
+ package is installed once (globally); each repository is initialised once:
200
251
 
201
252
  ```bash
202
253
  pip install disensor # or pipx install disensor, recommended for CLIs
@@ -238,8 +289,12 @@ disensor prompt --gate diff # the brief, to the reviewer from another f
238
289
  disensor new --gate diff --level B # and you fill the declaration with what happened
239
290
  disensor validate .residue/<id>.json
240
291
  disensor gate --no-comment --base <base-sha> --head HEAD
292
+ disensor report --open # the residue report the green gate just wrote
241
293
  ```
242
294
 
295
+ A green gate writes `informe-residuo.html` at the repository root on its own;
296
+ `disensor report --open` writes it again and opens it in the browser.
297
+
243
298
  Only when you want it to **enforce** do you run the full `disensor init` (which
244
299
  writes the workflow) and apply the deployment requirements below. Before that it
245
300
  is a tool that tells you how you would do; after that it is a control that
@@ -277,10 +332,10 @@ jobs:
277
332
  gate:
278
333
  runs-on: ubuntu-latest
279
334
  steps:
280
- - uses: actions/checkout@v4
335
+ - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
281
336
  with:
282
337
  fetch-depth: 0
283
- - uses: NicolasRocchia/disensor@v0.14.0
338
+ - uses: NicolasRocchia/disensor@v0.16.0
284
339
  ```
285
340
 
286
341
  The gate validates the declarations **the PR adds**, applies the policy and
@@ -301,6 +356,7 @@ models by hand.
301
356
  disensor reviewer suggest # what this machine has, offline
302
357
  disensor reviewer add codex --model <model> --yes # once per machine, with a model your account runs
303
358
  disensor reviewer login codex # once, as the owner: the isolated home of the reviewer signs in
359
+ disensor reviewer consent codex # once per repository, as the owner: its material may leave the machine
304
360
 
305
361
  disensor round --gate diff --generator-family anthropic \
306
362
  --base main --head HEAD --result ../result.json
@@ -331,6 +387,48 @@ That home needs its own credentials, so `disensor reviewer login codex` runs
331
387
  the CLI's login there once, with your terminal; disensor never reads, copies
332
388
  or stores credentials, and it checks that home on disk before every attempt.
333
389
 
390
+ **Registering is not consenting.** `reviewer add --yes` registers a reviewer
391
+ and authorises nothing: the material of a repository leaves the machine only
392
+ after the owner runs `disensor reviewer consent <id>` from that repository,
393
+ and that consent covers that repository, that recipe and those executable
394
+ bytes. An agent does not give it. The catalogued `ollama` asks for it too: a
395
+ model served on this machine sends nothing out, but `ollama run <model>:cloud`
396
+ and an `OLLAMA_HOST` that points at another server do, and the runner cannot
397
+ tell them apart from the command. Only an entry you register by hand with
398
+ `--egress local` runs without consent, and that claim is yours. The registry records how each consent was
399
+ given: when, with which disensor, and whether standard input and output were
400
+ a terminal. The round prints that every time it uses the consent, its result
401
+ carries it, `new --round` puts it in the declaration and the report shows it.
402
+ It records what the process saw, not who typed: an agent that drives a real
403
+ terminal looks like the owner, a terminal that talks through pipes (mintty
404
+ without winpty) looks like none, and whoever can write `~/.disensor` can
405
+ write the record. What it buys is that a consent given from a script or from
406
+ an agent's tool no longer leaves the same record as one a person typed
407
+ ([#84](https://github.com/NicolasRocchia/disensor/issues/84)).
408
+
409
+ **A reviewer that cannot run git still sees the change.** In a diff round the
410
+ package names the range, and an agentic reviewer like `codex` reads it with git
411
+ itself. A chat model cannot: handed only the range, it answers anyway, and the
412
+ round would close on a change nobody saw
413
+ ([#152](https://github.com/NicolasRocchia/disensor/issues/152)). So each recipe
414
+ says how it gets the material: `codex` is `agentic`; `ollama`, `claude`,
415
+ `gemini` and any entry you register by hand are `inline`, and the diff travels
416
+ inside their package, made with `git diff-tree` so your diff configuration does
417
+ not change it, with its hash in the result and the declaration
418
+ (`material_hash`). An entry of yours that does read the range is registered
419
+ with `--material agentic`. A package with material inside (that diff, a plan,
420
+ an architecture decision) has two limits, both checked before anything is sent.
421
+ One is the model's context: a backend can cut a long prompt without saying so,
422
+ as `ollama` does with its `num_ctx`, and the round cannot see the cut, so
423
+ `ollama` and any entry of yours take no such package until you register them
424
+ with `--max-inline-bytes N`, what fits in the model's context window with room
425
+ for the answer. The other is the system's: a recipe that passes the package as
426
+ an argument cannot exceed the command line (32 767 characters on Windows,
427
+ quoting included), and on Windows a `.cmd` or `.bat` launcher never gets it,
428
+ because cmd.exe cuts an argument at its first line break. A reviewer that does
429
+ not fit is skipped and the chain moves on; if none fits, the round exits with
430
+ `4` and says why.
431
+
334
432
  **What runs alone, and where you come in.** The runner asks the policy whether a
335
433
  round is required at all (a change that only touches exempt paths does not spend
336
434
  a token), refuses to run on a dirty tree, picks the most independent reviewer
@@ -363,6 +461,15 @@ same reviewer (Codex, `gpt-5.6-sol`) on this repository's own pull requests.
363
461
  from `.residue/`, not a total, and a test compares them with the declarations
364
462
  up to that date.
365
463
 
464
+ **Plan and architecture rounds.** They review a document, not a range, and they
465
+ still ask for a clean tree: the runner checks that the reviewer wrote nothing by
466
+ comparing the tree before and after, so the plan is committed or kept outside
467
+ the repository. Their criticality level comes from the configuration: the one at
468
+ `--base` when it is given, the one at `HEAD` otherwise. At Level A the chain is
469
+ cut down to cross-family reviewers with verified hardening before anything is
470
+ spent. That filter saves a round; the control is still the rule on the
471
+ declaration and the gate with the policy of the target.
472
+
366
473
  **When there is no second family.** The method wants a reviewer from another
367
474
  model family, and that is still what the policy demands at Level A. Below that,
368
475
  a round with the same model and no context is a declarable degraded mode: the
@@ -371,6 +478,27 @@ and a residue item saying that the errors the model shares with itself were not
371
478
  covered. Worse than the real thing, and infinitely better than not being able to
372
479
  declare what happened.
373
480
 
481
+ With a single assistant, the reviewer is your own model with a fresh context,
482
+ and two names make that true in the record: register the reviewer with your
483
+ model's full name, and pass that same name to the round as
484
+ `--generator-model`.
485
+
486
+ ```bash
487
+ disensor reviewer add claude --model claude-opus-5-5 --yes # your own model, by its full name
488
+ disensor reviewer consent claude # once per repository, as the owner
489
+ disensor round --gate diff --generator-family anthropic --generator-model claude-opus-5-5 \
490
+ --base main --head HEAD --result ../result.json
491
+ ```
492
+
493
+ The `claude` and `gemini` recipes put that model in the argv, as `codex` does,
494
+ so what the declaration names is what ran; an entry registered before 0.15
495
+ does not, and the round leaves it out with the command to register it again.
496
+ The round compares the two names literally: the same name is
497
+ `same_model_fresh_context`, and an alias (`opus`) reads as another model.
498
+ Without `--generator-model` the round cannot tell the two apart: it records a
499
+ reviewer of your family as your own model, the least independence it can
500
+ claim, and says so ([#79](https://github.com/NicolasRocchia/disensor/issues/79)).
501
+
374
502
  ## The residue report
375
503
 
376
504
  `disensor report` reads the declarations and writes one self-contained HTML
@@ -461,7 +589,7 @@ Per PR:
461
589
 
462
590
  - **G1**: if the PR touches paths that require review, it adds at least one valid declaration.
463
591
  - **G6, coverage**: every changed path is covered by a declaration whose gate the scope policy accepts for that path, and which **qualifies** for it, meaning the path did not change between the reviewed commit and the head. A stale declaration covers nothing.
464
- - **G7, integration witness**: some declaration saw the complete final tree. Path-by-path coverage is not enough: two side branches reviewed separately and later merged cover every path between them while nobody reviewed the integration.
592
+ - **G7, integration witness**: some declaration saw the complete final tree. Path-by-path coverage is not enough: two side branches reviewed separately and later merged cover every path between them while nobody reviewed the integration. The witness has to have seen every path the scope policy demands a review for; a later change to a path the policy exempts does not unseat it.
465
593
  - **G8, evidence is append-only**: a PR cannot modify, delete or rename declarations that were already there, nor reuse an existing `event_id`.
466
594
  - **G9, new declarations state the current version**: a declaration the PR adds has to declare `residue/v0.4`. Superseded versions are still read so that history is not rewritten; that readability is not a permit to keep emitting under the weaker rules. The evidence plane applies the same criterion at ingestion.
467
595
 
@@ -528,10 +656,10 @@ This is a requirement, not a suggestion. The gate runs inside the workflow it
528
656
  audits, so there is a boundary no code of its own can cross and the platform has
529
657
  to resolve:
530
658
 
531
- - **Strict required check** (or merge queue) on `pull_request`, so that the check has to correspond to the latest head.
659
+ - **Strict required check** on `pull_request`, so that the check has to correspond to the latest head. The merge queue is not supported: on a `merge_group` event the gate exits 6 and says so, because the range of a merge group can gather several pull requests and G5 to G7 would be judged over commits no pull request gate saw together. A queue that requires this check does not advance.
532
660
  - **CODEOWNERS** over the effective configuration path (it may not be called `disensor.config.json` if `--config` is used) and over `.github/workflows/`.
533
661
  - **Organisation ruleset or required workflow**, defined outside the audited repository.
534
- - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys.
662
+ - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys. The `actions/checkout` step of that workflow is written pinned to a commit as well, since it runs in the same job before the gate; `disensor pin` does not move it and `init` does not rewrite a workflow that already exists, so keeping it current is the job of a Dependabot entry for `github-actions`. The SHA freezes what the Action installs too: its dependencies come from `requirements-action.txt`, a lock with the hash of every file, as wheels only and into a venv of its own, and disensor builds with the locked setuptools, so nothing is resolved at run time. The `python-version` input takes CPython 3.10 or later with a wheel for every locked dependency; today 3.13 free-threaded and 3.10 on Windows ARM have none. disensor is not left installed in the job's Python.
535
663
  - **Secret scanning with push protection** on the repository that hosts `.residue/`: evidence quotes real material and lives in git forever, and the validator checks shape, not meaning, so nothing of disensor's own will catch a pasted credential. Detection belongs to the platform; the remedy for a leaked secret is rotation, not deletion ([#14](https://github.com/NicolasRocchia/disensor/issues/14)).
536
664
  - **Bootstrap**: the first PR that adds the config and the workflow cannot make itself the root of trust. Initial activation is an administrative step, prior to the gate meaning anything.
537
665
  - **When the pin goes up**: the workflow sits in the non-relaxable floor, so raising the pin through a PR costs an adversarial round for a change whose correctness a `git rev-parse` verifies better than any model. The convention in this repository is that a new pin **travels in the next PR of real work**, with its declaration, rather than in a PR of its own. **Exception**: if the release fixes gate security or changes the schema version, the pin goes up immediately, because the window in which the repository judges itself with the previous version stops being harmless: an old gate does not know the new contract and rejects what the freshly published CLI emits. This is a convention, not a control: as long as the branch does not require pull requests with bypass disabled for administrators too, nothing prevents pushing the pin directly ([#17](https://github.com/NicolasRocchia/disensor/issues/17)).
@@ -559,10 +687,13 @@ run Python over a checkout of the repository can host it. It takes four things:
559
687
  be read from an older commit than the tip of the target.
560
688
  - **The whole history**, the equivalent of `fetch-depth: 0`: without it there
561
689
  is no merge base and the gate fails closed. In GitLab, `GIT_DEPTH: "0"`.
562
- - **`--no-comment`, and the verdict by exit code**: 0 is green, and 1 is red or
563
- a gate that could not decide. The body the comment would carry goes to
564
- stdout, and on a green verdict `--report-out <file>` writes the HTML report
565
- where the CI can archive it.
690
+ - **`--no-comment`, and the verdict by exit code**: 0 is green, 1 is red (the
691
+ gate judged the change and a check failed) and 6 is a gate that could not
692
+ decide (no range, a commit it cannot find, a shallow clone without the merge
693
+ base, a policy on the target it cannot read, or a crash). Both fail closed;
694
+ a 1 asks for work on the change and a 6 for work on the CI. The body the
695
+ comment would carry goes to stdout, and on a green verdict
696
+ `--report-out <file>` writes the HTML report where the CI can archive it.
566
697
  - **The same deployment requirements, under the names each platform gives
567
698
  them**: a required check that runs on the head of every change, the
568
699
  configuration and the pipeline definition owned outside the audited
@@ -675,7 +806,8 @@ things.
675
806
  exhausted, `5` tree modified during the round, `6` could not decide whether a
676
807
  round was required), and the three of them that `disensor round --check`
677
808
  answers with (`0` a round is required, `3` it is not, `6` it could not be
678
- decided); the subcommands and flags documented in this file; the four
809
+ decided); those of `disensor gate` (`0` green, `1` red, `6` could not decide);
810
+ the subcommands and flags documented in this file; the four
679
811
  inputs of the Action (`github-token`, `directory`, `config`, `python-version`);
680
812
  and the keys of `disensor.config.json`, which already fail closed on anything
681
813
  unknown. Breaking these needs a major.
@@ -846,7 +978,7 @@ it says.
846
978
 
847
979
  ## Status
848
980
 
849
- v0.14.0, on **residue/v0.4**. What each version changed is in
981
+ v0.16.0, on **residue/v0.4**. What each version changed is in
850
982
  [CHANGELOG.md](https://github.com/NicolasRocchia/disensor/blob/main/CHANGELOG.md),
851
983
  newest first.
852
984
 
@@ -21,6 +21,55 @@ scrutiny instead of reading as a seal of quality. A CLI validates it, and a CI
21
21
  gate stops the pull request when the change calls for a record and the record
22
22
  is missing, generic, or does not match the change the pull request makes.
23
23
 
24
+ The limit, said once: the machine checks the shape and the coherence of the
25
+ record, not whether it is true. A made-up declaration with the right shape
26
+ passes, and human sampling is the only thing that catches it.
27
+
28
+ ## Quick start
29
+
30
+ One path, from nothing to the report. It needs a git repository with a branch
31
+ to review and a second assistant on this machine: the example registers Codex,
32
+ and `disensor reviewer suggest` lists what yours has.
33
+
34
+ ```bash
35
+ pip install disensor
36
+ disensor init --no-workflow # config, CLAUDE.md and skill; nothing under .github/
37
+ git add .claude .gitignore CLAUDE.md disensor.config.json && git commit -m disensor-init
38
+
39
+ disensor reviewer add codex --model <model> --yes # once per machine, with a model your account runs
40
+ disensor reviewer login codex # once: the isolated home of the reviewer signs in
41
+ disensor reviewer consent codex # once per repository, as its owner: the material may leave the machine
42
+
43
+ disensor round --gate diff --generator-family anthropic --generator-model <your-model> --base main --head HEAD --result ../result.json
44
+ disensor new --gate diff --level B --round ../result.json
45
+ # fill in what the template left as FILL_IN; `disensor guide` says how
46
+ disensor validate .residue/<id>.json
47
+ git add .residue && git commit -m residue-declaration
48
+ disensor gate --no-comment --base main --head HEAD # what CI will run; green writes the report
49
+ disensor report --open
50
+ ```
51
+
52
+ The two commits are part of the path: the round reviews commits and asks for a
53
+ clean tree, and the gate reads the declaration from a commit, not from the
54
+ working tree. The last command opens the residue report in the browser, with
55
+ what the round left open first and the coverage in grey. Driving the round by
56
+ hand, the hashes and the rest of the commands are in
57
+ [Command reference](#command-reference). This repository carries its own
58
+ declarations, so `disensor report --open` on a clone of it shows a real report,
59
+ and [disensor.dev/demo](https://disensor.dev/demo/) walks through a finished
60
+ round without installing anything.
61
+
62
+ Three things here can be checked instead of believed. This repository goes
63
+ through its own gate: its pull requests carry their declarations under
64
+ [`.residue/`](https://github.com/NicolasRocchia/disensor/tree/main/.residue), and [CI](https://github.com/NicolasRocchia/disensor/blob/main/.github/workflows/ci.yml) runs this Action on them. An external
65
+ reader cloned the v0.9.4 tag and ran both implementations cold, 89 vectors and
66
+ 28 ordinality cases with zero divergences
67
+ ([message of 31 August 2026 on the W3C public-agent-conformance list](https://lists.w3.org/Archives/Public/public-agent-conformance/2026Aug/0006.html));
68
+ that is one reader's run, not an endorsement by the group. And the method is
69
+ published with a DOI, [10.5281/zenodo.21633495](https://doi.org/10.5281/zenodo.21633495).
70
+
71
+ ## The method
72
+
24
73
  The method behind it is **controlled disagreement**: one model generates, a
25
74
  model from another family attacks, the generator verifies every finding, and
26
75
  the cycle ends when each finding has been resolved, refuted with evidence, or
@@ -168,9 +217,11 @@ field-by-field guide is `disensor guide`.
168
217
  - `docs/integracion-claude-code.md` (Spanish only): how the real flow (Claude Code plus a reviewer from another family) emits the artifact at the close of each event.
169
218
  - `docs/antecedentes.md` (Spanish only): where the method sits relative to the literature (residual doubt and defeaters, design rationale and its capture bottleneck, multi-agent adversarial review, governance runtimes, supply chain provenance), with the verification status of each reference.
170
219
 
171
- ## Quick start
220
+ ## Command reference
172
221
 
173
- The package is installed once (globally); each repository is initialised once:
222
+ Every command in one place, with both ways of running the round: orchestrated
223
+ (`round`, then `new --round`) and by hand (`prompt` or `pack`, then `new`). The
224
+ package is installed once (globally); each repository is initialised once:
174
225
 
175
226
  ```bash
176
227
  pip install disensor # or pipx install disensor, recommended for CLIs
@@ -212,8 +263,12 @@ disensor prompt --gate diff # the brief, to the reviewer from another f
212
263
  disensor new --gate diff --level B # and you fill the declaration with what happened
213
264
  disensor validate .residue/<id>.json
214
265
  disensor gate --no-comment --base <base-sha> --head HEAD
266
+ disensor report --open # the residue report the green gate just wrote
215
267
  ```
216
268
 
269
+ A green gate writes `informe-residuo.html` at the repository root on its own;
270
+ `disensor report --open` writes it again and opens it in the browser.
271
+
217
272
  Only when you want it to **enforce** do you run the full `disensor init` (which
218
273
  writes the workflow) and apply the deployment requirements below. Before that it
219
274
  is a tool that tells you how you would do; after that it is a control that
@@ -251,10 +306,10 @@ jobs:
251
306
  gate:
252
307
  runs-on: ubuntu-latest
253
308
  steps:
254
- - uses: actions/checkout@v4
309
+ - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
255
310
  with:
256
311
  fetch-depth: 0
257
- - uses: NicolasRocchia/disensor@v0.14.0
312
+ - uses: NicolasRocchia/disensor@v0.16.0
258
313
  ```
259
314
 
260
315
  The gate validates the declarations **the PR adds**, applies the policy and
@@ -275,6 +330,7 @@ models by hand.
275
330
  disensor reviewer suggest # what this machine has, offline
276
331
  disensor reviewer add codex --model <model> --yes # once per machine, with a model your account runs
277
332
  disensor reviewer login codex # once, as the owner: the isolated home of the reviewer signs in
333
+ disensor reviewer consent codex # once per repository, as the owner: its material may leave the machine
278
334
 
279
335
  disensor round --gate diff --generator-family anthropic \
280
336
  --base main --head HEAD --result ../result.json
@@ -305,6 +361,48 @@ That home needs its own credentials, so `disensor reviewer login codex` runs
305
361
  the CLI's login there once, with your terminal; disensor never reads, copies
306
362
  or stores credentials, and it checks that home on disk before every attempt.
307
363
 
364
+ **Registering is not consenting.** `reviewer add --yes` registers a reviewer
365
+ and authorises nothing: the material of a repository leaves the machine only
366
+ after the owner runs `disensor reviewer consent <id>` from that repository,
367
+ and that consent covers that repository, that recipe and those executable
368
+ bytes. An agent does not give it. The catalogued `ollama` asks for it too: a
369
+ model served on this machine sends nothing out, but `ollama run <model>:cloud`
370
+ and an `OLLAMA_HOST` that points at another server do, and the runner cannot
371
+ tell them apart from the command. Only an entry you register by hand with
372
+ `--egress local` runs without consent, and that claim is yours. The registry records how each consent was
373
+ given: when, with which disensor, and whether standard input and output were
374
+ a terminal. The round prints that every time it uses the consent, its result
375
+ carries it, `new --round` puts it in the declaration and the report shows it.
376
+ It records what the process saw, not who typed: an agent that drives a real
377
+ terminal looks like the owner, a terminal that talks through pipes (mintty
378
+ without winpty) looks like none, and whoever can write `~/.disensor` can
379
+ write the record. What it buys is that a consent given from a script or from
380
+ an agent's tool no longer leaves the same record as one a person typed
381
+ ([#84](https://github.com/NicolasRocchia/disensor/issues/84)).
382
+
383
+ **A reviewer that cannot run git still sees the change.** In a diff round the
384
+ package names the range, and an agentic reviewer like `codex` reads it with git
385
+ itself. A chat model cannot: handed only the range, it answers anyway, and the
386
+ round would close on a change nobody saw
387
+ ([#152](https://github.com/NicolasRocchia/disensor/issues/152)). So each recipe
388
+ says how it gets the material: `codex` is `agentic`; `ollama`, `claude`,
389
+ `gemini` and any entry you register by hand are `inline`, and the diff travels
390
+ inside their package, made with `git diff-tree` so your diff configuration does
391
+ not change it, with its hash in the result and the declaration
392
+ (`material_hash`). An entry of yours that does read the range is registered
393
+ with `--material agentic`. A package with material inside (that diff, a plan,
394
+ an architecture decision) has two limits, both checked before anything is sent.
395
+ One is the model's context: a backend can cut a long prompt without saying so,
396
+ as `ollama` does with its `num_ctx`, and the round cannot see the cut, so
397
+ `ollama` and any entry of yours take no such package until you register them
398
+ with `--max-inline-bytes N`, what fits in the model's context window with room
399
+ for the answer. The other is the system's: a recipe that passes the package as
400
+ an argument cannot exceed the command line (32 767 characters on Windows,
401
+ quoting included), and on Windows a `.cmd` or `.bat` launcher never gets it,
402
+ because cmd.exe cuts an argument at its first line break. A reviewer that does
403
+ not fit is skipped and the chain moves on; if none fits, the round exits with
404
+ `4` and says why.
405
+
308
406
  **What runs alone, and where you come in.** The runner asks the policy whether a
309
407
  round is required at all (a change that only touches exempt paths does not spend
310
408
  a token), refuses to run on a dirty tree, picks the most independent reviewer
@@ -337,6 +435,15 @@ same reviewer (Codex, `gpt-5.6-sol`) on this repository's own pull requests.
337
435
  from `.residue/`, not a total, and a test compares them with the declarations
338
436
  up to that date.
339
437
 
438
+ **Plan and architecture rounds.** They review a document, not a range, and they
439
+ still ask for a clean tree: the runner checks that the reviewer wrote nothing by
440
+ comparing the tree before and after, so the plan is committed or kept outside
441
+ the repository. Their criticality level comes from the configuration: the one at
442
+ `--base` when it is given, the one at `HEAD` otherwise. At Level A the chain is
443
+ cut down to cross-family reviewers with verified hardening before anything is
444
+ spent. That filter saves a round; the control is still the rule on the
445
+ declaration and the gate with the policy of the target.
446
+
340
447
  **When there is no second family.** The method wants a reviewer from another
341
448
  model family, and that is still what the policy demands at Level A. Below that,
342
449
  a round with the same model and no context is a declarable degraded mode: the
@@ -345,6 +452,27 @@ and a residue item saying that the errors the model shares with itself were not
345
452
  covered. Worse than the real thing, and infinitely better than not being able to
346
453
  declare what happened.
347
454
 
455
+ With a single assistant, the reviewer is your own model with a fresh context,
456
+ and two names make that true in the record: register the reviewer with your
457
+ model's full name, and pass that same name to the round as
458
+ `--generator-model`.
459
+
460
+ ```bash
461
+ disensor reviewer add claude --model claude-opus-5-5 --yes # your own model, by its full name
462
+ disensor reviewer consent claude # once per repository, as the owner
463
+ disensor round --gate diff --generator-family anthropic --generator-model claude-opus-5-5 \
464
+ --base main --head HEAD --result ../result.json
465
+ ```
466
+
467
+ The `claude` and `gemini` recipes put that model in the argv, as `codex` does,
468
+ so what the declaration names is what ran; an entry registered before 0.15
469
+ does not, and the round leaves it out with the command to register it again.
470
+ The round compares the two names literally: the same name is
471
+ `same_model_fresh_context`, and an alias (`opus`) reads as another model.
472
+ Without `--generator-model` the round cannot tell the two apart: it records a
473
+ reviewer of your family as your own model, the least independence it can
474
+ claim, and says so ([#79](https://github.com/NicolasRocchia/disensor/issues/79)).
475
+
348
476
  ## The residue report
349
477
 
350
478
  `disensor report` reads the declarations and writes one self-contained HTML
@@ -435,7 +563,7 @@ Per PR:
435
563
 
436
564
  - **G1**: if the PR touches paths that require review, it adds at least one valid declaration.
437
565
  - **G6, coverage**: every changed path is covered by a declaration whose gate the scope policy accepts for that path, and which **qualifies** for it, meaning the path did not change between the reviewed commit and the head. A stale declaration covers nothing.
438
- - **G7, integration witness**: some declaration saw the complete final tree. Path-by-path coverage is not enough: two side branches reviewed separately and later merged cover every path between them while nobody reviewed the integration.
566
+ - **G7, integration witness**: some declaration saw the complete final tree. Path-by-path coverage is not enough: two side branches reviewed separately and later merged cover every path between them while nobody reviewed the integration. The witness has to have seen every path the scope policy demands a review for; a later change to a path the policy exempts does not unseat it.
439
567
  - **G8, evidence is append-only**: a PR cannot modify, delete or rename declarations that were already there, nor reuse an existing `event_id`.
440
568
  - **G9, new declarations state the current version**: a declaration the PR adds has to declare `residue/v0.4`. Superseded versions are still read so that history is not rewritten; that readability is not a permit to keep emitting under the weaker rules. The evidence plane applies the same criterion at ingestion.
441
569
 
@@ -502,10 +630,10 @@ This is a requirement, not a suggestion. The gate runs inside the workflow it
502
630
  audits, so there is a boundary no code of its own can cross and the platform has
503
631
  to resolve:
504
632
 
505
- - **Strict required check** (or merge queue) on `pull_request`, so that the check has to correspond to the latest head.
633
+ - **Strict required check** on `pull_request`, so that the check has to correspond to the latest head. The merge queue is not supported: on a `merge_group` event the gate exits 6 and says so, because the range of a merge group can gather several pull requests and G5 to G7 would be judged over commits no pull request gate saw together. A queue that requires this check does not advance.
506
634
  - **CODEOWNERS** over the effective configuration path (it may not be called `disensor.config.json` if `--config` is used) and over `.github/workflows/`.
507
635
  - **Organisation ruleset or required workflow**, defined outside the audited repository.
508
- - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys.
636
+ - **Pin the Action by SHA**, not by tag: a tag is movable and is not a root of trust. `disensor init` resolves the tag of the installed version to the commit it points at and writes the workflow already frozen; without network at init time the tag stays and `disensor pin` finishes the job. The command resolves annotated tags to the commit they wrap, never to the tag object, which is the classic trap of doing it by hand. This repository's documentation still uses the tag, because it documents which version corresponds; the frozen SHA is produced by whoever deploys. The `actions/checkout` step of that workflow is written pinned to a commit as well, since it runs in the same job before the gate; `disensor pin` does not move it and `init` does not rewrite a workflow that already exists, so keeping it current is the job of a Dependabot entry for `github-actions`. The SHA freezes what the Action installs too: its dependencies come from `requirements-action.txt`, a lock with the hash of every file, as wheels only and into a venv of its own, and disensor builds with the locked setuptools, so nothing is resolved at run time. The `python-version` input takes CPython 3.10 or later with a wheel for every locked dependency; today 3.13 free-threaded and 3.10 on Windows ARM have none. disensor is not left installed in the job's Python.
509
637
  - **Secret scanning with push protection** on the repository that hosts `.residue/`: evidence quotes real material and lives in git forever, and the validator checks shape, not meaning, so nothing of disensor's own will catch a pasted credential. Detection belongs to the platform; the remedy for a leaked secret is rotation, not deletion ([#14](https://github.com/NicolasRocchia/disensor/issues/14)).
510
638
  - **Bootstrap**: the first PR that adds the config and the workflow cannot make itself the root of trust. Initial activation is an administrative step, prior to the gate meaning anything.
511
639
  - **When the pin goes up**: the workflow sits in the non-relaxable floor, so raising the pin through a PR costs an adversarial round for a change whose correctness a `git rev-parse` verifies better than any model. The convention in this repository is that a new pin **travels in the next PR of real work**, with its declaration, rather than in a PR of its own. **Exception**: if the release fixes gate security or changes the schema version, the pin goes up immediately, because the window in which the repository judges itself with the previous version stops being harmless: an old gate does not know the new contract and rejects what the freshly published CLI emits. This is a convention, not a control: as long as the branch does not require pull requests with bypass disabled for administrators too, nothing prevents pushing the pin directly ([#17](https://github.com/NicolasRocchia/disensor/issues/17)).
@@ -533,10 +661,13 @@ run Python over a checkout of the repository can host it. It takes four things:
533
661
  be read from an older commit than the tip of the target.
534
662
  - **The whole history**, the equivalent of `fetch-depth: 0`: without it there
535
663
  is no merge base and the gate fails closed. In GitLab, `GIT_DEPTH: "0"`.
536
- - **`--no-comment`, and the verdict by exit code**: 0 is green, and 1 is red or
537
- a gate that could not decide. The body the comment would carry goes to
538
- stdout, and on a green verdict `--report-out <file>` writes the HTML report
539
- where the CI can archive it.
664
+ - **`--no-comment`, and the verdict by exit code**: 0 is green, 1 is red (the
665
+ gate judged the change and a check failed) and 6 is a gate that could not
666
+ decide (no range, a commit it cannot find, a shallow clone without the merge
667
+ base, a policy on the target it cannot read, or a crash). Both fail closed;
668
+ a 1 asks for work on the change and a 6 for work on the CI. The body the
669
+ comment would carry goes to stdout, and on a green verdict
670
+ `--report-out <file>` writes the HTML report where the CI can archive it.
540
671
  - **The same deployment requirements, under the names each platform gives
541
672
  them**: a required check that runs on the head of every change, the
542
673
  configuration and the pipeline definition owned outside the audited
@@ -649,7 +780,8 @@ things.
649
780
  exhausted, `5` tree modified during the round, `6` could not decide whether a
650
781
  round was required), and the three of them that `disensor round --check`
651
782
  answers with (`0` a round is required, `3` it is not, `6` it could not be
652
- decided); the subcommands and flags documented in this file; the four
783
+ decided); those of `disensor gate` (`0` green, `1` red, `6` could not decide);
784
+ the subcommands and flags documented in this file; the four
653
785
  inputs of the Action (`github-token`, `directory`, `config`, `python-version`);
654
786
  and the keys of `disensor.config.json`, which already fail closed on anything
655
787
  unknown. Breaking these needs a major.
@@ -820,7 +952,7 @@ it says.
820
952
 
821
953
  ## Status
822
954
 
823
- v0.14.0, on **residue/v0.4**. What each version changed is in
955
+ v0.16.0, on **residue/v0.4**. What each version changed is in
824
956
  [CHANGELOG.md](https://github.com/NicolasRocchia/disensor/blob/main/CHANGELOG.md),
825
957
  newest first.
826
958
 
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "disensor"
7
- version = "0.14.0"
7
+ version = "0.16.0"
8
8
  description = "A versioned record of what an AI code review could not establish: a CLI and a CI gate that validate the residue declaration a cross-model adversarial review leaves in the repository."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
@@ -57,7 +57,12 @@ Los pasos 2, 4, 5 y 6 son los mismos en los dos caminos.
57
57
  Mandar el material a un revisor fuera de esta máquina necesita el consentimiento
58
58
  del dueño del repositorio, y un agente nunca lo da: no corre
59
59
  `disensor reviewer consent`. Cuando `disensor round` sale con 4 porque falta ese
60
- consentimiento, el agente se detiene y le pide al dueño que lo dé.
60
+ consentimiento, el agente se detiene y le pide al dueño que lo dé. El registro
61
+ guarda cómo se dio cada consentimiento (cuándo, con qué disensor, y si la
62
+ entrada y la salida estándar eran una terminal); la ronda lo muestra cada vez
63
+ que lo usa, y `new --round` lo lleva como `consent` bajo
64
+ `extensions["dev.disensor.round"]`. Es lo que vio el proceso, no quién lo
65
+ tipeó.
61
66
 
62
67
  Declará lo que pasó, no lo que debería haber pasado. Un evento sin hallazgos y
63
68
  con una declaración expresa de ausencia es un dato válido, no un fracaso.
@@ -98,7 +103,14 @@ Por defecto todo exige `diff`.
98
103
  (por qué la ronda se conformó con menos) y un ítem de residuo de clase
99
104
  `reviewer_correlation` que nombre a ese revisor: los errores que un modelo
100
105
  comparte consigo mismo no los cubrió esta ronda, y eso es residuo. El nivel A
101
- no lo admite.
106
+ no lo admite. Con `disensor round` se calcula, no se elige: otra familia es
107
+ `cross_family`; la familia del generador con otro nombre de modelo,
108
+ `same_family_distinct_model`; un revisor registrado con el nombre que se
109
+ pasó como `--generator-model`, `same_model_fresh_context`. La comparación es
110
+ literal, así que pasá el nombre exacto del modelo, el mismo con que se
111
+ registró el revisor: sin `--generator-model` un revisor de tu familia queda
112
+ registrado como tu propio modelo, la menor independencia que la ronda puede
113
+ afirmar, y la ronda avisa.
102
114
  - `reviewers[].hardening`: `verified` si el revisor corrió por un adaptador
103
115
  que neutraliza, para versiones y condiciones concretas, las fuentes
104
116
  enumeradas que el CLI carga solo antes de tu consigna: los archivos de
@@ -266,7 +278,9 @@ booleano, `null`, o contenedores de esos) y toda clave tiene que tener forma de
266
278
  identificador: un nombre, no un mensaje. El espacio de extensión no lo
267
279
  interpretan las reglas a propósito, que es exactamente por qué el texto libre
268
280
  estacionado ahí sale del entorno igual que en cualquier otro lugar al que el
269
- perfil no llega.
281
+ perfil no llega. `new --round` lo cumple: en el perfil minimizado el `consent`
282
+ de su extensión conserva solo los booleanos, porque la fecha y la versión son
283
+ texto.
270
284
 
271
285
  ## Mapa rápido de las etiquetas del validador
272
286
 
@@ -53,7 +53,12 @@ run it. Steps 2, 4, 5 and 6 are the same on both paths.
53
53
  Sending the material to a reviewer outside this machine needs the consent of
54
54
  the owner of the repository, and an agent never gives it: it does not run
55
55
  `disensor reviewer consent`. When `disensor round` exits with 4 because that
56
- consent is missing, the agent stops and asks the owner to give it.
56
+ consent is missing, the agent stops and asks the owner to give it. The
57
+ registry records how each consent was given (when, with which disensor, and
58
+ whether standard input and output were a terminal); the round shows it every
59
+ time it uses it, and `new --round` carries it as `consent` under
60
+ `extensions["dev.disensor.round"]`. It is what the process saw, not who
61
+ typed it.
57
62
 
58
63
  Declare what happened, not what should have happened. An event without
59
64
  findings and with an express declaration of absence is valid data, not a
@@ -94,7 +99,14 @@ paths. By default everything demands `diff`.
94
99
  `fallback_reason` (why the round settled for less) and a residue item of
95
100
  class `reviewer_correlation` naming that reviewer: the errors a model shares
96
101
  with itself were not covered by the round, and that is residue. Level A does
97
- not admit it at all.
102
+ not admit it at all. With `disensor round` it is computed, not chosen:
103
+ another family is `cross_family`; the generator's family with a different
104
+ model name, `same_family_distinct_model`; a reviewer registered with the
105
+ name passed as `--generator-model`, `same_model_fresh_context`. The
106
+ comparison is literal, so pass the exact model name, the one the reviewer
107
+ was registered with: without `--generator-model` a reviewer of your family
108
+ is recorded as your own model, the least independence the round can claim,
109
+ and the round warns.
98
110
  - `reviewers[].hardening`: `verified` if the reviewer ran through an adapter
99
111
  that neutralises, for concrete CLI versions and conditions, the enumerated
100
112
  sources the CLI loads on its own before your brief: the instruction files
@@ -261,6 +273,8 @@ boolean, `null`, or containers of those) and every key must be identifier-shaped
261
273
  a name, not a message. The extension space is deliberately not interpreted
262
274
  by the rules, which is exactly why free text parked there leaves the
263
275
  environment as readily as anywhere else the profile does not reach.
276
+ `new --round` follows that: in the minimized profile the `consent` of its
277
+ extension keeps only its booleans, because the date and the version are text.
264
278
 
265
279
  ## Quick map of validator labels
266
280
 
@@ -1,2 +1,2 @@
1
1
  """disensor: residue declaration of adversarial review (controlled disagreement)."""
2
- __version__ = "0.14.0"
2
+ __version__ = "0.16.0"