Handbook

L1.3 — Batch of independent functions

Status: Defined

Updated

Sub-level at a glance
Parent level L1 — Function
Autonomous unit Batch of N independent functions in one run
Distinct assay evidence ≥2 function units, each individually verified
Grade today a

Canonical policy, grades a-d, and promotion criteria: Autonomy levels (Blueprints). Per-project scoring: Autonomy maturity framework (Blueprints).

Gates and evidence

All gates and core evidence of the parent level (L1 — Function) apply unchanged. Declaring this sub-level adds the distinct check:

  • ≥2 function units in the plan, each with its own individual apply+verify pass

A run that fails the sub-level check may still be reported at the plain parent-level grain if the parent's evidence holds — sub-level claims are strictly additive.

Prompt pack

Execution rubric (repo path, nav-hidden): prompts/autonomy/sublevel-l1-3.md — workcell-skeleton prompt declaring this sub-level, its evidence-to-return shape, and human gates.

Worked case

Hypothetical case — no campaign run has declared L1.3 yet; this shows what would pass or fail.

Field Value
Repo forge-dark-factory PoC (hypothetical sandbox fixture)
Goal Fix two independent functions (add and subtract) in one run, each with its own apply+verify
Evidence produced Pattern: runs/campaigns/<campaign>/<item>/run-*/machine/plan.json with unit_count: 2 and per-unit proof
Assay pass rationale L1.3 _check_sublevel: unit_count >= 2 — each function unit individually verified in sequence
Assay fail example Single-function plan (unit_count: 1) → L1.3 evidence: need >=2 function units, got 1