[π·πΊ Π ΡΡΡΠΊΠ°Ρ Π²Π΅ΡΡΠΈΡ]
Engineer-practitioner. Civil engineering technician (PGS) by education, systems researcher by calling.
I build software systems with the same level of responsibility I would apply to construction: focus on structure, protocols, and long-term reliability. My path is one of "learning-by-doing", supported by rigorous engineering protocols and living documentation.
Extending Zed IDE. My main "proving ground" where I implement AST-aware search, LanceDB, and complex indexing pipelines.
AI agent experiments. Exploring where LLM "magic" ends and strict protocol constraints begin.
I don't just write code β I build environments that adhere to strict principles:
- Clean Architecture (The "Tumbler" pattern: technology shouldn't dictate architecture).
- Transparency (Every architectural decision is backed by experiments recorded in
EXPERIMENTS_LOG.md). - Safety (Code without tests is incomplete construction).
- Living Documentation (Code and documentation are synchronized in every commit).
Detailed breakdowns of specific technical discoveries and architectural challenges encountered during development:
- PageRank vs RAG on a Real Codebase β semantic vs structural retrieval, with two rounds of honest metric self-correction.
- I Asked One AI to Fact-Check Another AI β cross-verification against high-confidence LLM hallucinations in security reviews.
- The Silent Vector Contamination Bug β thread-safety and memory isolation in concurrent embeddings (OpenVINO).
Live portfolio β mansio.github.io/MSPortfolio Β· Writing β dev.to/mansio Β· LinkedIn β in/ManSio
claude mcp add --transport http msp-portfolio https://msp-portfolio.mansio-dev.workers.dev/mcp
Ask the portfolio anything β it answers through MCP tools, not vibes.