Skip to content

feat(trust): a census over every config field, and the coverage it forces #543

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wenzowski merged 4 commits into from
Aug 20, 2026
Merged

feat(trust): a census over every config field, and the coverage it forces #543

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
caebfe1
test(trust): fail on any config field with no weakening verdict
wenzowski Aug 19, 2026
d697061
feat(trust): compare every config key the census demanded a verdict for
wenzowski Aug 19, 2026
c7a3392
test(trust): a both-directions case per compared key, and one that re…
wenzowski Aug 19, 2026
cde9916
refactor(trust): split the comparison in two so each half stays readable
wenzowski Aug 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion .serena/memories/core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -388,7 +388,16 @@ period (2)` in SCHEMA order — so the report never depends on the order the aut
expired, since the diff is a fact about two files and the lapse is the run's.
Pointer-only `Weakening`s (key path + two verdict tokens),
sorted so the report is byte-stable. `config lint` (CLOUD-87) reuses both
rather than growing a second trusted-load path.
rather than growing a second trusted-load path. **What is compared is a census,
not a habit (CLOUD-721)**: `CENSUS` carries a verdict per `Config` field —
compared (with its kinds), no monotone reading, or not policy-bearing, the last
two with the reason — and its test reads the field list off `config.rs`'s own
source, so a key added to the struct fails until somebody decides. `Rule`'s
predicate columns work the same way one level down: every column is compared as
a byte change (`RulePredicateChanged`, digest tokens, never a ranking of two
globs) unless `RULE_NON_PREDICATE` exempts it with a reason. `WaiverExpiryExtended`
is the pairing `Waiver::key` cannot see — same rule and path, expiry pushed out —
and stays date-independent by comparing one file's `expires` against the other's.
- `resolve.rs` — house-style §8 precedence resolver: `flag > env > local file >
repo config > default`, declared as data in `SETTINGS` (per-key env var/flag),
not hard-coded per field.
Expand Down
Loading
Loading