Virgil

Virgil · Build log

Build log

Selected milestones that changed what Virgil is or what a learner can do with it. Newest first.

Submission buildOpen source
Browse milestones

31 August 2026 · submission build

Virgil becomes an owner-managed AI learning manager

The product is now expressed through five connected parts: Capture, Learn, Grow, Manage and Customize. Grow is the centerpiece: eleven Google ADK stages work through the learner's material and evidence in the background, then a separate verifier can withhold defective teaching.

The public repository contains the exact hosted Service and Job checkpoint. Each installer supplies their own Google Cloud, Firebase and model credentials. Owners can admit verified-email members from Settings while each member keeps an isolated learner board.

27 August 2026

Settings and recovery survive interruption

Model routing, processing and privacy preferences, backups, restore, and account deletion now preserve the learner's exact next step through a service failure or expired sign-in. Virgil does not silently repeat a failed request, and only a confirmed service response becomes current.

Backups, restore, and deletion keep a recoverable next step after an interrupted request. A partial deletion is reported as partial, not complete.

26 August 2026

The full learner loop passes end-to-end testing

A learner can now capture a passage, receive a save receipt, and open that pin's lesson in the same side panel. Quick takes, guided steps, and recall return to Learn with their result. Queued captures remain visible and recoverable.

End-to-end testing has exercised the complete flow in one product: reviewed course intake, a time-sized next move, learner-started background processing, a checked lesson with a recall or practice action, a recorded result, and an updated recommendation.

26 August 2026

Evidence changes what Virgil teaches

Insights now labels each statement as my read or your words. A learner correction becomes authoritative in the following teaching brief instead of leaving an incompatible machine opinion underneath it.

Five-minute lessons contain something to recall, apply, observe, or continue. External study receives a return receipt, draft feedback stays tied to the learner's own words, and every product room now survives Refresh and browser Back at a durable address.

26 August 2026

Virgil gets a public product surface

The website now explains the learner experience before the machinery behind it: save something, get one useful next move, act, and let the result change what comes back.

The public shell now has the three routes a visitor needs: Guide, Install, and Build log. Its clearly labelled page-theme selector offers Whiteboard and Blackboard across every route.

26 August 2026

The learner-facing build returns ownership to the installation

The full Virgil page now comes from the same service that owns its board. Each account-backed installation provides its own Google identity configuration and service origin. Google handles the credential; Virgil never asks for a separate password.

The extension and full page use the same account. The compact side panel stays beside the page being read.

26 August 2026

The background system runs without a laptop

The ordered background stages have run in Google Cloud against a hosted board and produced a checked session. Learner-started processing, run receipts, and the learner-facing service are deployed components.

This established the background route. The later submission lock added the public repository, checked self-host instructions and owner-managed access.

23 August 2026

The separate screens become one product

Today, Learn, Plan, My studies, Check a draft, Insights, and Settings now share one frame, navigation, account state, and theme control.

The side panel is smaller than the full product. It holds the current lesson, the page beside it, and a link to the full product.

22 August 2026

Today becomes the front door

Virgil stops opening on the collection and starts answering one question: what should I do right now? One ready lesson, one dated commitment, or one short recall move can lead, sized to the time available.

The learning board also separates Recharging, Paused, and Learnt. Stopping a topic no longer lets the product claim it was mastered.

20 August 2026

The capture loop works in a real Chrome session

A learner can save an exact passage or whole page without opening Virgil first. The side panel confirms what happened and can open a Quick take while the question is still alive.

The saved source, the fast response, and the learner's Understood or Add to my lessons verdict now belong to one record instead of three disconnected moments.

19 August 2026

The first end-to-end session is composed and checked

The first full run turns saved sources into stable topics, selects a lesson style for each topic, composes a session to a time budget, and sends every section through a separate verification pass.

A defective or unverified section is withheld. The model that wrote it cannot approve its own repair.

Next

Let real use test the learning manager

The milestones above describe build and browser testing, not evidence of external adoption or improved learning outcomes. The source and self-host route are public. The next work is external use: which captures become valuable later, which recommendations are acted on, and whether evidence-driven adaptation earns long-term trust.

Now · ShowTell the complete product story.Demonstrate Capture, Learn, Grow, Manage and Customize against the locked hosted build.
Next · InstallExercise the public self-host route.Use an operator-owned project, credentials and member boundary from the published instructions.
Then · LearnLet outside use set the roadmap.Retention, recommendation quality and trusted adaptation become the evidence for what should be built next.