The plan is not the permission.
Planning turns the request into bounded work that a person can inspect before implementation begins.
Authorization is represented separately and remains bound to the reviewed plan and observed baseline.
01 / 04
A complex request
A request becomes a plan.
Loom begins with the owner request and the observed project, then records the facts, assumptions, decisions, and proof the work will require.
Loom lifecycle
Three parts.
One flow.
A request moves through explicit records. Planning, authority, evidence, and recovery do not collapse into one optimistic status.
01 Plan and review
Loom records the request, project evidence, assumptions, work orders, and the proof required for completion.
02 Authority and proof
A separate boundary represents permission to implement. Validation then asks the declared medium to prove the outcome.
03 Recovery and completion
Failures preserve their cause and return to an explicit route. Completion closes only when authority and evidence still match.
Current status
Inspect the plan before the work begins.
Loom 1.8.30 is published with durable cross-turn plan decisions, structured review output, and exact work-order completion contracts.
View Loom on GitHub