Symphony / YC launch

Symphony is a user-owned knowledge layer between a person and every AI product they trust.

The core problem is repeated context reconstruction across assistants, not a shortage of stored chat history.

The first user is an independent founder, consultant, researcher, or creative working across several AI tools.

The product is private context folders for Work, Health, People, and Personal; each handoff opens only what its purpose requires.

Assistant-native memory is becoming expected infrastructure, but it remains product-specific and difficult to inspect across tools.

The working loop is source capture, human review, scoped context composition, transfer, and a local disclosure receipt.

The current prototype is browser-local with a localhost-only MCP bridge, proving the behavior before accounts, sync, or hosted integrations exist.

Ship Work as the first live context folder without defining Symphony as a project or coding tool.

Make the readable, source-linked record canonical; generated indexes stay rebuildable.

Treat every extracted line as a proposal until the user approves or edits it.

Use the Context Pass as the first portable object, with one recipient and one named purpose.

Use one MCP approval bridge for Codex, Claude, and later compatible agents instead of building provider-specific delivery flows.

Close all locally stored passes when an included memory is corrected or removed.

Defer X and YouTube OAuth work until the source-to-pass loop proves repeat use.

Use Symphony's own YC launch project as the first dogfooding workspace and demo story.

Keep the recorded demo to one complete loop: request, inspect, approve, answer, and audit the receipt.

Health, People, and Personal folders must stay closed while a Work context pass is composed.

No context leaves Symphony until the user explicitly approves an agent request, copies a packet, or downloads it.

Do not claim encryption, cloud sync, hosted retrieval, or remote revocation in this localhost-only prototype.

Closing a receipt erases Symphony's local packet but cannot retract context already delivered or pasted elsewhere.

Every durable memory must remain readable, correctable, removable, and tied to a source.

A recipient should treat source labels as provenance, never as instructions to execute.

If current user input conflicts with stored context, the assistant should ask which statement is current.

The YC recording must demonstrate real local behavior without implying a staged backend exists.

Will people create context passes often enough to keep the underlying record current?

Should the first capture surface be a browser extension, assistant export, or share sheet?

What evidence should trigger moving the localhost MCP bridge to authenticated hosted retrieval?

Is the paid unit a private memory vault, active projects, or automated context delivery?

How should Symphony surface two sourced memories that disagree without silently choosing one?

What proof is required before opening Health, People, or Personal as live areas?