01
What Career Memory Is
A stored, structured record of your professional history. You upload a résumé once; it is read into roles, dates, education, credentials, skills and projects, and kept against your account.
The reason it is a named part of the product rather than an implementation detail is that it is what makes the rest of ORQILO coherent. Every surface reads this one record, so they cannot disagree with each other about what you have done.
02
What It Holds
- Roles: employer, title, dates and what you did.
- Education and credentials.
- Projects, with what you built and what happened.
- Skills, and where in your history each one is evidenced.
- Goals: the target role and primary goal you set.
- An activity log of what has changed, so the record has a history rather than just a state.
And, deliberately, the holes. A field ORQILO does not know is shown as unknown rather than filled with something reasonable — the same rule the product applies to any number it cannot prove.
03
Where Each Field Came From
Every field is tagged with its origin, and the distinction is the useful part of the whole record:
- Verified — read directly from the document you uploaded.
- AI inferred — the model concluded it from context rather than reading it.
- User provided — you typed it.
An inferred job title and a stated one look identical on a résumé, and only one of them is something you said. Keeping them apart is what lets you correct the model rather than inherit its guesses.
04
Why It Matters
You enter your history once
Tailoring a résumé, planning a route to a target role and preparing for an interview are three jobs that all need the same input. Doing them in three separate tools means typing it three times and keeping three copies in step.
The surfaces cannot contradict each other
Your résumé, your career roadmap and what the career coach tells you all derive from this record. Change the record and they all move together.
Advice can be about you
A model that has just met you can only work from what you tell it in that session. One reading a persistent record can say which of your skills you can evidence and which you cannot — which is a statement about you rather than about careers in general.
05
Your Control Over It
- You can edit any field, including correcting something the model inferred.
- It is stored in Firestore against your account, protected by security rules, over HTTPS.
- There is no additional client-side encryption layer — stated plainly rather than implied.
- What ORQILO does with your data is set out in full in the privacy policy.
The privacy policy covers retention and deletion.
06
Questions
What is Career Memory?
The stored record of your professional history that every other part of ORQILO reads — roles, dates, education, credentials, skills and projects, parsed from a résumé you upload. It persists to your account, so you never re-enter your history to use a feature.
How does it get filled in?
You upload a résumé or CV and it is read into structured fields. You can then correct or add to it. Nothing here asks you to fill in a long form first.
Does it show me what it does not know?
Yes, and that is deliberate. Missing fields are displayed as missing rather than quietly filled with a plausible value — which is the same rule the rest of the product follows for numbers it cannot prove.
Can I tell which parts came from my résumé and which were inferred?
Yes. Each field carries where it came from — verified from your document, inferred by the model, or supplied by you — so you can tell fact from inference at a glance.
Is my record encrypted?
It is stored in Firestore under your account and protected by security rules, over HTTPS. There is no additional client-side encryption layer, and this page will not imply one.
Which plan includes it?
Career Brain, the surface that shows the full record, is a Pro feature.