What is a Living Career Portfolio?

A CV is a snapshot. A LinkedIn profile is a platform’s view of you. Neither is a portfolio.

A portfolio used to mean something specific. Designers had one. Architects had one. Photographers had one. Everyone else had a CV — a one-page advertisement, rewritten for every application, forgotten between job hunts.

That is finally changing. Not because anyone invented portfolios for the rest of us. Because the idea of a portfolio — a living body of evidence that proves what you can do — is the right shape for a career, and the infrastructure to build one for any worker, in any field, finally exists.

This is what a Living Career Portfolio is. This is what most people have been quietly building for years without anywhere to put it.

What “portfolio” used to mean — and why it failed everyone except creatives

A designer’s portfolio is a stack of work. A writer’s clip folder is a stack of articles. A musician’s reel is a stack of recordings. The pattern is the same: gathered evidence of past work, arranged for someone to evaluate, kept and added to over time.

For everyone else, the equivalent is a CV. One page. Reformatted constantly. A list of titles and dates that compresses a working life into a document a recruiter will spend ninety seconds with. The CV is not a system. It cannot capture skill nuance. It cannot connect a claim to its proof. It cannot update itself when you finish a project. It is built to be reduced — never to be grown.

The European Union saw the gap and tried to close it. Europass has been the official European attempt at a citizen-owned skills passport since the early 2000s. The design intent was right: a portable, multilingual record of qualifications and experience, owned by the citizen, recognised across member states. The execution stopped at a static PDF most people fill in once and never open again.

LinkedIn became the global default by being slightly more dynamic. You can edit it. Other people can see it. But a LinkedIn profile is the platform’s view of you — laid out the way it wants, ranked by its algorithm, governed by its terms, structured around its idea of what your career looks like. It is not yours. It is theirs, with you in it.

The result is that most workers have no portfolio at all. They have a CV they update under duress, a LinkedIn profile they rarely look at, and a fifteen-year accumulation of professional evidence scattered across places they cannot search.

Where your career evidence actually lives right now

Open the average professional’s filing system and you will find some version of this:

A paper folder in a drawer with the university diploma, the language certificates, the printed Coursera certificate from the year remote learning got serious. An Evernote account with notes from team meetings going back several years, partly searchable, mostly forgotten. A Google Docs folder where things go to disappear — you saved it, you cannot find it again. A Notion workspace, beautifully structured, half-built, abandoned mid-renovation. File folders on the laptop following the eternal ~/Documents/Work/Q4/finals_v2_FINAL.pdf convention. Email threads with the salary review you can never search for. Slack DMs with the message from the CTO that said “honestly the best deck I’ve seen this year” — gone in ninety days unless you screenshotted it. A LinkedIn profile, which is someone else’s database, with someone else’s UI, governed by someone else’s Terms of Service. Recommended by people who have moved companies twice since they wrote it.

The portfolio you have been building for fifteen years exists. It is just spread across nine places, none of which talk to each other.

The kicker comes the moment you actually need it. Performance review. Salary negotiation. Redundancy in week six. The role you didn’t think you’d apply for until it appeared. You can find half of the evidence. The half you find isn’t connected to the half that proves it. The testimonial is in Slack. The project that earned the testimonial is in Drive. The skill the project demonstrated is somewhere on the CV. The certificate that backs the skill is in a paper folder in a different country. None of it composes.

This is not a personal failing. It is a structural one. Career evidence has had nowhere to live. The tools you used to make the evidence were never built to hold the evidence — Slack is for talking, Drive is for files, LinkedIn is for status, the drawer is for diplomas. There has not been a place that exists, in your control, that holds and connects all of it.

A Living Career Portfolio is that place.

Five properties of a Living Career Portfolio

A Living Career Portfolio is not a tool category. It is a set of properties. Anything that has these five things is one. Anything that misses one of them is not.

Structured. Every claim has a record behind it. A skill is not a string in a list — it is an entity, with provenance, mapped to a recognised taxonomy, linked to the experience that proves it. A project is not a paragraph — it is a record with a role, dates, outcomes, and the artifacts that demonstrate it. The structure is what lets the rest work.

Living. It is additive over time. New evidence enters, old evidence stays. Nothing decays because the calendar moved. The portfolio you had at twenty-eight is still inside the portfolio you have at forty-two — the early-career project that proved your first management instinct is still in the record, still queryable, still relevant the day a hiring manager asks about it.

Owned. It belongs to you. You can export the whole thing as structured data. You can delete it in one action. You can take it to another tool. No platform holds it hostage. No proprietary format locks it in. The right to data portability is not a feature you have to ask for — it is the foundation everything else is built on.

Connected. Skills link to the experiences that prove them. Experiences link to the artifacts that demonstrate them. Artifacts link to the testimonials that confirm them. Certifications link to the issuers that verified them. The portfolio is a graph, not a list — which means it can be queried, scored, and read in directions a CV never could be.

Productive. Other systems can use it. Job-scoring engines can read it. CV generators can compose views of it. Cover-letter writers can cite from it. Coaching tools can evaluate gaps in it. The portfolio is not a vault; it is an engine. It generates work.

A folder on your laptop is structured but not connected, productive, or living. A LinkedIn profile is living but not owned. A Notion workspace can be all five — but only if you build the structure yourself, by hand, and very few people will. A Living Career Portfolio is what you get when something gives you all five at once, without making you the data engineer.

What “evidence” actually means

A skill on a CV is a claim. Project management. Strategic planning. Stakeholder engagement. Words a recruiter has read ten thousand times, attached to no proof.

Evidence is what turns a claim into a record. Evidence is the project you led from kickoff to delivery, with the dates, the team size, the outcome, and the deck you presented at the end. Evidence is the certification with the issuer, the date, the validation URL. Evidence is the testimonial from the colleague who saw the work, captured in writing, attributed to a person who can be checked. Evidence is the artifact — the PDF, the link, the photograph of the diploma, the GitHub repository, the published article — that anyone can inspect.

The practice of capturing this kind of evidence has its own name in some professional communities. Julia Evans’s brag document — a private record of work that made you proud, kept across years and re-read at performance review time — has become a cultural touchstone among engineers. The brag document is the evidence layer of a portfolio, written down before it disappears. The instinct is right. What it has been missing is structure and a place to live.

That structure exists now. The European Commission has spent years building ESCO — a taxonomy of every occupation and skill in the European labour market. It is the reference layer that lets a forklift operator’s skills be treated with the same structural rigour as a software architect’s. When evidence in a portfolio is mapped to ESCO, it becomes legible — to scoring engines, to public employment services, to anyone trying to match a person to an opportunity. Without that mapping, every system has to invent its own categories, and nothing composes.

The CV is one view of your evidence. The cover letter is another. The LinkedIn profile is another. The portfolio holds the underlying records — the atoms. The CV, the cover letter, and the profile are arrangements of those atoms for a specific audience. When you have the atoms, you can compose any view you need, for any role, in any language. When you only have the views, every new audience is a rewrite.

Why this hasn’t existed before, and why it can now

The idea is not new. The execution was waiting on three things that did not exist together until very recently.

First, a mature taxonomy that covers every occupation and skill in a labour market. ESCO reached that maturity over the last decade. Before ESCO, every system invented its own categories, and nothing composed.

Second, open data standards for the records themselves, so evidence can move between systems without losing its meaning. The Experience API (xAPI) — originally built for learning records, now usable for any structured evidence statement — is the standard that makes this work. xAPI was created on a simple principle: the learner owns the record. The same principle scales directly to careers.

Third, AI capable enough to read messy evidence and extract structure from it. Five years ago, building a Living Career Portfolio would have required users to manually enter every skill, link it to every project, type out every certification. Almost no one was going to do that. Today an extractor can read a CV, a LinkedIn export, a project description, a Slack appraisal, a photographed certificate, and surface the structured records — with the user reviewing, correcting, and approving. The data entry tax that killed every previous attempt is gone.

The pieces exist now. The portfolio your career has been quietly waiting for is finally buildable.

How Kitsuno implements it — the Library

Kitsuno’s implementation of a Living Career Portfolio is called the Professional Record Store — the PRS. The user-facing surface is the Library.

The Library accepts every form your career evidence comes in. A photographed paper certificate. A pasted-in Slack appraisal. A PDF of a performance review. A link to a project. A free-text note describing something the formal record will never capture. The extractor reads each one, proposes structured records — skills, experiences, certifications, testimonials — mapped to ESCO where the mapping makes sense. You review what was extracted, correct what is wrong, approve what stays.

The records connect. A skill links to the experience that proves it. The experience links to the project artifacts that demonstrate it. The artifacts link to the testimonials that confirm them. The whole thing is queryable — by skill, by period, by role, by proof type, by language.

Other parts of Kitsuno read from the Library. The Scorer matches jobs against your real evidence, not keyword overlap. The Writer drafts CVs and cover letters that cite specific projects from your records. The Validator checks every AI-generated document against the Library before you see it, and flags claims that have no backing.

The Library belongs to you. Every record exports as structured JSON at any time. Every record deletes in one action. The whole Library deletes in one action. You can take it elsewhere — to another tool, to a successor product, to nowhere at all. GDPR is not a compliance checkbox here; the right to data portability is the foundation the system sits on.

That is one implementation. There can be others. The point is that the architectural shape — structured, living, owned, connected, productive, with the user in control — is buildable now in a way it was not a few years ago. Kitsuno is building it. Other tools should too.

”Why not just upload everything to an LLM project folder?”

A reasonable thought, and a common one in 2026. Claude Projects, ChatGPT custom GPTs, Notion AI — drop your CV, your certificates, your testimonials, your project descriptions. Ask the model anything. For one-off questions and quick rewrites, it works.

But it leads to a question worth pausing on: would you trust an LLM your full life?

Because that is what an “upload everything into a project folder” workflow asks you to do. The painful chapter you would rather not surface right now. The role you would prefer not to lead with for this application. The medical context. The year that did not go well. The testimonial that is true but private. The folder does not ask. The model picks.

An LLM project folder is a honeypot. Every file is in scope for every prompt. The model decides what is “relevant” using its own training, its own opinions, its own context window. You have one knob: what to put in the pile. Everything after that is the model’s call.

A Living Career Portfolio is the opposite shape. Your evidence lives in a database, not a pile. The model does not browse — it gets handed exactly what you authorised for the task at hand. In Kitsuno, four layers of control sit between your evidence and any AI output:

• The Library decides what evidence exists at all. You add it deliberately. You delete it in one action.
• Profile activation decides which subset of the Library is active for which job search. The career chapters you do not want featured for this search are simply not active for this profile. Same Library, different active subset.
• Weighting decides what matters more for this task. You tell the system which dimensions of your evidence to emphasise. The model does not guess at what is important to you.
• Transparency shows you, after every AI action, exactly what was accessed and how it shaped the output. Score breakdowns name the evidence. Cover letters cite the project. The Validator flags claims that cannot be backed. Try getting that from a project folder.

A Living Career Portfolio is the structured data layer underneath your career — not an LLM. You can absolutely point an LLM at it. Kitsuno does: that is what Kitso is. But your portfolio is the system of record, and the LLM is one consumer of it, with controlled access, on your terms, with full visibility into what it sees.

The honeypot model trades user agency for convenience. The Living Career Portfolio refuses the trade.

What changes when you have one

Several things change in ways that compound.

Job scoring becomes meaningful. A score against your real, structured evidence tells you whether your career maps to a role. A score against keywords tells you whether your CV happens to use the same words as the job description. They are not the same number, and the first one is the only one worth acting on.

The CV stops being a one-shot rewrite. It becomes a view. Need a CV emphasising your data work for a quantitative role? The portfolio composes one from the records that demonstrate that work. Need one emphasising leadership for a manager role? Same portfolio, different composition. The hours you used to spend reformatting are now spent thinking about which evidence to feature.

Cover letters cite real projects. When the writer generating a draft has structured evidence to draw from, the resulting letter references the work you actually did, with the dates and outcomes that prove it. There is no model-invented accomplishment to embarrass you in an interview. The letter is provably yours, because the records it cites are yours.

You can see your gaps. The portfolio is queryable in both directions. You can ask not only “what evidence do I have for this skill?” but “what skill keeps appearing in roles I want, that I have no evidence for?” That second question is what turns a portfolio into a career-development tool, not just a record-keeping one.

You can take it with you. Whatever tool helped you build the portfolio is not the tool that owns it. Export the whole thing as JSON. Hand it to another product. Hand it to a coach. Hand it to nothing at all and keep it on your laptop for a year. The portability is not a politeness — it is the architecture.

This is what people have been improvising toward for years with their nine-place filing systems. The improvisation has never quite worked because the pieces were not connected. When the pieces are connected, the work the improvisation tries to do becomes nearly automatic.

The principle underneath — your career data belongs to you

The architecture is not new.

Over a decade ago, education research described what it called a Personal Learning Environment — informal learning resources under individual control, originating from the learner, only loosely tied to any institution. A learner’s own ecosystem of notes, networks, references, tools, conversations: shaped by the learner, owned by the learner, maintained by the learner across whatever institutional contexts come and go (Wampfler, Zimmermann & Turkawka, 2019).

A Living Career Portfolio is the same architectural shape, applied to careers. The principle is identical: the individual is the durable entity, institutions are temporary, and the system of record should belong to the durable entity, not the temporary ones.

The principle has other names elsewhere. The right to data portability in GDPR Article 20 — the legal right, in European law, to receive your personal data in a structured, commonly used, machine-readable format and transmit it elsewhere. The xAPI standard, which formalised “the learner owns the record” as technical infrastructure. The MyData movement, the Nordic-led effort to put individuals in operational control of their own data across providers. Different domains, same principle: the durable entity should own the record.

A Living Career Portfolio is the implementation of that principle for working life. Your career data should outlive any platform that helps you organise it, including the one you are using right now.

This is also the first principle of Kitsuno. Your data is your soul. In kitsune mythology, every fox carries a hoshi no tama — a soul gem that contains its power. Without it, the fox is nothing. The PRS is yours in exactly that sense. It belongs to you. It can be exported, deleted, or taken with you at any time. Kitsuno holds it in trust. We will never sell it, trade it, or use it to train models. GDPR is not the compliance checkbox — it is the architecture.

A portfolio you do not control is not a portfolio. It is someone else’s database with you in it.

What your career deserves

You have been building a career your whole working life. A real one, with real evidence, scattered across real places. A drawer with diplomas. An inbox with appraisals. A Slack with appraisals you screenshotted before they expired. A laptop with finals_v2_FINAL.pdf. A LinkedIn that is mostly someone else’s view of you.

You deserve a place to put it that you actually own. A place that holds the evidence in structured form, so it can be queried, composed, scored, and used. A place that grows with you across roles and decades and tools. A place that is yours to take wherever you go next.

That is what a Living Career Portfolio is. The infrastructure to build one finally exists. Kitsuno builds one — even on the free Kit tier, the Library is yours, fully exportable, with no lock-in. Other tools should too.

The fox’s first principle is that your data is your soul. The portfolio is the system that gives the principle a place to live.

Frequently asked questions

What’s the difference between a portfolio and a CV?

A CV is a one-page document built to be read by a recruiter in ninety seconds. A Living Career Portfolio is a structured, growing record of your career evidence — skills, projects, certifications, artifacts, testimonials — that you own and control across a working life. The CV is one view composed from the portfolio. The portfolio is the system underneath.

Where does career evidence usually live, and what’s wrong with that?

For most professionals it lives in nine places at once: paper folders, Evernote notes, Google Docs, Notion workspaces, file folders on a laptop, email threads, Slack DMs, certification provider sites, and a LinkedIn profile. None of them talk to each other. None are designed to hold connected, structured evidence. The moment you actually need a specific testimonial or project for an application, you can find half of it, the half you find isn’t connected to the proof, and the time tax is enormous. A Living Career Portfolio is one place that holds all of it in structured form, queryable in any direction.

How is this different from a LinkedIn profile?

A LinkedIn profile is the platform’s view of you — structured the way LinkedIn wants, ranked by its algorithm, governed by its Terms of Service. A Living Career Portfolio is yours: structured records you control, exportable as data, deletable in one action, transferable to another tool when you choose. LinkedIn can be one consumer of your portfolio’s evidence. It is not the portfolio itself.

Can I take my portfolio with me if I leave Kitsuno?

Yes. The Professional Record Store is built around the right to data portability — you can export every record as structured JSON at any time, on any tier including the free Kit tier. You can delete the entire Library in one action. Kitsuno holds your data in trust; we never sell it, trade it, or use it to train models. If you leave, you take everything with you.

Why is this called a living portfolio?

Because it is additive over time and does not decay. New evidence enters, old evidence stays. The early-career project that proved your first management instinct is still in the record at year fifteen, still queryable, still relevant the day a hiring manager asks about it. A static portfolio is a snapshot of one moment. A living portfolio is a body of evidence that grows with the working life it documents.

References

Wampfler, P., Zimmermann, T., & Turkawka, G. (2019). Personal Learning Environments als Ressource in Lehr-Lern-Settings. In T. Zimmermann, G. Thomann, & D. Da Rin (Eds.), Digitalisierung und Lernen. Gestaltungsperspektiven für das professionelle Handeln in der Erwachsenenbildung und Weiterbildung. Bern: hep-Verlag. ISBN 978-3-0355-1334-9. Publisher page →

---

Published 1 May 2026. No affiliate links. No sponsored placements.