Foundational work referenced in docs/development/architecture.md ("Connector System: Planned — Abstract connector interface for pluggable sources") and docs/features/connectors.md ("Connector Architecture" / "Register in src/Compendium.Connectors/ConnectorRegistry.cs").
Today the only ingestion path is the local file system connector via compendium ingest. To support the connectors on the roadmap (SharePoint, Confluence, wiki, and beyond) we need a pluggable connector abstraction:
IConnector interface (sketched in docs/features/connectors.md under "Connector Architecture")- A
ConnectorRegistry for registration/discovery, following the pattern used by src/Compendium.Ingest's extractor registry
- A
compendium connect <name> CLI verb that dispatches to registered connectors
- Common pipeline: fetch → extract → map to OKF concept → provenance stamping (
sources[].resource, sources[].commit/version where available)
This is a prerequisite for the SharePoint, Confluence, and Markdown Wiki connector issues.
Foundational work referenced in
docs/development/architecture.md("Connector System: Planned — Abstract connector interface for pluggable sources") anddocs/features/connectors.md("Connector Architecture" / "Register insrc/Compendium.Connectors/ConnectorRegistry.cs").Today the only ingestion path is the local file system connector via
compendium ingest. To support the connectors on the roadmap (SharePoint, Confluence, wiki, and beyond) we need a pluggable connector abstraction:IConnectorinterface (sketched indocs/features/connectors.mdunder "Connector Architecture")ConnectorRegistryfor registration/discovery, following the pattern used bysrc/Compendium.Ingest's extractor registrycompendium connect <name>CLI verb that dispatches to registered connectorssources[].resource,sources[].commit/version where available)This is a prerequisite for the SharePoint, Confluence, and Markdown Wiki connector issues.