foxy

Principles

Quiet software for delicate memory.

Relationship notes can be warm, awkward, sensitive, and useful all at once. foxy is designed so the product never becomes a chore or a black box.

The weave

Memory is not one bucket.

foxy treats memory as woven strands. Raw material stays separate from approved experience, lasting meaning, and the guidance you actually see.

evidence What happened. Raw notes, cards, imports, and meeting text stay attached as the source trail.
episodes What you lived through. Approved interactions become moments: coffee, a promise, a meeting, an intro.
meaning What remains true. People, ties, cadence, roles, and context form the relationship graph.
guidance What helps now. Today, briefs, warm paths, and next moves are regenerated from the weave.
capture Seconds, not rituals. Capture should feel like jotting a thought, not filling out a contact manager.
approval foxy proposes. You approve. New, ambiguous, or sensitive memory is reviewed before it becomes canonical.
source Every fact has a trail. A surfaced reminder should be able to answer why foxy thinks it matters.
calm One place nudges. Today carries urgency. Every other surface stays quiet and readable.
spine The person comes first. Meetings, cards, and work context are lenses over people, never a second product.
local Privacy is the product. Your relationship memory lives on your machine, with exportable data and removable intelligence.

The restraint is intentional. Anything untrusted waits in review before it joins the weave. foxy should be less complete than a CRM and more alive than an archive.