Principlev1

Define roles with explicit authority domains, accountability

Define roles with explicit authority domains, accountability metrics, information requirements, and operational constraints to prevent boundary ambiguity.

Why This Is a Principle

Derives from Goals as Perceptual Filters (goals as perceptual filters define relevance), Schemas as Knowledge Organization Structures (schemas organize knowledge relationships), and Signal detection involves independent dimensions of (signal detection has independent sensitivity/specificity). This is role design principle following from how cognition uses structure to determine relevance and action.

Source Lessons

L-1690

Role-based authority

Authority flows from roles, not from hierarchy — anyone in a role has the authority that role requires. In traditional organizations, authority is personal — it belongs to the individual who holds a position in the hierarchy. A manager has authority because they are a manager, and they carry that authority across all the domains their position encompasses. In role-based authority, authority is functional — it belongs to the role, not the person. A person exercises authority when they are acting within a role they hold, and they hold no authority outside that role. This separation of person from role enables distributed authority: one person can hold multiple roles (and exercise different authorities in each), and authority can be reassigned by reassigning the role rather than reorganizing the hierarchy.

Connections

Derived From (3)

AxiomGoals as Perceptual Filters AxiomSchemas as Knowledge Organization Structures AxiomSignal detection involves independent dimensions of

Back to Concepts