Room 05 · Framework

Luncheon vs Acteon

Place in the record

A distinction between systems optimized for continuity and systems that produce consequence.

Framework

Luncheon vs Acteon

I use the distinction luncheon vs acteon to separate systems optimized for continuity
from systems optimized for consequence. Luncheon systems gather, teach, service,
and repeat. Acteon systems decide, exclude, commit, and close.

Luncheon systems feel productive because they generate motion without risk.
Acteon systems feel uncomfortable because they generate outcomes that cannot
be undone.

Most institutions today are luncheon systems mistaken for engines of action.
This confusion sustains legitimacy while avoiding responsibility.

Continue through the record

Previous · FrameworkFunctional Role MappingNext · FrameworkConcentric Systems