Ceremonial Law vs Law of Necessity: Rules, Exceptions and Practical Applications in Modern Industry

Imagine a factory where a critical production machine develops a dangerous electrical fault.

The operator notices smoke coming from the control panel. There is an immediate risk of fire, equipment damage and injury to workers.

The organization's standard operating procedure requires the operator to report the problem, obtain authorization from the supervisor, submit a maintenance request and wait for an approved technician.

However, the supervisor is unavailable.

Should the operator wait for authorization while the machine continues overheating?

Or should the operator immediately activate the emergency stop, isolate the equipment using the approved emergency isolation procedure and alert the emergency response team?

Now consider another situation.

A production server belonging to an organization becomes compromised. It starts sending thousands of unsolicited emails, consuming resources and damaging the organization's IP reputation.

The ICT administrator identifies the incident and requests permission from the ICT manager to restrict the malicious traffic.

The manager does not respond.

Should the administrator wait for approval while the compromised server continues causing damage?

These situations introduce an important philosophical, legal and operational question:

Is strict adherence to established procedures always the right decision, or can circumstances make immediate action more important than following ordinary formal requirements?

This discussion connects two different concepts: Ceremonial Law and the Law of Necessity.

Although they originate from different contexts, examining them together provides an opportunity to understand the relationship between established rules, their underlying purposes, exceptions, human judgment and practical responsibility.

The objective is not to encourage lawlessness or disregard for organizational policies. It is to understand when rules serve their intended purpose and when rigid application of procedures may undermine the very interests those procedures were designed to protect.

1. Understanding Ceremonial Law

Ceremonial Law traditionally refers to the religious and ritual requirements given to the Israelites through Moses in the Old Testament.

These provisions governed the religious worship and ceremonial life of ancient Israel.

They included:

• Sacrifices and offerings.
• Priestly duties.
• Religious festivals.
• Purification requirements.
• Dietary restrictions.
• Circumcision.
• Regulations concerning ritual cleanliness.
• Prescribed forms of worship.

In Christian theological interpretation, the ceremonial law is commonly distinguished from moral and civil or judicial laws.

The distinction is important because ceremonial laws were associated with prescribed religious practices, while moral laws concern principles of right and wrong.

For example, the requirement to observe a particular sacrificial procedure was ceremonial, whereas prohibitions against murder and theft concern moral conduct.

In many Christian traditions, ceremonial requirements are understood to have been fulfilled through Jesus Christ, although theological interpretations differ among denominations.

The purpose of ceremonial requirements

Ceremonial laws were not necessarily meaningless formalities.

They served particular purposes:

1. Maintaining religious identity.
2. Establishing an organized system of worship.
3. Defining religious responsibilities.
4. Promoting discipline and order.
5. Communicating spiritual principles through prescribed practices.

The important lesson is that a rule may have a purpose beyond the physical action it requires.

A prescribed procedure should be understood in relation to the objective it is intended to achieve.

This becomes particularly relevant when examining modern institutional procedures.

Note: In industrial management, the term ceremonial law should not be used as a synonym for standard operating procedures. Industrial procedures have their own legal, technical and safety foundations.

2. Understanding the Law of Necessity

The Law of Necessity, more commonly discussed in jurisprudence as the doctrine or principle of necessity, concerns exceptional circumstances in which an otherwise prohibited action may be legally justified or excused to prevent a greater harm.

The principle recognizes that emergencies sometimes create situations where ordinary requirements cannot reasonably be followed.

Examples include:

• Breaking into a locked building to rescue someone from a fire.
• Taking emergency action to prevent an immediate threat to human life.
• Isolating a compromised production server to stop an ongoing cyberattack.
• Activating emergency shutdown procedures when industrial equipment presents an immediate danger.
• Taking reasonable emergency measures to protect essential public services.

Two Latin maxims are frequently associated with the philosophical discussion of necessity.

Necessitas non habet legem.

Meaning: Necessity knows no law.

Salus populi suprema lex esto.

Meaning: The welfare of the people shall be the supreme law.

These expressions emphasize that preserving life and protecting society are fundamental objectives.

However, they should not be interpreted as unlimited permission to disregard applicable law.

The doctrine of necessity has specific legal requirements, and its application depends on the jurisdiction and circumstances.

The central idea

The Law of Necessity asks whether strict compliance with an ordinary requirement would create or permit a greater harm than a reasonable emergency intervention.

It introduces the importance of:

• Immediacy.
• Proportionality.
• Reasonableness.
• Absence of reasonable alternatives.
• Prevention of greater harm.
• Accountability.

3. Comparing Ceremonial Law and the Law of Necessity

Although these concepts have different origins, they provide an interesting comparison concerning prescribed requirements and exceptional circumstances.

An important qualification is that ceremonial law does not simply mean bureaucracy, and necessity does not automatically cancel established rules.

The useful comparison is philosophical: the relationship between prescribed requirements and the purpose behind them.

4. The Greater Question: Is the Purpose of a Rule More Important Than Its Procedure?

Consider an organization that requires three management signatures before any critical system modification.

The policy exists to prevent unauthorized changes and protect production infrastructure.

Under normal circumstances, this is a reasonable governance measure.

But suppose a server is actively distributing malware.

The administrator has identified the source of the malicious activity and knows that blocking a specific outbound connection will contain the immediate threat.

The three required approvers are unavailable.

Would waiting for all three signatures protect the organization?

Or would it expose the organization and its customers to avoidable damage?

This raises an important distinction between:

The purpose of a rule: What is the rule intended to protect?

The procedure of a rule: What steps must be followed to comply?

A mature organization should ensure that its procedures support the intended protection.

Where an emergency exists, the organization should have a mechanism for proportionate emergency action.

The purpose of authorization is not to delay the protection of organizational assets. It is to ensure that changes are controlled, justified and accountable.

5. Practical Applications in Industrial Operations

Industrial environments provide some of the clearest examples of the relationship between established procedures and emergency necessity.

Manufacturing facilities, power plants, processing factories, construction sites and logistics operations depend on standardized procedures.

These procedures protect employees, equipment, products and the surrounding environment.

However, industrial operations also face unexpected events.

A. Manufacturing and production machinery

Consider a production machine operating at high temperature.

An operator notices that the cooling system has failed.

The normal maintenance procedure requires:

1. Reporting the fault.
2. Opening a maintenance ticket.
3. Obtaining supervisor approval.
4. Waiting for a qualified technician.
5. Scheduling maintenance.

However, the machine continues overheating.

A reasonable emergency response may require the operator to activate the emergency stop and notify the responsible engineering team immediately.

The operator should not attempt dangerous electrical repairs outside their competence.

The distinction is between emergency shutdown, which may be an established safety action, and unauthorized maintenance intervention.

Industrial lesson: Emergency protection must not be delayed by routine maintenance authorization.

B. Electrical engineering

Electrical installations require strict isolation and safety procedures.

Suppose an electrical distribution panel begins sparking and presents an immediate fire or electrocution risk.

An employee should raise the alarm, keep people away and use the designated emergency isolation mechanism if trained and safe to do so.

They should not wait for an ordinary maintenance approval before initiating the site's emergency response.

However, the principle of necessity does not authorize an unqualified employee to open energized electrical equipment or perform dangerous repairs.

Industrial lesson: Immediate hazard control and technical repair are two different responsibilities.

C. Chemical and processing industries

Chemical plants operate with potentially dangerous materials.

A leak may create risks of poisoning, fire, explosion or environmental contamination.

The emergency response may require:

• Activating alarms.
• Evacuating affected areas.
• Isolating the relevant process through approved emergency controls.
• Contacting emergency response personnel.
• Implementing containment measures.
• Notifying relevant authorities where required.

Waiting for routine administrative approval during an escalating chemical emergency may expose workers and surrounding communities to serious harm.

Nevertheless, chemical isolation and shutdown decisions must follow process-safety engineering requirements.

D. Construction industry

Construction sites have formal procedures governing permits, equipment use, excavation and working at height.

Suppose a worker notices that a scaffold is unstable.

The normal procedure may require reporting the issue to the site supervisor and waiting for inspection.

But workers should immediately stop using the unsafe scaffold, warn others and prevent access according to site safety procedures.

The danger should be addressed before work resumes.

Industrial lesson: Safety controls exist to prevent accidents, not merely to satisfy documentation requirements.

6. Practical Applications in Information Technology and Cybersecurity

Modern organizations increasingly depend on digital infrastructure.

Banking systems, hospitals, universities, government agencies, manufacturing facilities and telecommunications companies rely on production servers and interconnected networks.

A cybersecurity incident can rapidly affect the availability, integrity and confidentiality of these systems.

This makes the doctrine of necessity particularly interesting when examining emergency ICT administration.

Case study: Compromised production servers sending spam

Imagine an organization operating several production servers.

An ICT administrator discovers:

• Unusual outbound SMTP traffic.
• Thousands of unsolicited emails.
• Suspicious processes.
• Unexpected network connections.
• Potentially compromised user accounts.
• Deteriorating IP reputation.

The administrator investigates and confirms that one production server is compromised.

They submit an emergency request to the ICT manager.

However, authorization is delayed.

Meanwhile, the server continues sending spam.

The administrator now faces a difficult operational decision.

Option A: Wait for authorization.

The incident continues, potentially resulting in:

• IP blacklisting.
• Email service disruption.
• Additional compromise.
• Customer complaints.
• Reputational damage.
• Financial losses.

Option B: Take immediate containment action within delegated emergency authority.

The administrator may:

• Restrict unauthorized outbound SMTP traffic.
• Isolate the confirmed compromised workload.
• Disable compromised accounts.
• Revoke exposed credentials.
• Preserve relevant logs.
• Notify management and the incident-response team.

The objective is to contain the threat while minimizing disruption to legitimate services.

Why immediate containment matters

Cyberattacks do not operate according to organizational office hours.

Malware can operate at night, during weekends and public holidays.

An attacker does not need managerial approval before exploiting a vulnerability.

Consequently, organizations must establish emergency-response authority that allows appropriately trained personnel to contain incidents.

However, necessity is not a blanket permission to delete databases, shut down all production systems or make irreversible changes.

The response must be proportionate, documented and within the applicable emergency authority.

7. Practical Applications in Healthcare

Healthcare environments provide another important example.

Imagine a hospital emergency department receives a critically injured patient.

The hospital has standard admission procedures, documentation requirements and payment processes.

However, delaying urgent life-saving treatment solely because routine administrative formalities have not been completed could create serious ethical and legal problems.

Emergency treatment should be governed by applicable clinical standards, professional duties and patient-care laws.

Similarly, when hospital systems are affected by ransomware, IT personnel must work with clinical leadership to preserve patient safety and essential medical services.

The response may involve:

• Isolating compromised systems.
• Activating downtime procedures.
• Using approved alternative patient-record processes.
• Protecting critical medical devices.
• Maintaining emergency communication.
• Restoring systems safely.

In this environment, cybersecurity decisions cannot be separated from patient safety.

A security intervention that unnecessarily disables a life-support monitoring system may introduce a new danger.

Lesson: Necessity must consider the total consequences of an action, not just the immediate problem being addressed.

8. Practical Applications in Corporate Governance and Management

Organizations establish policies to promote consistency, transparency and accountability.

Common requirements include:

• Procurement approval.
• Financial authorization.
• Access control.
• Change management.
• Contract approval.
• Asset management.
• Employee disciplinary procedures.

These requirements are essential.

However, management systems must account for exceptional situations.

Consider a company whose payment processing system becomes compromised.

The finance department requires approval from the finance manager before restricting payments.

The finance manager is unavailable.

If fraudulent transactions are actively occurring, the organization needs a predefined emergency mechanism to suspend the affected transaction channel or payment credentials.

The organization should not depend entirely on the availability of one individual.

A good governance framework provides:

1. Delegated emergency authority.
2. Alternative approvers.
3. Defined escalation paths.
4. Pre-approved emergency actions.
5. Mandatory documentation.
6. Retrospective management review.

This is how organizations reconcile procedural control with practical necessity.

9. The Legal Perspective: Is Necessity Above the Law?

This is one of the most important questions in the discussion.

The answer is no.

The doctrine of necessity does not automatically place an individual or institution above the law.

In a constitutional democracy, the Constitution remains supreme.

The Kenyan constitutional position

Article 2(1) of the Constitution of Kenya, 2010, establishes the supremacy of the Constitution.

It binds all persons and State organs.

Therefore, an individual cannot simply invoke necessity to disregard constitutional requirements.

Article 24 also establishes the framework for limitations of constitutional rights.

Any limitation must satisfy the applicable constitutional requirements.

The Kenyan Supreme Court and the Doctrine of Necessity

An important Kenyan illustration is:

Jasbir Singh Rai & 3 Others v Tarlochan Singh Rai & 4 Others, Petition (Application) No. 4 of 2012 [2013] eKLR.

The Supreme Court considered the doctrine of necessity in relation to judicial recusal and the Court's ability to perform its constitutional functions.

The issue involved whether the Court could continue performing its duties despite circumstances that could otherwise result in judicial recusals and a lack of quorum.

The discussion illustrates that necessity can be relevant in preserving the functioning of an essential constitutional institution.

However, the doctrine is not a general licence to disregard the Constitution.

The case is particularly useful when discussing institutional continuity and exceptional circumstances.

Other relevant Kenyan legislation

Organizations should also consider:

• Computer Misuse and Cybercrimes Act, 2018.
• Data Protection Act, 2019.
• Occupational Safety and Health Act, 2007.
• Applicable environmental and industry-specific regulations.

These laws create obligations that must be considered when responding to emergencies.

For example, a cybersecurity incident involving personal data may trigger obligations under the Data Protection Act.

Emergency containment does not eliminate the need for subsequent legal compliance.

10. The Industrial Balance: Standard Operating Procedures vs Emergency Procedures

One of the most important lessons for modern industry is that normal operating procedures and emergency operating procedures should not be confused.

A normal operating procedure governs routine activities.

An emergency operating procedure governs abnormal conditions that require immediate protective action.

For example:

The emergency approach should not mean abandoning safety controls.

Instead, it should activate a different, predefined set of controls designed for abnormal conditions.

11. The Importance of Proportionality

Necessity is not simply about acting quickly.

It is also about choosing the right action.

An emergency response must be proportionate to the threat.

Consider a production server sending unauthorized emails.

Possible responses include:

1. Blocking the malicious outbound SMTP connection.
2. Disabling the compromised email account.
3. Isolating the affected workload.
4. Taking the entire server offline.
5. Shutting down the organization's entire network.

These actions have different operational consequences.

The best response is generally the least disruptive measure that can effectively control the threat, provided it does not leave the organization exposed to unacceptable risk.

The same principle applies in industrial environments.

An overheating machine may require an emergency stop, but it does not automatically justify shutting down an entire factory.

A chemical leak may require isolating a process unit, but the response must be based on the facility's safety engineering.

The objective is to prevent greater harm without introducing unnecessary additional risks.

12. A Practical Framework for Organizations: The Necessity-Based Decision Model

Organizations can convert the philosophical principle into an operational decision-making framework.

The following model can be used in ICT departments, manufacturing facilities, hospitals and other critical operations.

Stage 1: Identify the threat

Establish what is happening.

Is there an actual emergency or merely an operational inconvenience?

Stage 2: Assess the severity

Determine the potential consequences.

Could the situation result in:

• Loss of life?
• Physical injury?
• Equipment damage?
• Data compromise?
• Financial losses?
• Service disruption?
• Environmental damage?

Stage 3: Determine the urgency

Is the harm immediate, developing or hypothetical?

An active fire requires a different response from a routine maintenance observation.

Stage 4: Identify available authority

Check whether an emergency procedure or delegated authority already permits the proposed action.

Do not confuse an unavailable manager with the absence of all organizational authority.

Stage 5: Consider alternatives

Is there a less disruptive measure that can effectively address the danger?

Stage 6: Act proportionately

Take the necessary action within the applicable authority and professional competence.

Stage 7: Notify and document

Record the circumstances, decisions, actions and outcomes.

Stage 8: Review and restore

After the emergency, conduct an assessment, restore normal operations and identify improvements.

13. A Proposed Emergency Authority Matrix for Industrial Organizations

Organizations should define emergency authority before an incident occurs.

An example framework is provided below.

This matrix should be adapted to the organization's actual legal duties, technical risks and operational structure.

The most important principle is that personnel should understand their authority before an emergency develops.

14. Why Organizations Should Adopt Emergency Change Management

Traditional change management often requires a request, risk assessment, approval, implementation plan and review.

This process is appropriate for ordinary infrastructure changes.

However, emergency changes require an accelerated process.

A mature emergency change-management system should include:

Pre-authorization: Identify actions that trained personnel can execute without seeking fresh approval during a qualifying incident.

Emergency approval: Establish an alternative approval route when the primary decision-maker is unavailable.

Incident documentation: Record all changes, reasons, timestamps and affected systems.

Risk assessment: Evaluate operational consequences before implementing disruptive measures.

Retrospective review: Have emergency actions reviewed after the incident.

Continuous improvement: Update procedures based on lessons learned.

In industrial control environments, management of change is particularly important because changes to software, networks and control systems may affect physical processes and worker safety.

A cybersecurity response that is appropriate for an ordinary business server may be unsafe for an industrial control system.

15. The Danger of Blind Compliance and the Danger of Uncontrolled Discretion

There are two extremes that organizations should avoid.

Extreme A: Blind compliance

This occurs when employees follow procedures without considering the actual circumstances.

Examples include:

• Waiting for authorization while a fire spreads.
• Allowing a compromised server to continue sending spam.
• Continuing production despite a serious equipment hazard.
• Delaying emergency patient treatment over routine administrative formalities.

Blind compliance can turn a manageable problem into a disaster.

Extreme B: Uncontrolled discretion

This occurs when employees believe that any action is acceptable because they consider the situation urgent.

Examples include:

• Shutting down critical systems without assessing the impact.
• Deleting production databases without preserving evidence.
• Bypassing electrical safety isolation.
• Performing dangerous maintenance without qualifications.
• Making irreversible organizational changes without authority.

Uncontrolled discretion can create additional harm.

The correct approach: Responsible judgment

A mature professional should understand:

• The rule.
• The purpose of the rule.
• The risk of following it without adaptation.
• The risk of departing from it.
• The available emergency authority.
• The proportionality of the proposed action.
• The need for accountability.

This is the difference between responsible professional judgment and arbitrary decision-making.

16. Lessons for Industrial Leaders and ICT Managers

Organizations should not measure compliance solely by the number of approvals obtained.

They should also evaluate whether their procedures enable timely and safe decisions.

Management should ask:

1. Can an employee activate an emergency response without waiting for a manager?
2. Are emergency responsibilities documented?
3. Are alternative decision-makers available?
4. Can critical infrastructure be isolated safely?
5. Are emergency changes recorded?
6. Are staff trained to recognize emergencies?
7. Are incident-response exercises conducted?
8. Are emergency actions reviewed afterward?
9. Can essential operations continue during an incident?
10. Are organizational policies consistent with applicable laws?

An organization that cannot answer these questions may have an important governance gap.

The goal is not to eliminate authorization.

The goal is to make authorization responsive to the actual operational risk.

Conclusion: Rules Must Protect Their Purpose, Not Defeat It

Ceremonial Law and the Law of Necessity originate from different intellectual and legal traditions.

Ceremonial law illustrates the role of prescribed religious practices and formal observance.

The doctrine of necessity examines exceptional circumstances in which preventing greater harm may justify otherwise restricted conduct.

When these concepts are examined alongside modern industrial operations, they introduce an important lesson about the relationship between rules, responsibility and practical judgment.

Industrial organizations need procedures. Hospitals need protocols. ICT departments need change management. Financial institutions need authorization controls. Manufacturing facilities need safety standards.

These requirements are essential.

But procedures must also anticipate emergencies.

A machine operator should not wait for routine maintenance approval before activating a designated emergency stop when a serious hazard develops.

A hospital should not allow administrative formalities to obstruct urgent patient care.

An ICT administrator should not allow an active security incident to escalate unnecessarily when authorized emergency containment measures are available.

A production manager should not continue unsafe operations merely because the scheduled shutdown approval has not been received.

The purpose of a rule is to achieve a particular protection or objective. When circumstances change, responsible decision-making must ensure that the objective is not defeated by rigid application of the procedure.

However, necessity is not an unrestricted exemption from law, professional standards or organizational accountability.

The strongest organizations are those that combine established procedures with clearly defined emergency authority, professional competence, proportionality and transparent accountability.

Ultimately:

Rules establish order. Procedures establish consistency. Necessity addresses exceptional circumstances. Professional judgment connects all three.

The measure of a good governance system is not merely how well people follow procedures when everything is normal, but how safely, lawfully and effectively they respond when normal procedures are no longer adequate.

Frequently Asked Questions

1. What is the difference between Ceremonial Law and the Law of Necessity?

Ceremonial Law traditionally concerns religious rituals and prescribed worship practices, particularly those associated with the Mosaic Law. The Law of Necessity is a legal and jurisprudential principle concerning exceptional circumstances in which otherwise restricted actions may be justified to prevent greater harm.

2. Does the Law of Necessity mean that rules can be ignored?

No. Necessity is not unlimited permission to disregard laws or organizational procedures. Its application depends on the circumstances, applicable law, proportionality and the existence of reasonable alternatives.

3. Can an employee take emergency action without managerial approval?

This depends on the employee's delegated authority, the organization's emergency procedures and applicable law. Many organizations should pre-authorize certain emergency actions to prevent avoidable delays.

4. Should an ICT administrator wait for authorization when production servers are compromised?

An administrator should immediately escalate the incident and use established emergency containment authority. Where pre-authorized measures exist, such as restricting confirmed malicious outbound traffic, they should not be unnecessarily delayed. Major disruptive or irreversible actions require appropriate authorization and risk assessment.

5. Does the doctrine of necessity apply in industrial operations?

The principle may be relevant to legal and ethical analysis, but industrial operations should primarily rely on established emergency procedures, workplace safety requirements, engineering standards and applicable laws.

6. What is the relationship between necessity and proportionality?

Necessity concerns whether an action is required to prevent harm. Proportionality concerns whether the action is appropriate and does not create excessive additional harm.

7. Can necessity override the Constitution of Kenya?

No. The Constitution remains supreme under Article 2(1). The doctrine of necessity must be understood within the constitutional and legal framework.

8. What should organizations do to avoid emergency authorization delays?

Establish emergency change-management procedures, delegated authority, alternative approvers, escalation channels, pre-approved containment measures, staff training and retrospective reviews.

Editorial note: This article distinguishes the theological meaning of ceremonial law from the legal doctrine of necessity. It uses industrial and organizational emergency management as practical applications of the wider discussion, not as a claim that industrial standard operating procedures are themselves ceremonial laws.

Disclaimer: This article is for educational and general informational purposes. Legal outcomes depend on the relevant jurisdiction and facts. Organizations should obtain appropriate legal, engineering, safety and cybersecurity advice when developing emergency-response policies.

These sources strengthen the legal and industrial dimensions of the article:

1. Kenyan Supreme Court – Doctrine of Necessity: Jasbir Singh Rai case and Supreme Court publication.

2. NIST – Industrial Cybersecurity Incident Response and Recovery (2026): Responding to and Recovering from a Cyber Attack

3. Government of Canada – Industrial OT and IT Incident Response: Developing an Operational Technology and Information Technology Incident Response Plan.

4. SANS Institute – Industrial Control Systems Change Management: ICS Security and Management of Change.

5. The Energy Institute – Process Safety Management: Management of Change and Project Management.