Why Your Current Architecture Workflow is Broken

Video by FINOS via YouTube
Why Your Current Architecture Workflow is Broken

Eddie Knight (Open Source Maintainer & Developer Advocate at Revanite) opens with the cautionary tale of the 1904 Great Baltimore Fire to illustrate the severe operational risks of un-standardized systems. Eddie introduces CALMSuite (comprising CALM Studio and CALM Guard) and the Jamara Modelโ€”a 4-layer framework that layers compliance controls from the FINOS AI Governance Framework (AIGF) and Common Cloud Controls (CCC) directly onto machine-readable CALM architecture graphs via an intuitive drag-and-drop web interface.

๐Ÿ—ฝ Catch Us in New York! Ready to standardize architecture-as-code, automate compliance controls, and eliminate architectural drift?
Join global technology leaders at OSFF New York on November 4โ€“5, 2026.
๐ŸŽŸ๏ธ Register Now: https://hubs.ly/Q04n_bZL0
๐Ÿ”ฅ 20% OFF DISCOUNT CODE: 26YTOSFFNY20C

๐Ÿ•’ Timestamps:
0:00 The Great Baltimore Fire (1904): The Devastating Cost of Non-Standardization
2:05 Pre-1990 Wiring vs. Standardized Homes: Why Engineering Standards Save Time
3:38 The Software Architecture Gap: Cell Phone Whiteboard Photos & Visio Decks
5:08 The Jamara Compliance Model: Layering AIGF, CCC, and CALM
7:20 Introducing CALM Suite: CALM Studio & CALM Guard
8:10 Live Demo: Visualizing Systems in CALM Studio
10:37 Attaching AIGF & Common Cloud Control (CCC) Decorators from OpenSSF
13:49 Q&A: Managing Architectural Drift & Reverse-Engineering Codebases with AI

๐Ÿ“Š The Problem: Non-Standardized Architecture & The "Baltimore Fire" Hazard
In 1904, fire departments from five neighboring cities stood by helpless as Baltimore burned because none of their fire hoses matched Baltimore’s 600 non-standardized hydrant configurations. In modern software engineering, architecture suffers from the same lack of standardization: designs live in static Visio diagrams, Confluence pages, or whiteboard photos emailed across teams. Without a machine-readable standard, enterprise systems diverge into un-auditable configurations where developers and security auditors constantly scramble to verify compliance.

๐Ÿ—๏ธ The Solution: The Jamara Model & CALMStudio Visualizer
Eddie Knight demonstrates how CALMSuite solves architectural fragmentation: The Jamara Compliance Model: A 4-layer standardization hierarchy mapping high-level AI Governance Frameworks (Layer 1 / AIGF), Common Cloud Controls (Layer 2 / CCC), Enterprise-specific policies (Layer 3), and CALM architecture-as-code (Layer 4). CALM Studio Web Visualizer: A drag-and-drop UI that allows architects to build multi-component node systems visually without hand-authoring complex JSON schemas. Automated Compliance Decorators: Automatically imports pre-approved FINOS AIGF and CCC security controls directly from OpenSSF registries and attaches them as non-intrusive decorators on architecture nodes. Automated Export & Automation: Generates schema-valid CALM JSON alongside vector diagrams (PNG, SVG), enabling downstream CI/CD pipelines to enforce drift detection automatically.

โš™๏ธ Why This Matters for Financial EngineeringZero-to-Hero Onboarding:
Eliminates the steep learning curve of hand-writing JSON specifications, allowing developers and architects to generate auditable architecture graphs in minutes. Machine-Speed Compliance Auditing: Attaches regulatory controls directly to architectural artifacts, allowing GRC and DevSecOps teams to verify compliance via simple CLI commands rather than manual spreadsheet reviews.

๐ŸŒ More about FINOS: https://www.finos.org/
๐Ÿ“ง Join our newsletter: https://www.finos.org/sign-up
๐ŸŽ™๏ธ Listen to our Open Source in Finance Podcast: https://www.youtube.com/@FINOS/podcasts
LinkedIn: https://www.linkedin.com/company/finosfoundation

#FINOS #OSFFNewYork #CALM #ArchitectureAsCode #DevSecOps #AIGovernance #CommonCloudControls #OpenSource #FinTech

Source