This is the first entry in the Arcasidian DevLog. From here on, every major architectural decision, every trade-off, and every lesson learned gets documented as it happens.
Why Build in Public
Building in public forces clarity. When you know someone might read your engineering journal, you think harder about why you made a choice — not just what you built.
What’s Coming
Over the next weeks and months, expect posts covering:
- Infrastructure decisions — why Rust, why GGUF, why we avoid Python in production
- Architecture deep dives — how the 7-repo ecosystem fits together
- Performance journals — real benchmarks, real trade-offs
- Lessons learned — what broke, what we’d do differently