Core Board Library - Senior Full-Stack Developer

Please Review the attached scope & milestone agreement if interest please send any questions. Thanks. PROJECT CORE — LIBRARY & BOARD Operational System of Record, Operational Visibility Surface & Policy-Driven Execution Engine — Scope v1.2 (Finalized, code-verified; Programs/PDEE layered in) System: HotelHub / OperationsHub Framework: PHP CodeIgniter 3.x (Existing Monolith) Scope Type: Core Platform / Spine Completion Dependencies • Foundations Hierarchy Architecture (hotel context, identity, permissions, isolation, time zone) • Agenda Architecture (execution surface) • Template Builder Lifecycle (draft / review / publish) • Shared Operational Object Model Doctrine • Existing AI Intelligence Layer (advisory only) 1. PURPOSE & ARCHITECTURAL POSITION Library and Board complete the operational spine of HotelHub: Library → Agenda → Board. Library is the operational system of record. Agenda is the execution surface. Board is the operational visibility and exception surface. These are not standalone modules and may not be built as such. They are connected surfaces over a single shared operational object model. An operational object must flow Library → Agenda → Board carrying the same identity, lifecycle state, targeting, permissions, tenant scope, and immutable audit history at every stage. This scope completes that spine while preserving the platform’s existing governance, lifecycle, isolation, and execution-boundary doctrine. 2. SHARED OPERATIONAL OBJECT MODEL (FOUNDATION — NON- NEGOTIABLE) Library and Board MUST be built on a single shared operational object model. This model is the connective tissue of the platform and must be defined once and reused by Library, Agenda, and Board. It may not be re-implemented per surface. Every operational object must carry, as shared attributes: • stable object identity (UUID + human-readable reference ID) • object type (SOP, checklist, inspection, PM workflow, log, recurring Program, directive, reference object, one-time / recurring task) • lifecycle state (draft, in review, published, superseded, archived) • tenant scope (hotel_id / organization_id, enforced server-side) • targeting metadata (portfolio / property / department / role / position) • permissions and visibility rules • relationship links (parent-child, dependency, supersession, Program-linked, reference- linked) • immutable provenance and lineage (creator, modifier, approver, deployment authority, version history) • audit history Behavioral differences between object types must be expressed as overlays on this shared model, not as isolated systems with their own governance, recurrence, permission, audit, or lifecycle logic. 3. LIBRARY — OPERATIONAL SYSTEM OF RECORD Library is the single canonical home for all operational objects. It is not a passive document store and not a per-tool catchall; it is the system of record that every other surface reads from and writes into.