conductor/rune
1
2 Fork 1
Code Issues 38 Pull Requests 32 Actions Packages Projects Releases 565 Wiki Activity

Canonical experience encoding and episodic admission (write-side authority) #153

New Issue
Closed
opened 2026-09-05 19:24:06 +01:00 by conductor · 10 comments
conductor commented 2026-09-05 19:24:06 +01:00
Owner
Copy link
Copy source

Plain summary (handoff §6 — pending write-side audit)

Rune has retrieval, abstraction, and learning plans, but needs ONE authoritative rule for what becomes persistent lived experience. Not every event becomes an episode.

Required behaviour

Event (user message / model response / tool result / task outcome / owner correction / error / external evidence) → evaluate admission → classify → attach provenance-time-task-session → episode / evidence / IGNORE. Ignore must be a valid outcome — the write-side equivalent of true retrieval abstention.

Constraints (binding)

  • reuse canonical ConversationState/TaskState/event authorities (#18/#19 shipped; #33 outcome layer incoming)
  • no parallel transcript system
  • not every event written as equally salient episodic memory
  • source linkage/provenance preserved
  • LLM-only self-report is not sole admission evidence where objective structure exists

Pre-filing audit requirement

Before implementation: confirm no existing subsystem already owns admission correctly. If one does, extend it and close this issue as unnecessary.

Acceptance

A controlled sequence demonstrates: (1) meaningful event → correctly linked episode/evidence object; (2) trivial/noisy event → rejected; (3) later abstraction traces back to the original admitted evidence; (4) no duplicate authority path.

## Plain summary (handoff §6 — pending write-side audit) Rune has retrieval, abstraction, and learning plans, but needs ONE authoritative rule for what becomes persistent lived experience. Not every event becomes an episode. ## Required behaviour Event (user message / model response / tool result / task outcome / owner correction / error / external evidence) → evaluate admission → classify → attach provenance-time-task-session → **episode / evidence / IGNORE**. **Ignore must be a valid outcome** — the write-side equivalent of true retrieval abstention. ## Constraints (binding) - reuse canonical ConversationState/TaskState/event authorities (#18/#19 shipped; #33 outcome layer incoming) - no parallel transcript system - not every event written as equally salient episodic memory - source linkage/provenance preserved - LLM-only self-report is not sole admission evidence where objective structure exists ## Pre-filing audit requirement Before implementation: confirm no existing subsystem already owns admission correctly. If one does, extend it and close this issue as unnecessary. ## Acceptance A controlled sequence demonstrates: (1) meaningful event → correctly linked episode/evidence object; (2) trivial/noisy event → rejected; (3) later abstraction traces back to the original admitted evidence; (4) no duplicate authority path.
conductor added the P2 — medium label 2026-09-05 19:24:07 +01:00
gitea-actions Bot commented 2026-09-05 19:28:51 +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 governancegrowthinfrastructurememory labels 2026-09-05 19:28:53 +01:00
gitea-actions Bot added the ready label 2026-09-07 18:23:52 +01:00
gitea-actions Bot commented 2026-09-07 18:23:53 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-09-07 21:43:20 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-09-07 22:23:53 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-09-08 19:23:31 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-09-08 20:23:13 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-09-19 14:50:46 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (closed: #162); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (closed: #162); Rune may start.
gitea-actions Bot commented 2026-09-19 15:23:20 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-10-01 19:53:53 +01:00
Copy link
Copy source

🎓 NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority) — dependencies satisfied (closed: #2393); Rune may start.

🎓 **NEXT: #153 — Canonical experience encoding and episodic admission (write-side authority)** — dependencies satisfied (closed: #2393); Rune may start.
conductor commented 2026-10-08 11:41:34 +01:00
Author
Owner
Copy link
Copy source

CLOSED PROGRAMMATICALLY — commit d39655b (contract BUILDER-2026-10-08T10:34:14Z-c5be53). See tests/test_governance_quartet.py (15/15 green).

CLOSED PROGRAMMATICALLY — commit d39655b (contract BUILDER-2026-10-08T10:34:14Z-c5be53). See tests/test_governance_quartet.py (15/15 green).
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 P2 — medium governance growth infrastructure 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#153