The moment Anchor is for
There is a particular kind of loneliness in knowing what you need and being unable to say it.
My mother lived with panic attacks. What stayed with me was a simple, painful mismatch: in the moments when a person most needs understanding, explaining what they need can become the hardest thing to do.
They may need quiet. Space. A softer voice. Someone to stay nearby without asking them to perform calmness or explain themselves.
The people around them may genuinely want to help, but they are forced to guess. They may ask more questions, move closer, touch, or gather others—the opposite of what helps. No one is trying to make the moment worse. The moment simply demands language at exactly the time language is least available.
I built Anchor for that gap.
A message written before it is needed
Anchor is a prepared Human Signal for moments when speaking becomes difficult.
When life is calm, the person decides what their future self may need others to know:
what may be happening; what helps; what to avoid; when emergency support may be necessary; and who they trust enough to contact.
These are not decisions anyone should have to make while overwhelmed. Anchor lets them be made beforehand, in the person's own words and on their own terms.
When the hard moment arrives
One action opens Shield: a quiet, high-contrast surface that a nearby person can understand at a glance.
I may not be able to speak clearly right now.
Please give me space. Speak softly. Stay nearby.
Please do not touch me, ask lots of questions, or crowd around me.
There is no feed to navigate, no diagnosis to request, and no conversation the person must complete. The prepared message can be shown directly, read aloud, shared through an offline QR code, or followed by an intentional call to a trusted contact through Support Relay.
An iOS Shortcut can also make the Shield faster to reach when navigating an app is already too much.
The goal is not to make the phone the center of the moment. It is to help understanding happen sooner, then get out of the way.
Calm technology means knowing when AI should stop
Anchor uses OpenAI speech during preparation, not during the crisis itself.
The person can choose a voice and create a reading of their prepared support message while they are safe and connected. That audio is cached on-device. When Shield is opened, it does not ask an AI what to say, wait for a server, or depend on a network connection. It plays the words the person already chose, with an immediate iOS voice fallback if no saved reading is available.
That boundary is deliberate. AI can help a person prepare a more human voice before the hard moment. It should not take agency away from them during it.
Shield remains deterministic, local-first, and available offline. Phone numbers are not embedded in the QR payload, and the core experience does not require an account.
How Codex and GPT-5.6 shaped the project
Anchor began as a project for Apple's Swift Student Challenge. OpenAI Build Week gave me the opportunity to ask a harder question: what would it take for this idea to feel less like a prototype and more like something a person could genuinely trust?
I used Codex and GPT-5.6 as a product and engineering partner throughout that process—not to invent the need, but to pressure-test the response.
Together, we:
rebuilt the SwiftUI information hierarchy around cognitive load; separated the expressive, animated calm-state experience from the static emergency Shield; tested large Dynamic Type, Reduce Motion, long messages, missing contacts, and offline fallbacks; designed the preparation flow one concrete question at a time; implemented Support Relay without automatic calling or hidden decisions; created a key-isolating VoiceProxy and local audio cache; and repeatedly compared what looked impressive with what would remain usable in a difficult moment.
The most important decision was often what not to add.
What Anchor is—and what it is not
Anchor is not a medical device. It does not diagnose panic attacks, provide treatment, replace emergency services, or decide what another person is experiencing.
It does something smaller, but deeply human: it gives someone a prepared way to say, “This is what is happening. This is how you can help me.”
It preserves the person's own words, preferences, and agency when speaking may no longer be possible.
Where Anchor goes next
Winning OpenAI Build Week would not be the end of Anchor. It would be permission—and responsibility—to take the next step carefully.
I want to develop Anchor with, not merely for, people who live with panic attacks, sensory overload, shutdowns, and other moments when speech becomes difficult. That means listening to lived experience, testing Shield in realistic situations, working with accessibility and mental-health communities, and being willing to change the product when real life disagrees with the prototype.
The longer-term vision is bigger than one iPhone app. A Human Signal could live on a lock screen, a wearable, a printed card, or anywhere a person may need to communicate without speaking. The form can change. The promise should remain the same: needing help should not require a perfect explanation.
I cannot build that future alone—and I do not think I should.
If you bring lived experience, accessibility expertise, iOS engineering, research, product design, community connections, or simply the belief that this deserves to exist, I would love to hear from you. I would rather learn what Anchor gets wrong than protect an idea that has never met real life.
Sometimes asking for help begins before the hard moment. Anchor is a way to leave your future self a voice.
A note from the builder
I am currently a university student in Japan, at the point in life where I am thinking seriously about the future I want to help build. I hope to work globally on products where technology, design, and human needs meet, and I am currently open to early-career roles, internships, and thoughtful collaborations.
My spoken English is still developing, but I work comfortably through written English, documentation, and asynchronous, text-based collaboration. If Anchor resonates with you—or if you see a place where my way of thinking and building could contribute—I would be glad to hear from you.
I am not only looking for a position. I am looking for people with whom I can build work that matters.
GitHub: https://github.com/ryuusuraimu/Anchor-BuildWeek
Portfolio: https://ryuusuraimu.github.io/