-
-
Notifications
You must be signed in to change notification settings - Fork 89
Extract content-lane/* as one vertical slice #4880
Copy link
Copy link
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Milestone
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is needed
Problem: The content-lane subtree (the curated-list rule engine) is explicitly self-documented as a leaf module with almost no cross-cutting imports into the rest of the review logic — the cleanest possible extraction boundary in the whole
review/tree, and a good place to validate the shim pattern on a genuinely new (not already-twinned) slice before touching anything more central.Area: ORB / gittensory-engine
Proposal: Move the entire content-lane subtree into
gittensory-engineas a self-contained unit, with a thin adapter file remaining insrc/to wrap it for the Worker.Deliverables:
Acceptance criteria: