Jibo-Revival-Group/JiboExperiments
8
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add person-aware state and sync roadmap

Browse Source
This commit is contained in:
Jacob Dubin
2026-05-14 20:48:55 -05:00
parent f299cef9be
commit ec786be797
10 changed files with 156 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
OpenJibo/docs/feature-backlog.md
View File

@@ -654,6 +654,8 @@ Current release theme:
- Follow-up:
- add durable persistence path for personal facts
- broaden fact categories further (multi-person household memory, relationship cues, and corrective updates)
- add explicit person-scoped state so future interactions can distinguish household members inside the same loop
- define the first server-to-server sync envelope for durable state before we need it in production
### 24. Memory-Triggered Proactivity Baseline
@@ -669,6 +671,7 @@ Current release theme:
- expand proactivity beyond pizza to additional Pegasus-backed categories
- add cooldown/throttle policy and observability around proactive offer frequency
- connect memory store to durable multi-tenant persistence
- keep the sync story visible so stateful offers can survive a multi-server deployment later
### 25. Weather Report-Skill Launch Compatibility

9
OpenJibo/docs/release-1.0.19-plan.md
View File

@@ -43,6 +43,15 @@ The goal is to keep compatibility work steady while shipping personality and cap
- define tenant boundaries across account, loop, device, and person-memory records
- add storage abstractions that can move from in-memory/local JSON to hosted SQL/Blob without reworking behavior layers
- implement memory-ready schemas and repository contracts for user facts (names, birthdays, personal dates, preferences) with strict tenant scoping
- seed person-aware state keys now so future interactions can scope to account + loop + device + person without another shape change
- keep stateful interaction flows repository-backed instead of embedding more ad hoc metadata in the websocket layer
### 6. Multi-Server Sync Path
- document the eventual sync boundary for stateful data that should move between servers
- treat the first pass as repository-local durability, then layer replication and conflict handling on top
- prefer explicit change records or versioned state snapshots over implicit last-writer wins when we outgrow a single node
- keep cross-server reconciliation out of the hot path until the single-server semantics are stable
## First Implemented Slice In `1.0.19`