A researched piece
Paste in a pile of article links. Let systems read and summarize all of them. Draft against those sources, edit the draft in your own editor at home, then run a fact-check pass whose corrections you approve one by one.
Ergoki
Stop re-explaining yourself to the AI.
Every new chat starts from nothing. Ergoki keeps your sources, lists and notes in one living document — so the next question starts with everything the AI already needed to know.
Everything you make lives in a single database file you can download whenever you like.
You paste the same background into a new chat. Again. You hunt down the same six links. Again. Last week’s good answer is buried in a conversation you can’t find, and the model has no idea what you already decided.
The thinking is not the hard part. The keeping is.
A small example
Say you keep track of films — what you loved, what you walked out of, what your partner refuses to sit through. Here that is a dictionary: a table you define yourself, one row per film, with whatever columns you care about.
You add a few dozen. Then you point a system at them and the AI fills the gaps — genre, year, runtime — across every row at once, not one chat at a time.
Now drop that list into a construct: a document you build out of parts. Add one line at the end asking for tonight’s pick. Copy the whole thing into whichever AI you already use, and the answer comes back knowing your taste, because it genuinely does.
Next Friday you change that last line. Everything above it is still there. That is the entire idea, and it scales from film night to a research report.
Construct — “Movie night”
1 · Text
What we like, what we avoid, how much time we have.
2 · Dictionary
Films — 214 rows: genre, year, runtime, verdict
3 · Prompt
“Under two hours, nothing we’ve seen, good for both of us.”
4 · Result
— paste the answer back here —
Copy the construct → paste into any AI → paste the reply back in. Next time, only the last part changes.
The four pieces
Four words to learn. Everything else in Ergoki is built out of them.
Dictionaries
Tables you define. Films, sources, clients, card designs, diary days — you choose the columns.
Entries
The rows. Start one with almost nothing — a URL, a half-remembered title — and fill it in later.
Systems
Do one thing to all the rows at once: read the page behind a link, summarize, classify, tidy up.
Constructs
The document everything lands in: notes, lists, prompts, drafts. It grows as the work does.
The same loop, on real work
A hundred images, one style
Card art, game assets, character portraits. Change a single style line — “90s comic book”, “16-bit pixel art” — and regenerate the whole set so every piece still matches every other piece.
Everything about you
Tastes, allergies, the kids’ ages, how your team writes, what you already rejected and why. Written once, attached to any question, for years.
Made by one person, used every day
No investors to answer to, no growth targets, no quarterly reason to make it worse. It is built by someone who has to live with it tomorrow morning.
You keep the file
All your content sits in one database file. Download it whenever you want, or upload one to replace everything. Leaving is a button, not a support ticket.
Whatever AI you already use
Systems can call AI directly, but the plainest path is copy out, paste back. Nothing here is welded to one model or one vendor.
Is this for you?
Worth being straight about, before you spend an evening on it.
Probably, if
- You already use AI most days and feel the friction of starting over
- Your work comes back in rounds — research, writing, catalogues, worldbuilding
- You would rather assemble your own tool than accept someone’s workflow
- You want to be able to walk away with everything you made
Probably not, if
- You want an agent that takes the whole job away unattended
- You need shared team workspaces, roles and admin controls
- You want one button per task rather than pieces you arrange yourself
- A one-off question to a chatbot already answers everything you need
Start with the film list
A new account comes with that example already set up — a small dictionary, a system to run on it, and a Getting Started construct to follow. Fifteen minutes tells you whether the idea fits how you think.