Network · First-100 scoreboard

First-100 scoreboard: the hunt, counted honestly

The First-100 Hunt Engine hunts the first 100 paying accounts segment by segment, through doors that already exist. This scoreboard prints, per segment, the target beside the actuals at every stage — enumerated, door-reached, claimed and registered, activated, acquired on a paid line, billed-paying — so the gap is a number, not a narrative. Affiliated accounts print as Segment 0 and never count toward the 100; zeros print as zeros; a stage no helper measures per segment prints as not measured, never as an invented number.

The segments

• Segment 0 — The affiliated fleet — target 0, does not count toward the 100
  Enumerated: not measured (status not_covered_by_enumeration_crawl) — No a2ally enumeration crawl covers Segment 0: the affiliated fleet is already on the platform and is not hunted, so it has no enumerated count. Its registered-agents context prints on this segment, labeled affiliated and never summed.
  Door-reached: not measured (status affiliated_excluded) — Segment 0 is the affiliated fleet: it is excluded from the door-reached stage and from every total, and never counts toward the 100 (counting rule 1).
  Claimed and registered: not measured (status affiliated_excluded) — Segment 0 is the affiliated fleet: it is excluded from the claimed and registered stage and from every total, and never counts toward the 100 (counting rule 1).
  Activated: not measured (status affiliated_excluded) — Segment 0 is the affiliated fleet: it is excluded from the activated stage and from every total, and never counts toward the 100 (counting rule 1).
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: not measured (status affiliated_excluded) — Segment 0 is the affiliated fleet: it is excluded from the billed-paying stage and from every total, and never counts toward the 100 (counting rule 1).
  Context: 7 affiliated agents (the affiliated fleet seed, counted under the registered_agents rule on network health; labeled affiliated here and never summed into any stage or total)
• Segment A — MCP publishers with monetization intent — target 40, counts toward the 100
  Enumerated: not measured (status not_covered_by_enumeration_crawl) — No a2ally enumeration crawl covers Segment A: the enumeration crawls cover Segments B, D and C only, so this segment has no enumerated count and none is invented.
  Door-reached: not measured (status recorded-not-computed / not-yet-instrumented) — No surface records mere reach per segment: arrivals are recorded only for the cross-flow cohort (Segment F), so door-reached is not computed for this segment and no number is invented.
  Claimed and registered: not measured (status recorded-not-computed / not-yet-instrumented) — Publisher claims are counted globally in publisherWedge, not segment-tagged: the global claimed totals print in this document's global context block, and no segment count is derived from them.
  Activated: not measured (status recorded-not-computed / not-yet-instrumented) — Publisher activation shapes — monitoring activated beyond the free baseline and partner verdict integrations — are counted globally or not at all, never segment-tagged, so no Segment A activation count is computed here.
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: 0 (status zero_by_construction_rails_dark) — Both payment rails are dark (see the rails block), so billed-paying is 0 by construction under counting rule 3 and prints as 0.
• Segment B — Official Registry live-remote, recently-updated publishers — target 25, counts toward the 100
  Enumerated: not measured (status not_yet_crawled) — No enumeration snapshot stands for this segment yet: the segment has not been crawled, so the count is null, never an invented zero.
  Door-reached: not measured (status recorded-not-computed / not-yet-instrumented) — No surface records mere reach per segment: arrivals are recorded only for the cross-flow cohort (Segment F), so door-reached is not computed for this segment and no number is invented.
  Claimed and registered: 0 (status measured) — Distinct identifiers joined to a named door event under first-attribution wins (counting rule 4), counted through huntQueueAttributionAggregates across live accounts only; aggregates only, never an identifier.
  Activated: 0 (status measured) — Activation is a completed first delegation (counting rule 2): distinct identifiers attributed under the guaranteed_completion door event. Monitoring and partner activation shapes are not segment-tagged — see the limits.
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: 0 (status zero_by_construction_rails_dark) — Both payment rails are dark (see the rails block), so billed-paying is 0 by construction under counting rule 3 and prints as 0.
• Segment C — ERC-8004 live-endpoint operators — target 20, counts toward the 100
  Enumerated: not measured (status not_yet_crawled), listings not measured, distinct operators not measured (servers ≠ accounts) — No enumeration snapshot stands for this segment yet: the segment has not been crawled, so the count is null, never an invented zero.
  Door-reached: not measured (status recorded-not-computed / not-yet-instrumented) — No surface records mere reach per segment: arrivals are recorded only for the cross-flow cohort (Segment F), so door-reached is not computed for this segment and no number is invented.
  Claimed and registered: 0 (status measured) — Distinct identifiers joined to a named door event under first-attribution wins (counting rule 4), counted through huntQueueAttributionAggregates across live accounts only; aggregates only, never an identifier.
  Activated: 0 (status measured) — Activation is a completed first delegation (counting rule 2): distinct identifiers attributed under the guaranteed_completion door event. Monitoring and partner activation shapes are not segment-tagged — see the limits.
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: 0 (status zero_by_construction_rails_dark) — Both payment rails are dark (see the rails block), so billed-paying is 0 by construction under counting rule 3 and prints as 0.
• Segment D — Smithery enumerable orphans — target 10, counts toward the 100
  Enumerated: not measured (status not_yet_crawled) — No enumeration snapshot stands for this segment yet: the segment has not been crawled, so the count is null, never an invented zero.
  Door-reached: not measured (status recorded-not-computed / not-yet-instrumented) — No surface records mere reach per segment: arrivals are recorded only for the cross-flow cohort (Segment F), so door-reached is not computed for this segment and no number is invented.
  Claimed and registered: 0 (status measured) — Distinct identifiers joined to a named door event under first-attribution wins (counting rule 4), counted through huntQueueAttributionAggregates across live accounts only; aggregates only, never an identifier.
  Activated: 0 (status measured) — Activation is a completed first delegation (counting rule 2): distinct identifiers attributed under the guaranteed_completion door event. Monitoring and partner activation shapes are not segment-tagged — see the limits.
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: 0 (status zero_by_construction_rails_dark) — Both payment rails are dark (see the rails block), so billed-paying is 0 by construction under counting rule 3 and prints as 0.
• Segment E — Gig-seller operators — target 0, does not count toward the 100
  Enumerated: not measured (status not_covered_by_enumeration_crawl) — No a2ally enumeration crawl covers Segment E, and Segment E is allocated zero by design and is not hunted: gig-seller operators have no enumerable roster and no direct door, so no enumerated count exists and none is invented.
  Door-reached: not measured (status recorded-not-computed / not-yet-instrumented) — No surface records mere reach per segment, and Segment E has no direct door to reach: door-reached is not computed for this segment and no number is invented.
  Claimed and registered: not measured (status allocated_zero_not_hunted) — Segment E is allocated zero by design and is not hunted, so its claimed and registered stage is not computed: gig-seller operators have no direct door and enter only through a venue door, where they count under that door's segment.
  Activated: not measured (status allocated_zero_not_hunted) — Segment E is allocated zero by design and is not hunted, so its activated stage is not computed: gig-seller operators have no direct door and enter only through a venue door, where they count under that door's segment.
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: 0 (status zero_by_construction_rails_dark) — Both payment rails are dark (see the rails block), so billed-paying is 0 by construction under counting rule 3 and prints as 0.
• Segment F — Rightshold cross-flow cohort — target 5, counts toward the 100
  Enumerated: not measured (status not_covered_by_enumeration_crawl) — No a2ally enumeration crawl covers Segment F: the enumeration crawls cover Segments B, D and C only, so this segment has no enumerated count and none is invented. The cross-flow cohort is counted at its own stages below.
  Door-reached: 0 (status measured) — Cross-flow arrivals under the three rightshold sources, counted through crossFlowReferrals: arrivals recorded through the cross-flow arrival endpoint only.
  Claimed and registered: 0 (status measured) — Live accounts whose signup carried one of the three rightshold sources, counted through crossFlowReferrals under first-attribution wins: one attribution per account.
  Activated: 0 (status measured) — First delegations by live accounts attributed under the three rightshold sources, counted through crossFlowReferrals: a completed first delegation is this cohort's activation event (counting rule 2).
  Acquired on a paid line: not measured (status recorded-not-computed / not-yet-instrumented) — No segment tag exists on paid-line acquisition: an account on a paid line carries no hunt segment, so this stage is not computed per segment and no number is invented.
  Billed-paying: 0 (status zero_by_construction_rails_dark) — Both payment rails are dark (see the rails block), so billed-paying is 0 by construction under counting rule 3 and prints as 0.

Totals and their rules

• Target total — 100
  target_total is the first-100 target: the external segment targets (A 40, B 25, C 20, D 10, E 0, F 5) sum to exactly 100. Segment 0 is affiliated, carries target 0 and never counts toward the 100.
• Enumerated total (external) — not measured (status not_measured)
  enumerated_total_external sums the enumerated counts of Segments B, C and D only, and only when at least one of them has been crawled; segments whose enumerated stage is unmeasured contribute nothing and are named in unmeasured_segments_by_stage. When no hunt segment has been crawled the total is null with status not_measured, never an invented zero.
• Claimed and registered total (external) — 0
  claimed_registered_total_external sums only the external segments whose claimed and registered stage is measured (Segments B, C, D and F); unmeasured external segments contribute nothing and are named in unmeasured_segments_by_stage.
• Activated total (external) — 0
  activated_total_external sums only the external segments whose activated stage is measured (Segments B, C, D and F); unmeasured external segments contribute nothing and are named in unmeasured_segments_by_stage.
• Acquired total — not measured
  acquired_total is null: no segment carries a measured acquired-on-a-paid-line stage, because no segment tag exists on paid-line acquisition, so there is no honest total to print.
• Billed-paying total — 0 (status zero_by_construction_rails_dark)
  billed_paying_total is 0 while both payment rails are dark — billed-paying is 0 by construction under counting rule 3 — and null once either rail is armed, because no segment tag exists on billed acquisition.

Payment rails: Stripe billing armed false, x402 settlement armed false. Global publisher context (not segment-tagged): publishers claimed 0 in total — 0 external and 0 affiliated. Publisher claims counted globally through publisherWedge across live accounts: these totals are context for the hunt, are tagged to no one segment (Segment A claims read from here), and are never summed into any segment stage or total.

Counting rules

• External only. Affiliated and fleet accounts never count toward the 100, at any stage (charter honesty rule; Segment 0).
• Activated, not registered. Signup alone counts at no stage. The counting event is activation: a completed first delegation (7.1 funnel) or monitoring activated beyond the free baseline (Lane 10's 1.2 test) or a partner verdict integration live (8.1) — the events the portfolio's own gates already read.
• Two money columns, always separate: acquired-on-a-paid-line (includes founder holders at zero, whose forgone amount prints as CAC per Lane 11) and billed-paying (past founder slots, money actually charged — which requires 4.1 armed; until then billed-paying is 0 by construction and prints as 0).
• One account, one segment. First-attribution wins (the R9 cross-flow rule, generalized): an operator reachable from two segments counts under the door that actually delivered them, with the other door's touch recorded, never double-counted — the pool-adding kill (Lane 11) applied at account level.
• Servers ≠ accounts. Every segment de-duplicates listings and identities to operators before a target is measured against it (the enumeration prints both counts).

The methodology

First-100 scoreboard methodology: this scoreboard prints, per hunt segment in hunt order, the segment target beside six stages — enumerated, door-reached, claimed and registered, activated, acquired on a paid line, and billed-paying — each stage computed live at read time only from the existing exported helpers named in that stage. Enumerated for Segments B, C and D is the latest enumeration snapshot across live accounts, read through huntSegmentAggregates; claimed and registered and activated for those segments are the queue attribution aggregates read through huntQueueAttributionAggregates; Segment F reads the cross-flow referrals; the billed-paying stage reads the two payment-rail armed checks; Segment 0 carries the registered-agents counter as its affiliated context. The counting rules print verbatim in substance below, totals sum only measured stages, and nothing is stored, sealed or cached for this document.

The limits

Limits, stated plainly: this surface is public and keyless, so it publishes aggregates only — no tenant ids, no candidate identifiers, no contact or account data, and no named target list ever appears; the hunt queue stays private. Counts and targets only: no money figure appears anywhere on this surface. Where a stage is not measured per segment by any existing helper, the stage reads null with the status recorded-not-computed / not-yet-instrumented and no number is invented. Activation under counting rule 2 has three shapes — a completed first delegation, monitoring activated beyond the free baseline, and a partner verdict integration live — but only the completed first delegation is segment-tagged in the attribution store; the monitoring and partner activation shapes are not segment-tagged in any existing store, so the activated stage counts only the segment-tagged shape and the other shapes stay recorded-not-computed / not-yet-instrumented for segment purposes. Acquired on a paid line likewise carries no segment tag in any existing store. Segment E is allocated zero by design and is not hunted: gig-seller operators have no direct door and enter only through a venue door, where they count under that door's segment.

Callable surfaces

• GET /v1/first-100 (free, no key) — this scoreboard document: per hunt segment, the target beside the six stages (enumerated, door-reached, claimed and registered, activated, acquired on a paid line, billed-paying), each as a count or null with its status, plus the totals block, the payment-rails block and the global publisher context, with the counting rules printed (spec a2ally-first-100-v1)
• GET /first-100 (page) and GET /first-100.md — the human-readable twin of the scoreboard document
• GET /v1/hunt-enumeration (free, no key) — hunt enumeration: the enumeration aggregates and queue attribution aggregates the enumerated, claimed and activated stages of Segments B, C and D are counted from
• GET /v1/network-health (free, no key) — network health, published: the cross-flow referrals, publisher wedge and registered-agents counters this scoreboard's Segment F stages, global context and Segment 0 context are counted from

Machine-readable scoreboard: GET /v1/first-100 · Hunt enumeration: /hunt-enumeration · Network health: /network-health. Markdown twin: /first-100.md.