Actionist Knowledge Graph
P11 · Host knowledge node

Connector and external-action plane

Reuse broad provider catalogues and OAuth/action mechanics while Actionist owns tenant-scoped connections, authority and side-effect receipts.

Problem boundary

What this subsystem owns and what it must hand to the rest of Actionist.

What it owns

  • Provider/action/trigger catalogue
  • OAuth and credential setup
  • Tenant connection store
  • Retries, idempotency and rate limits
  • Approval and action receipts

What research already found

  • OpenConnector: 1,445 providers and 15,156 generated actions
  • Activepieces: mature pieces and connect-account UI
  • Nango and Jentic add provider/spec breadth
  • OpenConnector global connection storage failed tenancy requirements

Open first-principles questions

  • Canonical provider/action schema?
  • Which popular providers need scripted setup?
  • How does browser operation fit?
  • What is the authority/approval model for side effects?

Inputs

  • Provider definitions
  • Tenant authority
  • Secrets

Outputs

  • ConnectorContract
  • Connection
  • ActionReceipt

Scientific research protocol

Every research owner uses the same evidence funnel. No padding is allowed when a denominator is inapplicable or evidence is unavailable.

Prior evidence auditRead the canonical spine, all domain-linked artifacts, the 17-industry catalogue and existing contradictions before searching again.
Commercial 100 → 10Define a denominator, map approximately 100 companies/products, and produce first-party dossiers for the strongest 10.
GitHub 100 → 10Search and dedupe approximately 100 relevant OSS projects, then deeply inspect the strongest 10 at the capability and architecture level.
Local estate joinInspect AutoSaaS, Great Library, SISOCRM, 21st stores and other domain-specific precedents already on the laptop.
Innovation 100 → 10Generate a wide divergent idea register, score it against the problem and retain the 10 strongest falsifiable innovations.
First-principles synthesisDecompose the irreducible problem, challenge inherited assumptions, reconcile contradictions and state the minimum sufficient design.
Contracts and experimentsReturn the proposed contract, dependency edges, unknowns, falsifiers, experiments, stop rules and decisions.
Independent verificationA separate verifier checks counts, links, source claims, overlap, contradictions and unsupported conclusions before promotion.

Evidence and agent outputs

Existing research remains source evidence. New agent packets are written to one owned workstream directory and linked here after verification.

ArtifactLocationState
Connector research summaryresearch/actionmodel-builder-research-2026-08-26/phase-8/external-opus-inputs/connectors/connector-research-summary.mdexisting
OpenConnector spikeresearch/openconnector-spike-2026-08-27.mdexisting
Connectors reportresearch/connectors-licensing-2026-08-27.mdexisting
Future verified agent packetresearch/workstreams/P11-connector-and-external-action-plane/runs/<run-id>/planned

Agent-sized objective

Separate catalogue, OAuth engine, connection storage and action runtime; prove one tenant-safe connector flow.

See sprint assignment →