ArchTenet is an engineering playbook: reference architectures and production notes from systems we build and run. Its goal is to help teams pick the approach that fits their stage — instead of blindly following best practices.
Ivan Baha
Founder / Development Team Lead | Software Architect
Software Development Team Lead and Architect focused on building, securing, and scaling complex distributed systems. Bridging technical strategy with hands-on implementation, he specializes in cloud infrastructure, microservices, and integrating cutting-edge AI coding tools and LLMs into enterprise workflows to boost team velocity.
What do firefighting and software design have in common? — If you aren't thorough, everything burns.
Vladyslava Prykhodko
Founder / Engineering Technical Lead | Software Architect
Engineering Technical Lead and Architect specializing in large-scale distributed platforms and globally replicated databases. With a background spanning from full-stack development to high-level system design, she focuses on system reliability, cost optimization, and integrating AI-driven development practices into enterprise engineering teams.
You cannot optimize what you cannot see. Designing globally distributed systems requires zooming out far enough to turn hundreds of moving parts into one predictable flow.
We split content into two streams to separate verified solutions from ongoing exploration.
If you feed architecture patterns into AI coding tools (like Cursor, Claude, or custom LLMs), you shouldn't have to scrape messy HTML. Every page is published in clean, token-efficient Markdown so agents can ingest context directly:
- Per page: Add
.md to any URL (see example) or request with Accept: text/markdown. - Entire playbook: Point agents to llms.txt for a structured index of all content.
