Source Capability seam; v1 ships only filesystem/object-store connectors

"Siloed data" is addressed architecturally by a Source Capability (list + fetch documents, stamping Provenance) that mirrors every other Capability — so the framework's "integrated" promise is real at the seam, not hardcoded. v1 ships only the Sources that come free through the fsspec Storage seam (ADR-0009): local folder, S3, GCS, Azure Blob. Connectors to source SYSTEMS (SharePoint, Confluence, Google Drive, databases, Slack) are defined as the first enterprise/community connector surface but deliberately NOT built pre-launch — each is an OAuth + pagination + rate-limit + maintenance project, and at Deloitte that connector work is exactly where delivery engagements bill. Rejected: a full connector suite in v1 (scope balloon, connectors rot unmaintained), out-of-scope-entirely (forces a caveat on the "siloed" pitch and a pre-staged demo corpus), and delegating wholesale to Airbyte/Fivetran/unstructured (couples the integrated story to a third party's data model and auth). The demo may still ship a pre-staged corpus; the Source seam is what makes real connectors a plugin, not a fork.