design(reminder): integrate @endo/reminder into Familiar - #938
Draft
kriscendobot wants to merge 1 commit into
Draft
design(reminder): integrate @endo/reminder into Familiar#938kriscendobot wants to merge 1 commit into
kriscendobot wants to merge 1 commit into
Conversation
Plans following up on the #721 review request to integrate the merged @endo/reminder message-scheduler into Familiar. Key finding: Familiar is a thin Electron supervisor with no capability code of its own; the integration lives in the bundled Endo daemon + packages/lal. The plan names the integration points (recipient adapter, node-fs store, setup.js provisioning + @pins retention, the powers guest, the agent scheduling tool, the familiar-bundle gate), the merged API surface actually used, persistence/lifetime, per-side changes, the trust posture, the test strategy, and the ordering against #721 (merged) and the two sibling integration plans (shared LAL substrate).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plans the follow-up requested in the review of endojs/endo-but-for-bots#721 (kriskowal, 2026-07-15): "Please post plans to follow-up with integration of this plugin into Chat, Familiar, and minion.town." This PR is the Familiar plan; sibling plans cover Chat and minion.town.
Adds
designs/endo-reminder-familiar-integration.md. Plan and propose only; no implementation here.Headline findings
@endo/reminderAPI is final. The integration is not blocked on the plugin changing shape, and the Phase 2 subscriber-capability delivery baseline needs no SturdyRef work.packages/lal(the LLM agent). "Integrate into Familiar" means wire the plugin against the LAL agent and have the Familiar deployment own the@pinsretention that makes it wake on restart. This realizes the design's Phase 3 "one worked integration demonstrating restart-survival".notifyfacet (its only exo isLal.help; the agent wakes only viafollowMessages()). A durable recipient-adapter exo must be built to translatenotify(message)into a wake of the agent loop and settle the one-shot response.What the plan delivers
The concrete integration points, the merged API surface actually used (read from sources + tests), persistence and lifetime, per-side changes, the trust-posture assessment (the unconfined shape fits, with interval-bomb and store-scope mitigations), the test strategy (recipient-adapter unit, restart-survival end-to-end,
familiar-bundleCI, agent-tool), and the ordering against #721 and the two sibling plans (one shared LAL substrate, built once). Open questions name what could not be established: the exact store-minting mechanism, provisioning home (setup.jsvsagent.js), recipient-adapter revival, and whether anypackages/familiarsource change is needed.Draft because it is design-stage; un-drafting is the maintainer's decision after review.
🤖 Generated with Claude Code