In the last part, we talked about why we built Vyshyvanka. Today, we're going to talk about how. Software architecture is often the difference between a project that scales and one that becomes a tangled web of technical debt after six months. For Vyshyvanka, we knew from day one that modularity wasn't an option - it was a requirement.
The Dependency Rule
If there's one rule we follow, it's the Dependency Rule: Dependencies flow strictly downward.
Vyshyvanka.Core is our heartbeat. It's pure C#, containing only domain models, interfaces, and contracts. It has zero dependencies on anything else. This makes our core logic incredibly easy to test and reason about - if it compiles, it's logically sound.
Vyshyvanka.Engine depends only on Core. It's where the magic happens: execution pipelines, persistence, and auth.
