Scion SDK · Connector runtime

Build one connector. Run it everywhere.

Scion SDK provides secure MCP connectors for the Arbora ecosystem. It defines source synchronization and governed write-back contracts.

Build the operator's first connector Explore the architecture

Serve

Create FastMCP servers with authentication, safe exposure, visibility, health, rate limits, and a consistent tool surface.

Synchronize

Discover certified source contracts, extract bounded pages, and advance EG-authoritative checkpoints from durable receipts.

Publish

Expose skills, prompts, ontologies, SHACL shapes, and manifests as deterministic ConnectorPack content.

Write back

Preview exact diffs, verify policy and source versions, apply idempotently, and reconcile uncertain effects.

Ingest repositories

Page authenticated immutable snapshots into deterministic manifests and bounded IndexRepository requests with typed per-file outcomes and tombstones.

One graph contract

The SDK depends directly on epistemic-graph>=2.27. Generated SourceIngest, ConnectorPack, and WriteBack models and clients are the sole graph boundary. Connector packages keep vendor logic local; durable identity, mapping, checkpoints, provenance, and receipts stay authoritative in epistemic-graph.

Explore the live architecture

Connectors own

Vendor requests, source revisions, paging tokens, and external effects.

The SDK owns

MCP lifecycle, capture, transport, certification, scheduling, and governed source execution.

epistemic-graph owns

Graph schemas, source state, content identity, reasoning, provenance, and durable receipts.

Arbora owns

Verified runtime identity, authority injection, composition, and protocol exposure.

From API to durable evidence

1. Describe
   A connector publishes its tools, content, source presets, and safety declarations over MCP.
2. Certify
   The SDK verifies package identity, live schemas, pagination, and extension behavior.
3. Transport
   Bounded pages and exact content archives cross generated epistemic-graph contracts.
4. Acknowledge
   epistemic-graph commits state and returns the receipt that authorizes the next step.

Choose a path

• New connector: follow Build the operator's first connector.
• Runtime owner: read Architecture and Connector sync.
• Repository operator: use Repository ingestion for immutable snapshot paging and durable indexing receipts.
• Extension author: implement Extension ports and run the Conformance kit.
• Security reviewer: start with Connector servers, HTTP clients, and Credentials.

Specification delivery

Open the specification dashboard for documented specifications, separate requirement status, delivery evidence, and open pull request and issue snapshots. It refreshes on pushes to main. Completion requires recorded delivery and acceptance; a merged requirement does not complete its parent specification. Dates and trends remain unknown until supported by recorded evidence.