<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>AlphaSwarm changelog</title>
        <link>https://alpha-swarm.ai/es/blog</link>
        <description>AlphaSwarm Blog</description>
        <lastBuildDate>Thu, 13 Aug 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>es</language>
        <item>
            <title><![CDATA[July–August 2026 — Safety gates, latency visibility, and BYOK]]></title>
            <link>https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release</link>
            <guid>https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release</guid>
            <pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Promotion evidence gates, approval expiry, six-clock order-latency dashboards, vendor BYOK, and streaming schema governance. Everything ships default-off.]]></description>
            <content:encoded><![CDATA[<p>The July–August development cycle focused on <strong>auditability and
safety before capital</strong>: statistically honest promotion gates, expiring
human approvals, per-segment order-latency visibility, and vendor
credentials that never sit in process environments.</p>
<p><strong>Every behaviour listed here ships default-off behind a feature
flag</strong> (with one deliberate exception: latency metrics auto-enable in
paper and development environments). Your deployment does not change
until an operator opts in.</p>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="safer-promotions">Safer promotions<a href="https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release#safer-promotions" class="hash-link" aria-label="Enlace directo al Safer promotions" title="Enlace directo al Safer promotions">​</a></h2>
<ul>
<li><strong>Trial ledger</strong> — every research trial is recorded, so the
deflated-Sharpe and overfitting statistics that gate promotion use an
honest experiment count. A lucky 1-in-10,000 backtest no longer looks
like skill.
<a href="https://alpha-swarm.ai/es/docs/concepts/strategy/promotion-evidence">Concept →</a></li>
<li><strong>Evidence-gated promotion</strong> — promotion requests fail closed without
a complete statistical evidence bundle, and paper execution refuses
artifacts that lack an approval token.</li>
<li><strong>Approvals now expire</strong> — pending human approvals (orders,
promotions, ingestion) carry a TTL; stale requests lapse instead of
firing late. <a href="https://alpha-swarm.ai/es/docs/concepts/trading/approval-queues">Concept →</a></li>
</ul>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="see-where-every-millisecond-goes">See where every millisecond goes<a href="https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release#see-where-every-millisecond-goes" class="hash-link" aria-label="Enlace directo al See where every millisecond goes" title="Enlace directo al See where every millisecond goes">​</a></h2>
<p>Six named clocks measure each segment of the order path — market-data
lag, strategy think time, risk gate, ledger write, broker
acknowledgement, fill apply — with a ready-made Grafana dashboard.
Auto-on in paper/dev environments.
<a href="https://alpha-swarm.ai/es/docs/concepts/trading/six-clock-latency">Concept →</a></p>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="bring-your-own-keys">Bring your own keys<a href="https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release#bring-your-own-keys" class="hash-link" aria-label="Enlace directo al Bring your own keys" title="Enlace directo al Bring your own keys">​</a></h2>
<p>Market-data and brokerage credentials (Alpaca, IBKR, Databento, Alpha
Vantage) now resolve through the platform credential vault at the
moment of use — organizations can bring their own vendor keys, and
worker processes no longer carry vendor secrets in their environment.
<a href="https://alpha-swarm.ai/es/docs/concepts/data/market-data-vendors">Concept →</a></p>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="governed-streaming">Governed streaming<a href="https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release#governed-streaming" class="hash-link" aria-label="Enlace directo al Governed streaming" title="Enlace directo al Governed streaming">​</a></h2>
<p>Kafka messages carry schema ids that consumers verify (refusing to
guess on unknown schemas), and stream consumers address topics through
the governed data catalog rather than hard-coded names.
<a href="https://alpha-swarm.ai/es/docs/concepts/data/streaming-governance">Concept →</a></p>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="also-in-this-cycle">Also in this cycle<a href="https://alpha-swarm.ai/es/blog/2026/08/13/safety-observability-release#also-in-this-cycle" class="hash-link" aria-label="Enlace directo al Also in this cycle" title="Enlace directo al Also in this cycle">​</a></h2>
<ul>
<li><strong>CLI sign-in fix</strong>: <code>alphaswarm-cli auth login</code> device flow now works
against hosts that previously only advertised the web app's OIDC
client.</li>
<li><strong>Clearer readiness</strong>: <code>/readyz</code> distinguishes "database migrations
pending" from "database down", and surfaces auth-service
reachability advisorily.</li>
<li><strong>License + customer management APIs</strong> for enterprise/BYOC
deployments.</li>
<li><strong>dbt semantic layer (preview)</strong>: named, governed business metrics
for agents and dashboards.
<a href="https://alpha-swarm.ai/es/docs/concepts/data/dbt-semantic-layer">Concept →</a></li>
</ul>
<p>The full engineering detail is in the
<a href="https://alpha-swarm.ai/es/docs/changelog/2026-08-13">2026-08-13 changelog</a>.</p>]]></content:encoded>
            <category>release</category>
            <category>safety</category>
            <category>observability</category>
            <category>data</category>
        </item>
        <item>
            <title><![CDATA[Release 2026-06-01 — Docs migration + first API epoch]]></title>
            <link>https://alpha-swarm.ai/es/blog/2026/06/01/initial-release</link>
            <guid>https://alpha-swarm.ai/es/blog/2026/06/01/initial-release</guid>
            <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[docs.alpha-swarm.ai launches as the canonical documentation site; first Stripe-style API epoch lands.]]></description>
            <content:encoded><![CDATA[<p>The canonical documentation site launches, and the first Stripe-style
API epoch (<code>2026-06-01</code>) lands.</p>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="new">New<a href="https://alpha-swarm.ai/es/blog/2026/06/01/initial-release#new" class="hash-link" aria-label="Enlace directo al New" title="Enlace directo al New">​</a></h2>
<ul>
<li><strong>The documentation site is live</strong> at <code>alpha-swarm.ai/docs</code>,
replacing the previous GitHub-rendered tree. Every previous link
continues to resolve via 301 redirects.</li>
<li><strong>Interactive API playground</strong> at
<a href="https://alpha-swarm.ai/es/docs/reference/api">/docs/reference/api</a>. Token persistence works
end-to-end; copy a <code>Bearer</code> from <code>alphaswarm-cli auth login</code> and every
request from the playground inherits it.</li>
<li><strong>AI-native surfaces.</strong> A curated <code>/llms.txt</code> index, the full corpus
at <code>/llms-full.txt</code>, and an MCP server at <code>/mcp</code> are first-class
agent entry points.</li>
<li><strong>In-product help panel</strong> in the operator UI — the help drawer reads
directly from the docs corpus, so in-product reference never drifts
from the public site.</li>
</ul>
<h2 class="anchor anchorWithStickyNavbar_ZAkS" id="api">API<a href="https://alpha-swarm.ai/es/blog/2026/06/01/initial-release#api" class="hash-link" aria-label="Enlace directo al API" title="Enlace directo al API">​</a></h2>
<ul>
<li><strong>First Stripe-style date epoch:</strong> <code>2026-06-01</code>. No surface changes
from the prior unversioned API; future epochs follow the documented
12-month sunset cycle with RFC 8594 <code>Deprecation</code> and <code>Sunset</code>
response headers.</li>
<li><strong>OpenAPI specs committed</strong> and drift-gated with <code>oasdiff</code> on every
PR.</li>
</ul>
<p>For the full details, see the
<a href="https://alpha-swarm.ai/es/docs/release-notes/2026-06-01-initial-release">release notes archive</a>.</p>]]></content:encoded>
            <category>release</category>
            <category>api</category>
            <category>docs</category>
        </item>
    </channel>
</rss>