Bound what gets loaded
Admit required and relevant context under an explicit budget instead of feeding the entire workspace into every decision.
Persistent memory, bounded context, tool/model routing and verified execution — organized as an inspectable control plane instead of a black-box chain of tool calls.
git clone https://github.com/robertoatila/jarvis-skill-registry.git
cd jarvis-skill-registry
python jarvis.pyMost agent stacks can call a model and execute a tool. Long-lived systems also need to decide what information deserves context, what authority exists, what evidence proves success and what should survive into memory.
Admit required and relevant context under an explicit budget instead of feeding the entire workspace into every decision.
Keep execution, verification, recovery and mission outcome separate. “The command ran” is not the same as “the job is proven done.”
Treat persistent memory as governed knowledge: freshness, source and confidence matter more than retaining every transcript.
The public release is fail-closed and evidence-bearing. Exact-tag validation runs before publication, and machine-readable artifacts are attached to the release.
The context number measures serialized UTF-8 bytes only — not token savings, cost, latency or answer quality. Open the v0.1.0 release and raw evidence.
J.A.R.V.I.S. is evolving toward a runtime where context, skills, tools and models are resolved through explicit contracts, authority checks, durable attempts and verification receipts.
v0.1.0 contains the governed skill registry, execution contracts/DAG, bounded inference primitives, verification structures, local HUD and memory/cognitive-vault foundations. Broader autonomy and empirical routing remain active development.
Run the three-command quickstart, inspect the release evidence, or pick a contributor-sized issue. Reproducible criticism is explicitly welcome.