-
-
Notifications
You must be signed in to change notification settings - Fork 89
Finish the settings/ slice extraction #4879
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: Most of ORB's settings-resolution logic is confirmed pure (no D1/
Envdependency) and is the lowest-risk, most-precedented extraction target — the engine package already has a working shim/twin convention established for part of this directory.Area: ORB / gittensory-engine
Proposal: Move the remaining confirmed-pure settings files into
gittensory-engine, converting each to a thin re-export shim insrc/, following the existing convention exactly. Leave the one confirmed I/O-bound settings file (the one that directly queries the database) behind insrc/.Deliverables:
src/settings/moved intogittensory-engine, with working shims.Acceptance criteria:
Boundaries: