Cortex

A journal that remembers, built for neurodivergent adults. Speak or type what is going on, on the iPhone or straight into the Apple Watch, and Cortex keeps every word, sorts it, and lets you ask an assistant that answers from your own entries. It never tells you what caused what. Your journal lives on your device, and when AI features need processing, the relevant text (with direct identifiers redacted) travels encrypted to AWS Bedrock and is not retained by the AI provider.

Learn More

A day with Cortex

Say it. Cortex files it. Ask for it back later.

  1. 1

    Say it, or type it

    Hold the button and talk, on the phone or on the Watch. The transcript knows your medication names. Nothing to pick first, no form to fill, no streak to keep.

  2. 2

    Cortex files it

    Every entry gets its type, its subjects and, when it fits, a thread. One short line comes back so you know it landed. Weeks later you find it again without ever having tagged anything.

  3. 3

    Ask for it back

    Ask Mimo what you noticed the last time you changed a dose. Open a thread to read everything about one question, in order. Write it up for the appointment in a tap.

What Cortex Does.

Sophisticated Voice Journaling

Speak naturally. On-device transcription understands medication names, emotional shorthand, and neurodivergent speech patterns that standard dictation gets wrong. Or type, whatever takes less energy.

Journal and Log From Your Watch

Say an entry into the Apple Watch and it lands in your journal, turned into text on the watch itself. Today's medications are on the wrist too, and each dose logs with one tap. No phone to find, nothing to unlock.

Threads: One Question, All Its Entries

A thread is a question you are working on, like "why do my teeth hurt?" or "why do outings drain me?". File entries into it, or let Cortex suggest them, and the thread page shows everything you ever wrote about it in order.

Medication Log

Medications, supplements, and accommodations organized by time of day. Log doses with a tap on the phone or the Apple Watch, track what you've taken, and see your routine at a glance, no spreadsheet required.

From Any App

Send text or a link into Cortex from Safari, Notes or Messages. It waits in your journal for a quick look and can go straight into a thread. Widgets on the home and lock screen open a new entry in one tap, and Siri or the Action button can start a voice entry.

Locked, and Yours to Take

Face ID or Touch ID guards the app. Everything you have written exports as plain, readable files whenever you want them. Write-ups for a doctor can be produced in English, German or Arabic.

Insights: What Keeps Coming Back

Cortex counts what you mention most and shows it to you, with nothing invented. Browse by subject, or by what you were doing when you wrote: observing, theorising, trying something, or holding on to a good moment. Release stays out of the browse view on purpose.

Anchor Your Day

A plaque on the home screen shows one good moment from your own entries, a new one every three hours. Not a quote from someone else. Something you wrote on a better day, back when you need it.

It Asks How It Went

Write that you will try something, and Cortex comes back later to ask. Did you get to it? Did it work, or not, or still testing? Your tap decides what the strategy becomes. The app never guesses.

Moments

Name a period: a trip, a new medication, a bad week. The moment opens as a portrait of that time, what you took, what came up, then the entries day by day. What was life like during that, as opposed to what do I know about it, which is a thread's job.

Share It With an AI

A third write-up is made for a model, not a person: a whole thread as one dated list, up to a hundred entries, with a short preface on how to read it. Paste it into any chat model and ask your own questions.

Try It Empty-Handed

A demo journal with seventy-two entries over several weeks lets you try threads, Mimo and the write-up before you have written a line of your own. Switch it off and it is gone, your journal untouched.

Health in the Margin

Sleep and heart rate from the Health app sit beside the day as context, if you allow it. Cortex shows them. It never draws conclusions from them.

One word, five kinds of entry

A thread holds everything you wrote about one thing. Cortex sorts it by what each entry does.

Teeth a thread
46 entries, Mar to Sep
Observation20 of 46
what I noticed
6 AprCoffee brings the throat feeling first, then the pain.
26 MayLess teeth pain than the days before.
14 SepTeeth pain back, cause unknown.
Insight14 of 46
what I suspect
6 MarAcid reflux reaching the teeth.
18 JunPain the day after a missed pantoprazole dose.
18 AugPain returned when the tyrosine dose went up.
Release6 of 46
letting it out
12 MarEvery fix brings the next problem.
26 MarToo much pressure already, and now the teeth on top.
15 MayThree hours at a clinic for a generic answer.
Strategy3 of 46
what I tried
1 AprNatron rinse, fluoride toothpaste and Gaviscon.
7 JunTooth mousse, the only toothpaste that helps.
Positive3 of 46
what held
29 AprA few better days. The teeth problem somehow easier.
26 MayLess pain after trying pantoprazole.
3 JunLess teeth pain, and the overwhelm eased with it.

This is a real thread from one journal, seven months of it. Every entry in it is about teeth. But "coffee, then the pain" and "less pain after pantoprazole" are not the same kind of sentence, and a dentist should not have to read them as one pile.

So each entry gets a type at the moment it is written. Observation for what you noticed. Insight for what you suspect. Strategy for what you tried. Release for letting it out. Positive for what held.

The lines show where the 46 entries went. Read the dates across the cards and one story appears: a suspicion in March, a bad night, things tried in April, the coffee trigger noticed, and in May something that helped.

Each line is the one-line summary Cortex keeps for an entry, not the entry itself. Shown with the writer's permission, chosen to carry no names, places or people.

Share made easy

Pick who it is for. Cortex picks what goes in.

Every entry already carries its type, so a share is a filter, not a rewrite. Doctor: noticed, suspected, tried, helped. Yourself: everything. A friend: how it felt and what helped. Social media: only what helped and what you tried. Change the ticks and the sheet follows.

What the dentist gets:

  • A dated pattern, not "it hurts sometimes".
  • The suspicions listed apart, so they can be checked, not argued.
  • What was already tried, so it is not tried again.

Three visits in this thread went nowhere: one clinic found nothing, one visit happened unprepared and under overload, one took three hours for a generic answer. Each time the seven months of timing stayed in my head. The sheet puts it on paper before the appointment starts.

Tick Release and the hard days come back, for a friend or for me on a better day. One tap keeps them out of the dentist's copy. Cortex never says what caused what. It remembers and sorts. The reading is the reader's job, and yours.

Teeth, written up for my dentist
46 entries, March to September 2026

What I noticed

6 AprCoffee brings the throat feeling first, then the pain.
14 SepTeeth pain back, cause unknown.

What I suspected

6 MarAcid reflux reaching the teeth, possibly pushed by tyrosine.
18 JunPain the day after a missed pantoprazole dose.

What I tried

1 AprNatron rinse, fluoride toothpaste and Gaviscon.

What held

29 AprA few better days. The teeth problem somehow easier.
26 MayLess pain after trying pantoprazole.
3 JunLess teeth pain, and the overwhelm eased with it.

How it felt

26 MarOverwhelmed, with the teeth problem on top of everything else.

Kept for me

Release, 6 entries

Meet Mimo

An AI That Actually Knows You.

Mimo reads everything you've written. It doesn't give generic advice, it answers from your own history and pushes back when you're jumping to conclusions.

You What have I written about my teeth this year?
Mimo 46 entries since March. Three things keep coming back.

• Pain, and when it shows up. 6 April: coffee brings the throat feeling first, then the pain. 17 April: pain even without tyrosine or coffee, on touch, pressure and heat. 14 September, the last entry: pain back, cause unknown.
• What you suspect. 6 March: acid reflux reaching the teeth. 18 June: pain the day after a missed pantoprazole dose. 18 August: pain returned when the tyrosine dose went up.
• What helped. 26 May: less pain on the higher pantoprazole dose. 7 June: tooth mousse, the only toothpaste that helps.

Six entries are you letting it out rather than noting anything. I left those out. Say so if you want them.
You So it is the coffee.
Mimo Your entries put coffee before the pain twice, on 6 April and 5 June. They also put pain with no coffee at all on 17 April, and pain with no cause you could name on 14 September. Two co-occurrences in seven months is a lead, not an answer. What would settle it: log the coffee and the pain as separate entries with times for a few weeks. And the reflux you suspected in March is something a dentist can check for directly. The write-up for that visit is one tap from this thread.

Powered by Adaptive AI.

Cortex uses large language model architecture as a conversational, low-demand interface. Rather than forcing structured forms, the system works from what you actually produce: a voice note, a short text, a line from the Watch.

The AI models run on AWS Bedrock in Frankfurt, through a small Cortex server that holds the AWS credentials so the app never does. AWS does not keep the text it processes. Voice transcription and search ranking run on your device; entry classification and chat are processed in the cloud.

Before any text is sent for processing, direct identifiers, your name, email, phone number, and postal address, are redacted on a best-effort basis. AI features require connectivity; there is no on-device language model.

AWS Bedrock On-Device Voice & Search Identifier Redaction GDPR Compliant
Voice or text, transcribed on the device
↓
Saved on the device. Sync only through your own iCloud
↓
Identifiers redacted, then sent through the Cortex server to AWS Bedrock in Frankfurt
↓
Type, subjects and a one-line summary come back and sit next to the entry

Always Within Reach.

Mac Version Coming Soon

Cortex for the Mac is coming soon, the same journal kept in step through your iCloud. Say something into the phone on the way home, and it is on the Mac when you sit down, already sorted and searchable. Write a long entry at the desk, and it is on the phone the next morning. Ask Mimo from whichever is in reach.

Apple Watch, Without the Phone

Raise your wrist and say what is happening. The words are turned into text on the watch itself and land in your journal a moment later. Today's medications are on the wrist too, and a dose logs with one tap. For the days when finding the phone and unlocking it is already too much.

Through Your iCloud, Not Mine

Sync runs through your own private iCloud, tied to your Apple Account. I cannot see it, and there is no Cortex server holding your journal. What travels is your text, the sorting already done for it, threads, notes and intake logs. Voice recordings stay on the device that made them. One switch in Settings clears the iCloud copy again.

Development Timeline.

Phase 1 Completed

Research & Concept Validation

Explored how AI can support neurodivergent self-tracking. Validated the core concept: free-form journaling with automatic classification and pattern extraction. Defined the architecture and data model.

Phase 2 In Development

The iPhone App, in Daily Use

The iPhone app with on-device voice, the five entry types, Mimo, threads, the doctor write-up and daily intake. Over seven hundred commits, one user, every day, and still changing every week. Along the way a whole causal-inference layer was built, measured, and removed.

Phase 3 In Progress

Mac, iPad and Apple Watch

A Watch app for journal entries and medication doses without the phone, and the same journal on the Mac and iPad, kept in step through iCloud. The Mac version is coming soon. Built and running. Being tested on my own devices before anyone else sees them.

Phase 4 Target: 2026

Beta Launch

Public beta on TestFlight for early testers from the neurodivergent community. Gathering feedback and preparing for App Store submission.

Phase 5 Planned

On-Device Apple Intelligence

Exploring Apple Intelligence and on-device foundation models for lightweight tasks that can run without the cloud, reducing how much text needs to leave the device. Not yet part of the app today.

About

Why I'm Building Cortex.

I'm Mohamad Sakkal. I'm autistic with ADHD, and I've spent years in the slow grind of burnout, the kind where social connections fade because keeping them feels impossible, where the executive function to start small tasks just isn't there, where sensory overload turns a normal day into something you have to recover from for two more. The things that worked last month are gone by next month. I forget my own patterns. I forget what helped. I make the same mistakes I made a year ago because the memory of figuring them out the first time is gone.

I've always envisioned an app that does what my brain can't. Voice journaling that doesn't ask me to organize my thoughts before I have them, automatic classification so I can find things later without tagging anything, a chat assistant that actually remembers what I wrote a month ago, intake tracking that doesn't punish me when I'm not consistent. Every app I tried did one or two of these things, but never all of them, and never in a way that worked for an ND brain. So I built it.

I built Cortex solo over several hundred commits, mostly in the evenings and on weekends. Along the way I made, and corrected, the same mistake the heavily funded apps in this space are still making: I tried to have the AI organize my notes for me, infer causal patterns, label everything. It produced confident-sounding nonsense that quietly biased every interpretation. I deleted that entire architecture and rebuilt the app around a simpler principle: store the user's raw words, retrieve them when needed, and let the AI read fresh every time. The journal is the memory; the AI is just a reader.

Cortex isn't a journaling app. It's a cognitive prosthetic. External memory and external organization for brains like mine. I'm releasing it for other autistic and ND adults because the world doesn't need another productivity app, but it does need tools built by people who actually live this.

One more thing.

I'm looking for testers, for research, and for further cooperation.

Testers. Autistic and ADHD adults who journal, or want to, and will use Cortex for a few weeks and tell me what breaks and what helps.

Research. Clinicians and researchers who want to study what a journal like this does for people like me: how the five kinds hold up over months, what a doctor actually gets from a share, where the risks are.

Cooperation. Clinics, universities, communities or other builders who want to take some of this further together. Pilots, shared data agreements, a feature you need, an integration.

Write to admin@ms-dev.app.

In daily use. Beta next.

A Journal That Remembers, and an AI That Reads It Fresh.

Raw words in, stored on the device. A search index over them, not a summary of them. An assistant that answers from the original entries every time, cites them, and never asserts a cause. Built for ADHD and autistic adults, by one.

Why Existing Solutions Fail.

The Demand Drop.

Standard habit-tracking applications are built on a foundation of compliance, daily check-ins, streaks, and prompts. For individuals with Pathological Demand Avoidance, each of these micro-demands triggers an autonomic avoidance response, causing immediate and permanent abandonment of the tool.

Executive Paralysis.

When users are experiencing autistic burnout, the cognitive overhead required to open an application, navigate menus, and fill structured input forms is physiologically impossible. Existing tools require precisely the neurological resources that burnout depletes.

Static Logic.

Current applications apply a fixed interaction model regardless of the user's daily neural capacity. A neurodivergent individual's functional capacity fluctuates significantly across hours and days. No commercially available tracker adapts its interface demands to this reality.

Retrieval-Augmented Conversation, Not Generic Advice.

Mimo queries your full journal history via hybrid search (vector similarity + FTS5), then interprets from raw context. It cross-references timestamps, physiological data, and prior entries to challenge premature conclusions.

User What were my observations when I was taking tyrosine?
Mimo You logged tyrosine for 5 weeks (Feb 12 to Mar 18, 80mg mornings). Three patterns showed up.

• Social: you initiated contact with friends 7 times (vs. 1 the month prior), and "connected" appeared in 6 entries
• Motivation: "got it done" showed up 11 times, mostly mornings; you cleared two long-stalled admin tasks in week 2
• Overwhelm: a new pattern by week 3, "too much input" or "overstimulated" 8 times, almost always 4 to 7pm

You stopped on Mar 18 after the entry: "running hot, need to back off."
User Was the overwhelm dose-related?
Mimo Can't say from the data. You held 80mg the whole time, no titration to compare against. What I can see: the overwhelm clustered ~6 hours after your morning dose, consistent with a peak-then-crash pattern, but also consistent with end-of-workday fatigue. If you try it again, splitting the dose or logging the time of overwhelm explicitly would let me actually answer this.

Core Feature Set.

Sophisticated Voice Journaling.

On-device speech-to-text via WhisperKit. No cloud roundtrip for transcription. Neurodivergent speech patterns parsed locally, then structured by the extraction pipeline.

Five-Type Classifier.

Every input classified: observation, venting, insight, strategy, positive. Each type triggers different extraction rules and contextual rendering.

Mimo: RAG Chat Engine.

Retrieval-Augmented Generation over full journal history. Hybrid search, vector similarity + FTS5 keyword, retrieves relevant entries. LLM interprets fresh from raw text every time.

Threads as Questions.

A thread is a user-stated question with a curated set of entries. New entries are routed in by term match and by embedding similarity against the thread's description, above a fixed threshold, and the user can always overrule the routing.

Clinician Handover.

A thread renders as a dated, month-by-month account built from the per-entry summaries already produced at analysis time. No extra model call. Observations and the writer's own theories are kept in separate sections, with sources marked.

Intake State Machine.

Medications, supplements, accommodations tracked with time-block scheduling. Multi-dose support, validation status lifecycle. Mirrored to watchOS for tap-to-log.

Share Sheet, Widgets, Siri.

Text or a URL from any app arrives through the share sheet, with article extraction and an optional thread pick. Home and lock-screen widgets for quick log. A voice entry starts from Siri or the Action button.

Lock and Export.

Biometric lock with inactivity timeout. iOS Data Protection at rest. Full structured export: entries with type, threads, intake, chat sessions, as JSON and readable text. Handover documents in English, German or Arabic.

Insights by Aggregation.

Subjects are the terms that recur across entries, counted locally with no model call. Stances group entries by the type assigned at classification, so history can be read by mode: observing, theorising, acting, anchoring. Venting is excluded from browsing by design.

Powered by Adaptive Generative AI.

Cortex utilises advanced large language model (LLM) architecture to serve as a conversational, low-demand interface. Rather than forcing the user to interact with structured forms, the system extracts behavioural data seamlessly from natural, ambient input, voice fragments, short text, or passive signals.

The inference pipeline is built on AWS Bedrock (EU, Frankfurt, region by default, configurable in-app), providing enterprise-grade model access with zero data retention. Voice-to-text (WhisperKit) and the search index run entirely on-device; classification, chat, and the text embeddings that power search are served by Bedrock.

Direct identifiers are redacted from text on a best-effort basis before it leaves the device. AI features require connectivity, the app does not run a language model on-device.

AWS Bedrock EU On-Device Voice & Search LLM Architecture Identifier Redaction GDPR Art. 28 Zero Retention

Technical Architecture Diagram

Ambient User Input (Voice / Text)
|
Cortex AI Interface Layer
|
AWS Bedrock (Cloud LLM)
|
Behavioural Extraction Model
|
Encrypted On-Device Data Store

To be replaced with final architecture illustration

Why I'm Building This.

Solo developer based in Vienna. Autistic with ADHD. Years of burnout, executive dysfunction, sensory overload, fading social connections. The standard ND adult experience that no journaling or productivity app has ever held onto correctly.

Always envisioned a tool that combined the parts no single app gets right: sophisticated voice journaling, automatic cognitive-type classification, retrieval-based chat over your own history, intake state tracking, all local-first. Built Cortex because that combination didn't exist.

Original architecture used an AI-extracted causal knowledge graph as the context layer. After 33 days of escalating fixes, recognized that AI-inferred labels fed back into prompts produced manufactured certainty, not insight. Removed 126 commits worth of graph code. Rebuilt around RAG over raw text. Store the user's words, retrieve them on demand, let the model interpret fresh.

The design choices here come from being the user, not from market research.

All Devices.

One Journal, Every Device.

iPhone, iPad and Mac run the same build and share one store through the user's private iCloud database. An entry captured on the phone arrives on the Mac with its analysis attached, so no device repeats work another already did. Voice audio stays local by design. On the Mac: Cmd+N for a new entry, Cmd+1 to 4 for the tabs. The Mac release is coming soon.

Watch Capture.

Record on the wrist, transcribe on the wrist, review, send. The text reaches the phone over the watch bridge and enters the normal pipeline. Today's intake list is mirrored to the watch with tap-to-log, and complications sit on the watch face.

No Journal Server.

Sync is Apple's CloudKit, tied to the Apple Account. No first-party server stores journal content. The only hosted component is a stateless AI relay that retains nothing beyond a usage count. Settings can purge the iCloud copy in one action; the local store is untouched.

Development Timeline.

Phase 1 Completed

Research & Concept Validation

Validated that unstructured journal input can be parsed into structured behavioural data. Defined extraction pipeline, classification taxonomy, and on-device storage architecture.

Phase 2 Completed

Built, in Daily Use

iOS app with cloud coprocessor (AWS Bedrock, EU). On-device voice, hybrid search, 5-type classification, RAG chat, threads, clinician handover, intake. 700+ commits, single user, daily. A causal knowledge graph and a Granger engine were built, measured and deleted.

Phase 3 In Progress

Mac, iPad and Watch

Mac Catalyst target with CloudKit sync, watchOS app with on-watch transcription and intake logging. Built and running. Under test on the developer's own devices.

Phase 4 Target: 2026

Beta Launch Test

TestFlight beta for neurodivergent early testers. Gathering feedback before App Store submission.

Phase 5 Planned

On-Device Apple Intelligence

Evaluating Apple Intelligence / on-device foundation models for lightweight inference, reducing data egress for tasks that don't require cloud models. Not yet integrated.

See Cortex Through a Different Lens

Natural shows how Cortex feels in everyday life, warm, intuitive, human.

Cortex maps your experience to how your brain actually works, through the language of neuroscience.