1.1 Governance Standards: Scope, Hierarchy, and Control

In a growing organization, operational ambiguity creates friction. It slows down execution and introduces variation in how different teams make decisions. The Company Operating System is designed to serve as the unified logic for human interaction, management structure, and corporate governance across the company.

Rather than relying on subjective management styles, defined standards are used for hiring, coordination, and evaluation. Just as manufacturing processes must obey the laws of physics, organizational processes must obey structured logic.

System Scope & Authority

The Operating System governs the “Management Layer” (the procedural framework of the company). It does not govern the “Technical Layer” (the engineering physics of the product).

Scope Decision Logic:

• Administrative and Organizational Queries: For questions concerning Recruitment, Org Structure, Corporate Meetings, or Approval Authority limits, the Operating System (this Handbook) must be consulted.
• Engineering and Process Queries: For questions concerning SMT Reflow Soldering Profiles, Component Footprints, or IPC-A-610 Classifications, the Technical Engineering Repository must be consulted.

Engineering Practice

For questions regarding secure component soldering, the Tech Repo should be consulted. For questions regarding official approval of capital equipment purchases, the Operating System should be consulted.

The Documentation Hierarchy

Not all corporate documents carry equal weight. True organizational alignment requires a clear distinction between immutable principles, mandatory rules, and flexible guidelines to ensure predictable execution.

1. Principles (The Constitution)

• Status: Immutable.
• Function: Strategic vectors used to guide decisions in situations where no specific rule currently exists.
• Change Control: Board of Directors or CEO consensus only.

2. Policies (The Rules)

• Status: Mandatory.
• Function: Risk mitigation (Legal, Financial, and Life Safety).
• Compliance Language: Expressly uses the words “MUST” or “SHALL”.
• Enforcement: 100% compliance is required. Unauthorized deviation presents a serious violation.

3. SOPs (The Workflows)

• Status: Standard Operating Procedure.
• Function: To guarantee baseline reproducibility and cross-departmental efficiency.
• Compliance Language: Expressly uses the word “SHOULD”.
• Enforcement: The SOP should be followed unless a specific constraint logically forces a deviation.

4. Templates (The Tools)

• Status: Highly Recommended.
• Function: To reduce cognitive load for routine tasks and standardize output formats.
• Enforcement: Templates may be modified as necessary for specific departmental contexts.

Language Standards (The Code)

Lexical precision prevents operational paralysis. Internal documentation uses specific language to indicate the level of enforcement.

• MUST / SHALL = Mandatory. Failure to comply is a disciplinary event.
• SHOULD = Strongly Recommended. Any operational deviation requires a formally documented justification.
• MAY = Optional. Entirely left to the professional judgment of the manager or team member.

Ownership & Change Control

Static corporate documents naturally decay into operational risks. The Operating System is a dynamic, living entity, but all changes to it must be controlled to prevent organizational confusion.

The Ownership Matrix

• Corporate Strategy or Culture: Owned by the CEO.
• Talent, Compensation, or Org Structure: Owned by the HR Director.
• Factory Operations or Logistics: Owned by the COO.

The Single Source of Truth

• Written = Standard: Only the processes permanently documented in this Handbook are enforceable standards.
• Verbal = Suggestion: Hallway agreements, phone calls, or chat messages do not equal operational mandates.
• Conflict Resolution: When a Verbal Directive contradicts the Written Handbook, the Handbook prevails.

The Process Waiver Protocol

Excessive rigidity causes systems to fracture under stress. Controlled flexibility allows for organizational resilience.

• The Action: Submit a formal “Process Waiver Request” directly to the Policy Owner.
• The Constraint: Approved waivers MUST carry a clear Termination Date (Maximum 90 days).
• The Outcome: Upon expiration, the system must revoke the waiver, or the Owner must rewrite the standard to accommodate the new reality.

Enforcement & Diagnostic Logic

Punishing human error without investigation hides systemic process failures. Managers must respond to violations based on the root cause, not just the outcome.

Violation Diagnostic Sequence:

1. Check the System: When the written standard is objectively unclear, hidden, or contradictory, rewrite the Policy (Zero Penalty to the employee).
2. Check the Training: When the individual lacks the necessary training to succeed, train them immediately (Zero Penalty to the employee).
3. Check the Intent: When the standard and training are clear, but the violation is a genuine accident, coach and warn.
4. Execute Discipline: When the violation is deliberately repeated, initiate Corrective Action.

Best Practice

Process Correction > Person Correction. A corporate rule that is consistently broken across the company is almost always a badly designed rule—it is rarely a sign of bad employees. The system must be evaluated first.

---

Recap: Document Hierarchy and Control Authority

Document Type	Status	Compliance Language	Change Control Authority
Principles	Immutable	Strategic vectors (no specific keywords)	Board of Directors or CEO consensus only
Policies	Mandatory	MUST / SHALL	Policy Owner
SOPs (Standard Operating Procedures)	Standard Practice	SHOULD	Process Owner
Templates	Highly Recommended	MAY	Departmental modification allowed