Skip to main content

EXTENSIONS

Built by operatives — models, drivers, vaults, and reports, the parts that plug into Swamp.

Filter by what you need and pull what fits.

Selection
4 results
label:meta

Swamp Adoption

@webframp/swamp-adoption · v2026.09.15.1

Guides new users through mapping their domain onto swamp primitives.

upd Sep 1514 pullsA100/100

Meta Publishing

@mgreten/meta-publishing · v2026.08.26.1

Fail-closed Meta Graph API models for exact-approved Facebook and Instagram publication and PAUSED-only Meta Ads draft creation.

upd Aug 261 pullsB78/100

Swamp Triage

@sntxrr/swamp-triage · v2026.08.04.4

Investigate why any swamp model or workflow is failing, without knowing anything about the domain it automates. Every method and workflow run leaves a @swamp/method-summary or @swamp/workflow-summary report behind as versioned model data, written on failure as well as success — so the full history of a target is already on disk with nothing extra instrumented. `investigate` resolves a target by name at call time, walks that history back to the boundary where it stopped working, and classifies the error into auth / unreachable / timeout / tls / rate_limit / not_found / config, each with a concrete next step. The distinction it exists to make is auth vs unreachable: a remote answering 403 is healthy and rejecting your credential (go to the vault), while a remote that never answers is a network problem (go to the host) — the two read almost identically in a notification and lead opposite ways. Unrecognised errors are reported as `unknown` verbatim rather than filed under a plausible-looking category. Read-only: it reads what previous runs recorded and never invokes the failing target.

upd Aug 522 pullsA100/100

Meta Factory

@atalanta/meta-factory · v2026.07.04.9

Deterministically assemble a @swamp/software-factory definition from the design

upd Jul 57 pullsB85/100