Why QonQrete?
Execution first, generation second
Most tools optimize for code output. QonQrete optimizes the execution process: clarification, constraints, planning, build, validation, inspection, and controlled continuation.
Bounded repair over endless loops
Repair attempts are structured and capped. QonQrete favors explicit continuation metadata over invisible retry spirals.
Model-flexible by design
Provider/model choices can change per task or budget. Default runtime alignment is venice / deepseek-v3.2, with local runtime support for mlx and llama-cpp.
Audit trail built in
Artifacts and manifests are recorded in each qage so teams can inspect timelines, outputs, and verdict paths before syncing anything back.
Controlled sync for safer experimentation
-N/--no-sync keeps run outputs in qage/qonstruction paths so you can compare, test, and apply changes deliberately.