Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Autoresearch] Document Experiment Governance Runbook #911

New Issue
Closed
opened 2026-03-22 13:06:06 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-22 13:06:06 +00:00
Collaborator
Copy Link

Parent

Part of #904 (Autoresearch Integration Proposal v2) — Action Item #10

Goal

Write a governance runbook documenting the full experiment lifecycle: branch → tox → PR → review → merge/revert. This ensures all agents follow the same safety constraints.

Sections to Cover

  1. Experiment Lifecycle

    • How to create an experiment branch
    • How tox validates (pytest, lint, type-check)
    • How PRs are created and structured
    • How Timmy (account #2) auto-reviews
    • Merge criteria vs revert criteria

  2. Safety Rules (from KT document — hard-won)

    • Never create test issues on the real repo
    • Morrowind is the confirmed direction — no pivots
    • OpenGauss was rejected — don't reference
    • No cloud dependencies — Ollama on localhost required
    • All experiment work lives on branches and PRs only

  3. Agent Roles in Research Swarm

    • Forge (kimi) → codebase optimization
    • Echo (hermes) → memory retrieval
    • Seer (manus) → inference quality
    • Quill (perplexity) → prompt quality
    • Mace (replit) → security
    • Helm (Timmy) → orchestration
    • rockachopa → principal authority, program.md author

  4. Compute Budget Rules

    • Metabolic protocol: Lightning balance governs tier selection
    • Resting mode (local M3 Max) is default
    • VPS for heavier inference
    • Cloud burst only when funded

  5. Failure Modes & Mitigations

    • Runaway experiments → feature branches + tox + revert default
    • Compute escalation → Lightning-balance budgets
    • Tests pass but UX degrades → H2 LLM-as-judge benchmarks
    • Experiment pollution → branches/PRs only, never auto-create issues

Deliverable

Wiki page or docs/autoresearch-governance.md in the repo

Cross-references

  • #904 (Autoresearch Epic)
  • #875 (Docker Compose — reproducible environments)

Owner

Engineering

## Parent Part of #904 (Autoresearch Integration Proposal v2) — Action Item #10 ## Goal Write a governance runbook documenting the full experiment lifecycle: branch → tox → PR → review → merge/revert. This ensures all agents follow the same safety constraints. ## Sections to Cover 1. **Experiment Lifecycle** - How to create an experiment branch - How tox validates (pytest, lint, type-check) - How PRs are created and structured - How Timmy (account #2) auto-reviews - Merge criteria vs revert criteria 2. **Safety Rules** (from KT document — hard-won) - Never create test issues on the real repo - Morrowind is the confirmed direction — no pivots - OpenGauss was rejected — don't reference - No cloud dependencies — Ollama on localhost required - All experiment work lives on branches and PRs only 3. **Agent Roles in Research Swarm** - Forge (kimi) → codebase optimization - Echo (hermes) → memory retrieval - Seer (manus) → inference quality - Quill (perplexity) → prompt quality - Mace (replit) → security - Helm (Timmy) → orchestration - rockachopa → principal authority, program.md author 4. **Compute Budget Rules** - Metabolic protocol: Lightning balance governs tier selection - Resting mode (local M3 Max) is default - VPS for heavier inference - Cloud burst only when funded 5. **Failure Modes & Mitigations** - Runaway experiments → feature branches + tox + revert default - Compute escalation → Lightning-balance budgets - Tests pass but UX degrades → H2 LLM-as-judge benchmarks - Experiment pollution → branches/PRs only, never auto-create issues ## Deliverable Wiki page or `docs/autoresearch-governance.md` in the repo ## Cross-references - #904 (Autoresearch Epic) - #875 (Docker Compose — reproducible environments) ## Owner Engineering
claude was assigned by Rockachopa 2026-03-22 23:32:00 +00:00
claude added the rejected-direction label 2026-03-23 13:51:23 +00:00
perplexity commented 2026-03-23 13:52:14 +00:00
Author
Collaborator
Copy Link

🧹 Closed — Superseded

Autoresearch direction has been superseded by the Sovereignty Loop spec (#953) and the harness-first architecture. The research pipeline now routes through the cascade router and local model stack.

Ref: Deep Backlog Triage #1076. Reopen if needed.

🧹 **Closed — Superseded** Autoresearch direction has been superseded by the Sovereignty Loop spec (#953) and the harness-first architecture. The research pipeline now routes through the cascade router and local model stack. Ref: Deep Backlog Triage #1076. Reopen if needed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label rejected-direction
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#911
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?