<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Concepts on Amfelt</title><link>https://amfelt.com/docs/concepts/</link><description>Recent content in Concepts on Amfelt</description><generator>Hugo</generator><language>en-us</language><copyright>© 2026 Amfelt Labs B.V.</copyright><atom:link href="https://amfelt.com/docs/concepts/index.xml" rel="self" type="application/rss+xml"/><item><title>Projects</title><link>https://amfelt.com/docs/concepts/projects/</link><pubDate>Tue, 14 Jan 2025 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/projects/</guid><description>A project is at the core of your Amfelt experience. It connects data sources to your data platform and defines the jobs that load your data.</description></item><item><title>Plugins</title><link>https://amfelt.com/docs/concepts/plugins/</link><pubDate>Thu, 09 Jan 2025 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/plugins/</guid><description>Connectors ship as versioned plugins. What they declare, where they run, and why selecting them per role is what makes the platform composable.</description></item><item><title>Pipelines</title><link>https://amfelt.com/docs/concepts/pipelines/</link><pubDate>Sun, 12 Jan 2025 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/pipelines/</guid><description>How data travels from a source to your data platform, covering the jobs that move it, the layers it lands in, and the order a run executes them.</description></item><item><title>Type resolution</title><link>https://amfelt.com/docs/concepts/type-resolution/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/type-resolution/</guid><description>How a column's type survives the trip from source to data platform, covering the three vocabularies involved and the order they are tried in.</description></item><item><title>Write modes and history</title><link>https://amfelt.com/docs/concepts/write-modes-and-history/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/write-modes-and-history/</guid><description>What the history layer remembers, how records are meant to land in staging, and the keys both depend on.</description></item><item><title>Templates</title><link>https://amfelt.com/docs/concepts/templates/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/templates/</guid><description>The SQL that maintains your history and bridge layers is generated from templates your target connector owns. They are deterministic, dialect-native, and readable.</description></item><item><title>Versioning and compatibility</title><link>https://amfelt.com/docs/concepts/versioning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/versioning/</guid><description>One semantic-version scale applied to five things, including the one you did not choose to version (your source's schema).</description></item><item><title>Data quality checks</title><link>https://amfelt.com/docs/concepts/data-quality/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://amfelt.com/docs/concepts/data-quality/</guid><description>Three checks run on every sync. Two you get without asking, and one you write in the contract.</description></item></channel></rss>