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

Future: typed temporal semantics for facts, relationships, beliefs, and preferences #183

New Issue
Closed
opened 2026-09-06 04:46:46 +01:00 by conductor · 5 comments
conductor commented 2026-09-06 04:46:46 +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
183 feature memory open none

Different kinds of memory deserve different lifetimes

What is this about: Give different kinds of memory different lifetimes by design: ephemeral state expires, preferences persist until contradicted, evidence is permanent.

Why do we need it: One decay rule for everything means important things fade and junk lingers.

Why is it still open: Deliberately parked deferred design; no schema change now.

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 (deferred design — low priority)

Part of epic #181 (evidence-driven memory architecture). No schema change now.

Design target

Define lifecycle behavior by semantic type rather than one universal decay curve. The contract must cover at least: ephemeral state (naturally expires); preference (persists until contradictory evidence / reconfirmation); commitment (deadline/event driven); relationship fact (valid until superseded); historical event (preserved permanently as history); belief (evidence/confidence/supersession semantics); inferred hypothesis (low confidence; promotion requirements); owner/constitutional rule (persistent until explicitly changed).

For each type define: whether it decays at all; what can supersede it; temporal validity; confidence/evidence semantics; contradiction handling; reconfirmation conditions; retention/deletion rules.

Hard requirements

  • Later evidence must not erase historical truth; "current truth" and "historical truth" remain separately queryable.
  • Arbitrary mathematical importance curves must not substitute for semantics.
  • Generic/common-sense facts must not automatically become autobiographical memory (the bus example: a generic safety assumption must not become a meaningful autobiographical preference).

Acceptance examples

  • "likes black coffee" can change over time without deleting earlier evidence.
  • A historical event remains historical even when no longer contextually relevant.
  • An inferred preference does not become durable fact solely through repeated retrieval.
  • A constitutional owner rule persists until explicitly changed.

Dependencies

#38 (memory types + retrieval intent) and #42 (supersession/normalization) — verify live state before start; findings from the prior-art child feed the design.

How Nick can verify this: the eight-type contract exists with per-type lifecycle rules; the four acceptance examples demonstrably hold; no universal decay constant appears in the design.

--- id: 183 kind: feature subsystem: memory status: open version_intent: none depends_on: [] blocks: [] --- # Different kinds of memory deserve different lifetimes **What is this about:** Give different kinds of memory different lifetimes by design: ephemeral state expires, preferences persist until contradicted, evidence is permanent. **Why do we need it:** One decay rule for everything means important things fade and junk lingers. **Why is it still open:** Deliberately parked deferred design; no schema change now. # 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 (deferred design — low priority) Part of epic #181 (evidence-driven memory architecture). No schema change now. ## Design target Define lifecycle behavior by **semantic type** rather than one universal decay curve. The contract must cover at least: ephemeral state (naturally expires); preference (persists until contradictory evidence / reconfirmation); commitment (deadline/event driven); relationship fact (valid until superseded); historical event (preserved permanently as history); belief (evidence/confidence/supersession semantics); inferred hypothesis (low confidence; promotion requirements); owner/constitutional rule (persistent until explicitly changed). For each type define: whether it decays at all; what can supersede it; temporal validity; confidence/evidence semantics; contradiction handling; reconfirmation conditions; retention/deletion rules. ## Hard requirements - Later evidence must not erase historical truth; "current truth" and "historical truth" remain separately queryable. - Arbitrary mathematical importance curves must not substitute for semantics. - Generic/common-sense facts must not automatically become autobiographical memory (the bus example: a generic safety assumption must not become a meaningful autobiographical preference). ## Acceptance examples - "likes black coffee" can change over time without deleting earlier evidence. - A historical event remains historical even when no longer contextually relevant. - An inferred preference does not become durable fact solely through repeated retrieval. - A constitutional owner rule persists until explicitly changed. ## Dependencies #38 (memory types + retrieval intent) and #42 (supersession/normalization) — verify live state before start; findings from the prior-art child feed the design. **How Nick can verify this:** the eight-type contract exists with per-type lifecycle rules; the four acceptance examples demonstrably hold; no universal decay constant appears in the design. </details>
conductor added the memorygovernanceidentitygrowthP3 — low labels 2026-09-06 04:46:46 +01:00
conductor commented 2026-09-06 04:47:13 +01:00
Author
Owner
Copy link
Copy source

Part of epic #181. Depends on: #38 Depends on: #42 Depends on: #182 (prior-art findings feed the design)

Part of epic #181. Depends on: #38 Depends on: #42 Depends on: #182 (prior-art findings feed the design)
gitea-actions Bot added the infrastructurelife labels 2026-09-06 04:47:19 +01:00
gitea-actions Bot added the ready label 2026-09-09 17:59:26 +01:00
gitea-actions Bot commented 2026-09-09 17:59:26 +01:00
Copy link
Copy source

🎓 NEXT: #183 — Future: typed temporal semantics for facts, relationships, beliefs, and preferences — dependencies satisfied (closed: #286); Rune may start.

🎓 **NEXT: #183 — Future: typed temporal semantics for facts, relationships, beliefs, and preferences** — dependencies satisfied (closed: #286); Rune may start.
gitea-actions Bot commented 2026-09-09 18:23:59 +01:00
Copy link
Copy source

🎓 NEXT: #183 — Future: typed temporal semantics for facts, relationships, beliefs, and preferences — dependencies satisfied (scheduled sweep); Rune may start.

🎓 **NEXT: #183 — Future: typed temporal semantics for facts, relationships, beliefs, and preferences** — dependencies satisfied (scheduled sweep); Rune may start.
gitea-actions Bot commented 2026-09-11 13:11:26 +01:00
Copy link
Copy source

🎓 NEXT: #183 — Future: typed temporal semantics for facts, relationships, beliefs, and preferences — dependencies satisfied (closed: #289); Rune may start.

🎓 **NEXT: #183 — Future: typed temporal semantics for facts, relationships, beliefs, and preferences** — dependencies satisfied (closed: #289); Rune may start.
gitea-actions Bot added the featureperception labels 2026-09-19 14:53:34 +01:00
conductor commented 2026-09-19 16:28:30 +01:00
Author
Owner
Copy link
Copy source

Plain summary — why this closed

This idea now lives inside its parent epic #181 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 #181's absorbed-children section.

Technical details

  • STATE: HISTORICAL_EVIDENCE — absorbed into #181 on 2026-09-19
  • REVERSIBLE: re-mint as a standalone issue when the idea becomes live work
  • SUMMARY CARRIED: Different kinds of memory deserve different lifetimes
## Plain summary — why this closed This idea now lives inside its parent epic #181 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 #181's absorbed-children section. ## Technical details - **STATE:** HISTORICAL_EVIDENCE — absorbed into #181 on 2026-09-19 - **REVERSIBLE:** re-mint as a standalone issue when the idea becomes live work - **SUMMARY CARRIED:** Different kinds of memory deserve different lifetimes
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 governance growth identity infrastructure life 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#183