Olea component workbench

Olea component workbench dev tooling

The product's own screens, running outside Obsidian against an invented practice vault.

What this shows

Everything below is the real product code — the same screens a student would see and answer, driven end to end. Two things about it are not real:

The material is invented. Coined words and made-up courses. Never a real student's notes.
The answers are pre-recorded. Real model calls, made once and saved. Every render since replays them, so clicking around costs nothing.

One consequence worth holding on to: because the material is nonsense by design, none of the numbers here — rankings, match scores, generated questions — say anything about how well Olea works. They show that it works at all.

Nothing reaches these yet

These two are not missing, and saying they were would be the easy version. The logic exists and is tested. What does not exist is any way for her to arrive at it — no screen, and nothing she can do that calls it. They are listed here because a capability nobody can reach is, to her, the same as one you never built; this project has found that defect five times by going looking for it.

Explain-back — she explains a concept in her own words and the AI grades the answer. The grading pipeline is built and wired into the plugin; the method that runs it has no caller. Phase 4
Misconceptions — the AI notices patterns in what she keeps getting wrong. Ten tested modules; nothing calls the matcher, and the seam it needs has no implementation. Phase 4

Mode

Review states

Today panel states

Due summary, per-course counts and streak (F6.1) only. The mastery overview and insights on this same pane (F6.2, F6.5) do not render here — this surface is never given a trends source. See "Trends states" below for those, on the same real TodayView.

Oracle states

The ranking, study-plan and gap/coverage chain (F4.2, F4.3, F4.5, F4.9, F4.10), driven by a synthetic curriculum and corpus over the same coined vocabulary a persona's stream already uses — never the fixture vault. Dev tooling only (D-021); zero model spend. (The walkthrough's own oracle steps are the one deliberate exception — D-041 — and live in "Mode" above, not here.)

Retrieval states

Query -> hybrid retrieve -> grounded context or refusal (C4.7, INV-5), replaying a pre-computed embedding cassette over a synthetic corpus — zero model spend at render time. No product view exists for raw retrieval results, so this surface reports through the inspector only; see its own note there.

Generation states

Retrieve -> generate -> accept (C4.7, INV-5, INV-6), replaying a pre-computed generation cassette over a synthetic corpus — zero model spend at render time. The "Accept" control is a REAL gate: nothing becomes vault-ready `McqFields` until it is clicked. No product view exists yet for reviewing a generated card (P3-T07b's accept step is still open in the product), so this surface reports through the inspector plus one live control; see its own note there.

Timeline states

The day loop (`ol-opmb.5` [TB-4]): the SAME mastery -> rank -> plan -> gap -> queue chain as the oracle states above, replayed across a simulated semester rather than at one fixed instant. Time is an axis, not another state — scrub the day with the controls at the top of the inspector. Zero model spend; dev tooling only (D-021).

Explain states

The passages an explanation would be built from, found by the product's own retrieval over the invented student's notes. The explanation itself is not written yet: the Worker does not serve the explain task. What you can see working here is the grounding and the refusal.

Session states

A time-bounded study session assembled from the highest-priority gaps, with the exam countdown and format preference matching folded in. Two states show what an empty session honestly looks like.

Trends states

Mastery per course, and the patterns the review log will support. The two neutralised states are negative controls: same seed, planted pattern removed. They are here so the detector's claim is checkable rather than asserted.

Walkthrough