HUMAN_LEARN / Widget Pipeline

⚙️ Widget Pipeline — how a request becomes a widget

One-sentence lead: what this is and when it runs. (Replace this whole page with the real, file:line-grounded explanation of the user's topic — this file is only the visual template.)

trigger what kicks it off core main logic worker spawned work store persistence
5
stages
20
batch cap
8 MB
read window

The flow, step by step

1 · Trigger
what starts it
file.ext:NN
→
2 · Read
bounded input read
file.ext:NN
→
3 · Transform
the core step
file.ext:NN
→
4 · Work
spawned subprocess
file.ext:NN
→
5 · Persist
atomic write
file.ext:NN

3 · Transform core file.ext:120-148

Prose explaining the step, with inline constants and a file.ext:NN for each claim. Show a real snippet when it clarifies:

doThing(input, { cap: 20, windowBytes: 8 * 1024 * 1024 })
Key insight. The one thing a reader must take away — e.g. why the design is correct, or the invariant it preserves.

The knobs

All constants (real names + values)
ConstantValueWhereBounds
BATCH20file.ext:50items per unit of work
MAX_BYTES8 MBfile.ext:52read window per run

Why it's shaped this way

Constraint A

The real reason — an incident, a platform limit, a cost guard.

Constraint B

Another forcing function that explains a non-obvious choice.