eduKate Singapore

How to Categorise Rules | Authority, Scope, Condition, Obligation, Exception and Enforcement

A rule is an explicit constraint or instruction that links conditions to permitted, required or prohibited behaviour.

Law, school policy, software validation, safety procedure, business logic, game rules and laboratory protocols all use rules, but they differ in authority, scope, jurisdiction, enforceability, exception structure and consequence.

Quick answer: how should rules be categorised?

  • Authority: who issued the rule?
  • Scope: who or what does it apply to?
  • Condition: when does it activate?
  • Modality: required, permitted, prohibited, recommended?
  • Exception: what cases override it?
  • Priority: what happens when rules conflict?
  • Enforcement: how is compliance checked?
  • Consequence: what follows from violation?
  • Jurisdiction: where and under which system is it valid?
  • Lifecycle: draft, active, superseded, withdrawn?

This article complements How Rule-Based Classification Works: that page explains how rules classify cases, while this page explains how rules themselves can be classified and governed.

1. Separate rule from goal

A goal describes a desired future state. A rule constrains or directs behaviour.

2. Separate rule from procedure

A procedure gives a sequence of steps; a rule may apply at one or many steps.

3. Separate rule from standard

A standard may define accepted criteria or specifications, while a rule determines what must, may or must not happen.

4. Authority is foundational

Law, regulator, employer, teacher, software owner and community each derive authority differently.

5. Formal rules differ from informal norms

Written policies and statutes are not the same as social expectations, even when both influence behaviour.

6. Mandatory rules impose obligations

They specify what must be done under defined conditions.

7. Prohibitory rules forbid actions

They define actions or states that are not permitted.

8. Permissive rules create allowed space

They state what may be done without requiring it.

9. Advisory rules recommend rather than compel

Guidelines can influence decisions without carrying the same enforcement as mandatory rules.

10. Default rules apply unless overridden

Defaults reduce repeated decisions while allowing exceptions where justified.

11. Exception rules narrow general rules

An exception should name the conditions under which the broader rule does not apply.

12. Too many exceptions indicate structural trouble

A heavily patched rule may be too broad, outdated or based on the wrong category boundary.

13. Scope must be explicit

Rules may apply to one person, one role, one organisation, one jurisdiction or one technical subsystem.

14. Temporal scope matters

Some rules apply only during emergencies, school terms, maintenance windows or specific historical periods.

15. Condition is part of rule identity

“Always wear protection” differs from “wear protection when operating this machine”.

16. Threshold rules need exact boundaries

Greater-than, at-least and within-range conditions must be represented precisely.

17. Compound rules combine conditions

AND, OR and NOT logic should be visible rather than buried in prose.

18. Priority resolves conflicts

Specificity, authority level, recency and explicit precedence can determine which rule wins.

19. Higher authority does not always mean newer

Conflict resolution should define the ordering rather than relying on assumption.

20. Jurisdiction controls validity

A legal or administrative rule can be binding in one place and irrelevant in another.

21. Role-based rules depend on relationship

The same person may be subject to different rules as employee, parent, customer or regulator.

22. Enforcement is separate from existence

A rule can exist formally while being weakly monitored or inconsistently enforced.

23. Preventive enforcement blocks violations

Software permissions and physical interlocks can prevent prohibited actions before they occur.

24. Detective enforcement identifies violations

Audits, sensors and reviews detect non-compliance after or during action.

25. Corrective enforcement restores compliance

Remediation, rework and rollback attempt to repair the state after breach.

26. Consequences should be typed

Warning, rejection, penalty, escalation, invalidation and termination are different outcomes.

27. Consequence severity should match authority

Rules should not imply powers the issuer does not actually hold.

28. Rules need provenance

Record issuer, source document, approval route and effective date.

29. Rules need versions

Historical decisions should be traceable to the rule version that was active at the time.

30. Superseded rules should remain retrievable

Retirement should not erase the history required to explain past actions.

31. Emergency rules need expiry

Temporary authority should not silently become permanent through neglect.

32. Rules should be testable

Positive, negative, boundary, exception and conflict cases reveal ambiguity.

33. AI can extract candidate rules

Models can identify obligations, prohibitions and conditions from text, but authority and legal meaning require source-aware validation.

34. Natural-language rules can hide ambiguity

Terms such as reasonable, promptly and significant may require domain definitions or human judgement.

35. Machine-executable rules need explicit semantics

Variables, operators, priorities and error states should be represented directly.

36. Rule taxonomies drift

New technology, law and organisational structure can create rule types that old schemes do not cover.

37. A practical rule record

  • rule ID;
  • authority;
  • scope;
  • jurisdiction;
  • condition;
  • modality;
  • required or prohibited action;
  • exceptions;
  • priority;
  • enforcement;
  • consequence;
  • source;
  • effective date;
  • expiry or review date;
  • version.

38. Rule categories should improve compliance and reasoning

A useful classification tells people which authority applies, what must happen and how conflicts are resolved.

39. Rules are structured commitments

They connect authority, conditions and consequences into an operational promise.

40. The deeper idea

A rule becomes trustworthy when another person can tell exactly when it applies, what it requires and what outranks it.

To categorise a rule well is to preserve authority, condition, obligation, exception and consequence in one auditable structure.

Final answer

Categorise rules by authority, scope, condition, modality, exception, priority, enforcement, consequence, jurisdiction and lifecycle. Keep rule separate from goal, procedure and standard, and version consequential rules so past and current decisions remain explainable.

Continue through the series

Explore the connected learning guides

Choose the question that brought you here. Open one useful guide, try a small task, and stop when you have what you need.

Take one question further

The same learning habit can travel across subjects, while each subject keeps its own methods. These routes help you notice a difficulty, understand one part of it, and return to something you can do.

A word is familiar, but using it is difficult.

Move from recognising a word to retrieving it in a new context. Understand vocabulary plateaus.

Try it without the guide: Choose one word you already know. Close the guide and use it in a new sentence. Explain why it fits; try another context tomorrow.

A piece of writing has ideas, but the reader loses the thread.

Make the order of events and the links between sentences clear. Explore composition writing.

Try it without the guide: Choose one short paragraph. Read the relevant explanation, close it, and revise the paragraph. Ask someone to tell you what happened and why.

The Mathematics seems familiar, but marks still disappear.

Find the first point where the working stops being reliable. Find Secondary 4 A-Math mark leakage.

Try it without the guide: For a Secondary 4 A-Math question you have attempted, locate the first uncertain line. Repair that step, then try a comparable question without the worked answer.

A Science fact is remembered, but the explanation is incomplete.

Connect the evidence to a scientific idea and the resulting change. Follow the Primary Science learning route.

Try it without the guide: Choose a familiar Primary Science example. Explain the evidence, the idea and the result without notes. Then change one condition and explain your prediction.

Two accounts of the world seem to disagree.

Check the question, source, date and evidence before combining claims. Explore the World Knowledge research library.

Try it without the guide: Take one claim. Find the source best placed to support it, note its date, and state what remains uncertain. Return to your original question.

There is plenty of help, but independence is hard to see.

Check what the learner can understand and do after support is removed. Understand how education works.

Try it without the guide: Choose one small task the child has practised. Agree on a calm, brief attempt without prompts. Use what happens to choose one next step, then stop.

For the structure behind these connections, read the eduKateSingapore runtime manifest and the eduKate ecosystem boot contract. The reader map describes public navigation; those manifests preserve the wider ownership and return rules.