<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>sigc Blog</title><description>Notes on building a typed DSL and Rust runtime for quantitative trading strategies, from the sigc team at Skelf-Research.</description><link>https://sigc.skelfresearch.com/</link><language>en-us</language><item><title>Reading sigc syntax: a 5-minute tour</title><link>https://sigc.skelfresearch.com/blog/reading-sigc-syntax-five-minute-tour/</link><guid isPermaLink="true">https://sigc.skelfresearch.com/blog/reading-sigc-syntax-five-minute-tour/</guid><description>A .sig file is four blocks. If you have read pandas before, you can read sigc. This is a guided tour of the syntax with three working examples and the operators you will use most.</description><pubDate>Thu, 20 Nov 2025 00:00:00 GMT</pubDate></item><item><title>Compiling an alpha idea: the stages between notebook and prod</title><link>https://sigc.skelfresearch.com/blog/compiling-an-alpha-idea-from-notebook-to-prod/</link><guid isPermaLink="true">https://sigc.skelfresearch.com/blog/compiling-an-alpha-idea-from-notebook-to-prod/</guid><description>A signal does not jump straight from a research notebook to a live trading account. It goes through stages. sigc makes those stages explicit, in the same binary, with the same operator semantics.</description><pubDate>Wed, 12 Nov 2025 00:00:00 GMT</pubDate></item><item><title>Why every quant fund rewrites the same backtester</title><link>https://sigc.skelfresearch.com/blog/every-quant-fund-rewrites-the-same-backtester/</link><guid isPermaLink="true">https://sigc.skelfresearch.com/blog/every-quant-fund-rewrites-the-same-backtester/</guid><description>Every desk that scales past a few researchers ends up writing the same typed signal language. We have seen the failure modes that drive it. This is why sigc treats the strategy as a program.</description><pubDate>Tue, 04 Nov 2025 00:00:00 GMT</pubDate></item></channel></rss>