Skip to content

Converge the scoring/rules twins #4881

Description

@JSONbored

Problem: The gate-decision advisory logic exists as two hand-maintained "twin" files today — one in src/, one already in gittensory-engine — and they're deliberately allowed to structurally diverge, specifically so the engine's copy doesn't have to pull the entire, much larger signals-engine file into the miner's own dependency graph. Whether to converge these to one real source, or keep them intentionally separate, is a real decision, not a mechanical move.

Area: ORB / gittensory-engine

Proposal: Evaluate each twin pair individually. For any pair where divergence no longer serves a real purpose, converge to one source with a shim. For the one pair explicitly documented as deliberately divergent, either keep it that way (documenting why, clearly, for future contributors) or design a way to satisfy both constraints (e.g. a shared type-only import that doesn't pull the larger file's implementation along with it).

Deliverables:

  • A clear, documented decision — converge or keep-divergent — for every twin pair in this area, not a blanket policy.

Acceptance criteria:

  • No gate-decision behavior changes as a result of this issue — this is the one phase where "no behavior change" needs to be actively verified, not just assumed from a clean diff.

Boundaries:

  • Don't converge the deliberately-divergent pair without first solving the dependency-graph-size problem it exists to avoid.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.roadmapOn the Wave-2 agent-layer roadmap board (project 9)

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions