conductor/rune
1
2 Fork 1
Code Issues 36 Pull Requests 30 Actions 69 Packages Projects Releases 564 Wiki Activity

Epic: pipeline-integrity hardening tranche (handoff §3) — type gate, coverage ratchet, dep locking, adversarial procedure, break-it phase #147

New Issue
Closed
opened 2026-09-05 19:22:56 +01:00 by conductor · 4 comments
conductor commented 2026-09-05 19:22:56 +01:00
Owner
Copy link
Copy source

Plain summary

Bounded five-item hardening tranche from RUNE_VIBE_CODE_INTEGRITY_HANDOFF §3 — engineering safeguards so LLM-authored changes that share one wrong assumption (implementation + tests + docs) are harder to merge. Explicitly NOT new cognitive architecture; NOT a permanent project — a finite tranche before P2 developmental-memory work (§9 Phase B).

Child issues

  1. Type-check dependency in the protected merge gate (§3.1)
  2. Coverage ratchet on changed/critical paths (§3.2)
  3. Reproducible dependency locking for CI (§3.3)
  4. Black-box adversarial test procedure for P0/P1 changes (§3.4)
  5. "Break-it" phase for constitutional paths (§3.5)

Anti-complexity rules (handoff §10, binding)

  • A concern is not automatically a subsystem. Prefer one invariant / one schema field / one trace relation / one test / one CI gate over a new service.
  • No future-scale machinery before current-scale evidence requires it.
  • Every mechanism must answer: trigger / state read / state changed / verification / failure mode / traceability / reversibility / benefit measurement / dormant cost / why an existing authority cannot own it.
## Plain summary Bounded five-item hardening tranche from RUNE_VIBE_CODE_INTEGRITY_HANDOFF §3 — engineering safeguards so LLM-authored changes that share one wrong assumption (implementation + tests + docs) are harder to merge. Explicitly NOT new cognitive architecture; NOT a permanent project — a finite tranche before P2 developmental-memory work (§9 Phase B). ## Child issues 1. Type-check dependency in the protected merge gate (§3.1) 2. Coverage ratchet on changed/critical paths (§3.2) 3. Reproducible dependency locking for CI (§3.3) 4. Black-box adversarial test procedure for P0/P1 changes (§3.4) 5. "Break-it" phase for constitutional paths (§3.5) ## Anti-complexity rules (handoff §10, binding) - A concern is not automatically a subsystem. Prefer one invariant / one schema field / one trace relation / one test / one CI gate over a new service. - No future-scale machinery before current-scale evidence requires it. - Every mechanism must answer: trigger / state read / state changed / verification / failure mode / traceability / reversibility / benefit measurement / dormant cost / why an existing authority cannot own it.
conductor added the P1 — high label 2026-09-05 19:22:57 +01:00
gitea-actions Bot commented 2026-09-05 19:27:35 +01:00
Copy link
Copy source

⚠️ Priority gate: this issue has no priority. Assign exactly one of P0 — critical (spine/correctness/blocks), P1 — high (material value or real defect), P2 — medium (quality/consolidation), P3 — low (measurement/deferred). An issue without a priority is not filed.

⚠️ **Priority gate:** this issue has no priority. Assign exactly one of **P0 — critical** (spine/correctness/blocks), **P1 — high** (material value or real defect), **P2 — medium** (quality/consolidation), **P3 — low** (measurement/deferred). An issue without a priority is not filed.
gitea-actions Bot added the custodianidentitymemory labels 2026-09-05 19:27:37 +01:00
conductor added P0 — critical and removed P1 — high labels 2026-09-07 11:13:55 +01:00
gitea-actions Bot commented 2026-09-07 11:14:02 +01:00
Copy link
Copy source

⚠️ Priority gate: this issue has no priority. Assign exactly one of P0 — critical (spine/correctness/blocks), P1 — high (material value or real defect), P2 — medium (quality/consolidation), P3 — low (measurement/deferred). An issue without a priority is not filed.

⚠️ **Priority gate:** this issue has no priority. Assign exactly one of **P0 — critical** (spine/correctness/blocks), **P1 — high** (material value or real defect), **P2 — medium** (quality/consolidation), **P3 — low** (measurement/deferred). An issue without a priority is not filed.
conductor commented 2026-09-07 12:49:36 +01:00
Author
Owner
Copy link
Copy source

Merged via PR #201 (head b77f4b4).

The research round gate is now evidence-enforced:

  • INWARD: ≥2 codebase citations (paths verified)
  • OUTWARD: ≥2 unique external URLs, live-fetched by CI (dead/hallucinated links fail), each with an inline per-source lesson (bare URL lists rejected); forge self-references excluded
  • INNOVATION: must re-reference OUTWARD sources — candidates derive from evidence, not invention
  • SYNTHESIS: evidence-sufficiency statement + realistic feasibility judgement (mechanism/assumptions/failure modes) + kill test (cheapest disproof, carried into the plan as an early frozen test) + plans/ artifact — OR honest MORE-RESEARCH with substantiated open questions (bound: 2 cycles → owner escalation + blocked label)
  • Issue thread = permalinked source-of-truth; rejection comments name exact gaps

Direct response to the observed failure: keyword-only gate cleared an improvised round identically to a genuine one. Verified: YAML valid, logic tested good/bad/self-exclusion, live fetch ok(200) vs unreachable, all four synthesis paths (clear/reject/loopback/loopback-reject) unit-tested.

**Merged via PR #201 (head b77f4b4).** The research round gate is now evidence-enforced: - **INWARD**: ≥2 codebase citations (paths verified) - **OUTWARD**: ≥2 unique external URLs, **live-fetched by CI** (dead/hallucinated links fail), each with an inline per-source lesson (bare URL lists rejected); forge self-references excluded - **INNOVATION**: must re-reference OUTWARD sources — candidates derive from evidence, not invention - **SYNTHESIS**: evidence-sufficiency statement + realistic feasibility judgement (mechanism/assumptions/failure modes) + **kill test** (cheapest disproof, carried into the plan as an early frozen test) + plans/ artifact — OR honest **MORE-RESEARCH** with substantiated open questions (bound: 2 cycles → owner escalation + blocked label) - Issue thread = permalinked source-of-truth; rejection comments name exact gaps Direct response to the observed failure: keyword-only gate cleared an improvised round identically to a genuine one. Verified: YAML valid, logic tested good/bad/self-exclusion, live fetch ok(200) vs unreachable, all four synthesis paths (clear/reject/loopback/loopback-reject) unit-tested.
gitea-actions Bot added the ready label 2026-09-07 16:23:55 +01:00
gitea-actions Bot commented 2026-09-07 16:23:55 +01:00
Copy link
Copy source

🎓 NEXT: #147 — Epic: pipeline-integrity hardening tranche (handoff §3) — type gate, coverage ratchet, dep locking, adversarial procedure, break-it phase — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #147 — Epic: pipeline-integrity hardening tranche (handoff §3) — type gate, coverage ratchet, dep locking, adversarial procedure, break-it phase** — dependencies satisfied (scheduled sweep); Rune may start.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
P0 — critical
Spine/core correctness or blocks other work — do first
 P1 — high
Material user value or real defect (money, bugs, next-stage dep)
 P2 — medium
Quality/consolidation improvement
 P3 — low
Measurement / benchmark / deferred policy
 blocked
Dependencies open
 bug
Confirmed defect or regression
 custodian
epic
Rune v1 course-correction issue graph
 feature
New capability or improvement
 governance
growth
identity
in-progress
Currently being worked on by Rune
 incomplete
Incomplete work — draft PR with ledger, awaiting resume
 infrastructure
life
memory
memory-atlas
Memory Research Atlas child domain
 needs-testing
Needs manual testing with dumbed-down steps before close
 perception
ready
Order satisfied - Rune may start
 release-drift
research
Research jobs — spikes, watchlists, evidence work
 rune
rune
 scaffolding
scaffolding
 spine,correction
spine,correction
 spine,deferred
spine,deferred
 spine,resolved
spine,resolved
 strangler,burn,endgame,deferred
strangler,burn,endgame,deferred
 strangler,burn,endgame,inventory,epic
strangler,burn,endgame,inventory,epic
 tui
tui
 tui,epic
tui,epic
 tui,openspec
tui,openspec
 v1-course-correction
Rune v1 course-correction issue graph
No labels P0 — critical custodian identity memory ready
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
conductor
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: conductor/rune#147