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

Gather project context, edit, verify, then request an independently scoped review. The course is not a reproduction of proprietary behavior or a file-rewind service. Primary source.

Framework versus application

ReviewBoundary requests a safe pause after verification. DurableWorkRuntime owns spawn/join and Session restore. The reviewer receives a separate Session and restricted registry; reviews are advice, not parent write authority. 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. Use a new external directory for every run; resume reconstructs this project’s factory and resolver. 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 the reviewer policy with a compatibility-focused reviewer; retain child identity and return evidence. Composition: Use Pi’s verifier; later add Hermes procedures as selected context, not an extra execution loop. 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/claude_coding/src/qitos_lab_claude/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

src/qitos_lab_claude/__main__.py
src/qitos_lab_claude/tasks.json
src/qitos_lab_claude/evaluate.py
src/qitos_lab_claude/agent.py
src/qitos_lab_claude/extension.py
src/qitos_lab_claude/review.py
src/qitos_lab_claude/__init__.py
pyproject.toml
agent.yaml