Skip to content

feat(scope-audit): evaluate transport-carrier view and observer-region filters #414

Open

Description

@dborup

Context

Assessment baseline: dborup/CoreScope master 4a5ec5e231dd97ed7a4392e50e5f409f4dc5fab0 (13 October 2026). Recheck current master and competing work before implementation.

Our existing Scope Audit candidate compares confirmed observer declarations with forwarding evidence. A transport-oriented view could include every repeater seen forwarding, including those never asked for a declaration, and show carrier/non-carrier observations for a selected scope and observer region.

Source for later comparison

Verified from GitHub's PR metadata and complete changed-file listing on 13 October 2026. The identifiers below are literal text, not hyperlinks or cross-repository references.

Source repository: Kpa-clawbot/CoreScope
Pull request number: 2167
PR head commit SHA: bb056a12d271059daa596c20729390d644f15a6c
Upstream merged SHA (merge_commit_sha): 696906315a04dd7fa50d2a01f385292f931fdc7d
Files changed in this PR:
  - cmd/server/area_filter_test.go
  - cmd/server/routes.go
  - cmd/server/scope_audit.go
  - cmd/server/scope_transport_2142_test.go
  - docs/api-spec.md
Source repository: Kpa-clawbot/CoreScope
Pull request number: 2169
PR head commit SHA: 1fe44fb8c56225293c1af15fe791e709a70a25b4
Upstream merged SHA (merge_commit_sha): deb55dc82eb011c2ff04f6999db40c2f88e0e879
Files changed in this PR:
  - cmd/server/area_filter_test.go
  - cmd/server/routes.go
  - cmd/server/scope_audit.go
  - cmd/server/scope_transport_2142_test.go
  - docs/api-spec.md
  - public/scope-audit.css
  - public/scope-audit.js
  - tests/unit/test-frontend-helpers.js
Source repository: Kpa-clawbot/CoreScope
Pull request number: 2171
PR head commit SHA: 6cd10a8b92c31ebb5cff7654308932fa354791b8
Upstream merged SHA (merge_commit_sha): a4ee3a7328614f86b6594e8d16f2a1e4ba3aa8a6
Files changed in this PR:
  - cmd/server/openapi.go
  - cmd/server/scope_audit.go
  - cmd/server/scope_audit_region_test.go
  - cmd/server/scope_transport_2142_test.go
  - docs/api-spec.md
  - public/scope-audit.css
  - public/scope-audit.js
  - tests/unit/test-frontend-helpers.js

These are historical upstream comparison sources, not proof of equivalence with our fork and not a request to cherry-pick blindly. Recheck our current implementation and preserve fork-specific behavior.

Proposed work

  • Coordinate with existing Scope Audit PR Add observer declaration scope audit #378; extend its contract rather than starting a competing basic audit implementation.
  • Keep declaration evidence separate from observed transport evidence and preserve transmission-level deduplication.
  • Define the population and window for carrier/non-carrier counts, including observer-region selection, incomplete captures and ambiguous hop attribution.
  • Never label a repeater misconfigured merely because it was not seen carrying a selected scope; quiet traffic and observer coverage can explain absence.
  • Keep lists/caches/pagination bounded, preserve identity visibility, and avoid per-node queries.
  • Add shared/deep-linkable UI state and API tests for never-queried nodes, empty declarations, low/ambiguous evidence, region filtering and cache reuse; measure cold queries on our snapshot.

Acceptance criteria

The transport view adds justified evidence beyond the declaration audit and reports limitations clearly. Observer-region filters apply consistently to API counts, displayed rows and details.

Existing work / dependencies

Builds on #378 and complements the observed-relay Regions map in #376.

Scope

This issue records evaluation/follow-up work in our fork. It does not authorize deployment, production/staging changes, mail delivery, automatic key promotion or other external actions. Preserve fork-specific correctness, bounded work and the read-only measurement-server database contract; any separate account database exception requires explicit review.

Source performance numbers are not measurements of our deployment. Any claimed improvement requires our own benchmark and an independently reviewed implementation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions