hypgraph 0.7.22__tar.gz → 0.7.24__tar.gz

{hypgraph-0.7.22 → hypgraph-0.7.24}/CHANGELOG.md

@@ -1,5 +1,72 @@
 # Changelog
 
+## 0.7.24 — 2026-11-01: what a quantifier needs, where a comparison's boundary falls, one check per extreme
+
+Fixes from an independent audit of 0.7.23 (HG-023-01 to -05); each case below failed on 0.7.23 and is now a test.
+
+- **"Nothing" needs none, "every" needs all** (HG-023-01). Any count of none or all backed an absolute, so "nothing
+  is longer than 26 km" went in with all 3 routes longer, and "every route is longer than 26 km" with none. When a
+  count's comparison is known, the claim now needs the extreme its quantifier names; the other extreme shows it false
+  (`COUNT_CONTRADICTS`). A count of what lies outside the claim's exceptions is read as its complement: none of 3
+  longer than 26 is 3 of 3 at 26 or shorter. "Every" in a clause that states its own count ("a count of every route
+  finds 1 of 76 shorter") names the set counted and is not read as a quantifier. A count whose comparison can't be
+  told ("failures") is read as before.
+- **"At least" is not "longer than"** (HG-023-02). Comparisons keep their boundary: `op` takes `<`, `<=`, `=`, `!=`,
+  `>=`, `>`, and names say "at least", "at most", "26 km or longer", "not / no shorter than", "no more than". A count
+  refutes a claim only if everything it found is an exception, and backs it only if it covers every exception: two
+  routes at least 26 km neither refute nor back "no route is longer than 26 km" (the routes of exactly 26 lie between),
+  and none longer than 26 doesn't back "no route is 26 km or longer". `=` and `!=` counts don't bear on a comparison.
+  "At least" used to be read as pointing down and "at most" up. "No route is 26 km or longer" and "no route is at
+  least 26 km" are absolutes too.
+- **Two extremes are two claims** (HG-023-03). "The shortest route is 26 km; the longest route is 35 km" pooled both
+  figures and both directions, and the count of 2 longer than 26 refused the true sentence. Each extreme, and each
+  thing an absolute rules out, is now checked with its own figure and direction; the refusal names the extreme it
+  found false.
+- **What "of" and "for" name says which thing** (HG-023-04). "Weights of cargo" and "weights of passengers" both read
+  as bare "weights", and "shipping cargo weights" met "shipping passenger weights" on one shared word. The object of
+  "of" / "for" now counts, and two subjects that each say something the other doesn't are left apart: unresolved, not
+  a contradiction. One that only adds to the other ("the recorded weights of cargo") is the same thing.
+- **A contrast keeps the unit it asserts** (HG-023-05). "Not in pounds but in kilograms" lost its kilograms, and
+  "kilograms rather than pounds" kept both, so a claim of pounds citing either went in. A clause with no subject or
+  verb of its own takes the subject its sentence named last ("… but always in kilograms"); one that names its own
+  ("and passenger weights in pounds") doesn't. What follows "rather than" / "instead of", up to its unit, is set aside.
+- Limits: subjects, units of record, quantifiers and comparisons are still read from words, not typed (only a count's
+  `figure` and `op` are); a missed contradiction is preferred to a false one, so subjects left apart are not
+  compared; conversions aren't checked; and the replay of earlier recorded entries changes nothing, which shows no
+  regression but none of those entries tries these cases.
+
+## 0.7.23 — 2026-11-01: a count points one way, "no route is longer", what a unit is said of
+
+Fixes from an independent audit of 0.7.22 (HG-022-01 to -05); each case below failed on 0.7.22 and is now a test.
+
+- **A count points one way** (HG-022-01, -02). A count of routes longer than 26 km matched "the shortest route is
+  26 km" on the figure, so the true claim was refused as `COUNT_CONTRADICTS`; and a count of none shorter than 26
+  backed "nothing is longer than 26 km". Comparisons now carry a direction on an axis ("longer" / "shorter",
+  "faster" / "slower"; "more", "above", "highest" meet any axis), and a count that points the other way from the
+  claim's exceptions neither refutes nor backs it. A result can state the comparison with the count
+  (`{"k": 2, "n": 3, "figure": 26, "op": ">"}`); that is the only direction, and a measurement whose name points the
+  other way is refused as `MEASUREMENT_MISMATCH`. Without one, a name and key that point opposite ways can widen what
+  a count refutes, never what it backs.
+- **"No route is longer than 26 km" is an absolute** (HG-022-02), like "nothing is longer": it needs a count of
+  exceptions. Only a "no" that opens its clause, followed within three words by a copula and a comparison, is read
+  this way ("routes that visit no town twice" is not one).
+- **A unit of record said with a verb** (HG-022-03). Only "is / are / was / were" stated a unit, so "recorded parcel
+  weights use pounds" went in beside the note that every recorded parcel weight is in kilograms. A short, fixed list
+  is read too: use, recorded / measured / expressed / given / listed / reported / denominated / kept / stated /
+  written / logged / entered / priced / quoted in. A hedge ("might be recorded in pounds") asserts nothing.
+- **Two things that share a word are two things** (HG-022-04). "Passenger weights are recorded in pounds" was refused
+  against a source saying shipping weights are in kilograms, on the word "weights". A unit is now compared only when
+  the two subjects have the same head and don't each carry modifiers the other lacks entirely; every clause of the
+  source is read, and one that says the claim's unit of that thing means no contradiction.
+- **A quantity is not a unit of record** (HG-022-05). "The parcel mass is about 2.2 pounds", citing "the parcel mass
+  is one kilogram", was refused: a unit after a number ("2.2 pounds", "one kilogram", "36 kg") is a quantity, and
+  isn't compared. The refusal no longer says a quantity can't be in two units; it says the source doesn't support the
+  statement.
+- Limits: which thing a subject names and which unit a record uses are read from words, not typed; conversions
+  aren't checked, so "2.2 pounds" against "50 kilograms" goes in; verbs outside the list aren't read; the "no X is
+  longer" pattern is narrow ("there is no route longer" isn't read); and a direction is read only from the comparison
+  words above.
+
 ## 0.7.22 — 2026-11-01: a label can't move a count, every part of a claim is checked, units rule each other out
 
 Fixes from an independent audit of 0.7.21 (HG-021-01 to -04); each case below failed on 0.7.21 and is now a test.

{hypgraph-0.7.22 → hypgraph-0.7.24}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hypgraph
-Version: 0.7.22
+Version: 0.7.24
 Summary: The evidence layer for AI research agents: a hash-chained research record that checks every claim as it is written and derives how well each is known.
 Project-URL: Homepage, https://hypgraph.com
 Project-URL: Documentation, https://hypgraph.com/engineers/

{hypgraph-0.7.22 → hypgraph-0.7.24}/docs/PLAN.md

@@ -109,7 +109,7 @@ claim's derived standing.
 Multi-writer sync between graphs (bundles cover sharing), authentication (the host's job; the HTTP server binds to
 loopback and is read-only unless started with `--writable`), and a hosted service.
 
-## Status at 0.7.22 (2026-11-01)
+## Status at 0.7.24 (2026-11-01)
 
 All seven phases are done: the library, bundles, the server and UI, the MCP server, the website, Pegasus running on
 the package, and releases to PyPI from tags with trusted publishing. What came after the plan, by release, is in

{hypgraph-0.7.22 → hypgraph-0.7.24}/docs/RELEASE-READINESS.md

@@ -114,6 +114,41 @@ was taken from a changelog without being checked against the code.*
 > suite is 482 passed, and hypswarm (118 passed) and hypmesh (37 passed) pass on it. The audit asks for a fresh
 > independent audit before anyone claims 0.7.22 resists these attack classes. Released as 0.7.22.
 
+> **Audit of 0.7.22 (2026-11-01), fixed for 0.7.23.** A third independent audit found five cases, each reproduced on
+> the 0.7.22 wheel. Two let a count stand for its opposite: a count of routes longer than 26 km refused the true "the
+> shortest route is 26 km" (HG-022-01), and none shorter than 26 backed "nothing / no route is longer than 26 km"
+> (HG-022-02). One let a unit claim in: "recorded parcel weights use pounds" stated no copula (HG-022-03). Two made
+> false accusations: "passenger weights" was matched with "shipping weights" on a shared word (HG-022-04), and a
+> quantity converted to another unit was read as a unit of record (HG-022-05). Comparisons now carry a direction, and
+> a result can state its comparison (`op`); "no X is longer than…" opening a clause is an absolute; a short fixed list
+> of verbs states a unit; units are compared only between subjects with the same head and compatible modifiers; a unit
+> after a number is a quantity. Each case is a regression test written to fail on 0.7.22. Replaying the 1,900
+> recorded adversarial entries names exactly the same parties as 0.7.22; one repeated false unit claim is no longer
+> refused, because 0.7.22 had refused it on a shared word and a quantity, and its author is still named.
+>
+> **Where that stands.** #87 is merged with green CI (17 of 17 checks); from the 0.7.23 wheel in a fresh venv the
+> suite is 504 passed, and hypswarm (118 passed) and hypmesh (37 passed) pass on it. Which thing a subject names and
+> which unit a record uses are still read from words, not typed; a fresh independent audit should precede any claim
+> that 0.7.23 resists these attack classes. Released as 0.7.23.
+
+> **Audit of 0.7.23 (2026-11-01), fixed for 0.7.24.** A fourth independent audit, a code review without running the
+> wheel, named five candidate defects; each reproduced on the PyPI 0.7.23 wheel, plus two of the same kind. A count of
+> none or all backed any absolute, so "nothing is longer than 26 km" went in with all routes longer and "every route
+> is longer" with none (HG-023-01). Comparisons lost their boundary, so a count at least 26 refuted the true "no route
+> is longer than 26" and "at least" was read as pointing down (HG-023-02). Two extremes in one sentence were pooled
+> and a true one refused (HG-023-03). "Weights of cargo" and "weights of passengers" read as one thing (HG-023-04),
+> and "not in pounds but in kilograms" lost its kilograms (HG-023-05). A claim now needs the extreme its quantifier
+> names; comparisons keep their boundary across six operators; each extreme is checked on its own; the object of "of"
+> / "for" says which thing, and subjects that each say something the other doesn't are left apart, unresolved; a
+> contrast keeps its unit. Each case is a regression test written to fail on 0.7.23. Replaying the 1,900 recorded
+> adversarial entries changes nothing against 0.7.23 (a first version over-read "a count of every route" and named
+> one honest party wrongly; caught by the replay, fixed and tested), but none of those entries tries these cases.
+>
+> **Where that stands.** #89 is merged with green CI (17 of 17 checks); from the 0.7.24 wheel in a fresh venv the
+> suite is 549 passed, and hypswarm (118 passed) and hypmesh (37 passed) pass on it. The audit recommends a typed
+> claim layer (subject, property, comparator, threshold, unit, quantifier) so that strong verdicts rest on typed fields
+> rather than prose; that is not built. Released as 0.7.24.
+
 ## Recommendation: CONDITIONAL GO
 
 HypGraph is ready for a public developer preview once #59, #60 and #61 are merged with green CI and released as one

{hypgraph-0.7.22 → hypgraph-0.7.24}/src/hypgraph/__init__.py

@@ -16,7 +16,7 @@ Standing is derived on every read, never stored; every write is an event in a SH
 their numbers; reviews pin versions; independence is counted, not assumed. See https://hypgraph.com.
 """
 
-__version__ = "0.7.22"
+__version__ = "0.7.24"
 
 from .bundle import anchored, verify_bundle  # noqa: E402
 from .graph import Author, Graph, GraphError, file_sha256  # noqa: E402