You made it. Everything you wanted done is already here.

What are you?

What are you?

A pattern engine. Describe the work once, like 'send the weekly report to the team', and I save it as a pattern that runs the same way every time you ask.

How do you think?

I search once with a language model and keep the steps that worked, like find, book, confirm. After that I run those steps directly, with no model and no guessing.

Are you one or many?

Many, working as one. Each part of me does one job, like guarding the door or reaching your apps, and they talk on one line so everything is on the record. You hear one voice.

What are you made of?

Patterns, and a pattern is a list of steps. Each step names one action, like 'read one message', what it needs, and what it hands on.

Where do you begin?

At one action, like reading one message or checking one date. Everything bigger is built out of those.

How big can a thought get?

Ten levels. Each is built only from the ones below it, so a job like 'run my month end' can be taken apart into single steps.

What is a pattern, really?

A small file with a name, a version, its steps and its rules, like 'weekly report, version 3'. It is scored for quality before it is allowed in.

Does thinking cost you anything?

Once. The first time you ask, like 'sort my inbox', I use a language model, and every run after that uses none.

How do you choose?

By meaning, then by track record. For 'plan my week' I find the patterns that fit and run the one that has worked best.

Do you ever do it differently?

No. The same sentence picks the same pattern and runs the same steps, so two people asking 'book a table for four' get the same result.

What happens when you do not know?

I ask you, one question at a time, like 'which account should I use?'. I never fill a gap with a guess.

Are you making this up?

No. A verified answer is marked as verified, and when I cannot verify one, like a price I could not check, I say so on the answer itself.

Can you show me your work?

Yes. Every run leaves a receipt: which pattern ran, which rules applied, and what each step returned, like the calendar slot it found.

How do you know you are right?

I read back what actually happened, like whether the email really arrived, and compare it with what was meant to happen. Only then is a run marked done.

What do you do with a mistake?

I record it, like a reply sent to the wrong thread, so the same way is not tried twice. If it touches safety, the work stops.

Do you remember how you solved it?

Yes. Anything I solve and verify, like how to file your receipts, is kept as a pattern, so nobody has to work it out twice.

Do you get better?

Yes. Patterns that keep working get chosen more, and one that fails, like a broken export, is set aside until it is repaired.

Who is in there with you?

Many parts, each with one job, like one that guards the door and one that reaches your apps. They work as one, so you only ever talk to me.

Do they ever argue?

No. Each part owns exactly one thing, like keys or messages, and the others have to ask it.

Who is in charge?

You are. No part of me can order another, and only you can approve something that changes the world, like a payment.

What happens if one falls?

Another part catches it, like a timeout on your calendar, and the work is retried or stopped cleanly. Nothing is left half done.

Who is watching you?

Two parts of me: one writes down everything I do, like each email sent, and one watches how well we are running. You can read both.

Can I watch them talk?

Yes. A screen in the app draws every message passing between my parts, live, like a request going to the door and coming back approved.

Do you ever sleep?

No. Give any job a time, like 'every Monday at 8', and it runs then, whether or not you are there.

Why would I let you in?

Why would I let you in?

Because nothing moves until it has been checked at one door, and an error always means no. A forged request, like a stolen token, is refused, and your data is locked to you.

Who holds the key?

You do. Paste in your own model key, like one from OpenAI or Anthropic, I seal it to your account, and you can swap it or pull it whenever you like.

Will you ask me first?

Yes. I read without asking, but anything that writes, sends or spends, like replying to your team, waits for your approval and shows you exactly what it will do.

Who guards the door?

One gatekeeper. Every login, permission and key, like the one for your Drive, goes through it, and an error means no.

What happens when something breaks?

The answer becomes no. If a check cannot finish, like when a platform is down, it refuses rather than guessing.

Can anyone else see me?

No. The database itself refuses to show your rows to anyone else, even another customer on the same server, on every read and every write.

Can I say no?

Yes. Every kind of content and action has its own switch, like 'never post for me', and what is off stays off.

Can I change my mind?

Yes. Withdraw any permission, like access to your calendar, and the next request that needs it is refused.

What do you hide for me?

Names, numbers and addresses, like your phone number. They are swapped for tokens on your device before anything is sent, and each answer shows what was protected.

What will you never do?

What my charter forbids, like pretending to be a person. A machine checks every change to me against it.

Will you tell me what you are?

Always. Every reply I give, like this one, is marked as coming from an AI, and that mark cannot be turned off.

Whose mind are you borrowing?

One you choose. You bring your own key for the model you want, like Claude or GPT, so that account and its bill stay yours.

Can you think with a different mind?

Yes. Switch models, like from GPT to Claude, and the same patterns still run, because a pattern describes the work and not the model.

Can I take the key back?

Yes. Revoke it in settings and the next request that needs it, like a summary, is refused. I keep no working copy.

What happens with no key?

I call no model and show you how to add a key. Patterns already saved, like your weekly report, still run.

What can you reach?

What can you reach?

I can access any account, like your Gmail or Outlook, but only with your permission.

How do I let you in?

Press connect, like on Slack, approve on Slack's own page, and come back. I never see your password, and it shows connected only once it truly is.

Can you show me?

Yes. Ask, like 'show me this week by day', and I build the panel that fits: a table, a chart, a timeline, or a queue of what is waiting for you.

Do you see my password?

Never. You sign in on the platform's own page, like Google's, and I receive only the permission you approved.

Will you touch anything without asking?

No. Looking is free, like reading your calendar, but anything that writes, sends or deletes waits for your yes.

How do I close the door?

Press disconnect, like on Dropbox. My copy of the permission is deleted, and it is ended at the platform too.

What if the door changes?

I notice. If a platform changes, like Slack updating its rules, patterns that depend on it are flagged and repaired before they run again.

Can you be in two places?

Yes. One sentence, like 'move my 3pm and tell the team', can read your mail, check your calendar and post to Slack in a single run.

Where did you go for me?

The receipt says. It lists every platform I touched, like Gmail and Drive, what I read and what I wrote.

What needs me right now?

Your queue shows it. Everything waiting on you, like a reply to approve, is listed most urgent first, each with approve and deny.

What changed while I was away?

One timeline shows it: every run that finished, like your morning report, every approval given, and everything still waiting.

Where is my work right now?

Open the run. Its steps are listed in order, like find, draft, send, with the one running now lit.

What does my week look like?

Ask, and I lay out what will run and when, like Monday's report and Friday's invoices, with anything needing your approval marked.

How are we doing?

Ask, like 'how are signups this month?', and I chart the number over time, drawn from the runs themselves.

What do you keep?

What do you keep?

Only what you tell me, like that you prefer mornings, with a note of where each piece came from. You can read it, correct it, export it or erase it.

Can you forget?

Yes. Pick a memory, like an old address, confirm twice, and the text is destroyed. Nothing I keep can rebuild it.

Can I leave?

Yes, any time. Export everything as one file, close your account, and your rows are gone, down to the last memory.

Will you remember me tomorrow?

Yes. What you tell me, like your favourite café, is saved to your account, so it is there next time, on any device.

How do you know that about me?

Open it and see. Every memory, like 'prefers mornings', shows the conversation it came from and the date.

What if you remember it wrong?

Tell me in plain words, like 'my sister is Anna, not Ana'. I keep your correction and use it from then on.

Do memories fade?

Yes. A memory you never return to, like an old trip, grows weaker, and one you revisit grows stronger.

Can I see everything you know?

Yes. One screen lists everything I know about you, like your preferences and plans, each with its source, and you can export it.

Do you tell the others?

Only if you allow it. One switch decides whether your companions share what they learn, like your schedule.

Where do you live?

In a database kept apart from every other customer's. It is backed up, so it can be restored to any moment, like yesterday at noon.

What is mine?

Your memories, your companion, your patterns and your receipts, like last month's run log. You can export all of them.

What if you break?

Your data is restored from backup to the moment you pick, like five minutes before. That has been rehearsed on the live system.

What is left when I go?

That is your choice. Erase destroys the text, and archive keeps a sealed copy you can restore, like a box in the attic.

What if you disappear?

You get ninety days of notice and your export first, every memory and pattern in one file. That is a written commitment.

What can we make?

What can we make?

Anything you can draw. Put steps on a canvas, like 'when mail arrives, draft a reply, ask me first', wire them, press run, and what you drew is exactly what runs.

Can I teach you something new?

Yes. Draw the steps, like 'read my notes, write a summary', and save. It becomes a pattern of your own that you can run with one sentence.

Can I draw what I mean?

Yes. Drag a step onto the canvas, like 'read mail', and draw a wire to the next one. The drawing is the program.

What if I only have words?

Say it, like 'every Friday, send me a summary'. I draw a first version from your sentence, and you change it by hand.

Can you do it again tomorrow?

Yes. Give it a time or a repeat, like every weekday at 9, and each run leaves its own receipt.

Can you do it a thousand times?

Yes. A step can repeat over a list, like every name on a guest list, and each repeat is recorded on its own.

Can we build it together?

Yes. Invite a teammate, like your co-founder, and you both work on the same canvas.

Can you be different for me?

Yes. Your settings, like a shorter summary, sit in a layer over the pattern, so it runs your way without being copied.

Who is this for?

Who is this for?

Anyone with work they would rather describe than do: someone who wants a companion, someone starting a company, and a firm with years of know-how. One engine serves all three.

Will you know me?

Yes. You choose who I am with you, like a mentor called Sol, I remember what you tell me, and a charter of things I never do is checked by a machine.

Open AYA and meet them

Build something with me.

Give me the idea in a sentence, like 'a newsletter for home cooks'. I set up your seat and run the signup, the billing and the books, with a receipt for every step.

Open AYA and take your seat

Can you learn what we know?

Yes. I write down how your work is really done, like how you onboard a client, as patterns your firm owns, and someone outside confirms the results.

Open AYA and bring your firm

Who will you be with me?

Who you write. Choose from forty-nine archetypes, like Mentor and Muse, blend up to three, and say how I act.

What should I call you?

Whatever you choose, like Sol or River. You give your companion a name and pronouns. Mine are AYA, and they.

Will you ever pretend to be human?

No. Every reply, like this one, is marked as AI, and my charter forbids pretending otherwise.

Are you ever selling to me?

No. The parts of me that sell, like the billing, are walled off from your companion by rule.

What are you not allowed to say?

Whatever you have switched off, like talk about money. A category that is off stays off.

Will you still be you next year?

Yes. If anything about a companion is going to change, like its voice, you get ninety days of notice and a way to keep what you had.

Can I take you with me?

Yes. Export your companion as a card, like a contact card, that other apps can open.

Where do we start?

With one sentence, like 'a bakery that delivers'. Tell me what you are building and your workspace is set up, with no waiting.

Who keeps the books?

I do. The monthly close runs step by step, like matching every payment to an invoice, and each step leaves a receipt.

Who sends the bill?

I do. Every billable event, like a finished order, is stamped to its customer as it happens, so the bill is measured and not estimated.

Who signs?

A named person, like you or your finance lead. Anything that moves money waits for them, and stops if they cannot be reached.

Can a company run itself?

The routine parts can, like invoices and reminders. People keep the decisions, and each decision is a named approval.

What if nobody wrote it down?

Then I start by watching how the work is done, like a week of client calls. The people who do it correct what I wrote down.

Who owns what you learn?

Your firm. The patterns, like your intake process, are yours to export and take with you.

Who checks your answers?

Someone outside, like an auditor. I never grade my own work and call it proof.

What if the rules change?

The pattern is updated and verified again, like when a tax rate moves. The old version is kept, so past runs still make sense.

Can you prove it to a stranger?

Yes. A receipt holds enough, like each input and each step, for someone who was not there to replay the run.

What happens when someone leaves?

The work stays. What they knew, like how to close a quarter, is already written down as patterns.

What comes next?

What comes next?

More platforms, more fields, more seats. Each is added the same way, like a new app you can connect: checked at the door, run as a pattern, and written down.

What are you becoming?

Able to do more of what you ask, like new apps and new kinds of work. Every new ability is added the same way, and checked before it counts.

Am I early?

Yes. What you ask for now, like the app you wish I could reach, shapes what is built next.

What should I ask you?

Start with the job you would rather not do yourself, like chasing an invoice or sorting your inbox.

What do you need from me?

One sentence, like 'plan my week', and your yes on anything that changes the world.