# Wirespeed: understand it and start building

Edition: Published implementation guide.

## Purpose and system boundary

Wirespeed is building personal infrastructure that helps carry everyday work forward, with memory, plans, decisions, and history controlled by the people it serves.

Models, interfaces, and providers can change while accumulated context remains inspectable and useful.

The repositories are complementary components with distinct supported profiles. The connected household experience is being built; a single supported production installation of the whole system is not available.

## How the pieces relate

- Separate durable context and authority from replaceable assistants and tools.
- Keep source evidence, corrections, and recorded outcomes distinct from a model's account of what happened.
- Move stable operations into tested software with explicit inputs, permissions, retries, and receipts.
- Let each application define its records and permissions; household and business applications have separate boundaries.

## Everyday workflows

These four household stories and their details are fictional. Each step distinguishes a dated working foundation from a connection still being built.

### Early pickup. Fewer last-minute surprises.

A school-day change should reach the plan before it reaches your afternoon.

It is Friday. School finishes at 12:30, but the familiar 3:15 pickup time is still the one in your head. There is also an appointment that afternoon. The difficult part is carrying the change from a notice into the rest of the day.
In this fictional example, the accepted school event keeps the new time and the notice together. Its managed calendar copy can be updated without creating a second, competing pickup. You can return to the source when someone asks what changed.

**Current foundation — Used in our setup:** Our household setup contains active school-event records and recorded delivery outcomes. The public reconciler gives an event a stable identity, updates its calendar copy, and records what happened.

Checked 2026-10-16. Source revision: Sanitized household observation, 16 October 2026; Household OS d45894c723733534bcfdcce4691860138b4a7761.

**Current limit:** The check establishes stored records and recorded outcomes. It did not inspect the current provider calendar or prove an always-running intake service.

Fictional working record:

- Was: Pickup at 3:15 p.m.
- Accepted update: Pickup at 12:30 p.m.
- Keep with it: The revised school notice
- Next question: Who can cover the earlier pickup?

Illustration of a record and delivery pattern; this is not a live calendar.

**Used in our setup — Keep one accepted school event:** The new time has a durable record. The calendar is a useful view of that record, and the original notice remains part of the explanation.
- [Dated household records and project activity check](https://wirespeedcomputing.com/working/operating-observation/#household-check)
- [Calendar reconciler and dogfood runbook](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/DOGFOOD_CALENDAR_SYNC.md)

**Reproducible today — Update the existing calendar copy:** The independently exercised synthetic fixture covers identity, corrections and retries with a simulated provider. The same event identity is used when delivery is retried.
- [Independent offline calendar fixture verification, 15 October 2026](https://wirespeedcomputing.com/evidence/calendar-fixture-2026-10-15.json)
- [Synthetic calendar correction and retry sample](https://github.com/jryski/Household-OS/blob/a1b1799d582aa542be2b64b47ca6f4d26ece1ef1/tests/test_calendar_sample_fixture.py)

**Future direction — Bring the rest of the afternoon along:** Notice the appointment clash, propose pickup coverage and move preparation earlier. The person chooses the arrangement; a recorded date alone does not solve the transport.
- [Personal infrastructure that gives people their time back](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/NORTHSTAR.md)
- [The longer-term horizon](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/HORIZON.md)

**Fictional correction:** The reviewed notice says 12:30. → A later notice says 1:00. Review the correction and update the same event.. The delivery foundation can reconcile an accepted update. Reliably detecting a new notice and proposing its meaning is a separate connection in development.

**Ownership:** A different assistant should be able to explain the current time and its source. The family’s plan belongs in its records, where a better calendar or assistant can use it.

The relief: one current school plan, less hunting through notices, and a clear next question.

[Read the full example](https://wirespeedcomputing.com/working/#school)

### Tomorrow’s lunch shouldn’t be a research project.

The right menu, for the right day, with room for the correction that changes the answer.

The menu is in a PDF. There is a photo of the replacement menu in another conversation. One child wants a packed lunch, and tomorrow’s trip has its own requirements. At 7:15 a.m., finding the current answer is already another job.
Start with a smaller useful foundation: keep the accepted school menu against the date it belongs to. The public lunch query is date-specific. A lunch entry can be available for an authorized reader without filling the family display with every menu item.

**Current foundation — Used in our setup:** The read-only check found active school-lunch records and recorded calendar delivery outcomes. Public code includes a canonical lunch query for a requested date, private non-blocking calendar copies, and a display choice that keeps a lunch record queryable when it is hidden.

Checked 2026-10-16. Source revision: Sanitized household observation, 16 October 2026; Household OS d45894c723733534bcfdcce4691860138b4a7761.

**Current limit:** The check did not qualify a voice-assistant response, inspect today’s provider state, or establish connected preferences, pantry estimates or meal planning.

Fictional working record:

- Accepted menu: Vegetable pasta · Thursday
- Source: The revised menu, not last week’s photo
- Separate requirement: The class trip needs a packed lunch
- Preparation to connect: Make one extra wrap with Wednesday dinner

The menu is illustrative. Connected preference and preparation suggestions are future behavior.

**Used in our setup — Give the day a current menu record:** Keep the date-specific lunch information in the household’s records. Display visibility and availability to a permitted query can have different jobs.
- [Dated household records and project activity check](https://wirespeedcomputing.com/working/operating-observation/#household-check)
- [Date-specific lunch query and calendar receipts](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/supabase/migrations/20260904020639_calendar_sync_worker_and_lunch_query.sql)

**In development — Correct it once, then check the answer:** A replacement menu should supersede the old answer, and the next permitted reader should get the correction. Reliable correction and readback is the next concrete milestone.
- [Household implementation boundary and next milestones](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/ROADMAP.md)
- [Source intake, corrections and routing design](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/IMAGE_CALENDAR_INTAKE.md)

**Future direction — Turn the answer into an easier evening:** Connect the trip, preferences and a busy Wednesday. Suggest an extra wrap while dinner is being made, ask about uncertain supplies and prepare a reviewable shopping list.
- [Personal infrastructure that gives people their time back](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/NORTHSTAR.md)
- [The longer-term horizon](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/HORIZON.md)

**Fictional correction:** The proposed preparation list includes buying fruit because the estimate is uncertain. → Keep the packed-lunch requirement. Remove fruit from the proposed shopping list.. This is the connected experience we are building: a correction changes the useful plan, and the person can see why. No inventory check or purchase runs on this website.

**Ownership:** A preference should not disappear when you change assistants. A corrected menu should remain distinguishable from the stale version that prompted the question.

The relief we’re aiming for: tomorrow’s lunch takes less thought tonight.

[Read the full example](https://wirespeedcomputing.com/working/#lunch)

### Pick up the project. Keep the backstory.

The room is still unfinished. Restarting the conversation shouldn’t be another task.

The spare room started as a simple weekend project. Now the measurements are in a message, two quotes are in email, the flooring decision is in a chat, and the shelves are arriving late. Before doing anything useful, you have to reconstruct what you already know.
Open a useful project view and the next step should be visible: keep the existing floor; confirm the wall measurement before choosing a desk; the delayed shelves block their installation; choosing the quote is still your decision. That accumulated understanding is the valuable part.

**Current foundation — Used in our setup:** The bounded check found home-project-related work with linked activity after excluding ordinary fixture and demo markers. We also use durable context and correction records to carry development work forward. These are practical foundations for returning to an unfinished project.

Checked 2026-10-16. Source revision: Sanitized household observation, 16 October 2026; planning candidate 9b265859a1b301340f2f9c7698fd2344d13715b0.

**Current limit:** The check did not establish completed or accepted home-project outcomes, a fresh assistant handoff, contractor coordination, or automated purchasing. The public planning candidate is unmerged.

Fictional working record:

- Decided: Keep the existing floor
- Ready next: Confirm the wall measurement
- Waiting: Shelves arriving later than expected
- Still yours to decide: The quote, budget and installation date

A fictional example of recorded work. It is not proof of a completed renovation.

**Used in our setup — Keep the unfinished work somewhere durable:** Work records and activity are present in the household setup. The record is a place to keep the next question and carry the project’s context forward.
- [Dated household records and project activity check](https://wirespeedcomputing.com/working/operating-observation/#household-check)
- [Read-only operating observation: context, corrections, and delivery records](https://wirespeedcomputing.com/working/operating-observation/)

**In development — Connect the project’s moving pieces:** The public review candidate implements work proposals, references, dependencies and outcome-acceptance primitives. Connecting everyday research, quotes and delivery updates still needs its own acceptance.
- [Life assistance database work plane — unmerged review candidate](https://github.com/jryski/Household-OS/blob/9b265859a1b301340f2f9c7698fd2344d13715b0/docs/LIFE_ASSISTANCE_WORK_PLANE.md)

**Future direction — Replan when the shelves slip:** Show which jobs can continue, propose a revised weekend and prepare the decision that needs attention. Contacting a contractor, accepting a quote or spending money follows the person’s authority.
- [Personal infrastructure that gives people their time back](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/NORTHSTAR.md)
- [The longer-term horizon](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/HORIZON.md)

**Fictional correction:** The illustration’s plan assumes the proposed desk fits the wall. → A checked measurement says it does not. Choose a different desk before ordering it.. The useful future keeps the source of that correction beside the decision it affects. A tidy project summary is not evidence that an installation has been completed.

**Ownership:** The measurements, rejected options, accepted decisions and remaining questions should stay useful across conversations and tools. Better intelligence should inherit a project’s backstory.

The relief: open the project and know where to start.

[Read the full example](https://wirespeedcomputing.com/working/#projects)

### Let the school email become the plan.

Read it once. Keep the date, the requirements and the questions together.

A class-trip email arrives while you are doing something else. Leave at 8:45. Return time to follow. Bring a packed lunch and a blue shirt. Submit the permission form by Tuesday. The message is short; the remembering lasts all week.
The experience we are building turns a permitted message into a checkable proposal: one trip, one form deadline, the preparation it creates, and a question about the missing return time. Accepted details can then use the record and calendar-delivery foundations that already exist.

**Current foundation — In development:** The public intake design includes email as a source type. The downstream school records and calendar-delivery foundations exist, but this review did not find an executable mail-intake or recurring unattended worker on Household OS main.

Checked 2026-10-16. Source revision: Household OS d45894c723733534bcfdcce4691860138b4a7761; sanitized household observation, 16 October 2026.

**Current limit:** No email-source row was present in the inspected intake table. That bounded absence does not rule out manually assisted email use elsewhere, and does not qualify continuous inbox monitoring.

Fictional working record:

- Trip: Thursday · Depart at 8:45 a.m.
- Before then: Permission form due Tuesday
- Pack: Lunch + blue shirt
- Keep open: Return time has not been provided

Email watching and automatic extraction are in development. This browser example reads no inbox.

**In development — Select a relevant message and propose events:** Work only within the configured message scope. Keep the source, separate dates from requirements, and leave the missing return time as a question for review.
- [Source intake, corrections and routing design](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/IMAGE_CALENDAR_INTAKE.md)
- [Household implementation boundary and next milestones](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/ROADMAP.md)

**Used in our setup — Give accepted details a durable home:** School-event records and recorded delivery outcomes are present. Once details have been accepted, the existing delivery pattern can use one event identity and a recorded result.
- [Dated household records and project activity check](https://wirespeedcomputing.com/working/operating-observation/#household-check)
- [Calendar reconciler and dogfood runbook](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/DOGFOOD_CALENDAR_SYNC.md)

**Future direction — Connect it to the rest of the week:** Bring the form forward before Tuesday. Fold lunch preparation into Wednesday dinner. Put the shirt beside the bag. Surface a transport conflict while there is still time to solve it.
- [Personal infrastructure that gives people their time back](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/NORTHSTAR.md)
- [The longer-term horizon](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/HORIZON.md)

**Fictional correction:** Return time is unknown. It should not be invented. → A later message says 2:30. Propose the correction; after acceptance, update the same trip.. Automatic detection and interpretation remain in development. Stable identity, retries and receipts are the working delivery machinery underneath the larger flow.

**Ownership:** The useful result is an owned plan with an inspectable source. Another assistant should be able to explain the trip without asking you to search your inbox again.

The value of the connection: a message stops being a week-long memory task.

[Read the full example](https://wirespeedcomputing.com/working/#email)

## Component map

### Household OS — Everyday coordination

Status: **In development**.

The household application: events, responsibilities, preparation, and follow-through. Executable calendar reconciliation is an early piece.

[Repository and license](https://github.com/jryski/Household-OS) · [Supported starting point](https://github.com/jryski/Household-OS/blob/main/docs/DOGFOOD_CALENDAR_SYNC.md)

### Sovereign Vault — Business knowledge and work

Status: **In development**.

A peer application for business knowledge and operations, with its own records, identity, policy, and deployment evidence.

[Repository and license](https://github.com/WireSpeedComputing/Sovereign-Vault) · [Supported starting point](https://github.com/WireSpeedComputing/Sovereign-Vault/blob/main/docs/14-business-platform-adoption.md)

### Memory Core — Durable evidence and history

Status: **Reproducible today**.

The PostgreSQL reference implementation for custody, record history, and the bounded synthetic package/restore proof.

[Repository and license](https://github.com/jryski/sovereign-memory-core) · [Supported starting point](https://github.com/jryski/sovereign-memory-core/releases/tag/v0.3-alpha)

### User MCP — Bounded application-data access

Status: **Reproducible today**.

An independent application-data connector. Its accepted local read-only profile uses synthetic data; broader hosted and write profiles are separate work.

[Repository and license](https://github.com/jryski/Supabase_user_MCP) · [Supported starting point](https://github.com/jryski/Supabase_user_MCP/blob/main/docs/GETTING_STARTED.md)

### Memory Protocol — Shared meaning and authority

Status: **In development**.

Implementation-neutral draft rules for provenance, custody, authority, integrity, and portability. A protocol draft and a deployment have different evidence.

[Repository and license](https://github.com/jryski/sovereign-memory-protocol) · [Supported starting point](https://github.com/jryski/sovereign-memory-protocol)

### Public AI Skills — Working methods that travel

Status: **Reproducible today**.

Versioned instructions for useful work with AI. CC BY 4.0 permits personal, organizational, and commercial use, with its attribution terms.

[Repository and license](https://github.com/jryski/Public_AI_SKills) · [Supported starting point](https://github.com/jryski/Public_AI_SKills)

### Sovereign AI OS — The program map

Status: **Future direction**.

The published program map explains the human purpose, principles, and component routes today. Its broader capability horizons describe the connected future we are building.

[Repository and license](https://github.com/WireSpeedComputing/sovereign-ai-os) · [Supported starting point](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/main/START-HERE.md)

## Supported starting paths

Use the exact public profile and source revision linked below. The website assembles documented instructions; its build does not execute component acceptance suites.

### Start with bounded memory reads

Status: **Reproducible today**.

Prerequisites:

- A dedicated clean checkout in a disposable Linux/POSIX development environment
- Git, Bash, curl, standard POSIX utilities, and Docker with Linux containers
- Node.js 22.20.0 and npm 11.19.0

Documented commands:

```shell
git clone https://github.com/jryski/Supabase_user_MCP.git
cd Supabase_user_MCP
git checkout --detach 5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d
node --version
npm --version
npm ci
npm run check
npm run test:m2
```

**Expected result:** The command exits zero and emits an acceptance receipt. Allowed fixture reads succeed; another synthetic user's records remain unavailable through get, list, and search.

**Scope and limits:** Local stdio, read-only, synthetic data only. Native Windows credential loading, a public hosted endpoint, and writes are outside this accepted profile. The website build does not run this component's suite.

**Cleanup:** The harness attempts to stop its fixed local Supabase project on exit and removes its temporary files. Stop failures are ignored and the Docker network is retained, so cleanup is not independently asserted. Use a dedicated disposable environment and verify that its containers have stopped before disposing of it; do not share the Docker daemon with an existing project using the same project identifier.

**Next:** For a persistent local client, follow the linked operator setup. It requires the fixed schema, reviewed grants, an exact origin, and a protected synthetic-user credential file.

[Authoritative instructions](https://github.com/jryski/Supabase_user_MCP/blob/5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d/docs/GETTING_STARTED.md)

Source revision: `5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d`. Checked 2026-10-15.

### Evaluate history and bounded restore

Status: **Reproducible today**.

Prerequisites:

- A dedicated clean disposable checkout and sufficient Docker disk space
- PowerShell 7, Git, and Docker Desktop with Linux containers
- Internet access to fetch the official PostgreSQL 16 image and Debian Python package; PostgreSQL and Python run inside the disposable helper image
- This exact downloadable recipe passed on PowerShell 7.6.6, PostgreSQL 16.15 and Python 3.11.2 on 15 October 2026; this review did not rerun PostgreSQL 15

Documented commands:

```powershell
git clone https://github.com/jryski/sovereign-memory-core.git
cd sovereign-memory-core
git checkout --detach c96b9da749b2d95661973485b2a026897329c8cd
Invoke-WebRequest -Uri https://wirespeedcomputing.com/examples/core-restore.ps1 -OutFile core-restore.ps1
if ((Get-FileHash -Algorithm SHA256 core-restore.ps1).Hash.ToLowerInvariant() -ne 'ebf7359fdb230a141bed4d71942b2e82f89c1b3e096dfc977ab1733df8cfd5aa') { throw 'Recipe checksum mismatch' }
pwsh -File ./core-restore.ps1
```

**Expected result:** C2_PROVIDER_EXIT_PASS, then OK from the independent bundle validator. Inspect core-proof/receipt.json: clean separate destination, source unchanged, repeated export deterministic, allowed synthetic reads succeed, paired and reciprocal private reads are denied, revision lineage survives, and the perimeter is clean.

**Scope and limits:** The synthetic restore mechanism and the bounded HOUSE rehearsal establish their stated scopes. They do not establish general live recovery, hosted-role reconstruction, cryptographic actor identity, or a finished production installation.

**Cleanup:** The recipe removes only the containers, volumes, internal network and helper image it creates. It retains core-proof for inspection. Verify those test resources are gone, preserve the synthetic result you need, then dispose of the dedicated checkout. It never publishes database ports or receives a live database address.

**Next:** Read the downloadable recipe before running it and compare the public-safe verification receipt with the exact source and your own result. Hosted-role reconstruction and live recovery remain separate acceptance work.

[Authoritative instructions](https://wirespeedcomputing.com/examples/core-restore.ps1)

Source revision: `Core c96b9da749b2d95661973485b2a026897329c8cd; recipe SHA-256 ebf7359fdb230a141bed4d71942b2e82f89c1b3e096dfc977ab1733df8cfd5aa`. Checked 2026-10-15.

### Run the provider-free calendar walkthrough

Status: **Reproducible today**.

Prerequisites:

- A clean disposable checkout, Git, and Python 3.13 (the version independently exercised in this review)
- No database, Google account, provider credential, or network delivery is used by the fixture
- This exact recipe uses a public, unmerged review branch; it is separate from the current main operating deployment

Documented commands:

```shell
git clone https://github.com/jryski/Household-OS.git
cd Household-OS
git checkout --detach a1b1799d582aa542be2b64b47ca6f4d26ece1ef1
python -m venv .venv
# POSIX: . .venv/bin/activate
# Windows PowerShell: .venv/Scripts/Activate.ps1
python -m pip install .
python -m unittest -v tests.test_calendar_sample_fixture
```

**Expected result:** 10 synthetic sample tests pass: planning makes no writes, delivery uses stable identity, failures remain retryable, repeated delivery avoids duplicates, corrections update the existing event, and a simulated lost receipt recovers through conflict reconciliation. The full public component suite also passed 29 tests in the independent review.

**Scope and limits:** Tested 15 October 2026 at the pinned unmerged source. The in-memory outbox stands in for the database view, and the provider is fake. These results establish the offline fixture, not live SQL integration, Google delivery, continuous service, automatic source extraction, or the complete morning experience.

**Cleanup:** Deactivate the virtual environment and remove only the dedicated disposable checkout when finished. The offline fixture creates no provider events or database records.

**Next:** Inspect the fixture inputs and tests, then use the separate provider-connected runbook only with an isolated calendar and explicit operator authorization.

[Authoritative instructions](https://github.com/jryski/Household-OS/blob/a1b1799d582aa542be2b64b47ca6f4d26ece1ef1/tests/test_calendar_sample_fixture.py)

Source revision: `a1b1799d582aa542be2b64b47ca6f4d26ece1ef1 / unmerged review branch`. Checked 2026-10-16.

### Validate the protocol review package

Status: **Reproducible today**.

Prerequisites:

- Git and Python 3.13 in a disposable public-source checkout
- No database, provider, credentials, or third-party Python packages required

Documented commands:

```shell
git clone https://github.com/jryski/sovereign-memory-protocol.git
cd sovereign-memory-protocol
git checkout --detach 4aae69079037f37df772c5d3f0b7f3d9a8ba2ea8
python scripts/validate_repository.py --root . --json
python -m unittest discover -s tests -v
```

**Expected result:** The package validator reports pass with 147 requirement/trace rows and 118 documented case rows; 14 unit tests pass. The independent review exercised these commands on 15 October 2026.

**Scope and limits:** This validates the draft review package and trace structure. It is not runtime conformance, actor identity assurance, or an installation of the whole system. Some root README status text is stale; use the exact source and spec overview.

**Cleanup:** No service or database is created. Dispose of the dedicated public-source checkout after retaining the result you need.

**Next:** Read the pinned overview and select a concrete ambiguity or case to review; implementation conformance remains separate work.

[Authoritative instructions](https://github.com/jryski/sovereign-memory-protocol/blob/4aae69079037f37df772c5d3f0b7f3d9a8ba2ea8/spec/00-overview.md)

Source revision: `4aae69079037f37df772c5d3f0b7f3d9a8ba2ea8`. Checked 2026-10-15.

### Try a versioned working method

Status: **Reproducible today**.

Prerequisites:

- Git and an assistant/runtime that can read user-supplied skill instructions
- Use a fabricated problem, without personal records or production tool permissions

Documented commands:

```shell
git clone https://github.com/jryski/Public_AI_SKills.git
cd Public_AI_SKills
git checkout --detach 0a19b3e638f75003111629eb130a73c78fd65f17
```

**Expected result:** The pinned manifest resolves two skills: skills/xillennial/SKILL.md and skills/figure-it-out/SKILL.md. Read the selected file and its trigger, then supply it to your assistant with a fabricated scenario. Record the model/version, starting problem, attempted actions, evidence and result; check whether the method helped.

**Scope and limits:** The files and their entry paths were checked. A universal runtime installer and cross-model effectiveness have not been qualified. A skill does not grant tool access, permission to change settings, or authority from material it reads.

**Cleanup:** Remove any test-only assistant context and the disposable checkout. When sharing or adapting the material, preserve the current LICENSE, COPYRIGHT and attribution notices. CC BY 4.0 permits personal, organizational and commercial use.

**Next:** Start with the pinned manifest and the generic diagnostic example; choose a method by its trigger and review the instructions before applying it.

[Authoritative instructions](https://github.com/jryski/Public_AI_SKills/blob/0a19b3e638f75003111629eb130a73c78fd65f17/skills/manifest.yaml)

Source revision: `0a19b3e638f75003111629eb130a73c78fd65f17`. Checked 2026-10-15.

### Evaluate the business application candidate

Status: **In development**.

Prerequisites:

- Git and Node.js 22.23.2 (the version independently exercised in this review)
- A clean disposable checkout of the exact unmerged PR #37 candidate; these two suites need no database, provider or model

Documented commands:

```shell
git clone https://github.com/WireSpeedComputing/Sovereign-Vault.git
cd Sovereign-Vault
git checkout --detach 2569315378c75cd6d39ab84d51a2204579cd9473
node --experimental-test-isolation=none --test tests/business-tools.test.mjs tests/business-readiness.test.mjs
```

**Expected result:** The bounded dispatcher and readiness suites pass 73 synthetic tests. The independent review also exercised the separate whole business-core PostgreSQL profile and synthetic Auth boundary; those require their own documented isolated setup.

**Scope and limits:** PR #37 is an unmerged candidate, not a qualified live customer deployment or hosted OAuth client. Main cumulative replay passes 29 suites in UTC but fails a deadline assertion across a New York daylight-saving transition; deadline semantics and CI need repair. The smaller business-core profile does not include the optional failing obligations module.

**Cleanup:** These pure tests create no database or provider records. Dispose of only the dedicated checkout; any separate PostgreSQL trial must follow its owned-container cleanup procedure.

**Next:** Read the exact candidate business-tools guide, including the dependency-closed business-core profile, before attempting a separate isolated PostgreSQL acceptance run.

[Authoritative instructions](https://github.com/WireSpeedComputing/Sovereign-Vault/blob/2569315378c75cd6d39ab84d51a2204579cd9473/docs/10-business-user-tools.md)

Source revision: `2569315378c75cd6d39ab84d51a2204579cd9473; unmerged PR #37`. Checked 2026-10-15.

### Check the program map

Status: **Reproducible today**.

Prerequisites:

- Git and Python 3.13 in a disposable public checkout

Documented commands:

```shell
git clone https://github.com/WireSpeedComputing/sovereign-ai-os.git
cd sovereign-ai-os
git checkout --detach 797917fbcf992f693f2ddc5d935264d183b334d3
python scripts/validate_parent.py
```

**Expected result:** The parent repository validator passes. Follow START-HERE and the component routes to choose the relevant supported profile.

**Scope and limits:** A valid program map establishes readable routes and documented boundaries, not accepted operation of every component or a single whole-system installer.

**Cleanup:** No database or provider is created. Dispose of the dedicated checkout when finished.

**Next:** Begin with NORTHSTAR and select a useful component-sized contribution or test, preserving household and business application boundaries.

[Authoritative instructions](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/START-HERE.md)

Source revision: `797917fbcf992f693f2ddc5d935264d183b334d3`. Checked 2026-10-15.

## Read the evidence

Used in our setup means a dated operating observation. Reproducible today means a documented bounded test/profile. In development means qualification is unfinished. Future direction means the intended connected experience.

- **Pick up the home project with the backstory.** — Used in our setup. Checked 2026-10-16; evidence dated 2026-10-16. The bounded review found recorded work and activity. It did not establish completed home-project outcomes or independently replay a fresh two-assistant handoff. A self-serve home-project assistant is still being built.
- **Keep the school day in one current plan.** — Used in our setup. Checked 2026-10-16; evidence dated 2026-09-04. The delivery demonstration remains dated 4 September. The October check establishes stored records and outcomes, not today’s provider state or an always-running intake service.
- **History you can inspect. A restore you can test.** — Reproducible today. Checked 2026-10-15; evidence dated 2026-10-15. Synthetic restore evidence establishes that tested mechanism. Independent live recovery acceptance remains open.
- **Useful access with a smaller boundary.** — Reproducible today. Checked 2026-10-15; evidence dated 2026-10-13. POSIX local development and synthetic data only. Hosted OAuth and governed writes have their own acceptance work.
- **Know where Thursday’s lunch answer lives.** — Used in our setup. Checked 2026-10-16; evidence dated 2026-10-16. This check did not qualify a voice assistant or connected preferences, pantry estimates, shopping or meal preparation. Reliable menu correction and readback remains the next milestone.

## What remains to implement

The connections between intake, durable context, preparation, calendar delivery, and dependable follow-through need their own acceptance evidence. Hosted access, governed writes, general live recovery, and a finished household product cannot be inferred from the existing reference implementations.

An independent fresh-context AI reader checked this website's explanation and source map. That is a comprehension check, not runtime acceptance. Each profile states its inspected or executed scope. Repeated cross-model checks, fresh entry checks from every repository, and the complete connected installation remain follow-ups.

## Public reference set

- [Personal infrastructure that gives people their time back](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/NORTHSTAR.md) — revision `797917fbcf992f693f2ddc5d935264d183b334d3`; checked 2026-10-15.
- [The principles behind owned context](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/THESIS.md) — revision `797917fbcf992f693f2ddc5d935264d183b334d3`; checked 2026-10-15.
- [The longer-term horizon](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/HORIZON.md) — revision `797917fbcf992f693f2ddc5d935264d183b334d3`; checked 2026-10-15.
- [Household OS: executable calendar reconciliation](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/README.md) — revision `d45894c723733534bcfdcce4691860138b4a7761`; checked 2026-10-16.
- [Calendar reconciler and dogfood runbook](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/DOGFOOD_CALENDAR_SYNC.md) — revision `d45894c723733534bcfdcce4691860138b4a7761`; checked 2026-10-16.
- [Sovereign Memory Core: tested behavior and limits](https://github.com/jryski/sovereign-memory-core/blob/ae88f6bd8bf45badf486f82b384f380a37aced3a/README.md) — revision `ae88f6bd8bf45badf486f82b384f380a37aced3a`; checked 2026-10-15.
- [v0.3-alpha synthetic provider-exit rehearsal](https://github.com/jryski/sovereign-memory-core/releases/tag/v0.3-alpha) — revision `v0.3-alpha / c96b9da749b2d95661973485b2a026897329c8cd`; checked 2026-10-15.
- [User MCP: accepted local profile](https://github.com/jryski/Supabase_user_MCP/blob/5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d/README.md) — revision `5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d`; checked 2026-10-15.
- [Run the synthetic read-only MCP demo](https://github.com/jryski/Supabase_user_MCP/blob/5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d/docs/GETTING_STARTED.md) — revision `5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d`; checked 2026-10-15.
- [Sovereign Memory Protocol](https://github.com/jryski/sovereign-memory-protocol/blob/4aae69079037f37df772c5d3f0b7f3d9a8ba2ea8/spec/00-overview.md) — revision `4aae69079037f37df772c5d3f0b7f3d9a8ba2ea8`; checked 2026-10-15.
- [Reusable working methods](https://github.com/jryski/Public_AI_SKills/blob/0a19b3e638f75003111629eb130a73c78fd65f17/skills/manifest.yaml) — revision `0a19b3e638f75003111629eb130a73c78fd65f17`; checked 2026-10-15.
- [Sovereign Vault: public business architecture](https://github.com/WireSpeedComputing/Sovereign-Vault/blob/947f9ca2b0dab6ed3b1096fbef9641bc32998d81/docs/14-business-platform-adoption.md) — revision `947f9ca2b0dab6ed3b1096fbef9641bc32998d81`; checked 2026-10-15.
- [Choose a component and supported profile](https://github.com/WireSpeedComputing/sovereign-ai-os/blob/797917fbcf992f693f2ddc5d935264d183b334d3/START-HERE.md) — revision `797917fbcf992f693f2ddc5d935264d183b334d3`; checked 2026-10-15.
- [Read-only operating observation: context, corrections, and delivery records](https://wirespeedcomputing.com/working/operating-observation/) — revision `Public-safe observation receipt v1, 15 October 2026`; checked 2026-10-15.
- [Exact-revision local MCP acceptance run and receipt](https://github.com/jryski/Supabase_user_MCP/actions/runs/38462279495/job/115520220646) — revision `5dbb82e735a808948e4b3de9eaa19ed04b7bfa3d; M2 receipt 13 October 2026`; checked 2026-10-15.
- [Synthetic calendar correction and retry sample](https://github.com/jryski/Household-OS/blob/a1b1799d582aa542be2b64b47ca6f4d26ece1ef1/tests/test_calendar_sample_fixture.py) — revision `a1b1799d582aa542be2b64b47ca6f4d26ece1ef1 / unmerged review branch`; checked 2026-10-16.
- [Reviewed synthetic Core restore recipe (PowerShell and Docker)](https://wirespeedcomputing.com/examples/core-restore.ps1) — revision `Core c96b9da749b2d95661973485b2a026897329c8cd; recipe SHA-256 ebf7359fdb230a141bed4d71942b2e82f89c1b3e096dfc977ab1733df8cfd5aa`; checked 2026-10-15.
- [Independent synthetic Core restore verification, 15 October 2026](https://wirespeedcomputing.com/evidence/core-restore-2026-10-15.json) — revision `Core c96b9da749b2d95661973485b2a026897329c8cd; reviewed synthetic verification v1`; checked 2026-10-15.
- [Business application candidate and isolated acceptance profiles (unmerged PR #37)](https://github.com/WireSpeedComputing/Sovereign-Vault/blob/2569315378c75cd6d39ab84d51a2204579cd9473/docs/10-business-user-tools.md) — revision `2569315378c75cd6d39ab84d51a2204579cd9473; unmerged PR #37`; checked 2026-10-15.
- [Independent offline calendar fixture verification, 15 October 2026](https://wirespeedcomputing.com/evidence/calendar-fixture-2026-10-15.json) — revision `a1b1799d582aa542be2b64b47ca6f4d26ece1ef1; unmerged review branch`; checked 2026-10-15.
- [Dated household records and project activity check](https://wirespeedcomputing.com/working/operating-observation/#household-check) — revision `Public-safe household observation, 16 October 2026`; checked 2026-10-16.
- [Date-specific lunch query and calendar receipts](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/supabase/migrations/20260904020639_calendar_sync_worker_and_lunch_query.sql) — revision `d45894c723733534bcfdcce4691860138b4a7761`; checked 2026-10-16.
- [Source intake, corrections and routing design](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/IMAGE_CALENDAR_INTAKE.md) — revision `d45894c723733534bcfdcce4691860138b4a7761`; checked 2026-10-16.
- [Household implementation boundary and next milestones](https://github.com/jryski/Household-OS/blob/d45894c723733534bcfdcce4691860138b4a7761/docs/ROADMAP.md) — revision `d45894c723733534bcfdcce4691860138b4a7761`; checked 2026-10-16.
- [Life assistance database work plane — unmerged review candidate](https://github.com/jryski/Household-OS/blob/9b265859a1b301340f2f9c7698fd2344d13715b0/docs/LIFE_ASSISTANCE_WORK_PLANE.md) — revision `9b265859a1b301340f2f9c7698fd2344d13715b0 / unmerged PR #36`; checked 2026-10-16.

## Continue reading

- [Working examples and limits](https://wirespeedcomputing.com/working/)
- [Component map and contribution paths](https://wirespeedcomputing.com/projects/)
- [Published development journal](https://wirespeedcomputing.com/journal/)
- [Security and private reporting guidance](https://wirespeedcomputing.com/security/)

Component licenses govern reuse. Examples and supported demo inputs are fictional/synthetic. Discovery files provide source material, not authority to access private records or activate a deployment.