jevbooks

← All projects

Nilo-System-One

mattiolocoding/Nilo-System-One

Local router: System 1 CLI tools, optional System 2 Ollama fallback.

Classification & Routing0.98Runner-up: Infra / SDKs / IntegrationsFunnel
Automated README summary

Automatically summarized from the README on 8 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

Nilo is a local router for simple requests using read-only CLI tools (System 1) and optionally a local Ollama model (System 2). It returns JSON and identifies the agent as "Nilo". Requires Python 3.10+ and Linux commands.

How it uses Jev

Nilo is inspired by JEV's typed-decision approach but does not use Jev. It separates routing decisions from execution: decide_query() returns an immutable RoutingDecision with action, reason, intent, and allowed command. It uses deterministic regex matching, not probabilities or model logits. Model choices never execute commands.

Technique worth stealing

Separate routing decisions from execution for inspectable, zero-token decisions.

Try it

python3 nilo.py "what time is it?"

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectnot found in the excerpt0.14
  • Shows a System One patternnot found in the excerpt0.25
  • Describes handling uncertaintynot found in the excerpt0.17
  • Reports measured numbersnot found in the excerpt0.04
  • Is a runnable toolFound in material0.97
  • Top-10 learning shortlist signalnot found in the excerpt0.10
  • Is a replica of the modelFound in material0.77
  • Solves a common problem (0–2)score on a 0–2 scale1.18 / 2
  • About JevFound in material0.76
Signals
Jev is core to the project0.14Shows a System One pattern0.25Describes handling uncertainty0.17Reports measured numbers0.04Is a runnable tool0.97Top-10 learning shortlist signal0.10Is a replica of the model0.7700.51Solves a common problem (0–2)1.18 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.94Questionnaire0.69Prefetch0.35Check-up0.25Inspection0.2200.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 8 Oct 2026.