Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
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.
2026-08-01 15:44:40 -07:00

75 lines
2.6 KiB
Python

"""At-signup enrichment snapshot.
Captures the firmographic enrichment values as they were at signup, separate from the
live values that later enrichment runs continuously refresh onto the organization group.
The snapshot is emitted once as a person-scoped event and never updated.
"""
import dataclasses
from typing import Any, Optional
from hanzo_insights.client import Client
from products.growth.backend.models import EnrichmentSignupSnapshot
SNAPSHOT_EVENT_NAME = "enrichment_snapshot_at_signup"
SNAPSHOT_PROPERTY_SUFFIX = "_at_signup"
@dataclasses.dataclass
class SignupEnrichmentSnapshot:
"""PII-light firmographic values captured at signup.
Only derived firmographic and ICP fields belong here. No raw personal data beyond
the person association that the emitted event inherently carries.
"""
company_type: Optional[str] = None
headcount: Optional[int] = None
headcount_engineering: Optional[int] = None
industry: Optional[str] = None
country: Optional[str] = None
founded_year: Optional[int] = None
funding_stage: Optional[str] = None
is_yc_company: Optional[bool] = None
icp_score: Optional[int] = None
icp_score_version: Optional[str] = None
def to_event_properties(self) -> dict[str, Any]:
"""Return the snapshot as `*_at_signup` event properties, dropping unset values."""
return {
f"{field.name}{SNAPSHOT_PROPERTY_SUFFIX}": value
for field in dataclasses.fields(self)
if (value := getattr(self, field.name)) is not None
}
def capture_signup_enrichment_snapshot(
pha_client: Client,
*,
organization_id: str,
distinct_id: str,
snapshot: SignupEnrichmentSnapshot,
) -> bool:
"""Emit the at-signup enrichment snapshot for an org, exactly once.
Returns True if this call emitted the snapshot, False if one already existed.
"""
# Claim the write-once slot atomically before emitting: the unique constraint on
# organization_id lets concurrent or repeated runs make at most one row per org.
_, created = EnrichmentSignupSnapshot.objects.get_or_create(organization_id=organization_id)
if not created:
return False
# Emit as a person-scoped event (not org group properties): DeletionType.Person erases
# all of a person's events, while group properties sit outside person-deletion scope,
# so an erase-by-person request would not remove snapshot values stored on the group.
pha_client.capture(
distinct_id=distinct_id,
event=SNAPSHOT_EVENT_NAME,
properties=snapshot.to_event_properties(),
groups={"organization": str(organization_id)},
)
return True