QonQrete Terminology

Version: v0.9.0-beta (See VERSION file for the canonical version).

This document defines the official vocabulary for the QonQrete Secure AI Construction Loop System.

Qrane: The host‑layer orchestrator (qrane/qrane.py) that runs outside the sandbox.
worQer: An AI agent that performs a specific role (instruQtor, construQtor, inspeQtor).
Qrew: The collection of agents that work together inside the Qage.
tasqLeveler: A specialized agent (v0.9.0+) that runs ONCE on Cycle 1 to enhance tasq.md with golden path tests, dependency graphs, mock infrastructure specs, and success criteria.
qompressor: A specialized agent that “skeletonizes” the codebase to create a low-token, high-context representation.
qontextor: A specialized agent that generates a machine-readable symbol map of the codebase. It can run in a fully local mode (using AST, Jedi, and PyCG) or use AI to analyze the “skeletonized” code.
qontrabender: A policy-driven hybrid caching agent that assembles variable fidelity payloads. It mixes full code (MEAT) and skeletons (BONES) based on configurable rules.
calqulator: A specialized agent that provides a token and cost estimate for an upcoming cycle.
Local Provider: A provider type for agents that do not use AI and run completely locally (e.g., calqulator, qompressor, qontrabender).
LoQal Verifier: A deterministic local verification agent that checks syntax and imports without AI.

Qage: The secure Docker container or Microsandbox that contains the Qrew.
Qodeyard: The output directory (.../qodeyard/) where all code is generated.
worQspace: The shared volume (worqspace/) for configuration and agent communication.
qache.d: The cache ledger directory managed by qontrabender.

cyQle: A full Plan -> Execute -> Review loop.
tasQ: The high-level user request (worqspace/tasq.md).
briQ: A single, atomic step of the plan, generated by the instruQtor.
Operational Mode: A setting (--mode or in config.yaml) that defines the “persona” or priority for the agents (e.g., security, performance).
Briq Sensitivity: A numeric setting (0-9) that controls the granularity of the instruQtor’s task breakdown.
Cheqpoint (Configuration): A boolean setting (cheqpoint) in config.yaml that determines the default execution mode. true for user-gated, false for autonomous.

Variable Fidelity: The practice of mixing full code (MEAT) and skeletons (BONES) in cache payloads.
MEAT: Full source code from qodeyard/, used for core/high-utility files.
BONES: Skeleton code from bloq.d/, used for massive/reference files.
Volatile: Files that change frequently and are excluded from cache, sent fresh via stdin.
Caching Policy: Configuration file (caching_policy.yaml) that defines Qontrabender behavior and modes.
Fidelity Rules: Configurable rules that determine whether a file gets full, skeleton, or omit treatment.
Core Score: A computed value (0.0-1.0) indicating how “core” a file is based on dependencies, symbols, and references.

Universal File Rule: The foundational rule for multi-cycle builds: if a file EXISTS, modify/extend it; if MISSING, create it. Prevents rebuild-from-scratch bugs.
s00permode: Nickname for the Universal File Rule approach that removes artificial “refinement modes”.
Golden Path Tests: Inline code blocks in enhanced tasq.md that define what MUST work for each module.
Batched Reviews: InspeQtor groups multiple briqs into single API calls for massive cost savings.
exeQ: Per-briq execution summary written by ConstruQtor.
reQap: Review/recap summary written by InspeQtor.

gateQeeper: The human user responsible for making decisions at the CheQpoint.
CheQpoint: The mandatory pause after a cyQle for user review.
Qommander: In TUI mode, the top panel showing the main execution flow.
Qonsole: In TUI mode, the bottom panel showing raw agent logs.