Skip to content

Roadmap: self-hosted review-stack enhancements (gittensory orb) #1953

Description

@JSONbored

Summary

ORB = One-shot Review Brain. The self-hosted maintainer review engine already goes by "orb" everywhere (the check-run is "Gittensory Orb Review Agent," releases tag orb-v*) — this formalizes it as a backronym: it renders a one-shot merge-or-close verdict with no back-and-forth, and it's the shared "Brain" the Autonomous Miner System's own roadmap already describes reusing (~80% of the miner's brain = this engine).

A multi-phase roadmap to deepen ORB: better review output, richer analysis depth, an interactive control surface, real maintainer analytics, and self-host-native differentiators. This epic is the umbrella for a wave of focused, config-driven improvements — each child issue is an independently shippable unit of work.

Scope: gittensory is purely self-hosted. Every item targets the self-hosted orb engine (Docker) and its operator/maintainer. No central or managed service is assumed; where cross-instance features appear they are strictly opt-in and operator-controlled.

Guiding principles (apply to every child issue)

  • Modular & config-driven — every behavior is toggled per repo via .gittensory.yml (review.* / gate.* / settings.* / features:), never hard-coded for one repo. Follow the FocusManifestReviewConfig wiring pattern in src/signals/focus-manifest.ts.
  • Default-OFF & byte-identical when off — a new knob left unset means the engine behaves exactly as it does today.
  • Fail-safe — any new path degrades gracefully and never affects the gate on error.
  • Precision-first — additions must reduce noise, not add it. Prefer deterministic signals; gate AI additions behind confidence/verification.
  • Deterministic-first — prefer pure, groundable computation over AI where possible.
  • Respect the one-shot gate — nothing turns the auto-merge/auto-close disposition into an advisory back-and-forth.
  • Respect the contributor boundary — no contributor source upload and no contributor-supplied AI keys; contributor-side actions run on the contributor's own machine/agent via the local-write-action-spec pattern (src/mcp/local-write-tools.ts).

Baseline (already shipped — build on, don't rebuild)

Auto-merge/auto-close gate with measured precision + circuit-breakers (src/rules/advisory.ts, src/review/auto-tune.ts); config-as-code (review.profile/path_instructions/instructions/exclude_paths/pre_merge_checks, src/signals/focus-manifest.ts); inline review comments (src/review/inline-comments.ts); grounding — CI truth + full-file context (src/review/grounding-wire.ts); codebase RAG (src/review/rag.ts); the review-enrichment service (review-enrichment/); deterministic slop scoring (src/signals/slop.ts); the outcomes/accuracy ledger (review_audit + src/review/parity.ts + src/review/ops.ts); and the self-host MCP + CLI (src/mcp/, packages/gittensory-mcp).

Phases & child issues

Phase 1 — Review output, noise & trust (deterministic, small PRs)

Phase 1b — Content-lane genericity (make the registry-review engine usable by any self-hosted registry, not just our own)

Phase 2 — Interactive control & issue intelligence

Phase 3 — Analysis depth, analytics & developer experience

Phase 4 — Self-host-native differentiators

Phase 5 — Repo-doc generation

Phase 6 — Keep the docs site from drifting

Out of scope / explicitly avoid

  • Any feature that requires a central or managed service; contributor AI-key BYOK; contributor source upload.
  • Noise for its own sake (verbose nitpicking, decorative comment flourishes).
  • Diff-only reasoning regressions — invest in grounding/RAG/enrichment depth, not verbosity.
  • Third-party tracker integrations unless an operator explicitly requests one.

Sequencing

Ship Phase 1 first (deterministic, low risk, immediate noise/trust wins), then Phase 1b (content-lane genericity — small, sequential, each blocked by the last), then Phase 2 (control + issue intelligence), then Phase 3 (the marquee depth + analytics work), then Phase 4 (the differentiators). Each item ships as its own small, green, config-driven PR.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.orbGittensory Orb related - maintainer self-hosting analytics.

Projects

Status
Todo

Relationships

None yet

Development

No branches or pull requests

Issue actions