🧭 Мой путь
Ordered routes through the wiki: read them in sequence, or jump to the step you need. Every step is a published article with sources and a check date.
New to Tvijo
Open the workspace, run your first capped task and read the receipt.
-
Start with Tvijo in ten minutes
Open the workspace, sign in with an eight-character code, run one bounded task and read the receipt that shows what it cost.
-
Install the Tvijo extension in your editor
Ask about a selection without leaving VS Code: the same account, the same capped task, the same receipt — and no API key stored in the editor.
-
Costs, budgets and limits
Every task has a cap, every attempt is counted, and an unknown cost is shown as unknown. The arithmetic behind the receipt.
Editor and reviewer
How articles move from draft to published, and who signs off sources.
-
How this wiki is edited and published
Articles live in Django with an editorial status, a source list, a reviewer and a revision log. Nothing reaches /wiki/ without passing those gates.
-
Sources, dates and what “verified” means
A checked date is the date a human opened the source. Documentation, code and a runtime test are three different levels of evidence — and we label them.
-
Permissions and data flow
What leaves your machine, what stays local, and which actions need an explicit human decision — including the licence question people skip.
Engineer
Models, routing, swarms, judging and recovery when a run fails.
-
Models and routing: what the composer control changes
You pick a route, not a vendor. The receipt is the source of truth for which model answered and what it cost.
-
Splitting work across agents — and when not to
A swarm in Tvijo is several bounded tasks in separate working copies, each with its own budget and receipt. Coordination cost is real; here is how to decide.
-
AI judging: why “it says it is done” is not acceptance
Deterministic checks decide. A model's self-report is a claim, and a separate read-only check is cheaper than shipping the failure.
-
Recovery after a failed, stuck or uncertain run
No automatic paid retries, an uncertain task blocks further spend, and reconcile never resends inference. The exact commands to get unstuck.
Team lead
Budgets, permissions and a pilot you can measure.
-
Costs, budgets and limits
Every task has a cap, every attempt is counted, and an unknown cost is shown as unknown. The arithmetic behind the receipt.
-
Permissions and data flow
What leaves your machine, what stays local, and which actions need an explicit human decision — including the licence question people skip.
-
Running a Tvijo pilot and measuring the benefit
A pilot that can be judged: one workflow, one acceptance check, four numbers per week, and exit criteria agreed before the first task.