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. We designed the Company Operating System to serve as the unified logic for human interaction, management structure, and corporate governance across the company.

Rather than relying on subjective management styles, we use defined standards for how we hire, coordinate, and evaluate. Just as our manufacturing processes must obey the laws of physics, our 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, consult the Operating System (this Handbook).
Engineering and Process Queries: For questions concerning SMT Solder Reflow Profiles, Component Footprints, or IPC-A-610 Classifications, consult the Technical Engineering Repository.

Pro-Tip: When you are asking, “How do I securely solder this component?”, check the Tech Repo. When you are asking, “Who officially approves the $500,000 purchase of the new soldering machine?”, check the Operating System.

The Documentation Hierarchy

Not all corporate documents carry equal weight. True organizational alignment requires that we clearly distinguish between immutable principles, mandatory rules, and flexible guidelines so everyone knows exactly what is expected.

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 Practice.
Function: To guarantee baseline reproducibility and cross-departmental efficiency.
Compliance Language: Expressly uses the word “SHOULD”.
Enforcement: You should follow the SOP 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: Modify the template as necessary for your specific departmental context.

Language Standards (The Code)

Lexical precision prevents operational paralysis. When we write internal documentation, we use 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

As leaders, 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:

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

Pro-Tip: 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. Evaluate your system first.

Final Governance Checklist

Parameter	The Specification	The Control Authority
Governance Scope	People, Decisions, Coordination	CEO / HR
Technical Scope	Manufacturing, Hardware Engineering, Quality	CTO / COO
Mandatory Language	MUST / SHALL	The Document Owner
Waiver Limit	≤ 90 Days (Mandatory System Expiration)	The Document Owner
Conflict Resolution	The Written Handbook explicitly overrides all Verbal Orders	CEO
Change Approval	Major rewrite (CEO + Owner) / Minor edit (Owner)	The Document Owner
Enforcement Logic	Fix the System → Train → Coach → Discipline	HR / Direct Manager