Research resolution queue

This queue prevents a plausible name from becoming a false fact. A question closes only when a reviewer records a canonical first-party source, the exact entity and version, the decision, and the pull request that changed the catalog. “No reliable identity found” is a valid reviewed outcome; guessing is not.

Open identity gates

Item	Current state	Evidence required	Publication effect
c-sentinel	Unresolved term	Owner-controlled repository or site; C-based host-observability scope; license; activity	No product profile; dashed catalog entry only
microBPF	Unresolved term	Paper, project, product, or corrected name from a canonical owner	No product profile or capability claims
Octave / Octant	Likely naming ambiguity	Confirm supplied intent; record Octant archive status and successor context	Octant remains historical; “Octave” is not silently substituted
Aperture	FluxNinja Aperture identified	Confirm this is the intended reliability-automation project and record evaluated release	May receive a profile after version review
CodeGen	Owner not identified	Exact organization, first-party architecture evidence, component versions, and permission to attribute	Reference stack cannot be represented as a verified case study

Scope and comparison gates

Enterprise vendors need an edition-and-deployment map before a like-for-like comparison. The record must distinguish SaaS, customer-managed, hybrid, regional control planes, optional modules, retention tiers, and separately priced security or incident products. It must also state the evaluation date.

Time-sensitive products—including Moogsoft and archived projects—need an ownership, availability, maintenance, and migration-path check. Historical entries remain discoverable, but cannot be labeled current without evidence.

Geography is split into five fields: organization origin, current headquarters, sales/service coverage, hosting region, and customer data-residency choices. A country label never implies the other four.

The initial mobile cohort must cover at least one open instrumentation approach and representative managed crash, RUM, performance, release-health, privacy, offline, battery, and cross-platform workflows. Inclusion requires a maintained SDK and dated platform support.

Cost scenarios use declared small, growing, and enterprise workloads. Each freezes hosts, users, monthly telemetry, retention, operations labor, region, currency, and excluded taxes or discounts. An altered workload is a new scenario—not a silent refresh.

Closure record

Every closed row must record: resolution date; reviewer; canonical sources; exact spelling; owner; version or lifecycle; classification; conflicts; affected stable IDs; and pull request. If evidence later changes, reopen the same stable queue item and retain the earlier decision in history.