The loop runs through the graph, not beside it
GraQle: the graph is the constant, the harness the interface, the model a swappable input · the loop runs ANCHOR → ACTIVATE → GENERATE → VALIDATE → COMMIT
HARNESS
what the model sits in
interface, not governance
tools it can call
files it can read
credentials it holds
channels it talks through
model · a swappable input
model A
model B
model swapped · graph unchanged
IDE or agent harness
LOOP
plan · act ·
observe · retry
in GraQle: five
named phases,
run through
the graph
ANCHOR
start from what the
organisation already knows
ACTIVATE
pre-reasoning selects the
relevant subgraph, not the
whole repository
GENERATE
the model runs, as a swappable
input
VALIDATE
below the confidence floor:
refused, not guessed
COMMIT
lessons that survive return to
the graph
the next loop starts from what the graph now knows
GRAPH
what the organisation
remembers
durable, typed state:
policy · 22
code · 74
decision · 14
lesson · 15
document · 21
146 nodes · 162 edges
a real GraQle project
graph, labels withheld
validated lesson
candidate
refused
below the confidence floor
new lesson · validated
new lesson · validated
ACTIVATE: the relevant subgraph, selected before the model runs
Quantamix Solutions · quantamixsolutions.com
source: github.com/quantamixsol/graqle (README; docs/dag/defensive-publication.md)