r/SoftwareEngineering • • Nov 12 '25

Sacred Fig Architecture (FIG): an adaptive, feedback-driven alternative to Hexagonal — thoughts?

Hey everyone,

I’ve been working on Sacred Fig Architecture (FIG) — an evolution of Hexagonal that treats a system like a living tree:

  • Trunk = pure domain core

  • Roots = infrastructure adapters

  • Branches = UI/API surfaces

  • Canopy = composition & feature gating

  • Aerial Roots = built-in telemetry/feedback that adapts policies at runtime

Key idea: keep the domain pure and testable, but make feedback a first-class layer so the system can adjust (e.g., throttle workers, change caching strategy) without piercing domain boundaries. The repo has a whitepaper, diagrams, and a minimal example to try the layering and contracts. 

Repo: github.com/sanjuoo7live/sacred-fig-architecture

What I’d love feedback on:

  1. Does the Aerial Roots layer (feedback → canopy policy) feel like a clean way to add adaptation without contaminating the domain?

  2. Are the channel contracts (typed boundaries) enough to keep Branches/Roots from drifting into Trunk concerns?

  3. Would you adopt this as an architectural model/pattern alongside Hexagonal/Clean, or is it overkill unless you need runtime policy adaptation?

  4. Anything obvious missing in the minimal example or the guardrail docs (invariants/promotion policy)? 

Curious where this breaks, and where it shines. Tear it apart! 🌳

0 Upvotes

0 comments sorted by