hypgraph 0.7.23__tar.gz → 0.7.25__tar.gz

{hypgraph-0.7.23 → hypgraph-0.7.25}/CHANGELOG.md

@@ -1,5 +1,65 @@
 # Changelog
 
+## 0.7.25 — 2026-11-01: which counts bear on a claim, joined comparisons, boundaries in names
+
+Fixes from an independent audit of 0.7.24 (HG-024-01 to -04); each case below failed on 0.7.24 and is now a test
+(`tests/test_counts_that_bear.py`).
+
+- **A count with no comparison doesn't back one** (HG-024-01). With no comparison of its own, a count of none or all
+  was read the old way, so "3 of 3 routes processed" backed "nothing is longer than 26 km" and "every route is longer
+  than 26 km". A count that states no comparison now doesn't bear on a claim that rules one out
+  (`ABSOLUTE_WITHOUT_COUNT`). A claim with no comparison ("no route ever failed") reads a plain count as before.
+- **A count of one kind doesn't back a claim about another** (HG-024-02). A count and a claim were matched on any shared
+  word, so none of 3 cargo routes longer than 26 km backed "no passenger route is longer than 26 km" while the passenger
+  count was 1 of 3, and backed "no route is longer" too. A count names what it counts in the plural ("cargo routes");
+  where the statement uses that word, the words right before it say which kind. A count backs a claim only if every
+  kind it names is one the statement names; a count of one kind that finds some still refutes a claim about all, and
+  two kinds named apart (cargo, passenger) are left unresolved.
+- **Two comparisons joined in one clause** (HG-024-03). "And" ended the clause, so "no route is shorter than 20 km and
+  longer than 30 km" was refused by a route shorter than 20, and "every route is longer than 10 km and shorter than 30
+  km" went in with "shorter than 30" unread, even with the count that refutes it bound. An "and" or "or" before a
+  comparison with no subject of its own now keeps it in the clause. "No … A or B" and "every … A and B" are false if
+  either part fails; "no … A and B" and "every … A or B" rule out only what meets both, so none of one part backs them
+  and a count of each part on its own leaves them unresolved.
+- **A count's name must say its boundary** (HG-024-04). Only a name pointing the other way was caught: a `>=` count
+  named "routes longer than 26 km", or a `>` count named "26 km or longer", went in. A name that leaves the figure out
+  where the count took it in, or the other way round, is now `MEASUREMENT_MISMATCH`.
+
+## 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.

{hypgraph-0.7.23 → hypgraph-0.7.25}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: hypgraph
-Version: 0.7.23
+Version: 0.7.25
 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.23 → hypgraph-0.7.25}/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.23 (2026-11-01)
+## Status at 0.7.25 (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.23 → hypgraph-0.7.25}/docs/RELEASE-READINESS.md

@@ -131,6 +131,41 @@ was taken from a changelog without being checked against the code.*
 > 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.
+
+> **Audit of 0.7.24 (2026-11-01), fixed for 0.7.25.** A fifth independent audit named four candidate defects; each
+> reproduced on the PyPI 0.7.24 wheel, plus four of the same kind. A count with no comparison of its own ("3 of 3
+> routes processed") backed "nothing is longer than 26 km" and "every route is longer" (HG-024-01). A count of cargo
+> routes backed a claim about passenger routes, and about every route, because they shared the word "route"
+> (HG-024-02). "And" ended a clause, so a true "no route is shorter than 20 km and longer than 30 km" was refused,
+> and "every route is longer than 10 km and shorter than 30 km" went in with its second half unread, even beside the
+> count that refutes it (HG-024-03). A `>=` count named "longer than 26 km" went in (HG-024-04). A count that states no
+> comparison no longer bears on one; a count backs only a claim whose kinds it names, and kinds named apart are
+> unresolved; a comparison joined by "and" / "or" stays in its clause and is read as both or either; a name must say
+> the boundary its count used. Each case is a regression test written to fail on 0.7.24. Replaying the 1,900 recorded
+> adversarial entries changes 7: one honest correction is no longer refused, and one correction that got in only
+> because an unrelated zero count backed it (the HG-024-01 case) is now refused; none of the entries tries these cases.
+>
+> **Where that stands.** #91 is merged with green CI (17 of 17 checks); from the 0.7.25 wheel in a fresh venv the
+> suite is 574 passed, and hypswarm (118 passed) and hypmesh (37 passed) pass on it. Kinds are read from a plural noun
+> and the words before it, a heuristic; the typed claim layer the audits recommend is not built. Released as 0.7.25.
+
 ## 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.23 → hypgraph-0.7.25}/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.23"
+__version__ = "0.7.25"
 
 from .bundle import anchored, verify_bundle  # noqa: E402
 from .graph import Author, Graph, GraphError, file_sha256  # noqa: E402