abhyasa
abhyasa (अभ्यास) means steady practice. It is a tutor that asks you questions and makes you do the thinking. It never gives the answer first. You answer in text or by voice, and you can think aloud. The tutor grades your reasoning, not only the result. A learner model keeps the depth of each concept that you know, and the date of its next review.
How it works
Each question goes through one loop:
- Pick. Code chooses the next concept and the depth: a due review first, then the frontier. The app shows the reason.
- Ask. A model writes one question at that depth, with a hidden model answer and a rubric.
- Struggle. You answer. A wrong try gets the first error and a nudge, but no fix. You can ask for hints, one rung at a time.
- Grade. The model grades the answer and the think-aloud. Code grades choice questions and code exercises.
- Update. Correctness and confidence move the floor, the ceiling and the next review date of the concept.
- Teach. After a miss, the tutor teaches the smallest step that fixes the first error. Then it asks a check question.
| term | meaning |
|---|---|
| concept | one idea that you can be asked about |
| depth | 0 unseen, 1 recognise, 2 recall, 3 explain, 4 apply, 5 transfer |
| floor | the highest depth that you pass reliably |
| ceiling | the lowest depth that you failed |
| attempt | one answer, kept as a vault document |
| session | one sitting of questions; saved after each move, so you can continue it after a restart |
| journey | a goal and a path of steps to it, one concept each; you can see and change the path |
| profile | what abhyasa knows about you: background, goals, the examples that help you, pace; you see and change all of it |
| hint | one rung of a ladder of six, from the least to the most revealing |
| lesson | the smallest step that the tutor teaches after a miss |
| demo | an interactive figure for one concept: you predict, lock in, and then change the inputs |
Install and run
Install the package and its dependencies:
uv sync
Start the web app on http://127.0.0.1:5077:
uv run abhyasa
The app listens on the loopback address only. These variables change the defaults:
| variable | what it sets | default |
|---|---|---|
ABHYASA_VAULT |
the vault file | the vault of vishalakshi |
ABHYASA_MODEL |
the rishi model for questions, grades, hints and lessons | claude/sonnet |
ABHYASA_STT |
the speech-to-text engine: gemma, whisper, parakeet, openai or mlx:<repo>. It is stronger than the Settings page. |
the Settings page, then gemma |
Surfaces
All surfaces use the same tutor and the same data.
Web app
The web app is made from blocks under abhyasa/blocks:
| block | what it does |
|---|---|
today |
the home page: continue, your journeys, the next review, this week |
journeys |
journeys: say a goal, and the tutor proposes a path of steps; move, skip, add or split a step; continue any journey |
history |
Your learning: each past session with what moved, what you learned each week, and Continue in the top bar (⌥C) |
profile |
What abhyasa knows about you: a short first conversation, your edits, and the changes that the tutor makes, each with its reason |
session |
one sitting with the tutor: one question at a time, with hints, confidence and “I don’t know” |
voice |
a mic for each text box where you answer or write; ⌥D speaks into the box in focus, on any page |
settings |
the speech model: pick, look up and get one; the OpenAI key; the tutor model |
concepts |
the list of concepts, and one page for each concept with its state |
graph |
the concept graph: a color for each floor, a ring when a review is due, arrows for prereqs |
search |
one search over the learning shelf and the other shelves of your vault |
add |
add concepts from a text, a vault document or vedicreader |
demo |
interactive demos from rupaka: “Show me a demo” on a concept page, a demo under the lesson after a miss, and one page for each demo |
Each page shows where you are, over its title. Esc goes up one level, ⌥T goes to Today, and browser Back and Forward work.
ramabana
The /learn extension gives the tutor in the terminal, beside your code.
To turn it on, make the file ~/.config/ramabana/extensions/abhyasa.py with this line:
from abhyasa.rama import setup
Notebooks
In leela or Jupyter, learn shows a question card. exercise gives a code exercise that its tests check in the kernel.
from abhyasa.nb import learn, exercise
learn('reciprocal-rank-fusion')
ex = exercise('reciprocal-rank-fusion')
Where the data is
All data is on the learning shelf of the vishalakshi vault.
Each concept, attempt and session is one vault document, so other tools can search it.
Tests use a vault in a temporary folder and never open your real vault.
Demos
Some ideas are easier to see than to read. A demo is one interactive figure from rupaka. It asks you to predict first, and it hides the result until you lock in (⌘↩). Then the controls are live, and the last line asks a new question.
- After two misses on a concept with the same kind of error, or for a concept with
visual: truein its meta, the tutor makes a demo in the background. A model writes it as data, and rupaka checks it in a headless browser. You never wait. - After a miss on a concept that has a demo, the session shows the demo under the lesson.
- “Show me a demo” (⌥E) on a concept page shows the newest demo, or makes one.
- Each prediction is kept as an attempt with
kind='demo', and it updates the learner model of the concept, as an answer does. A prediction with a reason counts at depth 3 (explain), and one without a reason at depth 2 (recall).
abhyasa.demo.import_gallery(learning) stores the rupaka gallery demos (vowel sandhi and others) for the concepts that match.
Example
This example runs offline. temp_learning makes a shelf in a temporary vault, and Fake replaces the model.
from abhyasa.store import temp_learning
from abhyasa.llm import Fake
from abhyasa.tutor import Tutor
lr = temp_learning()
lr.put('Ranking', 'Order items by a score.', 'ml')
fake = Fake({'You grade one answer': dict(correct=True, grade=8, first_error='', misconception='', feedback='Yes. Only the order counts.')},
dflt=dict(question='Why can you compare ranks from two systems, but not their scores?', answer='Ranks share one scale.', rubric=['ranks share one scale']))
t = Tutor(lr, fake, context=False)
Ask the first question. why gives the reason for the choice. A new concept starts at depth 3 (explain).
q = t.next()
assert q.why == 'next on the frontier: its prereqs are in place'
assert q.depth == 3
print(q.question)
Answer with high confidence. A solid pass at depth 3 raises the floor to 3.
r = t.answer(q.id, 'A rank is a position, and positions use the same scale in each list.', confidence=80)
assert r.outcome == 'solid'
assert lr.concept('ranking').floor == 3
Metadata
Release files for abhyasa 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| abhyasa-0.0.7.tar.gz | 1.1 MB | Without provenance | Details for abhyasa-0.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| abhyasa-0.0.7-py3-none-any.whl | Python 3 | none | any | Details for abhyasa-0.0.7-py3-none-any.whl |
Total release size: 2.1 MB
Release files / abhyasa-0.0.7.tar.gz
| Download URL | abhyasa-0.0.7.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bed5916f2c1b2f52802f00c782fc045a0bf50a2e33a677d82119ae1a27bc9565
|
|
BLAKE2b-256 checksum How to use checksums |
246d5d534919c3692461d95bcdd8cd004d213fdd4cf7ce742748a6e53883edca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / abhyasa-0.0.7-py3-none-any.whl
| Download URL | abhyasa-0.0.7-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d067dafcdd2e9dea775e724555ff37f54c1c8aa4f68794dab49fb13a8cedc84
|
|
BLAKE2b-256 checksum How to use checksums |
0b3b9fad2a36ef9ff7e83bc2d61b3e410286bd4a1e82f869d46204ebbcbc0e14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for abhyasa 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.