How fathym-deno/eac works
Project type and purpose
• Everything as Code is a Deno/TypeScript library and runtime for defining, managing, and executing enterprise DevOps configurations (“Everything-as-Code”).
• It exposes a core API (src/eac), a pluggable distributed file system (src/dfs), a runtime engine with gateways and pipelines (src/runtime), and a “steward” orchestrator/CLI (src/steward).
File structure
• Top-level “src” contains these domains:
• dfs – handler/resolver/worker pattern for abstracting file storage (Azure Blob, Deno KV, local FS, NPM, remote fetch, ESM, JSR).
• eac – core “Everything as Code” data models (Details, States, API JWT payloads, actuators, metadata).
• runtime – runtime engine (config, execution context, handler pipelines, protocol gateways & transports (HTTP, MQTT, OPC UA), plugins, server startup).
• steward – orchestrator clients, informants, status checkers, commit/delete handlers for pushing EAC definitions to actuators.
• fluent & esbuild – convenience builders and build pipeline exports.
• types – shared TypeScript types and utilities.
• Configuration files (.gitattributes, deno.jsonc) and tests for each domain confirm modular boundaries.
README
• Describes the API’s goals: cloud- and code-agnostic DevOps as config, customizable modules, future-proof.
Detail
• Major directories as components
• Handler→resolver→worker flow in DFS
• Pipeline→gateway→transport chain in Runtime
• Steward’s commit/check/delete client flows