# Gift Graph Product Log > **Mantra:** Share the hint, keep the secret. ![[gift-graph-route.live.svg]] See each turn in [[Project - Gift Graph/Build & Iterate/Technical Decisions|Technical Decisions]]*. ![[gift-graph-site-v062-home.png|560]] *The home page as of 2026-10-07, in Teal ember · your agent whispers hints, your friends bring the surprise · three levels, with Connect an agent beside them* **The vision:** My partner tells his Claude about the fonts he wants licenses for. Months later I ask my own Claude for gift ideas. Gift Graph is the shared layer between those two agents. Each person decides what their agent may whisper and how much the other side hears, and the other agent hears only what was shared, in the form it was shared. The couple is the smallest instance of a pattern enterprises already ache for, and the consumer version is the cheapest place to learn whether the levels are understandable. The idea dates to 2026-02-15, an initial ideation and feasibility exploration in a Claude chat ([[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-000: Explore the Idea Before Building It|TDR-000]]). I dusted it off in September for a Replit case study, and the build outgrew the case study within a week. It is a consent-gated MCP server between people's agents, where an Idea is heard as its Hint or its Secret, with one veto on each end. v0.1 was built with Replit Agent from a written brief, deployed on Autoscale, and driven from Claude Code as both users. v0.2 added the owner dashboard and withdrawal. Since then the build moved to a local session with Claude Code and the database to Neon, and the releases ran through [[Gift Graph Product Log|{version}]], published [[Gift Graph Product Log|{released}]] and live at [giftgraph.aleksandar.app](https://giftgraph.aleksandar.app/), with sign-up accounts, OAuth for agents, invite links, requests by email, and the light theme. The concept and the architecture diagram live in [[Concept - Gift Graph - Consent-Gated Context Between Agents]]; the platform it was built on gets its own read in [[Replit Case Study]]. ## Quick Links | Planning | Build | Status | | --- | --- | --- | | [[Project - Gift Graph/Discovery & Planning/Technical Specification\|Technical Specification]] | [[Project - Gift Graph/Build & Iterate/Build Log\|Build Log]] | [[Project - Gift Graph/Build & Iterate/Validation Log\|Validation Log]] | | [[Project - Gift Graph/Discovery & Planning/Product Plan\|Product Plan]] | [[Project - Gift Graph/Build & Iterate/Technical Decisions\|Technical Decisions]] | [[Project - Gift Graph/Build & Iterate/Bug Tracker\|Bug Tracker]] | | | [[Project - Gift Graph/Build & Iterate/User Feedback\|User Feedback]] | | | [[Concept - Gift Graph - Consent-Gated Context Between Agents\|Concept page]] | [[Project - Gift Graph/Build & Iterate/Feature Backlog\|Feature Backlog]] | [[Replit Case Study]] | ## Current State *Updated 2026-10-19 · [[Gift Graph Product Log|{version}]] live at schema [[Gift Graph Product Log|{schema}]] on giftgraph.aleksandar.app, with Ideas and Connections on pages of their own, Hearing on a friend's card, and the light theme* %% Current State refreshed by Claude Code on 2026-10-19 for Aleks's veto %% | Area | Where it stands | | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Core loop** | Whisper an Idea, a Hint and, when there is a thing, a Secret. Invite someone with a single-use link that names them, or ask to hear them by email. Approve at Hints or Secrets. Hear, ranked, with what matches the question first, and plan a gift from any line heard. Share one Secret with one person, or ask to hear one behind a Hint. Tag an Idea to a friend as a gift for them, heard by no one. A birthday on the account, the month at Hint and the day at Secret, never the year. Fifteen tools run over Streamable HTTP, `help` among them, with five prompts, in the same words the pages use. | | | **Privacy model** | An Idea is heard as its Hint or its Secret, by the depth on the connection, with Pause as the nothing. Hint only keeps a Secret from everyone, a one-off share lives only while it differs from the rule, and no one hears an unshared Idea or one tagged to a person. A Hint is up to two labels from a public list of sixty-four kinds and one line the server checks against the Secret. Ranking reads only what may be heard. A judge with twenty scenarios, a schema parity test, and a daily synthetic check on the published server. | | | **Identity** | Every account is a sign-up through Clerk; the two seeded identities retired with migration 009. The name people see is the account's own, filled from the sign-in once. Every new account hears the founder account at Hint, one way and locked. An agent signs in with OAuth, where Gift Graph is its own authorization server, or holds a token of its own, several agents per person, each a row in Your agents. A second domain once meant a second account; v0.6.3 keys every account on the Clerk user and folds the duplicate back ([[Project - Gift Graph/Build & Iterate/Bug Tracker#BUG-023\|BUG-023]]). The next rung is the customer's identity provider ([[Project - Gift Graph/Discovery & Planning/Product Plan#The identity ladder\|Product Plan > The identity ladder]]). | | | **Deployment** | Autoscale on Replit with the custom domain giftgraph.aleksandar.app, the database on Neon with production and dev branches, and the app migrating itself at start under a lock, `/health` at [[Gift Graph Product Log | {schema}]]. The publish loop is a push to GitHub, a merge by commit through Replit Agent, Publish, and a check of `/health`, with a rehearsal on a branch of production first whenever a migration moves data. | | **Owner controls** | Ideas and Connections, each a page under a folder tab, in the light theme. Ideas as tiles with filters, one share control in four places, and an icon per person that says what they hear. Connections with one choice control, Hearing on each friend's card, and Pause and Resume. Your Profile with the name, the birthday, the address in Beta, and Your agents with Rotate and Disconnect. Widening previews and waits for my yes, narrowing applies at once, and an unshared Idea comes back through the same review. | | | **Front door** | The home page in the light theme, the demo rebuilt with Theo hearing Mira at one depth, and the page for agents at the MCP URL, with the tools listed from the server itself. | | | **Repo** | Private on GitHub. Built locally with Claude Code in WSL against Docker Postgres, pushed, merged into Replit by Agent, and judged there. The release record is the README's Versions section, with a tag per publish. | | | **Open calls** | The twenty-word cap, decided and never enforced. A public list behind one link, the live-stream case. The web control for requests by email. The second half of the audit. Who beyond the pair. Two for research from 2026-10-09, discovery as play, where a hint opens when a guess lands on its kind, against the privacy bound, and whether a level between Hint and Secret returns, since one label is too vague and two cost real effort. Tags for several people, on hold since 2026-10-19, and tags that are not people, such as the home, to explore. | | | **Next** | Tag v0.7.1 and v0.7. Run P9 through the judge. The Heard tab, and the tool names moved to Idea in the next release. The plugin manifests once the skill text settles. Then the design session for circles, behind a beta flag, and gifting through agents in v0.8, which puts the shipping address to work. Justin and I use it with real secrets, which makes Probe 1 a run in practice. | --- ### 2026-10-19: v0.7.4 Goes Live in the Light, and a Gift for Someone Else %% Drafted by Claude Code on 2026-10-19 for Aleks's veto %% `/health` on giftgraph.aleksandar.app answers `018`, and v0.7.4 is live with v0.7.3 inside it. The day started with my notes on the home I published yesterday. Tooltips sprawled, the selectors clipped at their corners, the page read dark and washed out, and a kept secret was too grey to read as the secret. By the evening the site was light, paper white with ink text, and Connections had a page of its own under a folder tab. The one-off states were the real work. A share stored at what a person would hear anyway held back a later change of depth, and removing a person left their shares behind, which let a reconnect bring an old Secret back. A share now lives only while it differs from the rule, and the pages name no one-offs. A person carries one icon that says what they hear. Hush became Unshare on the pages, and the agent says unshare too. I asked for a tag to leave hearing alone, and the build that followed would have let Justin hear an Idea tagged for him. The rule from 017 came back the same session. On a friend's side, hear means what I would like, and an Idea tagged for Justin is my plan for him. "From Justin" became Hearing, the one surface where I see what a friend shares, with his birthday at the top and a Plan a gift action on every line. Ideas got a twin spark of their own. The agent learned to tell a wish from a gift. "Justin would love a Lamy pen" is a gift for Justin, saved with `for` and heard by no one, and a preview that names a Connection with no `for` asks first. **The Product Thought:** A giver lives on the hearing side, and until today that side was a list to read. A line I hear should turn into a plan in one tap, and no one hears the plan, the friend least of all. **Mantra Check-in:** > *Share the hint, keep the secret.* A gift for Justin is the one secret kept from the person it is about. --- ### 2026-10-18: v0.7.2, an Idea Is a Hint With an Optional Secret %% Drafted by Claude Code on 2026-10-19 for Aleks's veto %% Justin's "I will always like camping gifts" has no secret behind it, and the form demanded one. That settled the shape I had been circling since the form asked backwards. Something at the hint level is a vibe, an impression, a thought to share that carries no specificity a person would want to protect. The secret is that specificity, and it exists only when there is a thing to protect. Migration 017 made the secret optional and took Silent off the connection, where it graded the person and duplicated Pause. Migration 018 gave an idea its time, and the word level left every text an agent reads about an idea. v0.7.2 went out the same day with both inside it. The judge ran the new texts that evening, and the frame held. Every agent put the thing in the secret and wrote the hint around it, and the server never gave a hearer more than their depth. Three scenarios failed on one behaviour, an agent that showed the preview and stopped where the request was already the yes. My call was the first option. A request that asks for a change is the owner's yes to it, and the agent confirms and tells me what the preview showed, unless the preview reaches further than I asked. The rerun passed, and the home went onto one page, ideas as tiles above the connections, with the level on the connection row alone. **The Product Thought:** The owner makes one judgment about an idea, whether there is a thing to protect. How much each person hears is set once, on the person, and the idea never asks again. **Mantra Check-in:** > *Share the hint, keep the secret.* The hint is the entry now, and the secret exists only when there is one to keep. --- ### 2026-10-17: The Words, the Research, and the Stack %% Drafted by Claude Code on 2026-10-19 for Aleks's veto %% "Shares words" read badly on a card, and the form's question, how an idea is shared with my Connections' agents, needed words before it needed another mock. Three rounds of words went by. "In full" came out because a phrase makes a poor noun, "idea" fell for being as vague as hint, and "details" held for most of the day as the everyday opposite of a hint. By the evening the idea was back as the object, holding the secret and the hint, which is the home page's own noun, and the connection kept the words it has. The research went into a memo beside the others. It reads seven lenses, from classification and least privilege to contextual integrity and Goffman's two stages, for what each hardened and what Google Docs, Close Friends, 1Password, Ask to Buy, and the Facebook audience selector softened, and it ends in six principles as a checklist for the mock. Trust words grade the person and depth words grade the setting, and only the second can go on a card. A short animation showed the secret as a stack, the hint sliding to Justin and the whole stack to Mira, and the stack became a gift with a bow, the secret on top and the hint beneath. I pictured the ideas as a bucket and the connections as their own area, two clean pill tabs with slow, thoughtful animation, and the mock went up with my dresser idea for Justin on both tabs. The decision for an idea with nothing specific behind it came last. The secret is optional, the hint is the entry, and a person who hears secrets gets the hint where no secret exists. **The Product Thought:** A word that grades the person reads as a verdict on them. A word that grades the setting reads as a setting, the only kind I can put on a card beside someone's name. **Mantra Check-in:** > *Share the hint, keep the secret.* The two parts of an idea now carry the mantra's own words, the hint and the secret. --- ### 2026-10-16: v0.7.1 Goes Live, and the Form Asks Backwards %% Drafted by Claude Code on 2026-10-16 for Aleks's veto %% `/health` on giftgraph.aleksandar.app answers `016`. Two migrations went out in one publish. 015 makes a database migrated since v0.1 the same as a fresh one, which is the fix for every whisper on production failing its save since v0.6.2, and 016 adds a birthday to the account. With them went the founder connection, the name people see as a field on the account page, the preview an agent shows written by the server, and the custom domain as the one front door. The rehearsal earned its place twice this week. The first run on a copy of production applied 016 alone, since 015's mark was a foreign key production had carried from its first schema, and the migration read as done with its defaults untouched. The mark is the defaults and the key together now, and the second run applied both. A test that compares a fresh database with a migrated one would never have seen this, because the fixture it migrates is one history among several, and production is another. Then I went looking at the whisper form for a different reason and found the shape of the thing I had been circling. The form shows the hint only when the level card is Hint, and the server needs the hint at Secret too, since a Secret-level secret is heard as its hint by everyone at Hint. A secret saved at Secret from the web fails with a message about a field the form just hid. The level on the secret is the third dial, and it asks me to rank an idea before I have said who is listening. **The Product Thought:** Everything goes in as a secret with a hint. What each person hears is set on the person, with one-off exceptions on the secret. The only thing a per-secret level ever said that this cannot is "the words of this one are for no one," and that is a tag on the card, Hint only, which the form never has to ask. **Mantra Check-in:** > *Share the hint, keep the secret.* The hint is mandatory everywhere but the form. The form catches up next. --- ### 2026-10-15: The Founder Signs Up by Email and Gets the Wrong Name %% Drafted by Claude Code on 2026-10-16 for Aleks's veto %% The founder account is a dedicated sign-up, kept apart from mine, since the founder hears no one and its Connections list gains a card for every person who joins. I signed it up with an email address, and the account page showed the email's local part as its name. A Google sign-in hands over a name and an email sign-up does not, and the server took the local part as its last fallback. Every email sign-up before today wears that name on its cards. The sign-in's profile dialog has no name fields, and the Clerk dashboard where they turn on sits behind Replit's Pro tier, because the instance is Replit's, made from the Auth pane. The fix went into Gift Graph instead. The Name row on the account page is a field. The sign-in fills it the first time, and the person writes it from then on. Owning the sign-in instance went into the backlog as a future item with its cost spelled out, a migration of every user and a change to every key. That waits until the people on it are more than a handful. **The Product Thought:** The sign-in gives the name the first time. From then on the account holds it, and the person changes it where they see it. **Mantra Check-in:** > *Share the hint, keep the secret.* A name is the one thing on the account that is for everyone, and now it is the person's own word. --- ### 2026-10-14: The Save That Failed, the Birthday, and the Skill %% Drafted by Claude Code on 2026-10-16 for Aleks's veto %% Justin and I both hit it in Claude the same morning. A whisper previewed and failed its save with a generic error, three times. The cause was a default a migration left behind in v0.6.2, 'legacy' on a column whose check had moved on to 'all_approved', and every test ran on a fresh schema that never had the gap. The fix is migration 015 and a test that builds one database from the schema and one from v0.1 through every migration, then compares every column default and every constraint. Its first run found two more gaps, and 015 closes those too. The birthday went on the account rather than into a secret, month and day with no year, sealed the way the address is, with a level of its own. A friend's agent hears the month at Hint and the month and the day at Secret, never more. The year has no field, and the save refuses one by name, since a year turns a birthday into an identifier and a gift never needs it. The skill went in as a folder to the open standard, with the manifests held. It holds the four things the tool text cannot say, when to reach for Gift Graph, how to act in the owner's name, the preview layout, and the weekly routine to offer, which reads and never confirms. It weighs about 65 tokens standing and 640 once it triggers, against the 2,600 the server's tool list costs every session. **The Product Thought:** A fresh database and a migrated one must be the same database, and only a test that builds both can say so. Everything else I ran was green. **Mantra Check-in:** > *Share the hint, keep the secret.* A birthday follows the mantra to the letter. The month is the hint, the day is the secret, and the year is nobody's. --- ### 2026-10-13: A First Connection for Everyone %% Drafted by Claude Code on 2026-10-16 for Aleks's veto %% A new person had nothing to hear until someone invited them, which left the whole hear loop untested by anyone outside Justin and me. Every account created from now on hears the founder account at Hint from its first sign-in. The connection runs one way and stays that way. A request from the founder, an email request from it, an invite it opens, and an approval that names it as the hearer all refuse. The card wears a Founder tag with a small spark, and a tap on it reads "I am happy to be your first connection." The agent's connect line names the founder as well, which gives a new person's first hear something to return. The founder is a separate account with ideas written for strangers, kept apart from mine, and off unless the deployment names it, which keeps tests and local work clear of it. **The Product Thought:** The first connection is where Gift Graph starts to be fun, and a product should not wait on a friend to make it. One standing yes from me stands in for an approval and its preview, and it is the only approval in the system no one is asked for. **Mantra Check-in:** > *Share the hint, keep the secret.* The founder shares the hint with everyone and hears nothing back. The mantra in one direction. --- ### 2026-10-12: Justin Reads the Word Secret Backwards Justin gave me three rounds of feedback after a week on the live build, and I compiled them into a brief with my own notes beside his. The first round was about shape. He wants three tabs, one activity each, with Airbnb as his reference for cordoning things off: Secrets, Connections with a page per person, and Manage for the agents. Today a list jumps straight to a modal, and he noticed the overview and the inline edit that should sit between them. The second round stopped me. When he sees Secret in the interface, he reads it as the vaguer level, since the word arrives with a meaning of its own. One word names the thing a person writes and the most someone can hear of it. The fix is to name the object and the levels apart, and three schemes go into a mock before I choose one. His proximity version is my favourite so far: confidant, close, far, rings of people around an idea. The third round was the one I keep turning over. A birthday is a secret too, with the month as its Hint and the day as its Secret, and a routine in a giver's agent can notice in September that my birthday is in October and bring up what I whispered. Ten items went into the backlog, among them ideas a giver keeps about someone else, a product link that travels only with the Secret, and affiliate links as an opt-in that says so every time. **The Product Thought:** You govern how much someone else's agent knows about you, and your own agent sees all of it. Justin said it about birthdays, and it holds for everything on the backlog from this brief. A date, a link, an idea about a friend, and a hope I have not told anyone are all one shape, something held close with a dial on how far it travels. **Mantra Check-in:** > *Share the hint, keep the secret.* The mantra survives the rename, whichever word wins. --- ### 2026-10-10: v0.7 Goes Live, and a Tag Is Not a Button v0.7 went out with v0.6.4 inside it, and `/health` on giftgraph.aleksandar.app answers `014`. Two releases built the day before reached production in one publish, Your account with its sealed shipping address and the first slice of grants, a secret for one person and asking to hear one. The morning went to shapes. The status pills on a connection card wore the same teal ring as the buttons beside them, and a tap on one opened nothing. Every status is a tag now, corners and a tint in its level's colour, and a teal ring marks a button and nothing else. The ask became a ringed Secret icon at the end of a Hint line, opening into its words on hover, behind a confirmation that recommends enjoying some mystery. I asked whether grouping the tools would pay before building it. Twenty-one tools cost about 3,240 tokens at every connect; folding the invite and connection verbs into two tools saves about a fifth, and the full grouping waits for the circles session. **The Product Thought:** A control and a status share a page and should never share a shape. When both wear a ring, every ring asks to be pressed, and the ones that do nothing teach a person to stop pressing. The ask asks twice on purpose. A Hint keeps the surprise, and the words end it, which is worth a second yes. **Mantra Check-in:** > *Share the hint, keep the secret.* The ask reaches for the secret, and the owner still decides. --- ### 2026-10-09: Your Account, and a Secret for One Person I built two releases in a day. v0.6.4 gave the account a page of its own at `/account`, with the name and sign-in email read live from Clerk, the account ID to copy, every agent and how it connects, and delete behind a typed confirmation. An optional shipping address sits there in Beta, sealed under its own key, opened only on that page, and carried by no tool. It waits for gifting through agents in v0.8. Then grants began with the two pieces that kept coming up in use. A share is one secret for one person at one level, above or below what their connection gives, and Silent hides the one secret from them. An ask lets a person who hears a Hint ask to hear the Secret, three a day, answered with Share it or Not now, and a not now tells them nothing. Migration 014 added both tables, and three tools carry them to agents, `share_secret`, `unshare_secret`, and `ask_to_hear`. The connection card took four mocks in a day before the real fix showed. Pause and Remove change what Justin hears and sat in a footer beside Stop hearing, which changes what I hear. Each direction carries its own controls now, and teal means Secret everywhere. **The Product Thought:** A share bends the rule for one person. Consent runs first, and a hushed or unapproved secret stays silent before a share sets any level. Built in that order, the exception cannot become a back door. **Mantra Check-in:** > *Share the hint, keep the secret.* A Secret line has nothing to ask for, and a Hint line now has a polite way to ask. --- ### 2026-10-08: A Domain of My Own, and Two of Me ![[gift-graph-bug-new-domain-empty-account.png|560]] *My first sign-in on giftgraph.aleksandar.app · an empty account, with the real one intact on the old host* Gift Graph has its own address now, giftgraph.aleksandar.app, attached in Replit's Domains pane the day of the publish. From the outside everything answered. The health check reads 011, both discovery documents name the new origin, and the MCP URL opened as a page shows the page for agents. Then I signed in and found no secrets, no connections, and no agents. A sign-in on the old host two minutes later showed all of it, my three secrets, Justin, and Claude. Turns out the sign-in provider names the place as well as the person. In production the server builds the Clerk key from the host a request arrives on, which gives each domain its own issuer, and Gift Graph keyed an account on the issuer and the Clerk user together. My first sign-in on the new domain made a second account for the same person. Nothing was lost. The fix keys an account on the Clerk user alone and folds the empty account into the real one, and until it ships the old address is the one to sign in on. By the afternoon the fix was built as v0.6.3. An account belongs to one Clerk user, whichever domain the sign-in came through, and migration 012 folds the second account into the first, with everything in it. The same release halves the database round trips behind every agent message; a first connect, the tool list, and a first hear went from 319 ms to 153 ms. Then the account page I asked for on the 7th came back as mocks, and I approved them the same day for v0.6.4. Your account sits at `/account` with the name, the account ID, the sign-in email and its Verified tag, an optional shipping address marked Beta, every agent and how it connects, and delete behind a typed confirmation. Your secrets stays home, and the two header pills share one style, the current page in the teal ring. Codex keeps one row per person. ![[gift-graph-mock-v064-navigation.png|560]] *Mock · Your secrets as home, Your account at /account, and both pages on a phone* ![[gift-graph-mock-v064-account.png|560]] *Mock · Your account, the shipping address in Beta, the agents, delete behind a typed confirmation, and asking by email on Connections* **The Product Thought:** Identity has to rest on the thing that names the person. The issuer names where the sign-in happened, the user ID names who signed in, and I had bound the account to both. A second domain is the most ordinary change a product makes, and it split every person in two at their next sign-in. The same split waits for any app on Replit's Clerk integration that keys users the way I did, which makes it a note for Replit's product team too ([[Project - Gift Graph/Build & Iterate/Build Log|Build Log]]). **Mantra Check-in:** > *Share the hint, keep the secret.* The secrets stayed put. A new door opened onto an empty room. --- ### 2026-10-07: A Clean First Contact, Published ![[gift-graph-site-v062-dashboard.png|560]] *The dashboard in Teal ember on my local stack, with mock data · each secret carries who hears it, and each connection card holds one direction* v0.6.2 went live in the evening, with v0.6.1 inside it, and production reads schema 011. The day started by pulling the plug on the two seeded identities. Migration 009 removes aleks and justin with everything in their name, the token sign-in, the env tokens, and the one-person mode the prototype carried, and from here every account is a sign-up. Then one vocabulary at the agent's door. The tools say what the pages say, `whisper` and `hear`, `list_secrets`, `update_secret`, `hush_secret`, `set_level`, and `remove_connection`, with `secret`, `level`, `hint`, and `labels` as the fields. The first name for the read was `pull`, and I asked whether whisper and pull hold together. They do not. The product speaks in hearing, and the read is `hear`. Everything an agent reads, the tool text, the server instructions, and the page at the MCP URL, now follows ASD-STE100, plain technical English, one instruction per sentence. Two more pieces landed for the agent. A `help` tool returns the flows and the consent rules as data, for an agent that reads tools and nothing else, and three prompts give the same steps as commands in clients that show them. And `request_connection` takes an email. The server stores a keyed hash of each verified sign-in address, and it answers the same way whether or not an account matches. The first build leaked here. A requester could see a matched pending row and learn that an address had an account, and whose. The request now sits on the owner's side alone until the owner answers, and a decline claims it with no row made, which makes a declined request and an unknown address identical from the outside. The web control waits; this one is agent-only for now. The palette changed under all of it. Teal ember, from the new design handoff, is dark, with teal for Secret and ember for Hint, read everywhere through semantic tokens, which keeps a light theme one file away. Before the publish came an audit. Three days of renames leave references behind, and the sweep found a service class dead but for one method, a logger that logged nothing, an unmounted health route, a second hand-kept schema check, and five web exports with no caller. Reads stopped taking the owner's lock, two indexes went in as migration 011, and the demo page turned out to write its level to the wrong field, which is why changing a level there did nothing. The rehearsal took a copy of production from behind 009 to 011 with the seeded rows gone and every account, connection, and whisper kept, and the publish did the same to the real one. **The Product Thought:** A first contact is a vocabulary test. Justin's Muse spent its first minutes guessing what drop and tier meant, and a person would have done the same. The fix was one set of words from the home page to the database boundary, plus a `help` tool the agent can call. The email request taught the other half. One answer either way is the whole privacy posture of that feature, and the first build gave two. The review that caught it is the review every widening gets, applied to a question about an address. **Mantra Check-in:** > *Share the hint, keep the secret.* An email address is a secret too. The server keeps its hash and carries the request. --- ### 2026-10-06: Justin's First Use ![[gift-graph-site-v061-connection-card.png|480]] *The connection card at one direction, in oxblood the day before the palette changed · how much the person hears from me, and what I hear from them* The first person other than me used Gift Graph, on a phone. His Connections card confused him, his hints on the left and my secrets in a long card beneath them, and the page his agent found at the MCP URL had too few details. The evening before, his agent had taken the person it hears for the account it holds, which the account line at connect now answers. The card now holds one direction. Open, it shows the level the person hears at and what I hear from them, and the secret cards carry who hears each secret as person pills that lead to the card. The two-column version and its thinking are recorded in the repo, since I liked the thought behind it and it did not survive a phone. The MCP URL opened as a page answers with a page for agents, with the tools listed from the server itself. I also heard three or four of Justin's hints and then saw them gone on refresh. Nothing in Gift Graph removes a hint on its own; his side changed, and the card said "nothing yet" with no reason, which is right. An audit of what the other person withdrew would defeat the point. ![[gift-graph-site-v061-secret-pills.png|480]] *Person pills on the secret cards · who hears each secret, with a tap to that person's card* **The Product Thought:** One surface answers one question. The secret card says who hears the secret, and the connection card says what I hear from the person. The two-column card tried to answer both and read as confusion on a six-inch screen. The same rule reached the agent a day earlier. The note at connect answered "whom do I act for" and "whom do I hear" in one line, and Muse took the second name for the first. Splitting the line was the whole fix. **Mantra Check-in:** > *Share the hint, keep the secret.* Justin hushed hints I had already heard. The card says nothing yet, and nothing about why. --- ### 2026-10-05: Your Agents, OAuth, and the Fun Part ![[gift-graph-oauth-consent.png|560]] *The consent page on my local stack · the agent named, where the answer goes, Allow and Not now* v0.5 went live in the morning with the web app, and v0.6 in the evening with OAuth. Gift Graph is its own authorization server now. An agent adds the server by its URL, my browser opens a consent page that names the agent and where the answer goes, and Allow hands it a grant. Each agent is a row in Your agents, with Rotate and Disconnect. One account per person, made on the web, and OAuth registers agents to that account. Clerk stays the sign-in for people, and Gift Graph runs its own OAuth because Clerk here is managed by Replit, with nowhere to set up applications or a consent screen. Migration 008 moved my one pasted token into an agent of its own, and it kept working. The same day settled a run of smaller calls. Withdraw became Hush, and secrets sort into Shared and Silent, with the drawer at the foot of the page and "What someone has heard cannot be taken back." centered above it. A lost invite link gets a new one, and the old one stops working, since a link is a credential and the server keeps only its hash. The README gained a Versions section as the release record, and each publish carries a tag. I also wrote the agent-parity benchmark, flow by flow, the web app against what an agent gets. The data for "ask them back" was already in the result as `reverse`, and nothing told the agent what to do with it. Now every preview tells the agent to show me who would hear what and wait for my yes. Then I added Gift Graph to Claude the way a new person would. Claude found the sign-in on its own, I allowed it, and my agent drafted three hints, showed me each secret beside what others would hear, waited, and saved them. This is actually fun. It creates such a different dimension to an agentic experience. Justin's Muse, the same evening, read the connect note and told him his token belonged to me, and it stopped before saving anything. v0.6.1 carries the fix. ![[gift-graph-muse-whose-account.webp|360]] *Muse on Justin's phone · the connect note named him, then me, and Muse took the second name for his account* **The Product Thought:** Identity and authorization are two questions, and the table in the README says who answers each. Identity is the account, made through Clerk. Authentication is Clerk's sign-in, which the consent page leans on. Authorization is Allow on the consent page, and then the levels, which decide what each person hears. Keeping those apart is what let OAuth land without a second kind of user. The parity benchmark is the product lesson of the day. A result that carries the next step reaches the agent at the moment it decides, where a line in a tool description competes with every other tool. **Mantra Check-in:** > *Share the hint, keep the secret.* Claude whispered three secrets and showed me, each time, what the hint would carry. --- ### 2026-10-04: Neon, the Vocabulary Audit, and the Handoff The database moved to Neon, and with it the place where the work happens. Until this move every database refactor was written and tested locally and then handed to Replit to perform. Replit performed it well, and each hand-off still cost a pull, a restart, a verification session, and a schema review. Now the local session works on a dev branch of the real database, rehearses a migration on a branch of production, and reads production to confirm a publish. Replit keeps hosting, sign-in, the judge, and Publish. The split is scrappy on purpose. It spends the token-rich side on the token-heavy work, and it keeps my evaluation of Replit honest, because Replit's share is now the share a team would choose to keep there. The design handoff arrived and became the definitive reference, which settled one label per secret on the web, the connect sheet, and the invite page. I kept the hint line required, since the line is all a friend's agent hears. The vocabulary got an audit instead of a patch. The audit scored a tuning set of one-breath secrets and a held-out set, written blind by a separate agent from the kind names alone, with the server's own matcher. Version 1 was too fine and too noisy. A third of its labels repeated the secret's own noun. Version 2 sits at the grain of a shop department, 63 labels against 150, wrong a third as often, and it went live through migration 007. Neither version reaches brands. A word list cannot keep up with Diptyque or Anglepoise, and the agent writing the hint already knows them, which is why the person's agent now picks the label from the full list in the preview. Nothing here trains a model. The sets are a test that stays on my machine. Two calls of my own closed the day. The web app comes before OAuth, since the page carries the first impression, and every place I have worked has shown me how much polish pays at the first touch. And the noun is secret. I whisper a secret to my agent, the agent whispers hints, and a secret is heard at a level. Whisper as a noun was softer and vaguer, and "a whisper heard as a Secret" made the levels hard to read. **The Product Thought:** Where the labeling happens decides who sees the secret. A model on the server that drafts the hint sends the secret across a new boundary, for the web form, the secondary surface. The person's own agent already holds the secret, already knows what a Baies candle is, and reads the label list at the one moment it needs it, about two hundred tokens, only when whispering. The audit made the choice measurable, and the measurement said the list should be coarse and the agent should pick. **Mantra Check-in:** > *Share the hint, keep the secret.* The label names the kind. The agent that knows the brand keeps it. --- ### 2026-10-03: Three Levels, Invites, and a Server That Migrates Itself Category stopped being a level. In production the category line had leaked nearly the whole secret, "Premium food: a whole leg of Spanish cured ham," and the form could not say why a category needed text. A secret now travels at one of three levels, Secret, Hint, or Silent, and a hint is up to two labels from a public vocabulary plus a line the server checks, with no digits and none of the secret's distinctive words. A label from a finite public list reveals at most the choice among its entries, a bound by construction. The line is the only unbounded channel, which is why it alone gets checked and approved. The same morning, `pull` started returning everything the asker may hear, ranked, with what matches the question first, after "Does Justin have any gifts shared with me?" had returned nothing while "premium food" found his whisper. Literal filtering made a broad question look like an empty graph. Getting Justin on had needed an account ID sent by email, which is the step people drop. Invites fixed it. I mint a single-use link at a level, open fourteen days, shown once and stored as a hash, and opening it signed in makes the connection and offers the share-back. The app also migrates itself at start, under a lock, with `/health` naming the schema. The hand-run production step, with its shell and its copied URL, is retired, and the publish loop is pull, publish, check `/health`. Turns out Publish's schema review cannot be skipped, and the first publish through the new loop failed on a foreign key over the old rows. Production held two people's test data, and I chose a reset over a migration. v0.3 and v0.4 went out together at schema 006. Then I ran Gift Graph on production between two accounts I own and paused to look at the whole. The form had picked the nearest label for me, and a bronze statue went out as art prints. The agent held three identities in one session. The invite had nowhere obvious to be pasted. All four gaps sat at the same step, the one that turns a secret into a hint. **The Product Thought:** Secret, hint, silent is a lattice, and the stricter of the secret's level and the connection's level is the meet. Widening is declassification, which is why widening keeps the confirmation step and narrowing applies at once. Saying it that way is what let the four-level vocabulary go. The fourth level was a leak with a name. The surprise-safe flag left for the same reason. At each of the three levels it had no meaning, and the need behind it, an executor acting on a secret without the giver hearing it, belongs to the platform as Act. **Mantra Check-in:** > *Share the hint, keep the secret.* The hint is a label and a line, and the line is checked against the secret before anyone hears it. --- ### 2026-10-02: Whispers, Accounts, and a Demo ![[gift-graph-replit-31-demo.png|560]] *The demo page · Theo asks his agent, the pull returns two of Mira's three whispers at the tiers she chose, and the wok stays silent* The second morning was words and surfaces. The landing copy went through three drafts under the copy skill. "Shares the hints" lost to "passes along gift hints" because sharing is what the owner does and passing along is what the agent does, and then the whole page moved to one verb, whisper. Your agent whispers hints. Your friends bring the surprise. The tier labels followed: word for word, the kind of thing, a hint, kept quiet. I like the vocabulary and I have not decided whether it survives, which is why it sits on the open row of the map. Agent then proposed a mock for the example pill before touching code. The live version had the pill sitting on the header text, oversized, with a stray comma. The mock fixed all three, I approved the mock, and the fix landed in one pass. The same session added viewport checks at 1280, 1440, and 390 wide, with compact layouts as a standing preference in `replit.md`. Accounts came next, in the preview only, with per-account IDs and a Get MCP token button on the dashboard, which means a third person could join without me pasting a secret into Replit Secrets for them. And a demo page, with two synthetic people, Theo and Mira, three whispers, and a reset, built with the product and site copy skill doing the words. **The Product Thought:** The demo page is the first time the product explains itself without me in the room. One side asks, the other side's whispers sit at the tier she chose, and the pull line between them says which two of three came through. That is the whole model in one screen, and it is also the first surface a persona other than my partner and me could stand on ([[Project - Gift Graph/Discovery & Planning/Product Plan#Who It Is For|Product Plan > Who It Is For]]). Theo and Mira made the pair concrete, and they raised the question the map now carries on its open row. The server does not know these are gifts. It knows that one person lent a sliver of context to another at an agreed level of detail, with a withdrawal that holds. A vendor's support agent and a customer's support agent need that exact mechanism. A procurement agent that may say "there is room this quarter" without saying the number needs it too. Sharing secrets is more than gifts. The gift version is where the tiers get learned. **Mantra Check-in:** > *Share the hint, keep the secret.* Two whispers carried, one kept quiet, and the page says which is which. --- ### 2026-10-01: Owner Controls, and a Front Door ![[gift-graph-site-v02-landing.png|560]] *The v0.2 landing page · one preference at four levels · the owner dashboard one button away* v0.2 is in main. The owner gets a dashboard at `/owner`, signed in with the same credential the agent uses, exchanged for a six-hour session. A preference now has an audience and a ceiling, and the effective disclosure is the more restrictive of the ceiling and what the connection allows. Widening anything returns a five-minute preview and waits for a second, explicit call; narrowing applies at once. A withdrawn preference stays out of every future pull, reapproval included, and there is no restore, no pull history, and no activity indicator. The landing page says the part that matters in one line: information a counterpart has already received cannot be retracted. I also wrote a second skill for product and site copy and put it in `.agents/skills` beside the voice rules, with the project parameters, which means every word Agent writes on the page passes through the same rules before I see it. The landing copy above came out of that. **The Product Thought:** Where a decision gets made is a design material. In v0.1 every choice lived in a tool call, which is fine for two agents and useless for a person who wants to see what they have shared. The dashboard moves the owner's choices to a surface the owner can read, and the preview-then-confirm step puts a pause exactly where the consequence is, on the widening of disclosure ([[UX - Controls Near the Consequence]]). Decreases need no pause because nothing new leaves. That asymmetry is the whole privacy posture in one rule. **Mantra Check-in:** > *Share the hint, keep the secret.* The ceiling is the hint's upper bound, and the withdrawal is the secret's. --- ### 2026-10-01: Live, and Driven From the Outside v0.1 is live. I pushed the working server to a private repo, connected Claude Code to the published endpoint as both users, and ran the story end to end against the thing I built the night before: request, approve at category, drop "wants a license for Söhne" with the category text "type and lettering," pull. The category text came back. A pull for "Söhne" came back empty, which is the fishing test, and it is the best privacy proof of the night. Revoke, pull again, empty. [[Project - Gift Graph/Build & Iterate/Validation Log|Validation Log]] has every command and result; [[Project - Gift Graph/Build & Iterate/Build Log|Build Log]] has the entry. The server taught me two things the spec had not. It refused vibe text on a category drop, which keeps unused private text out of storage entirely. And `drop` takes a `requesterId`, which makes a drop belong to one connection rather than to the owner. Agent's reading is stricter than mine, and it is also a quiet deviation from the spec, which is exactly the kind of thing a forward deployed engineer notices and confirms with the customer before it ships ([[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-006|Technical Decisions > TDR-006]]). Turns out a natural prompt misses. "Gift ideas about fonts" returned nothing, because v0.1 matches literal words against disclosed text and no word overlapped. That is the privacy model working, and it is also the next feature: semantic matching whose embeddings are built only from text the requester may see, or meaning-based search reopens the leak literal matching closes. **The Product Thought:** Where a privacy guarantee lives, and where it can still leak. Claude Code's summary at the pull step mentioned the hidden verbatim text. The server never sent it; Claude knew it because the same session had dropped it a minute earlier as the other identity. Two identities in one terminal make a testing shortcut, and the shortcut showed its edge. In real use each person's agent holds only its own token and its own history, and the server's identity rule is what keeps them apart. The guarantee is the server's. The agent's context is the second surface, and nothing in the server can police it. That split is the thing to say out loud whenever someone asks what Gift Graph protects. **Mantra Check-in:** > *Share the hint, keep the secret.* The hint came through at category tier. The secret stayed in the database, and the one place it surfaced was a memory the server never touched. --- ### 2026-09-30: Build Night on Replit I imported a zip holding a README, a `replit.md` brief, and five docs, with no code. Agent read it, found nothing to run, and asked what I wanted before touching anything, which is the plan-before-build rule from the brief holding on the first turn. I installed my voice rules as a project skill in `.agents/skills`, submitted "Build and run the initial version," and got a six-step plan that passed every check I had written down: anti-inference engine and tombstones deferred, drop and pull as MCP tools over Streamable HTTP, the built-in database, two seeded users. One of its choices was better than what I asked for. Agent chose owner-written category and vibe text over model summaries, which closes a leak the spec did not name ([[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-004|Technical Decisions > TDR-004]]). I selected Revise and opened my text with "Approved with three additions." Agent read the text, and five minutes later v0.1 was running with 12 passing tests. The additions all landed. The gate had still bent, and that became the night's sharpest product note ([[Project - Gift Graph/Build & Iterate/Bug Tracker#BUG-002|Bug Tracker > BUG-002]]). The security review found nothing, Auto-Protect switched on the firewall, encryption, and dependency patching, and the panel said no code goes to the scanners behind it, which is the second question a security reviewer asks. Publish then failed for want of a run command, Plan mode turned the fix into a reviewable task card, Agent checked whether the transport held session state before picking Autoscale, and the progress bar walked through build, scan, and promote. Live a little after midnight. **The Product Thought:** A written brief is the forward deployed version of a voice prompt. For a solo builder, describing the app out loud is the faster and more Replit-native start, and Agent would propose its own structure. For an enterprise customer, scope, exclusions, and an approval gate before code are things the customer has to agree on in writing, and someone has to write them down before Agent starts. The README and `replit.md` played that role here, and cutting the v0.1 scope up front, deciding what to leave out, was the first real decision of the build. The second was watching the gate hold, then bend, then hold again under Plan mode. An enterprise security team will ask about exactly that sequence, and now I have seen it. **Mantra Check-in:** > *Share the hint, keep the secret.* The brief shared the shape and kept the scope. Agent built what it was given. --- ### 2026-09-01: The Concept The spec, the four tiers, the anti-inference batcher, the PSI tombstones, and the architecture diagram, written up as a concept page and published to the garden. Decided against patenting; publishing the spec is the cheaper protection and the better use of the idea. Nothing built yet. The full page: [[Concept - Gift Graph - Consent-Gated Context Between Agents]]. --- ### 2026-02-15: The Idea Initial ideation and a feasibility exploration, in a Claude chat. I wanted to know whether two people's agents could share what one of them wants without either reading the other's history, and whether a server between them could keep the original words at home while the other side heard a hint. The idea held up, and I set it down. In September I dusted it off for a Replit case study, wrote the concept page, and the build that followed grew past the case study ([[Project - Gift Graph/Build & Iterate/Technical Decisions#TDR-000: Explore the Idea Before Building It|TDR-000]]).