# TrinityIDC Architecture Overview ## TrinityIDC Documentation Intelligence System Created By: Dale T. Anderson Created On: 2026-02-04 *** ## A metadata-driven, AI-ready, Data platform for Intelligent Automation TrinityIDC is an enterprise platform engineered around a simple but powerful principle: **Metadata is the foundation for clarity, governance, and automation.** The architecture is intentionally modular, governed, and semantically consistent. Every component—from schemas to frameworks to the user experience—is designed to work together as a unified system that evolves with the business. TrinityIDC is not a collection of applications.\ It is a metadata-driven automation ecosystem. *** ## Core architectural pillars TrinityIDC is built on five major architectural pillars. Each plays a distinct role, but all share a common metadata foundation. *** ### 1. iGNOSIS — The metadata intelligence engine iGNOSIS is the semantic core of the platform. It provides the meaning, structure, and governance that drive every other component. Key responsibilities: * Business Glossary (USL) * Data Dictionary (SOCS) * Ontologies and domain models * Workflow definitions * Business rules * Mappings and transformations * Semantic relationships * Governance metadata (AMML, Integrity Levels) Why it matters:\ iGNOSIS ensures that TrinityIDC is explainable, governed, consistent, and self-documenting. It is the “brain” of the platform. *** ### 2. TCMS — Tenant & Customer Management System TCMS manages the organizational and operational boundaries of the platform. Key responsibilities: * Tenants and accounts * Subscriptions and licensing * Roles and permissions * User identity and access * Module entitlements * Device and environment associations Why it matters:\ TCMS ensures that every user, module, and device operates within the correct governance and licensing context. *** ### 3. TIDC — The operational layer TIDC is the system-level operational backbone that connects metadata to execution. Key responsibilities: * Device registration * Module activation * Environment provisioning * System configuration * Operational metadata * Integration with cloud services Why it matters:\ TIDC is the bridge between semantic intent (iGNOSIS) and real-world execution (modules, workflows, devices). *** ### 4. UAMF & UMMF — The application & module frameworks These frameworks define how applications and modules are built, registered, and executed inside TrinityIDC. UAMF provides: * Standardized module structure * UI/UX patterns * Navigation and layout rules * Event and action patterns UMMF provides: * Module registration * Module lifecycle management * Integration points * Governance enforcement Why they matter:\ UAMF and UMMF ensure that every module behaves consistently, regardless of who builds it or what it does. *** ### 5. TrinityIDC PORTAL — The unified user experience The PORTAL is the front-end experience that brings the entire platform together. Key responsibilities: * Role-based navigation * Module access * Data exploration * Workflow execution * Governance visibility * Administrative controls Why it matters:\ The PORTAL is where users interact with the metadata, automation, and governance that TrinityIDC provides. *** ## How the architecture works together The TrinityIDC architecture is intentionally layered and recursive. Each layer depends on the metadata and governance of the layer beneath it. From bottom to top: * iGNOSIS Layer: Defines meaning through glossary, dictionary, ontology, workflows, rules, mappings, and governance metadata. * TCMS Layer: Defines boundaries through tenants, accounts, licensing, roles, and permissions. * TIDC Layer: Defines operational context through devices, environments, configurations, and system-level metadata. * UAMF / UMMF Framework Layer: Defines module behavior through structure, UI patterns, integration points, and lifecycle. * TrinityIDC PORTAL: Delivers the experience through role-based access, navigation, workflows, and governance visibility. The flow of intelligence: 1. iGNOSIS defines meaning. 2. TCMS defines boundaries. 3. TIDC defines operational context. 4. UAMF/UMMF define module behavior. 5. PORTAL delivers the experience. This creates a closed-loop, governed automation system where every action can be traced back to metadata and governance decisions. *** ## Automation Maturity Model (AMML) integration TrinityIDC is designed to support all AMML levels (0–6). Each level builds on the metadata and governance of the previous one. AMML0: Foundational reference data (for example, REF.SYSTEM\_CALENDAR).\ AMML1–3: Structured metadata, workflows, rules, and mappings.\ AMML4–6: Advanced automation, optimization, and intelligence. The architecture ensures that as organizations mature, the platform matures with them. *** ## Why the architecture works The TrinityIDC architecture is effective because it is: * Metadata-driven: Meaning is defined once and reused everywhere. * Governed: Every component respects AMML, Integrity Levels, and USL/SOCS metadata. * Modular: Components evolve independently but remain semantically aligned. * Explainable: Every workflow, rule, and module can be traced back to metadata. * Future-proof: New modules, schemas, and workflows can be added without breaking the system. *** ## The role of TDIS in the architecture The TrinityIDC Documentation Intelligence System (TDIS) sits alongside the architecture as a meta-layer. TDIS provides: * Automated documentation generation * Schema-driven data dictionaries * Glossary and ontology extraction * Workflow and rule documentation * Developer and user guides * Governance alignment * Multi-audience content generation TDIS ensures that the architecture is not only powerful, but also understandable, searchable, governed, consistent, and always up-to-date. It is the documentation engine that completes the TrinityIDC ecosystem.