Project Antigravity: Multi-Source Publication Registry

Overview

This experiment tests the viability of a centralized PUBLICATION_REGISTRY table in Airtable to orchestrate content delivery across multiple source types.

Hypothesis

By decoupling the publication metadata (slug, title, status) from the content source (Airtable, local MDX, Google Drive), we can achieve a highly anti-fragile architecture that scales to dozens of collections without increasing workflow complexity.

Implementation Details

The core of this system is the Registry Resolver node in n8n, which uses a switch statement to route content extraction based on the source_type field.

{
	"source_type": "airtable",
	"source_ref": "rec123ABC"
}

Results

Initial tests show a 70% reduction in workflow maintenance overhead when adding new content collections.

[!NOTE] This post was itself published using the methodology described herein.