<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Christian T. Macion to Solutions</title>
    <link>https://christianmacion.github.io/portfolio/</link>
    <atom:link href="https://christianmacion.github.io/portfolio/feed-solutions.xml" rel="self" type="application/rss+xml" />
    <description>Client engagements and shipped deliverables. Newest first.</description>
    <language>en</language>
    <lastBuildDate>Sun, 09 Aug 2026 03:08:15 GMT</lastBuildDate>
    <managingEditor>christianmacion26@gmail.com (Christian T. Macion)</managingEditor>
    <item>
      <title>11-Agent Eval-First Research Platform</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#11-agent-eval-platform</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:11-agent-eval-platform</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>A small systematic-trading desk needed an AI workflow that could keep pace with the research pipeline
*without* shipping hallucinated or unverifiable analysis. The naive path : a single agent with one
prompt : produced plausible but unfalsifiable outputs. The desk needed something closer to a research
organization than a chatbot.
</description>
      <category>multi-agent</category>
      <category>eval-harness</category>
      <category>MCP</category>
      <category>model-routing</category>
      <category>walk-forward</category>
      <category>deflated-sharpe</category>
    </item>
    <item>
      <title>7-Agent Venture Incubation Pipeline</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#7-agent-venture-pipeline</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:7-agent-venture-pipeline</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>An operator-led venture incubation arm needed a repeatable way to triage, brief, and ledger new
business ideas : without one human bottleneck, and without the agent that proposes a decision
being the same one that approves it.
</description>
      <category>multi-agent</category>
      <category>governance</category>
      <category>venture</category>
      <category>prompts</category>
      <category>separation-of-duties</category>
    </item>
    <item>
      <title>8-Agent Editorial Production Pipeline (SLOP ↓ 96%)</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#8-agent-editorial-pipeline</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:8-agent-editorial-pipeline</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>A high-volume editorial workflow was generating content with a measurable &quot;slop index&quot; : generic,
templated, easily-detected text. Quality gate was after-the-fact and manual. Production scaled
faster than the editorial team could review.
</description>
      <category>multi-agent</category>
      <category>content</category>
      <category>eval-gate</category>
      <category>slop-scanner</category>
    </item>
    <item>
      <title>9-Project Public-Data Quant Research Library</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#9-project-quant-library</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:9-project-quant-library</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>Most online quant research demos are not reproducible: closed datasets, undisclosed parameters,
un-reported multiple-testing bias, and no OOS discipline. A hiring-grade research portfolio
needs every one of those addressed explicitly.
</description>
      <category>deflated-sharpe</category>
      <category>PBO</category>
      <category>CSCV</category>
      <category>walk-forward</category>
      <category>block-bootstrap</category>
      <category>multiple-testing</category>
    </item>
    <item>
      <title>Crypto Statistical-Arbitrage Pipeline with Funding-Carry</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#crypto-stat-arb-funding</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:crypto-stat-arb-funding</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>Crypto perps run funding payments every 8h. A naive long-short book ignores funding carry and
bleeds slowly when the spread is inverted. A working stat-arb needs the funding cost added back
to P&amp;L *before* sizing.
</description>
      <category>crypto</category>
      <category>stat-arb</category>
      <category>funding-carry</category>
      <category>cointegration</category>
      <category>half-life</category>
    </item>
    <item>
      <title>Public Finance Curriculum (CTA-Track, Self-Directed)</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#cta-curriculum-public</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:cta-curriculum-public</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>The Philippines has limited access to rigorous CTA-grade technical analysis training. Most
curriculum is either imported (US/UK, expensive) or shallow (TA-by-rote). There&apos;s a gap for
affordable, rigorous, evidence-based technical analysis education.
</description>
      <category>education</category>
      <category>STA</category>
      <category>CTA</category>
      <category>public-curriculum</category>
      <category>open-source</category>
    </item>
    <item>
      <title>Deflated Sharpe Ratio as a Built-in Pipeline Gate</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#deflated-sharpe-gate</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:deflated-sharpe-gate</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>Naive Sharpe ratios ignore the search effort : if you try 100 variants of an idea, the
best-looking one will overstate the true edge. The desk needed this multiple-testing
correction built into the validation pipeline, not stapled on at the end.
</description>
      <category>deflated-sharpe</category>
      <category>PBO</category>
      <category>MinBTL</category>
      <category>multiple-testing</category>
      <category>scipy-free</category>
    </item>
    <item>
      <title>Eval MCP Server : 31 Gates as First-Class Tools</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#eval-mcp-server</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:eval-mcp-server</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>LLM eval harnesses live in code or in spreadsheets : neither is a clean integration target for
multi-agent pipelines. A multi-agent system needs the eval gates exposed as **tools**, not as
Python imports.
</description>
      <category>MCP</category>
      <category>eval-harness</category>
      <category>multi-agent</category>
      <category>contract-first</category>
    </item>
    <item>
      <title>Look-Ahead-Bias Audit Suite</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#lookahead-bias-audit</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:lookahead-bias-audit</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>Look-ahead bias is silent: a backtest that uses future data looks great until you deploy it.
A serious research portfolio needs an **explicit audit suite** : a checklist of failure modes
with mechanical tests.
</description>
      <category>lookahead-bias</category>
      <category>point-in-time</category>
      <category>survivorship</category>
      <category>frozen-spec</category>
    </item>
    <item>
      <title>Transaction-Cost-Aware Backtest Engine</title>
      <link>https://christianmacion.github.io/portfolio/solutions/#txn-cost-aware-backtest</link>
      <guid isPermaLink="false">tag:christianmacion26.github.io,2026:solution:txn-cost-aware-backtest</guid>
      <pubDate>Sun, 09 Aug 2026 03:08:15 GMT</pubDate>
      <description>Backtests that ignore transaction costs, slippage, and latency are the most common source of
overfit research. A backtest engine needs all three treated as first-class inputs, not as
after-the-fact deductions.
</description>
      <category>txn-costs</category>
      <category>slippage</category>
      <category>capacity</category>
      <category>walk-forward</category>
    </item>
  </channel>
</rss>
