Skip to content

ProtocolWarden

External Integrations

ProtocolWarden/ProtocolWarden.github.io

External Integrations¶

External integrations are not automatically core ProtocolWarden repos. They become platform components only when an adapter, contract, and boundary story exists for them.

Current examples¶

Repo	Role	Notes
firecrawl	external integration	candidate backend / crawl integration
PraisonAI	external integration	candidate backend or orchestration input
Wan2GP	external integration	candidate capability source
openclaw	external integration	candidate integration surface
Zonos-API	external integration	candidate backend API
neuro-game-sdk	external integration	candidate capability source

Retired forks (ADR 0005, 2026-05-18)¶

Repo	Replaced by	Notes
kodo	TeamExecutor	team coordination role absorbed into owned executor
Archon	DAGExecutor	DAG workflow role absorbed into owned executor

Rules¶

Forks are not core architecture by default.
External repos are documented as dependencies, adapters, or capability sources.
A repo only becomes part of the platform when its contracts and boundaries are explicit.
SourceRegistry tracks source and fork lifecycle.