A school email can create a surprising amount of work. There is a date to remember, a form to return, a lunch to pack, and a departure time that changes in the follow-up message. Add appointments, dinner, a repair, and the project waiting for your next free weekend. You become the connection between all of it.
We are building Wirespeed to help carry those connections. The useful result is easy to recognize: less searching, less reconstructing, fewer things that depend on remembering at exactly the right moment.
There are working pieces behind that ambition. We use durable memory, project records, household information, and calendar foundations while building the system. A read-only review on 16 October 2026 confirmed home-project work with linked activity, active lunch and school records, and recorded calendar delivery receipts in our setup. The bounded project check excluded ordinary fixture and demo markers; it establishes the presence of records. The detailed household stories below are fictional illustrations; they do not describe private family records or establish completed household outcomes.
Start with Thursday's school trip
Imagine a notice from Example Primary. The trip is Thursday. The permission form is due Tuesday. The children need a packed lunch and a blue shirt. Another message moves departure to 8:45 a.m.
The connected experience should turn that into a plan a person can review: two dates, preparation requirements, the changed time, and a link back to the source. An unclear pickup time should remain a question. Once accepted, the current plan should stay available to the people and tools allowed to use it.
The calendar foundation already has an implementation. A documented September 2026 run delivered accepted household events into managed calendars and recorded delivery outcomes. The public reconciler connects a delivery outbox to Google Calendar, uses stable event identifiers, records receipts, and supports retries.
Stable identity matters when the second school message arrives. An update needs to find the accepted trip. A failed request needs a safe retry. The outcome needs a record that someone can inspect. The provider-free sample independently tested in October exercises planning, delivery, duplicate prevention, correction, and recovery after a simulated lost receipt. Its provider and outbox are simulated; it makes no live Google request.
Automatic email intake and the full preparation experience remain in development. The dated operating run and the synthetic sample each establish a specific part of the path. Neither establishes continuous calendar operation or a complete email-to-prepared-morning service.
Remember the lunch correction
In the fictional week, Thursday also needs a packed lunch. Wednesday evening is busy. A useful suggestion could be as small as making an extra wrap while dinner is being prepared, with a reminder to pack it before bed.
That suggestion needs context: the school menu, preferences that may have changed, available preparation time, and what is already in the kitchen. A person should be able to say, "There are apples in the fridge," and see the shopping suggestion change. The correction should still be useful the next time an authorized assistant helps with lunch.
Our setup contains lunch and school records. Public Household OS code includes a date-specific lunch query. A lunch record can remain available to a permitted query even when it is hidden from the family display.
The next concrete work is reliable school-menu correction and readback: change the information, then check that the next permitted reader receives the current answer. Source intake and correction have a public design; automatic email interpretation still needs implementation and acceptance. The broader connection between menus, preferences, preparation, groceries, and schedule pressure is the future we are building toward.
Pick up the home project without starting its story again
A home project can be scattered across a measurement note, two quotes, a delivery update, and a decision made in an old conversation. Before doing the work, you have to remember where the work stands.
In a fictional spare-room project, useful help would bring forward the goal, the quotes still to compare, the decision to keep the floor, the missing measurement, and the shelf delivery that blocks the next step. When the delivery slips, the remaining work should still make sense.
We already use durable memory and project records to carry development work between sessions, and home-project work is also represented in the setup. The records retain context, decisions, corrections, and activity outside an individual chat. That gives a new session something durable to return to.
An unmerged public planning candidate implements work proposals, references, dependencies, and outcome-acceptance primitives. It is a review candidate. Connecting everyday quotes, research, and delivery changes still needs its own acceptance.
Finding the right current record, applying the right permission, and carrying a handoff through successfully still need their own checks. The October inspection did not replay a fresh two-assistant handoff or verify a completed home-improvement outcome. A complete household project assistant remains work in progress.
Make the records worth depending on
The system needs to preserve more than a polished summary. The source, the accepted decision, and the correction help explain why the current answer is the current answer. They also give another tool a place to start.
Sovereign Memory Core tests record lifecycle, history, custody, and authority boundaries. Its immutable v0.3-alpha release includes a package-and-restore rehearsal on synthetic data. That recipe was independently reproduced on PostgreSQL 16 during the October review. It gives another builder a specific mechanism to inspect and run. Independent acceptance of live recovery remains open.
User MCP provides a reproducible experimental local, read-only path against fabricated data. Developers can investigate permitted and denied application-data reads through that supported profile. Hosted OAuth and governed writes have separate acceptance work.
These foundations support different parts of the experience. Their tests help us see which connection is ready to build next and which result still needs evidence.
Build one dependable loop, then connect it
The next useful slice is a correction that reaches the next authorized reader reliably. Calendar execution also needs to hold up when a provider is unavailable, an update is retried, a source changes, or an earlier result is stale.
Those are practical requirements behind the larger vision. Thursday's trip should be able to inform Wednesday's preparation. A changed lunch preference should improve the next suggestion. A home project should retain the decisions that make the next hour useful.
As models improve, the person's accumulated context should make that intelligence more valuable. Keeping the history useful lets us choose better tools without asking the household to begin again.