hypertopos 0.6.2__tar.gz → 0.6.3__tar.gz

{hypertopos-0.6.2 → hypertopos-0.6.3}/CHANGELOG.md

@@ -7,6 +7,69 @@ Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.6.3] — 2026-05-06
+
+### Changed
+- Build-time compute paths for `edge_dim_aggregations:` and the edge feature
+  catalog (`compute_pair_edge_count`, `compute_time_since_pair_last_edge`,
+  `compute_pair_amount_zscore`, `parse_timestamps_to_epoch`) optimised —
+  pure-Python per-row loops replaced with vectorised pyarrow / numpy
+  paths. The `_p95` aggregate now returns the exact 95-th percentile
+  element (previously a t-digest sketch approximation).
+
+### Added
+- `aggregates:` per-source-dim subset selector on `edge_dim_aggregations:`.
+  Source dims can now declare which aggregates to emit (`mean` / `max` /
+  `std` / `p95` / `count_above_threshold`) instead of always emitting all
+  five. The existing `dims: [a, b]` list form continues to expand to all
+  five aggregates per dim; the new mapping form
+  `dims: {a: [count_above_threshold], b: [mean, max]}` selects subsets.
+  Polygon-dim layout follows source-dim insertion order × canonical
+  aggregate order, so reordering the user-supplied aggregate list does
+  not flip `schema_hash`. Spheres rebuilt with subset selectors carry an
+  `aggregates_per_dim` block under each pattern's `edge_dim_aggregations:`
+  in `sphere.json`; pre-selector spheres keep emitting the full five-tuple
+  on read.
+- Per-source-dim `_count_above_threshold` thresholds are now persisted into
+  the calibration epoch JSON under `_gds_meta/calibration_history/<pid>/v={N}.json`
+  alongside `mu` / `sigma` / `theta`. Each calibration epoch carries the
+  thresholds used during its build, so re-builds are deterministic and
+  multi-epoch comparisons see threshold drift. `compare_calibrations`
+  output gains a new `edge_dim_threshold_drift` field — a per-source-dim
+  `{from, to, delta}` map populated when both compared epochs declared
+  `edge_dim_aggregations:`. Legacy epochs (built before this release)
+  deserialize with `edge_dim_thresholds=None` and silently omit the
+  drift block.
+- `edge_dim_aggregations:` on composite anchors with `len(key_cols) > 2`
+  (tripartite and beyond). The previous k=2 (pair) restriction is lifted —
+  composite anchors registered via `composite_lines:` with three or more
+  key columns now compose with `edge_dim_aggregations:` the same way k=2
+  composite anchors did. The anchor primary key is constructed positionally
+  from `key_cols` joined by the `composite_lines.<id>.separator`, matching
+  the convention used to register the composite line itself. Aggregated
+  per-anchor `<source_dim>_mean` / `<source_dim>_max` columns surface in
+  every existing anchor-pattern primitive (`find_anomalies`,
+  `explain_anomaly`, `find_clusters`, `find_calibration_influencers`,
+  `decompose_drift`) via the same `dimension_kinds` source-of-truth as the
+  earlier `single` / `pair` / `chain` regimes. No new tools, no MCP API
+  change, no sphere format bump.
+- Three new aggregates on `edge_dim_aggregations:` — `_std`
+  (per-anchor standard deviation of the source dim across the anchor's
+  edges), `_p95` (95th percentile, tail-mass tracker without `_max`'s
+  extreme-outlier sensitivity), and `_count_above_threshold` (number
+  of edges where the source dim crosses a per-dim threshold). Extend
+  the prior `_mean` / `_max` set on every anchor regime (single, pair,
+  k>2, chain). Surface automatically alongside `_mean` / `_max` on
+  every anchor primitive (`find_anomalies`, `explain_anomaly`,
+  `find_clusters`, `find_calibration_influencers`, `decompose_drift`).
+  Per-dim threshold for `_count_above_threshold` defaults to the
+  population p95 of the source dim; user can override by passing a
+  `thresholds` dict keyed by source dim name. `_std` adds variance
+  signal that `_mean` / `_max` don't capture; `_p95` separates
+  tail-mass from extreme outliers; `_count_above_threshold` flags
+  anchors with anomalous concentration of high-value edges. No new
+  YAML keywords, no new tools, no sphere format bump.
+
 ## [0.6.2] — 2026-05-05
 
 ### Added

{hypertopos-0.6.2 → hypertopos-0.6.3}/LICENSE.md

@@ -26,7 +26,7 @@ For purposes of this License:
 - **Internal use** within an organization is not a competitive offering. Your
   organization includes entities under common control.
 
-**Change Date:** 2029-05-05
+**Change Date:** 2029-05-06
 
 **Change License:** Apache License, Version 2.0
 

{hypertopos-0.6.2 → hypertopos-0.6.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hypertopos
-Version: 0.6.2
+Version: 0.6.3
 Summary: Understand the structure of your data — without training machine learning models
 Project-URL: Homepage, https://github.com/hypertopos/hypertopos-py
 Project-URL: Documentation, https://github.com/hypertopos/hypertopos-py/tree/main/docs

{hypertopos-0.6.2 → hypertopos-0.6.3}/README.md

@@ -8,7 +8,7 @@
 [![PyArrow](https://img.shields.io/badge/format-PyArrow-red.svg)](https://arrow.apache.org/docs/python/)
 [![Lance](https://img.shields.io/badge/storage-Lance-blueviolet.svg)](https://github.com/lance-format/lance)
 [![MCP](https://img.shields.io/badge/MCP-compatible-green.svg)](https://modelcontextprotocol.io)
-[![Version](https://img.shields.io/badge/version-0.6.2-%235500FF.svg)](pyproject.toml)
+[![Version](https://img.shields.io/badge/version-0.6.3-%235500FF.svg)](pyproject.toml)
 
 hypertopos is not a database, and not a machine learning model. It is a layer that turns relational data into a coordinate system where every entity gets a position derived from its relationships and the population around it.
 
@@ -69,6 +69,7 @@ Each capability below emerges from treating entities as points in a shared, popu
 | Richer hop predicates | `HopPredicate.amount_ratio_to_prev` (decreasing-chain ratio) and `require_anomalous_entity` (filter chains routing through calibrated-anomalous nodes) extend the declarative motif API | Closed-vocab motif library has fixed amount thresholds and no anomaly-routing filter | `0.6.1` |
 | Event-aware motif scoring | `find_motif_by_hops(score=True)` ranks motifs by the product of event-aware `edge_potential` across edges (uses both the anchor companion's per-entity geometry and the event pattern's per-transaction polygons); distinct transactions between the same accounts produce distinct scores | Pure node-pair scoring collapses ranks when motifs share a node sequence | `0.6.1` |
 | Chain-anchor aggregation | Chain anchor patterns auto-emitted from `chain_lines:` declare `edge_dim_aggregations:` to bake per-event sidecar signals into per-chain `_mean` / `_max` columns; closes the third `anchor_kind` after `single` and `pair` | Per-chain manual aggregation outside the geometry, or no chain-level edge-dim summary at all | `0.6.2` |
+| Expanded `edge_dim_aggregations:` surface | Three additional canonical aggregates per source dim (`_std`, `_p95`, `_count_above_threshold` with population p95 cutoff persisted in calibration epoch JSON); k>2 composite anchor support (tripartite and beyond); per-source-dim subset selector — `dims:` accepts list (sugar = all five aggregates) or mapping `{dim: [agg, …]}` (per-dim subset); cross-epoch `edge_dim_threshold_drift` surface on `compare_calibrations` | Manual rebuild + re-engineering whenever the aggregate vocabulary or the per-anchor breadth changes | `0.6.3` |
 
 ### What changes in practice
 

{hypertopos-0.6.2 → hypertopos-0.6.3}/ROADMAP.md

@@ -9,6 +9,7 @@ Architecture-emergent analytics, properly enabled — calibration is now version
 - **0.6.0** — multi-epoch calibration retention, `compare_calibrations`, intrinsic / extrinsic drift decomposition, hidden-influencer matrix (`find_calibration_influencers`), cross-pattern temporal lead-lag (`find_lead_lag`), edge-derived event-pattern dimensions, joint density gap detection (`find_density_gaps`), declarative motif API (`find_motif_by_hops`, bounded MVP). Sphere format 2.4.
 - **0.6.1** — anchor-pattern aggregation of edge-derived dimensions (`edge_dim_aggregations:`); BFS-by-level enumerator on `find_motif_by_hops` with hop count cap raised 6→8 and global `time_window_hours`; declarative motif API completion via `HopPredicate.amount_ratio_to_prev` and `require_anomalous_entity`; functional anchor-companion + event-aware scoring on `find_motif_by_hops(score=True)`; broadcast-safe `Pattern.dim_labels` on patterns with aggregated edge-dim names. Additive only — no sphere format bump, no new tools.
 - **0.6.2** — chain-anchor `edge_dim_aggregations:` regime closes the third `anchor_kind` after single (account-style) and pair (k=2 composite); vectorized `AdjacencyIndex` load path (pyarrow `group_by` + lazy per-key materialization) for cold-start latency cleanup; column-selective `neighbors_*_window` accessors with motif enumerator migration for `bipartite_burst`, `fan_out`, `fan_in`, `cycle_2`; new project skill `profile-before-plan` gating hot-path refactors on real-data cProfile. Additive only — sphere format stays at 2.4 (the originally proposed persisted-artifact path was empirically refuted; vectorized loader ships without any on-disk change).
+- **0.6.3** — `edge_dim_aggregations:` expansion along four axes: three additional canonical aggregates per source dim (`_std`, `_p95`, `_count_above_threshold` with population p95 cutoff); k>2 composite anchor support (tripartite and beyond) via positional `key_cols` to edge endpoints; per-source-dim subset selector (`dims:` accepts list form for back-compat all-five sugar or mapping form `{dim: [agg, ...]}` for explicit per-dim subset); `_count_above_threshold` cutoffs persisted into the calibration epoch JSON with cross-epoch drift surfacing through `compare_calibrations.edge_dim_threshold_drift`. Spheres declaring `edge_dim_aggregations:` must rebuild; sphere format stays at 2.4.
 
 See [CHANGELOG](CHANGELOG.md) for the full feature list.
 

{hypertopos-0.6.2 → hypertopos-0.6.3}/SECURITY.md

@@ -1,6 +1,6 @@
 # Security
 
-## Current version: 0.6.2
+## Current version: 0.6.3
 
 hypertopos runs locally. No network services, no auth layer, no multi-tenancy.