mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.7 KiB
1.7 KiB
List the persons behind one bar of a stickiness insight — the users who were active in a given number of intervals.
Pair this with query-stickiness: first run the stickiness query to read the distribution (the X-axis is the number of active intervals, the Y-axis is the number of users), then call this tool with the same stickiness query as source and day set to the bar you want to drill into.
Selectors:
day(required): the number of active intervals to drill into — the X-axis value of the bar. Despite the name, this is an interval count, not a date. For a daily insight,day: 13lists the users who were active on exactly 13 days within the source's date range; for a weekly insight it is a count of weeks, and so on.series: 0-based index of the series to drill into when the stickiness query has multiple series. Defaults to 0.compare:current(default) orpreviouswhen the source hascompareFilterenabled.
Response:
Each returned row contains distinct_id, email, and name. Results are limited to the top 100 actors. There is no event_count, and there is no includeRecordings selector — stickiness drilldown is membership-based (active on exactly N intervals) and does not surface a matched-recordings column.
Guidance:
- Keep the
sourcestickiness query identical to the one whose bar the user is asking about — the series, interval granularity, date range, and filters all determine who falls in each bar. dayselects a single bar (a specific active-interval count), not a date. To list the users at a different bar, changeday.- For large result sets, tighten the source (date range, filters) rather than expecting more than 100 rows.