Moustachir
IT ProtocolsCore Protocols

General IT Protocol

Foundational guide for all Engineering, Design, and Product operations at Moustachir Com

1. INTRODUCTION & PURPOSE

This document serves as the foundational guide for all Engineering, Design, and Product operations at Moustachir Com. It defines the shared standards, tools, and governance principles that apply to every individual contributing to our technical ecosystem, whether they are internal employees, freelancers, or external partners.

Moustachir Com is the service arm of the Moustachir Platform, providing clients with specialized assistance in IT solutions, Branding, Community Management, Web/Mobile Development, Audits, SEO, and Content Creation.

1.1 Governance & Validation

This protocol is a living document that ensures operational excellence.

  • Validation Authority: This document and its subsidiary protocols is validated by the IT Director and the Operations Director.
  • Compliance: Adherence to these standards is mandatory for all members of the technical team in Moustachir Com.

2. OPERATIONAL TOOLS & ECOSYSTEM

To maintain a cohesive workflow, we utilize a specific stack of tools. Usage of these tools as described below is non-negotiable.

2.1 Project & Task Management: Notion

Notion is our single source of truth for project structure and task tracking.

  • Structure: The hierarchy of Teams, Projects, and Sprints is defined here.
  • Tasks: All work items must be represented as cards in Notion.
    • Dynamic Nature: Task lists are dynamic and specific to each project.
    • Updates: Every contributor is responsible for keeping their task status up-to-date in real-time.

2.2 Communication: Discord

Discord is our virtual office.

  • Channels: Communication is organized by project and team channels to keep discussions focused.
  • Availability: Contributors are expected to be active and responsive during their agreed working hours.
  • Commercial Team Interface:
    • Direct communication between the Technical Team and the Commercial Team is restricted.
    • Point of Contact: All exchanges with the Commercial Team must go through the IT Projects Manager. This ensures clear requirements gathering and prevents scope creep.

2.3 Design: Figma

Figma is our design workshop.

  • Workspace: All design work occurs within the private Moustachir Figma workspace.
  • Templates: We use a centralized Design System and templates to ensure brand consistency and speed up project initiation.

2.4 Development: GitHub

GitHub is our code vault.

  • Organizations: Code is hosted in private repositories within the Moustachir GitHub Organization.
  • Submodules: We utilize a submodule architecture to share core libraries and utilities across projects, ensuring code reusability and maintainability.

3. PROJECT CLASSIFICATION

Understanding the nature of the project is crucial for applying the right workflow.

3.1 Internal Projects

  • Definition: Strategic platforms and tools owned and operated by Moustachir (e.g., The Moustachir Platform itself).
  • Focus: Long-term scalability, technical debt management, and continuous improvement.

3.2 Client Services Projects

  • Definition: Projects delivered to external clients (e.g., a custom website for a brand, a mobile app for a startup).
  • Focus: Delivery speed, adherence to client specifications, and milestone completion.

4. AI USAGE POLICY

Moustachir Com embraces innovation while valuing human expertise.

  • Assistance, Not Replacement: We encourage the use of AI tools (e.g., GitHub Copilot, ChatGPT, Midjourney) to accelerate workflows, generate boilerplate code, or brainstorm design ideas.
  • Human Responsibility: AI is a tool, not a team member. You are fully responsible for the output. Code generated by AI must be reviewed, tested, and understood. Design concepts from AI must be refined to meet professional standards.
  • Prohibition: It is strictly forbidden to use AI to replace core roles or to submit raw, unverified AI output as final work.

5. SECURITY & COMPLIANCE

  • Data Privacy: Client data is sacred. Never store sensitive client data on personal drives or share it on unauthorized channels.
  • NDA: All contributors must sign a Non-Disclosure Agreement.
  • Access Control: Access to repositories and workspaces is granted on a need-to-know basis and revoked immediately upon project completion or contract termination.

6. ROLE-SPECIFIC PROTOCOLS

For detailed workflows, methodologies, and onboarding checklists specific to your role, refer to the following documents:

Moustachir Documentation Hub

Centralized documentation platform for Moustachir SPA - protocols, guidelines, and technical resources

Internal IT Protocol

Specialized operational guide for Internal Product Teams at Moustachir Com

Table of contents

1. INTRODUCTION & PURPOSE1.1 Governance & Validation2. OPERATIONAL TOOLS & ECOSYSTEM2.1 Project & Task Management: Notion2.2 Communication: Discord2.3 Design: Figma2.4 Development: GitHub3. PROJECT CLASSIFICATION3.1 Internal Projects3.2 Client Services Projects4. AI USAGE POLICY5. SECURITY & COMPLIANCE6. ROLE-SPECIFIC PROTOCOLS