Source edge cases
Making conditional imports, exclusions, and repository-specific configuration explicit in the project model.
Language & Ecosystem Lead
Tristan Kruse
Tristan contributes across ArchUnitPython and leads the development of ArchUnitRuby and ArchUnitJava. His work focuses on translating a shared architecture-testing model into language-native APIs, analyzers, test integrations, and developer workflows across different ecosystems.
View GitHub profile ↗
About Tristan
Making architecture tests useful outside the happy path.
Tristan works across ArchUnitPython and leads ArchUnitRuby and ArchUnitJava. He focuses on the details that determine whether an architecture test remains useful in a real repository: accurate extraction, explicit configuration, trustworthy rule evaluation, and documentation that explains the result rather than merely listing an API.
In ArchUnitPython, his work includes conditional-import classification, reusable configuration, project-level .archignore support, because rationales, and clearer guidance for metrics and graph exports. In ArchUnitRuby, he translates the shared architecture-testing model into Prism-based analysis, Ruby-native fluent rules, and RSpec, Minitest, and framework-neutral assertions.
For ArchUnitJava, Tristan helped take the project from an early foundation to a published public beta on Maven Central. The implementation reads compiled classes and JARs without loading application code, then connects deterministic policies, structured evidence, JUnit, CLI workflows, and generated documentation. Across all three ecosystems, the goal is a familiar ArchUnit mental model expressed through the language and toolchain developers already use.
Focus
Where Tristan contributes.
Explainable rules
Connecting a failed relationship to its rationale, threshold, and actionable evidence.
Ecosystem fit
Adapting the shared ArchUnit model to Python, Ruby, and Java without flattening their different analyzers, APIs, and test workflows.
Selected project work
Work that makes the library family stronger.
- 01
Added conditional-import classification, common rule configuration, project exclusions, and human-readable rationales to ArchUnitPython.
- 02
Leads ArchUnitRuby across Prism-based extraction, graph and metric capabilities, language-native rules, test integrations, and documentation.
- 03
Leads ArchUnitJava as a compiled-bytecode architecture engine with Maven Central distribution, JUnit and CLI integration, deterministic reports, and public documentation.
Working principle
“Trust comes from handling the awkward repository cases with the same care as the clean example.”
Contact Tristan
Ready to make architecture visible?
Talk with Tristan about architecture testing, the ArchUnit library family, or how executable guardrails can fit your engineering workflow.
krusetristan1@gmail.com
