Sabine
A personal AI chief of staff for people running complex lives.
Sabine isn't a chatbot or a smarter search. She's built on a living knowledge graph — a structured model of your life that grows with every conversation, email, schedule, and purchase. People, preferences, patterns, history: she remembers all of it, connects it, and acts on it across Slack, SMS, email, and web. The memory is the product.
3D Memory Graph
[US-013 will supply screens]
Slack Conversation
[US-013 will supply screens]
SMS Thread
[US-013 will supply screens]
Family Calendar
[US-013 will supply screens]
Cart Build Sequence
[US-013 will supply screens]
Monday Top 5 Email
[US-013 will supply screens]
Morning Briefing
[US-013 will supply screens]
Memory Browser
[US-013 will supply screens]
She remembers — not your chat history, your life.
Every other AI assistant treats memory as a feature bolted on. Sabine is built memory-first. Every conversation, email, schedule, and order builds a structured knowledge graph of entities — people, places, events, preferences, patterns — that she actively uses in every future interaction. You see it. You tune it. You edit it.
[Preview: 3D memory graph]
She acts, not just answers.
Sabine doesn't return search results or draft text for you to paste elsewhere. She builds the cart. She creates the calendar event. She fires the reminder at 8am via whatever channel you want. She forwards the email to the right person. The output is an action in the world, not a suggestion.
Typical chatbot: "Here's a link to Amazon where you can buy batteries..."
Sabine:
✓ Found your preferred brand (Duracell AA, 24-pack)
✓ Price is $0.40 higher than last purchase
✓ Cart link ready: amazon.com/cart/...
She is present everywhere you are.
The same Sabine — same memory, same context, same history — is available via Slack, SMS, email, and web chat. You use whatever is most natural in the moment. She is not an app you have to open.
"What's on Jay's schedule?"
Same conversation continues...
Forward any email to Sabine...
Full interface with history...
She is built for family complexity.
School schedules, sports calendars, multi-kid coordination, the Sunday logistics you always forget. Sabine handles the coordination layer no general-purpose assistant has ever addressed. She knows whose practice is when. She knows to check the TeamSnap feed before answering.
She shops for you.
Short looping sequence: visitor sends "order more batteries" → Sabine resolves preferred brand from memory → checks current price → flags it's gone up $0.40 since last purchase → returns a cart link OR completes checkout per user policy.
"Order more batteries"
✓ Found preferred brand: Duracell AA 24-pack
✓ Current price: $18.99
⚠ Price increased $0.40 since last purchase
✓ Cart ready: amazon.com/cart/...
She handles a chaotic Saturday.
Jay's game at 9. Devin's recital at 10. School fundraiser pickup at 12:30. Two TeamSnap feeds, one school calendar, three Google Calendar entries — all merged, all conflict-checked, all on the family calendar without you opening an app.
Every sports schedule, everywhere, always current.
Subscribe to a TeamSnap feed once → games appear on your family calendar → rainouts flow in automatically. Connects to the same family coordination infrastructure that powers Strug City Sports.
teamsnap.com/schedules/jay-u12-soccer
New games flow to Google Calendar
Game canceled → Sabine updates calendar automatically
I struggled to: parse the attachment format in your school email
To resolve this, I'd need: a dedicated PDF table-extraction skill
Logged for: 2026-06-15 improvement review
She tells you what she cannot do.
End-of-conversation moment where Sabine surfaces a capability gap and proposes a scoped fix — the self-improvement loop made visible. Every gap is logged, classified by blast radius and risk level, and queued for review.
She sends you a briefing before you even ask.
7:00 AM SMS render — calendar for the day, kids' schedules, anything flagged from inbox, top goals for the week. Unprompted. Recurring weekday.
Good morning!
TODAY'S SCHEDULE
- • 9am: Team standup
- • 3pm: Jay soccer pickup
- • 6pm: Parent-teacher call
FLAGGED ITEMS
School permission slip due Friday
You can see inside her mind.
Sabine's memory isn't hidden behind an API. It's a navigable, searchable, editable knowledge graph — entities, relationships, salience scores — rendered in 3D. You see exactly what she knows and how she connects it.
Memory visualization
3D knowledge graph, MAGMA architecture, memory browser
The architecture that makes the memory real.
Sabine's differentiation isn't a smarter prompt. It's the architecture under the prompt.
Multi-Graph Memory Architecture
Four-layer memory system: sensory → working → episodic → semantic. Vector embeddings, entity extraction, salience scoring, automatic deduplication, archiving. Not RAG over a chat log. An actual knowledge graph that grows with the user and degrades gracefully under uncertainty.
Sub-3s fast path + async slow path
Every message receives a sub-3-second response while a separate async path consolidates memory, updates salience scores, and writes new entities to the graph. Speed and intelligence are not traded off.
Multi-retailer adapter architecture
Playwright for Amazon, UCP for Target and Walmart. Preference resolution from memory. Price-change detection. Per-transaction and per-day spending limits. Configurable autonomy modes — the user controls how much Sabine acts on her own.
Sabine detects her own capability gaps
Mid-conversation gap detection. Classification by blast radius and risk level. Logged to a structured table. Scoped improvement proposals with priority scores. Fully implemented and running in production.
Same agent core across Slack, Gmail, SMS, web
Slack Socket Mode, Gmail Pub/Sub with polling fallback, Twilio SMS, web chat — all route to one agent. Domain-aware memory retrieval scores work and personal context separately.
New skills sandboxed before deployment
New skills tested in an E2B sandboxed environment before promotion. Promoted skills stored as executable code in the database, compiled dynamically at load time. The agent's toolset grows without a redeployment.
TeamSnap, GameChanger, rSchoolToday, generic ICS
Squad filtering. Ghost-event deduplication. Tournament coalescing. The result is a family calendar that accurately reflects multi-child, multi-sport schedules without any manual entry after initial setup.
Sabine runs on Anti-Strug.
The MAGMA architecture is Anti-Strug's memory layer. The dual-stream pipeline is Anti-Strug's runtime. The self-improvement loop is Anti-Strug's introspection surface. Every capability above is powered by the agentic operating system Strug City built.
See the platform →What Sabine looks like.
Real screens from a production agent — memory graphs, conversations, calendars, and cart builds.
3D Memory Graph
[US-013 will supply screens]
Slack Conversation
[US-013 will supply screens]
SMS Thread
[US-013 will supply screens]
Family Calendar
[US-013 will supply screens]
Cart Build Sequence
[US-013 will supply screens]
Monday Top 5 Email
[US-013 will supply screens]
Morning Briefing
[US-013 will supply screens]
Memory Browser
[US-013 will supply screens]
Some of the work happens before you ask.
Morning briefing
Sabine synthesizes your work and personal events and texts you a briefing — calendar, kids' schedules, flagged inbox, top goals. No prompt required.
Reminder delivery
Reminders fire automatically at their scheduled time via whichever channel they're set to — SMS, email, Slack, or calendar.
Weekly Top 5
Sabine queries Linear for issues labeled Win and Top Goal and emails the weekly summary.
Calendar feed sync
Subscribed ICS / TeamSnap / GameChanger feeds are polled automatically; new events flow to Google Calendar without you touching an app.