Reading preferences

RAGBAZ / grove / Sylvae

Sylvae

The right worker for the job, with a receipt.

En portabel färdighetskörare: bär en SKILL.md-instruktion till en lokal modell, ett externt API eller en agent, välj körmiljö medvetet och behåll ett beständigt körningskvitto.

Active development · v0.1.0 prototype runner with local review surface

Sylvae project mark

The grove: shared knowledge, different workers, visible roots.

01 / Portability

The skill is not the vendor

Keep instructions in SKILL.md frontmatter and body. The same know-how travels between a local model, a hosted API and an agent harness without rewriting.

02 / Honesty

A receipt, not a promise

Every run has an identity, a backend, a model, timing and an outcome. Unavailable budget, refused invocation and unsuccessful results are three different records.

03 / Economy

Name the tier before spending

Cheap, frontier and agent are different resources with different fixed costs. Declared routing keeps a trivial prompt off a six-second agent bootstrap.

A skill travels through an explicit tier choice to a backend; the run receipt returns to review while the audit chain stays separate.

The receipt problem / Brief 01

From a skill to a useful receipt

A practical path from an explicit backend choice to a run record and commit-bound evidence.

Read the runs brief

01 Sylvae

Kunskap med rötter, inte leverantörslås

Sylvae kör en SKILL.md-instruktion mot Ollama, Claude Code, Codex, OpenCode eller Anthropics API. Fyra av fem bakgrunder återanvänder CLI-verktyg du redan är inloggad på.

Välj nivå uttryckligen: billig, frontier eller agent. Automatik gissar aldrig att något är billigt. Explicita val spelar roll eftersom verkliga körningar kostar verklig tid, tokens och pengar.

02 Sylvae

Börja i terminalen, fortsätt i granskningssidan

Installera från källkod, kör en liten färdighet mot en lokal modell och läs kvittot. En saknad bakgrund, en förbrukad budget eller ett nekat anrop är inte samma sak som ett misslyckat resultat.

De engelska fördjupningarna visar bakgrunder, granskningssidan och ombudsvägen för agenter. De blandar inte ihop lokal verifiering med ett beslut om driftsättning.

A cooperative workshop

Four responsibilities. One clearer story.

Use one tool where it helps, or connect the whole workshop. People keep the purpose and judgment; the tools make the work easier to explain.

From intention to understanding

A workflow you can explain to another person

  1. Write one useful skill

    Describe the job and expected output in SKILL.md with a declared tier. Start small enough that another person can assess the result.

  2. Choose a backend deliberately

    Name a local model for a first experiment, or map tiers to your actual host and accounts. Read what auto would choose before letting it choose.

  3. Read the receipt

    Inspect input, output, model, timing and status. Unavailable, failed and successful runs answer different questions.

  4. Bring the result into review

    Correlate the run ID with WeftMark evidence, check audit integrity with Nostoi where useful, and keep the human judgment explicit.

    Bring the threads to the loom →

A small first step

Run one local skill

Use a source checkout, Python environment and an already configured Ollama installation. Download the model you intend to use and prepare a small input file.

Model downloads need storage and bandwidth. Hosted and agent backends have their own credentials and costs; do not assume automatic routing is free.

Install

git clone https://github.com/tabenius/sylvae.git
cd sylvae
python3 -m venv .venv
. .venv/bin/activate
pip install .

Choose a model and run a skill

ollama pull mistral:latest
sylvae run skills/summarize-diff --backend ollama \
  --model mistral:latest --input /path/to/a/diff.txt

Inspect your records

sylvae runs
sylvae review
Full installation and operating guide →

The routing desk / Illustrated cases

The same prompt can cost four different things.

Select a case to see how a declared tier, an explicit backend and a recorded outcome relate. Backend and model names are the documented ones, not live measurements.

Presentation-only illustrations. No model runs, no spending occurs, and no review is authorised by this explorer.

Declared cheap stays local

The skill names its tier; the router honours it without interpretation.

Declared tier
cheap
Backend
ollama / mistral:latest
Spend
Local compute, no API fee

Illustration: explicit cheap work never leaves the machine. Operating the model remains your own cost to weigh.

Undeclared defaults to frontier, not to cheap

No tier key means the safe choice, on a separate account.

Declared tier
(absent)
Backend
opencode / capable model
Spend
Hosted inference, metered

Illustration: the default protects an interactive budget from silent consumption; it does not promise the cheapest adequate answer.

Agent work pays its bootstrap

A harness with tools is a different resource from a bigger model.

Declared tier
agent
Backend
shellout (Codex)
Fixed overhead
Seconds and thousands of tokens, every run

Illustration: route multi-step work here deliberately; keep trivial prompts away from it.

A missing budget is unavailable, not failed

The run never happened, so there is nothing to debug in the skill.

Observed head
Quota exhausted
Recorded outcome
unavailable
Next action
Wait, re-authenticate, or choose another backend

Illustration: record the absence and act on it. Do not rewrite the skill to fix a run that never ran.

A conversation, not a sales funnel

What would you like to build together?

Ask a question, tell us what you need, offer a contribution or simply show your support. RAGBAZ is a software studio working toward kindness, mutual cooperation and the good of all beings.

Prefer email? ragbaz@proton.me

No advertising trackers or fingerprinting. Browser privacy signals take precedence over optional attribution. How we look after your information.