Skip to content

Restore 2026-07-09 gate incident-response fields to global.gittensory.yml (VPS) #5274

Description

@JSONbored

Context

global.gittensory.yml's gate: block on the dedicated server is just {enabled: false, linkedIssue: advisory} (2 keys). All 3 live repos (gittensory/metagraphed/awesome-claude) independently carry a much larger, mutually-identical gate block (enabled: true, pack: oss-anti-slop, duplicates: block, readiness.mode/minScore, slop.mode/minScore/aiAdvisory, linkedIssueSatisfaction: advisory, aiReview.mode/byok/allAuthors), each annotated with the byte-identical comment "restored 2026-07-09 (post token-spend-freeze-gate fix #4420 + priority-reward fix #4422 + contributor-trust fix #4423)". This is a fleet-wide incident-response fix applied identically to every repo's file but never folded back into the shared global default.

No active runtime bug today (all 3 repos fully self-specify), but any repo that ever loses its per-repo override, or a new repo onboarded without copy-pasting the whole gate block, silently falls back to a materially weaker posture: gate.enabled: false disables the check-run publish, and the DB defaults for slopGateMode, manifestPolicyGateMode, linkedIssueSatisfactionGateMode, aiReviewMode are all "off".

Requirements

  • This is a direct edit to the private, uncommitted dedicated-server config (edge-nl-01), not a GitHub PR. No code changes.
  • Take a timestamped backup of global.gittensory.yml before editing, per house convention.
  • Only promote fields confirmed byte-identical across all 3 repos — do not promote fields that genuinely differ per repo.

Deliverables

  • Back up global.gittensory.yml on edge-nl-01.
  • Promote enabled: true, pack: oss-anti-slop, duplicates: block, readiness.mode/minScore, slop.mode/minScore/aiAdvisory, linkedIssueSatisfaction: advisory, aiReview.mode/byok/allAuthors into global.gittensory.yml's gate: block, carrying the same 2026-07-09 provenance comment.
  • Leave linkedIssue, manifestPolicy, and aiReview.closeConfidence OUT of the promotion — these three genuinely differ per repo.
  • Trim all 3 per-repo files down to only their real deltas from the new global default.
  • Verify the effective merged config for each of the 3 repos is unchanged (diff before/after).

Expected Outcome

A 4th repo onboarded to the fleet — or any of the 3 existing repos if its override file is ever lost — gets the correct, restored gate posture by default instead of silently reverting to the pre-incident weak state.

Links & Resources

  • Evidence: global.gittensory.yml:6-8; jsonbored__gittensory.gittensory.yml:134-153, jsonbored__metagraphed.gittensory.yml:154-172, jsonbored__awesome-claude.gittensory.yml:124-149; src/signals/focus-manifest.ts:459-511 (gate.enabled only controls check-run publish, every other gate.* field independently null-gated); src/db/schema.ts (DB defaults)

Part of #5270 (roadmap epic).

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions