AI Platform - Senior Full-Stack Systems Engineer

OPS STUDIO — OPERATIONAL CONVERSION & DEPLOYMENT ARCHITECTURE ADDENDUM v1.2 System:HotelHub / OperationsHub Operations Studio (Studio) AI-Powered Operational System Generation Scope v3.1 — Elite (Final) · HotelHub / OperationsHub · PHP CodeIgniter 3 Monolith 1. Objective Operations Studio is HotelHub’s AI-powered operational architect. It transforms plain-language operational intent into governed HotelHub operational objects — without requiring users to manually build templates, forms, or workflows. The user describes what they need. HotelHub generates the operational system: structured, versioned, numbered, governed, and ready for review. The experience should feel familiar to anyone who has used a conversational AI tool — type a request, watch the system build it on a live canvas — but produce real, governed HotelHub objects rather than free text. 2. Core Principle Users should never have to fit operational content into HotelHub. HotelHub fits the content into HotelHub automatically. AI accelerates creation; it never bypasses governance and never publishes on its own. 3. The Operationalization Principle (Foundational) This is the principle the entire system is built around, and it is non-negotiable: nothing is created into a void. Every object that enters the HotelHub ecosystem — whether generated by Studio, brought in through Import, or hand-built in Template Builder — must pass through the same conversion before it is considered complete: Operational Object Model (Foundational) Studio does not fundamentally generate SOPs, Tasks, Logs, Inspections, or Programs. Studio generates Operational Objects. Object types represent implementations of the Operational Object model. Current supported object types include SOPs, Tasks, Recurring Tasks, Inspections, Logs, Training Objects, and Programs. The architecture must remain extensible so future HotelHub modules can introduce additional Operational Object types without requiring Studio redesign. All Operational Objects pass through the same lifecycle: Draft → Verification → Approval → Operationalization → Destination Assignment → Library Publication. Object-specific behavior is determined by type, but governance remains universal.