Step 1: Signal IngestionV1 Architecture

Turning Developer Activity into
Account Readiness

Developers don't click ads. They commit code, read docs, and pull packages. We ingest these signals to build a deterministic Identity Graph.

A single GitHub star is vanity. A GitHub Issue + 20 minutes in "Advanced Configuration" docs + a Python SDK download is Buying Intent.

Live Ingestion Feed

[GitHub] hashicorp/terraform issue #881...

[Docs] viewed /guides/sso-setup (12m)...

[Pkg] npm install @sdk/enterprise...

We don't guess. We map developer identities to Accounts using a rigid confidence model.

Ingest & NormalizeStandardize events from GitHub, Segment (Docs), and Package Managers.
Match IdentityMap `github:user` -> `company_domain` via verified org membership or email.
Score ReadinessCompute stage based on activity depth, not just frequency.

Signal Processor v1

Sources: All Identity: Active

github

2h ago

OPA Policy integration patterns

Discussion on enforcing compliance tags automatically during apply stage using OPA.

docs

4h ago

High-volume ingestion: Kafka connector

User viewing 'Advanced Configuration' for Stream Connectors > 5 mins.

pkg

1d ago

SDK Download Spike (Python)

v3.0.1 downloads increased by 400% from known IP block.

Method: deterministic (v1)

Matched Account

Acme Financial(acme.io)

High Confidence

Rationale: Matched via verified GitHub Org membership

Plain English

"They are tightening controls to pass audits and reduce risk."

Business Value

Governance priority. Target CISO & Compliance leads.

Account Readiness

Evaluating (72/100)