Fig 0.1 The verification loop
Personal mastery for the AI era

Know what to learn next. Prove you actually know it.

AI can finish your work without proving you understand it. Nivela maps your goal against what you can explain and apply, finds the gaps that matter, and gives you one clear next action.

Free first report. Private by default. No credit card. You approve what Nivela keeps.

In validation

Nivela is not a finished product yet. The first Deep Checks are delivered manually. Join the waitlist to get notified when your slot opens.

You're on the list. We'll notify you when validation slots open.
1
Import
2
Map
3
Verify
4
Schedule
5
Action
CV claims for AI Backend Engineer
From your CV
"Built RAG pipeline for document Q&A using OpenAI and pgvector. Integrated streaming responses. Optimized inference with batching. Designed prompt templates for production use."
Built RAG pipeline for document Q&A
Claimed
Integrated OpenAI API with streaming
Claimed
Set up pgvector for embeddings
Claimed
Optimized inference with batching
Claimed
Designed prompt templates for production
Claimed
CV vs target role: AI Backend Engineer
RAG pipelinesEmpirical
LLM integrationEmpirical
Vector databasesEmpirical
Inference optimizationEmpirical
Prompt engineeringEmpirical
Model servingMissing
Evaluation & monitoringMissing
5 empirical, 2 missing, 0 verified. Nothing is verified yet. Verification determines what is defensible.
Probing RAG pipelines
HowWhyWhen notTransfer
N
Nivela asks: how
What retrieves the chunks, and what decides they are relevant?
U
Your answer
The question gets embedded, we search the vector DB for similar vectors, top results go into the prompt.
N
Follow-up: why
OK. How did you decide the chunk size? What happens if retrieval returns irrelevant chunks?
U
Your answer
We used 512-token chunks. If results are bad, the model usually still handles it.
Needs verificationTradeoff gap
How: Can explain embedding, vector search, and context injection.
Why: Cannot defend chunk size choice or explain failure when retrieval returns irrelevant chunks.
When not: No reranking layer. No fallback for bad retrieval.
After verification: spaced repetition
3
days
RAG pipelines
Re-verify after study session
next
LLM integration
Not yet probed, queue
next
Vector databases
Not yet probed, queue
next
Inference optimization
Not yet probed, queue
gap
Model serving
No evidence to schedule
Your next action
Highest leverage
Study RAG chunking and reranking
Your RAG claim is the most visible skill on your CV but you cannot defend it under probing. Learn chunking strategies, reranking with a cross-encoder, and failure modes when retrieval returns irrelevant context.
2 skills blocked
~4h estimated
3 days to re-verify
Scroll to explore
Fig 0.1b The problem is real
External evidence

AI assistance can speed up code without building the same understanding.

Anthropic · January 2026
Randomized controlled trial · 52 developers
0%
AI-assisted group
mastery quiz score
0%
Hand-coding group
mastery quiz score
0pt
Statistically significant
comprehension gap

How people used AI mattered. Participants who asked conceptual questions or generated code and then worked to understand it showed stronger mastery than people who delegated the task completely.

Scope: This study measured one coding task with 52 mostly junior developers learning an unfamiliar library. It supports the comprehension-risk hypothesis; it does not prove that every AI workflow reduces learning or that Nivela improves outcomes.
Read Anthropic's study

This has a name: epistemic debt. Three of them, actually.

Three writers named the same failure mode from different angles:

Ginac · arXiv 2026
Epistemological Debt
Academic: the delta between what code executes and what the engineer understands it to do.
Hall · failingfast.io
Epistemic Debt
Industry: the hidden cost of AI speed, paid as review load, churn, and security risk.
Osmani · O'Reilly
Comprehension Debt
Practitioner: the growing gap between how much code exists and how much any human understands.

All three describe the same failure mode: code exists, the engineer responsible cannot explain it. As Hall writes, the handover is gradual enough that you only notice it later — you still feel like you're writing code, but your role has shifted from driving to supervising.

01
Fig 0.2 Role readiness

Add jobs to your watchlist.
Nivela maps your CV against what they actually ask for.

Not a generic skills checklist. Real job postings, real requirements. Nivela shows which of your claims would hold under probing, and which would collapse in the interview.

Your watchlist
Jobs you're tracking. Nivela maps your CV against what they actually ask for.
Add a job posting
3covered
6at risk
1gaps
Covered: would survive probing
RAG pipelines
PostgreSQL
TypeScript
At risk: on your CV, but can you defend it?
Vector DBs
LLM integration
NestJS
Docker
Scalability
REST APIs
Gaps: offer requires, you don't have these
Distributed inference
Nice-to-have: non-blockers
Kubernetes
Kafka
AWS
Nivela suggests
Research their interview rounds: fintechs often include a system design round plus a live coding round
Ask how the AI team is structured: are you the only ML engineer or part of a team?
Distributed inference is required and you can't defend it. This will likely be probed in depth
AI Backend Engineer at Series B Fintech asks for 10 things. You cover 3, 6 are at risk under probing, and 1 are gaps you need to cover.Run a full Deep Check
2covered
6at risk
2gaps
Covered: would survive probing
PostgreSQL
TypeScript
At risk: on your CV, but can you defend it?
NestJS
Redis caching
Docker
Scalability
Consistency
REST APIs
Gaps: offer requires, you don't have these
Load balancing
Sharding
Nice-to-have: non-blockers
Kubernetes
Kafka
Nivela suggests
Logistics companies probe scalability and consistency hard. Expect a system design round about routing or inventory
Ask about on-call expectations: logistics often means 24/7 systems
Kafka is listed as plus. Prepare the Redis Streams substitution, it's a non-blocker
Senior Backend Engineer at Logistics Scale-up asks for 10 things. You cover 2, 6 are at risk under probing, and 2 are gaps you need to cover.Run a full Deep Check
2covered
6at risk
0gaps
Covered: would survive probing
PostgreSQL
TypeScript
At risk: on your CV, but can you defend it?
NestJS
React
CSS / Tailwind
Docker
REST APIs
JWT / OAuth
Nice-to-have: non-blockers
GraphQL
Nivela suggests
YC startups often skip formal rounds. Expect a single technical conversation with the founder
Ask about the engineering team size. At this stage you might be the only full-stack hire
GraphQL is plus only. Don't block on it, mention your REST API design experience
Full-Stack Developer at Y Combinator Startup asks for 8 things. You cover 2, 6 are at risk under probing, and 0 are gaps you need to cover.Run a full Deep Check
02
Fig 0.3 Career Deep Check
Career Deep Check

Your first Deep Check in five steps.

Career Deep Check is the first Nivela workflow. It is a real asynchronous report, not a generic resume score.

01

Set the target

Share your CV and the role you want. The target determines which claims and gaps matter now. A generic "backend engineer" produces a different report than "AI Backend Engineer at a Series B using NestJS."

02

Separate evidence from assumption

Nivela classifies each important claim as supported, empirical but unverified, missing evidence, too broad, or unsupported. Ambiguity stays visible instead of being rewritten into confidence.

03

Prepare for the probe

Recall, mechanism, reasoning, boundaries, transfer, and tradeoffs. The probe list is specific to your claims, not generic interview prep. Delivery is a separate skill — knowing the pattern matters more than having production experience.

04

Schedule re-verification

Verified claims get a re-evaluation date based on stability and difficulty. Unverified claims get queued for study. The schedule adapts as you learn and re-probe.

05

Get one next action

One prioritized next step to improve your readiness. Not a list of twenty things to study. One action that changes your position.

Sample Deep Check (fictional)
"Improved API performance with Redis caching."
Likely interview probes
  • What was slow before the cache?
  • Why was Redis better than fixing the database query?
  • How did invalidation work?
  • What happened when Redis was unavailable?
  • Which performance number did you measure, and how?
Defense gap: The solution is named, but the baseline, mechanism, failure behavior, and tradeoff are not yet defensible.
What defensible sounds like — technical
1I chose Redis because we needed sub-millisecond reads for hot keys.
2I considered fixing the query with a composite index, but the join cost stayed O(n) at our scale.
3We get 10x faster reads, but we trade cache invalidation complexity and a stale-read window.
4That's acceptable because our stale-read tolerance is 5 minutes and TTL is 60 seconds.
Choice, alternative, tradeoff, justification. Nothing hand-waved.
What defensible sounds like — behavioral
1Domain: Payments infrastructure for a Series B fintech.
2Problem: Idempotency failures caused duplicate charges under retry storms.
3Why it mattered: Each duplicate charge triggered a support ticket and a chargeback fee.
4What I did: Designed a deduplication layer using a Postgres unique constraint on (payment_intent_id, attempt_hash).
5Outcome: Duplicate charges dropped to zero across 50K daily transactions.
Context, problem, stakes, action, result. No vague "I helped with X."
Next action
Attach the original measurement, explain the request path before and after caching, and defend one rejected alternative.
The four-gap conversion
1What — the problem it solves, in your words.
2How — the mechanism, not just the outcome.
3When not — where and when it breaks.
4Why — what you rejected and why.
When all four are filled and you can explain without AI, the item is defensible. Not about removing AI-assisted work — about converting shipped output into knowledge you can defend under pressure.

Request your free Career Deep Check

Nivela is in validation. The first Deep Checks are reviewed manually and delivered asynchronously. Share your target and contact, and you will be notified when your slot opens. Nothing is stored beyond your explicit approval.

Drop your CV here, or browse
PDF only, max 5MB
Uploading...
or paste a link or text instead
Request received. You will be contacted at the email you provided when your validation slot opens. No data was stored automatically; you will be asked to confirm before anything is kept.
03
Fig 0.4 The method
The method

From your goal to one defensible next step.

Nivela connects the parts that usually live in separate tools: your goal, current knowledge, trusted sources, learning process, verification evidence, and next action.

01
Set the concrete goal.
02
Separate claimed, exposed, empirical use, needs-verify, verified, stale, and missing.
03
Learn from selected books, articles, videos, courses, and work evidence.
04
Test recall, reasoning, tradeoffs, and transfer over time.
05
Recommend one action that changes readiness.

Mastery is a probability, not a label

Most systems use a binary knows / does-not-know label. That hides the most common and dangerous state: has used it, cannot explain it. Nivela tracks a probability that decays over time, separated by how you encountered the concept. Seven states across a progression from claim to mastery to decay.

The danger zone
Empirical use
Used it in production, possibly with AI help. Cannot explain why it works or when to avoid it. The most dangerous state: you shipped with it, but an interviewer could expose you in 30 seconds.
Verified
Can explain why it works, when not to use it, and apply it to a new context. P(known) above 0.9. Earned through interactive evaluation across multiple sessions, not a single test. Requires 2+ sources and prerequisite check.
Claimed
On CV. No evidence yet.
Exposed
Read or watched. Never applied.
Needs-verify
Studied, not tested. Can follow, can't produce.
Stale
Was verified. Retrievability decayed. Due for re-evaluation.
Missing
No exposure. Blocks the goal.
Verified does not mean permanent.

Mastery decays if not re-tested. Nivela schedules re-verification based on stability and difficulty, before retrievability drops to 90%. A verified concept that is due for re-evaluation is flagged at session start, not silently treated as still mastered.

The verification rubric

Nivela does not ask "do you know X?" It probes six dimensions. Levels 1-2 mean empirical use. Levels 3-5 mean verified — these are the questions interviewers ask to separate real understanding from buzzwords. Level 6 is the interview-readiness layer: whether you can articulate it out loud under pressure. Behavioral answers are preparable: the system tracks which stories you can defend and which ones still have gaps.

01
Recall
What
Can you define it in your own words?
Recall gap: cannot remember the fact.
02
Mechanism
How
Can you explain the mechanism, step by step?
Mechanism gap: remembers the fact, cannot explain how it works.
03
Reasoning
Why
Can you reproduce the reasoning behind a design decision?
Reasoning gap: knows how, cannot explain why it works.
04
Boundaries
When not
When should you not use it? What fails? What did you reject?
Boundary gap: knows how and why, not when to avoid it.
05
Transfer
Transfer
Apply it to a new context you have not seen.
Transfer gap: knows the concept, cannot apply it elsewhere.
06
Tradeoffs
Articulate
Can you articulate the tradeoff out loud, under pressure?
Performance gap: understands it, cannot defend it in an interview.

How verification works

Verification is not a quiz. It is a structured process with gates, fading, and metacognitive tracking.

01
Source gate
A concept needs 2+ independent sources before evaluation. One source is exposure, not understanding.
02
Prerequisite check
Before evaluating a concept, check its prerequisites. A failure may be upstream: you don't understand X because you don't understand Y that X depends on.
03
Fading stages
Complete walkthrough, then backward fading (you finish), then forward fading (you start), then independent problem solving. Pace adapts to difficulty.
04
Confidence calibration
Before feedback, you rate your confidence. Over time this reveals whether you know what you actually know. Overconfidence is tracked, not hidden.
01

See your real state

Separate claimed, exposed, empirical use, needs-verify, verified, stale, and missing. Do not call a skill mastered because it appears on a CV or course certificate.

02

Learn from sources you trust

Turn selected books, articles, videos, courses, and work evidence into source-grounded explanations built around your existing knowledge and current goal.

03

Prove the knowledge holds

Use recall, reasoning, tradeoff questions, and transfer challenges. Recheck knowledge over time instead of treating one correct answer as permanent mastery.

04

Act on the next gap

Connect the evidence to the goal and receive one prioritized action: study a prerequisite, defend a project claim, revisit a stale concept, or prepare for the next interview requirement.

04
Fig 0.5 Source to mastery
Source to mastery

Do not collect summaries. Build knowledge that survives.

Uploading a source does not mean you learned it. Nivela turns trusted material into a traceable learning and verification loop. Same engine as Career Deep Check, different entry point.

See what happens when you share an article to learn.

Example source
System Design: What is Availability?
AlgoMaster Newsletter, Ashish Pratap Singh, 8 min read
blog.algomaster.io/p/system-design-what-is-availability

Nivela runs the same loop: ingest, extract, learn, verify, schedule. Click through the stages.

1
Ingest
2
Extract
3
Learn
4
Verify
5
Schedule
Source received
URLblog.algomaster.io/p/system-design-what-is-availability
TypeArticle (Substack)
AuthorAshish Pratap Singh
Length~1,800 words, 5 sections
Fetching content...
Content extracted. Ready for concept mapping.
Powered bymdingestarticle-to-markdown ingestion API
Concepts extracted from source
Availability
Uptime / (Uptime + Downtime). Measured in nines.
Redundancy
Backup components take over when primary fails.
Failover
Active-passive vs active-active. Automatic switch on failure.
Data replication
Synchronous vs asynchronous. Consistency tradeoffs.
Monitoring & alerts
Heartbeats, health checks, alerting systems.
5 concepts extracted. 3 new, 2 connect to existing knowledge. Prerequisites checked: none missing.
Personalized essay: Availability
AnchorYou already understand load balancing from your NestJS project. Availability is what load balancing protects.

Availability is the proportion of time your system is operational. If your API is up 99.9% of the year, that is 8.76 hours of downtime.

Each additional "nine" is a 10x improvement. 99.99% = 52 minutes downtime. 99.999% = 5 minutes.

The strategies you just read about (redundancy, failover, replication) all serve one goal: reduce downtime when components fail.

CaseYour NestJS API has one instance. It crashes. Availability = 0%. Add a load balancer + second instance. If one crashes, the other serves. Availability jumps. This is active-passive failover.
Verification: Availability
HowWhyWhen not
N
Nivela asks: how
Your API has 99.9% availability. How many minutes of downtime per year is that?
U
Your answer
About 500 minutes. 0.1% of 525,600 minutes in a year.
N
Follow-up: why
Correct. Now: you chose active-passive failover. What is the tradeoff vs active-active?
U
Your answer
Active-passive is simpler but wastes the standby. Active-active uses both but is harder to coordinate.
Verified: P(known) = 0.92
Mechanism and tradeoffs both solid. Promoted to verified. Schedule stability check in 7 days.
Spaced repetition: extracted concepts
7
days
Availability
Stability check, just verified
3
days
Redundancy
Re-verify after study
3
days
Failover
Re-verify after study
next
Data replication
Not yet probed, queue
Next action: Study redundancy and failover patterns, then verify in 3 days. Both connect to your existing load balancing knowledge.

How mastery is measured

Nivela does not grade with a single score. It tracks two models over time:

BKT: Bayesian Knowledge Tracing
P(known) updates after every evaluation. Correct answers increase it, incorrect answers decrease it. P(slip) and P(guess) correct for noise. Above 0.9 = verified. Below 0.5 = demoted.
FSRS: Spaced Repetition
Difficulty and stability adjust based on performance. Easy + correct = longer interval. Hard + correct = shorter interval. Incorrect = reset. Next review when retrievability drops to 90%.
Confidence-accuracy
After each answer, before feedback, Nivela collects self-reported confidence. Over time this reveals metacognitive calibration: do you know what you actually know?
Prerequisite chains
Before verifying a concept, Nivela checks its prerequisites. A failed evaluation without checking prerequisites produces a false diagnosis. The real gap may be upstream.
05
Fig 0.6 Correct action
Correct action, not more content

More content is not the goal.

The goal is to identify the smallest action that changes your readiness.

Stop studying everything

Prioritize the missing capability that blocks the current goal instead of following every new roadmap or job-posting keyword.

Stop mistaking familiarity for mastery

Reading a clear explanation feels like understanding. It isn't. Researchers call this the fluency illusion — exposure to a well-written answer inflates perceived comprehension without building retrievable knowledge. Nivela tests retrieval, not recognition.

Stop preparing stories you cannot defend

A polished claim is a liability when the reasoning behind it is missing. Narrow it, prove it, or remove it.

Keep progress connected to the goal

Every study session, verification result, correction, and source changes the next recommendation.

Agent continuity

Your progress should not disappear when the chat ends.

Your goals, approved facts, demonstrated knowledge, recurring gaps, preferred learning style, and next actions should belong to you, not to one conversation or model.

Nivela is designed to become a portable context layer that supported AI agents can read with permission. The same approved state can eventually guide learning, research, career decisions, and other capability packs.

Planned after validation: Hosted personal profile, full export, agent skills, workflow packs, and MCP access. No third-party logos are shown as active integrations until each connection works in production.
06
Fig 0.7 Trust and privacy
Trust and privacy

Your context is not a marketing asset.

A useful personal system needs sensitive information. Nivela must earn that access through control and evidence.

You approve persistent facts

Nothing becomes canonical personal context without confirmation. Nivela may suggest, but you decide what stays.

Evidence remains attached

Important claims keep their source and status so you can inspect why Nivela believes them. Every concept page carries verbatim quotes from the original source, not paraphrases. A claim without a source is a hypothesis, not a fact.

Uncertainty stays visible

If the evidence is incomplete, Nivela says unverified. It does not turn a guess into a confident profile fact. You always know what is proven and what is not.

You can leave

The planned product requires full export and deletion. Customer data must not be used for model training without explicit opt-in consent. Your data is yours, including the right to remove it.

Built on a working system

This is not theory. I am running it right now.

304
Concepts tracked
51
Deterministic scripts
18
Books processed
14
Course platforms

Nivela comes from a personal knowledge system I have been building and testing for months. It tracks 304 concepts across system design, databases, JavaScript, and backend engineering. Each one has a probability of mastery that decays over time. Each one has a scheduled re-evaluation date. Most of them are not verified yet. That is the honest starting point.

Topics that were hard to talk about are now easy. Not because I read more, but because the system evaluated me: it asked for recall, mechanism, reasoning, boundaries, transfer, and tradeoffs. When I could not produce the answer, it recorded the gap. When I could, it scheduled when I needed to defend it again.

The system behind Nivela is complete, large, and hard. Source extraction from books, courses, articles, and videos into concept pages with verbatim citations. BKT probability tracking. FSRS spaced repetition. Prerequisite chain checking. Metacognitive calibration. It works because it is rigorous, not because it is simple.

Making it accessible to everyone as a sole engineer is the challenge I chose. The landing page you are reading is the first step: I want to know if this resonates before I build more. There is no product yet. There is a working system that proved the methodology, and a question: does this matter to anyone else?

FAQ

Questions before your first Deep Check

No. A resume writer improves presentation. Career Deep Check first asks whether the underlying claim is accurate, supported, and defensible. Rewriting comes only after the truth is clear.
Flashcards test recall. Nivela tests understanding: recall, mechanism, reasoning, boundaries, transfer, and tradeoffs. It tracks a probability of mastery per concept that decays over time, checks prerequisites before evaluation, and schedules re-verification based on difficulty. Anki asks "do you remember X?" Nivela asks "can you defend X in an interview tomorrow?"
No. It proves exposure or completion. Nivela keeps that separate from the ability to retrieve, explain, and apply the knowledge under pressure.
No. AI assistance does not make real work false. The question is whether you can explain what happened, why the solution works, what can fail, and which tradeoff you accepted.
It reviews one CV against one target role, identifies the claims most likely to be challenged, and recommends the first gap to close. Optional evidence can improve the report.
No. Nivela is in validation. The first Deep Checks are a manually delivered service used to test the problem and workflow before software is built.
The report is private. Nothing is stored beyond your explicit approval. The planned product requires full export, deletion controls, and clear data retention terms before submissions open.
Free during validation

Start with one honest question:
where do I actually stand?

Your free Career Deep Check includes:

  • A private review of your CV against one target role
  • Important claims classified by evidence and defensibility
  • Likely interview probes for your highest-risk claims
  • The most important comprehension gap to close
  • One recommended next action

Initial reports are delivered asynchronously during validation. Pricing for continued access is still being tested.

Stop guessing what you know.

Choose the role you want. See which claims hold, which gaps matter, and what to do next.