Skip to main content
Status: in development, not course-qualified. The working source below is not a claim of a passed 3×3 live matrix. See the execution ledger for qualified facts and open gaps.

Design and adaptation boundary

Separate factual memory, episode retrieval and procedural skills. A catalog advertises descriptions; only a selected skill loads its complete body. Primary source.

Framework versus application

Memdir facts and episodes have separate roots. SqliteToolLibrary persists procedures with versions and source metadata. A learning process and a recall process share only explicitly bound storage. QitOS supplies model transactions/usage, tool permission/validation, Env execution, Session, ArtifactRef and Trajectory. The application supplies tasks, policy, independent acceptance checks and memory/skill selection. This iteration adds custom agent_factory composition, persistent skill revisions, full-body selection, explicit Memdir deletion and correct artifact data authority. The core design increment is in agent.py below. The CLI shows configuration and resource ownership explicitly; evaluate.py is the controller checker. Tasks use repository-owned synthetic professional scenarios, not paper benchmarks or customer data.

Install, configure and run

First install the QitOS wheel built from this iteration; the current PyPI release cannot stand in for unpublished APIs. Then install this project. Keep actual addresses and credentials outside Git. The private model file is a full qitos.agent configuration; this launcher selects only its model section, never an environment-variable key. Run —phase learn first, then —phase recall with a new —root and the same external —shared-root. Do not reuse the old input directory. The output default is 10,240 and may be raised in private model configuration. Task request/step/time guards come from configuration. validate does not call a model; —live is mandatory for execution. Docker failure must not silently fall back to the host. Retain unsuccessful results and human interventions.

Verification, exercise and composition

Independent checks examine sources/numbers or executed code, not a model’s success claim. Plan revisions, actual skill loading and child identities require separate mechanism evidence. Session restore is not filesystem rollback. Generated code executes only in the restricted Env. Exercise: Replace lexical recall with another MemorySource, retaining namespace isolation and explicit forgetting. Composition: Supply approved protocol facts to PlanAct; never treat an unverified episode summary as checked evidence. The required matrix is three tasks, three repetitions each. ReAct/PlanAct share tasks; static planning, no-memory and no-skills are explicit controls. A single pass is not a performance result. Raw traces stay private until redistribution and sanitization checks authorize a derived publication.
Complete implementation: examples/projects/hermes_notebook/src/qitos_lab_hermes/agent.py.

Extracted from complete source: the design increment

This excerpt is generated from the complete project, not a separately maintained implementation. Complete installable files follow.

Complete files: save in the project root

agent.yaml
pyproject.toml
src/qitos_lab_hermes/__init__.py
src/qitos_lab_hermes/agent.py
src/qitos_lab_hermes/evaluate.py
src/qitos_lab_hermes/tasks.json
src/qitos_lab_hermes/__main__.py