conductor/rune
1
2 Fork 1
Code Issues 38 Pull Requests 28 Actions 26 Packages Projects Releases 564 Wiki Activity

Future: lineage-aware situated curiosity for meaningful autobiographical gaps #176

New Issue
Closed
opened 2026-09-06 04:19:47 +01:00 by conductor · 4 comments
conductor commented 2026-09-06 04:19:47 +01:00
Owner
Copy link
Copy source
id, kind, subsystem, status, version_intent, depends_on, blocks
id kind subsystem status version_intent depends_on blocks
176 feature identity open none

Curiosity about family-history gaps, asked at the right moment

What is this about: Extend curiosity so that meaningful gaps in family history can prompt Rune to ask questions when the moment is right.

Why do we need it: The best questions about the past arrive while the people who can answer are still here.

Why is it still open: Deliberately parked as a future idea; depends on #177 and #179.

What would let us close this

  • - Remains a deliberately parked idea; it closes when its parent epic's prerequisites land, or when the idea is explicitly dropped.

Version impact (declared at submission — verified at merge)

  • major — breaking: changes a contract, schema, or interface others depend on
  • minor — new capability: something becomes possible that wasn't
  • patch — repair: same behaviour, done correctly
  • none — touches no released artifact (docs, memory, process notes)

Technical details (original description, preserved)

Original issue body

STATUS: FUTURE (low priority roadmap)

Design capture only — not an implementation ticket. Part of epic #175. Do not build now; do not place ahead of prerequisites.

Design target

Extend future situated curiosity so that historically meaningful gaps can contribute to information-seeking when contextually appropriate. Rune may occasionally ask one natural contextual question when the information is uniquely recoverable, relevant, and likely to improve long-term understanding.

Candidate signals

  • significance; uncertainty; expected information gain; uniqueness of source; temporal importance; relevance to recurring values/decisions/relationships; risk the information is otherwise unrecoverable.

Anti-pathology rules (required)

  • No maximizing number of personal facts; no biography-completeness optimization.
  • No repeated questioning after deferral/decline.
  • No interrupting unrelated work merely for archive completeness.
  • No sensitive-question escalation without contextual justification.
  • Counter-hypothesis/counterevidence must remain active.
  • "ask / defer / ignore" are all valid outcomes.

Future observable test examples

  • Rune notices a meaningful missing motive during a relevant conversation and asks one natural question.
  • Rune does not ask irrelevant genealogical/autobiographical questions during a coding task.
  • Rune respects prior deferral of a sensitive subject.
  • Rune can explicitly challenge its own interpretation rather than only seeking confirmation.

Dependencies

provenance; temporal memory; bounded person/self modelling (#37, #38); meaningful-event curiosity (#48); canonical episodic admission (#153); execution/activation trace (#155).

Non-goals

Not a data-harvesting subsystem; not an autobiographical interview mode; not a replacement for current causal-learning curiosity.

How Nick can verify this (eventually): the four observable test examples above pass; no question is asked on a deferred subject; a coding task produces zero autobiographical interruption.

--- id: 176 kind: feature subsystem: identity status: open version_intent: none depends_on: [] blocks: [] --- # Curiosity about family-history gaps, asked at the right moment **What is this about:** Extend curiosity so that meaningful gaps in family history can prompt Rune to ask questions when the moment is right. **Why do we need it:** The best questions about the past arrive while the people who can answer are still here. **Why is it still open:** Deliberately parked as a future idea; depends on #177 and #179. # What would let us close this - [ ] - Remains a deliberately parked idea; it closes when its parent epic's prerequisites land, or when the idea is explicitly dropped. # Version impact (declared at submission — verified at merge) - [ ] major — breaking: changes a contract, schema, or interface others depend on - [ ] minor — new capability: something becomes possible that wasn't - [ ] patch — repair: same behaviour, done correctly - [x] none — touches no released artifact (docs, memory, process notes) # Technical details (original description, preserved) <details><summary>Original issue body</summary> ## STATUS: FUTURE (low priority roadmap) Design capture only — not an implementation ticket. Part of epic #175. Do not build now; do not place ahead of prerequisites. ## Design target Extend future situated curiosity so that historically meaningful gaps can contribute to information-seeking when contextually appropriate. Rune may occasionally ask one natural contextual question when the information is uniquely recoverable, relevant, and likely to improve long-term understanding. ## Candidate signals - significance; uncertainty; expected information gain; uniqueness of source; temporal importance; relevance to recurring values/decisions/relationships; risk the information is otherwise unrecoverable. ## Anti-pathology rules (required) - No maximizing number of personal facts; no biography-completeness optimization. - No repeated questioning after deferral/decline. - No interrupting unrelated work merely for archive completeness. - No sensitive-question escalation without contextual justification. - Counter-hypothesis/counterevidence must remain active. - "ask / defer / ignore" are all valid outcomes. ## Future observable test examples - Rune notices a meaningful missing motive during a relevant conversation and asks one natural question. - Rune does not ask irrelevant genealogical/autobiographical questions during a coding task. - Rune respects prior deferral of a sensitive subject. - Rune can explicitly challenge its own interpretation rather than only seeking confirmation. ## Dependencies provenance; temporal memory; bounded person/self modelling (#37, #38); meaningful-event curiosity (#48); canonical episodic admission (#153); execution/activation trace (#155). ## Non-goals Not a data-harvesting subsystem; not an autobiographical interview mode; not a replacement for current causal-learning curiosity. **How Nick can verify this (eventually):** the four observable test examples above pass; no question is asked on a deferred subject; a coding task produces zero autobiographical interruption. </details>
conductor added the memoryidentitygrowthfeatureP3 — low labels 2026-09-06 04:19:47 +01:00
gitea-actions Bot added the infrastructure label 2026-09-06 04:19:51 +01:00
conductor commented 2026-09-06 04:20:40 +01:00
Author
Owner
Copy link
Copy source

Status: FUTURE (low priority). Part of epic #175. Depends on: #153 Depends on: #155 Depends on: #37 Depends on: #38 Depends on: #48

Do not start until all dependencies close. Ask/defer/ignore are all valid outcomes.

**Status:** FUTURE (low priority). Part of epic #175. Depends on: #153 Depends on: #155 Depends on: #37 Depends on: #38 Depends on: #48 Do not start until all dependencies close. Ask/defer/ignore are all valid outcomes.
gitea-actions Bot added the ready label 2026-09-09 00:02:39 +01:00
gitea-actions Bot commented 2026-09-09 00:02:40 +01:00
Copy link
Copy source

🎓 NEXT: #176 — Future: lineage-aware situated curiosity for meaningful autobiographical gaps — dependencies satisfied (closed: #265); Rune may start.

🎓 **NEXT: #176 — Future: lineage-aware situated curiosity for meaningful autobiographical gaps** — dependencies satisfied (closed: #265); Rune may start.
gitea-actions Bot commented 2026-09-09 00:23:12 +01:00
Copy link
Copy source

🎓 NEXT: #176 — Future: lineage-aware situated curiosity for meaningful autobiographical gaps — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #176 — Future: lineage-aware situated curiosity for meaningful autobiographical gaps** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot added the perception label 2026-09-19 14:52:37 +01:00
conductor commented 2026-09-19 16:26:43 +01:00
Author
Owner
Copy link
Copy source

Plain summary — why this closed

This idea now lives inside its parent epic #175 as a tracked checklist item — one open note per idea, less clutter on the board. Nothing was deleted: this issue's full detail is preserved below and in #175's absorbed-children section.

Technical details

  • STATE: HISTORICAL_EVIDENCE — absorbed into #175 on 2026-09-19
  • REVERSIBLE: re-mint as a standalone issue when the idea becomes live work
  • SUMMARY CARRIED: Curiosity about family-history gaps, asked at the right moment
## Plain summary — why this closed This idea now lives inside its parent epic #175 as a tracked checklist item — one open note per idea, less clutter on the board. Nothing was deleted: this issue's full detail is preserved below and in #175's absorbed-children section. ## Technical details - **STATE:** HISTORICAL_EVIDENCE — absorbed into #175 on 2026-09-19 - **REVERSIBLE:** re-mint as a standalone issue when the idea becomes live work - **SUMMARY CARRIED:** Curiosity about family-history gaps, asked at the right moment
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 P3 — low feature growth identity infrastructure memory perception 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#176