Interface: SourceDetailResponse
@kortexya/reasoninglayer / SourceDetailResponse
Interface: SourceDetailResponse
Section titled “Interface: SourceDetailResponse”Defined in: src/types/sources.ts:367
Response with source details and health.
Properties
Section titled “Properties”available
Section titled “available”available:
boolean
Defined in: src/types/sources.ts:373
Whether the source is currently available.
lastSyncAt
Section titled “lastSyncAt”lastSyncAt:
string|null
Defined in: src/types/sources.ts:384
When the most recent SUCCESSFUL ingest of this source finished (RFC 3339,
UTC), or null when no ingest of it has completed. See
SourceSummaryDto.lastSyncAt.
mode:
string
Defined in: src/types/sources.ts:378
Resolved write-path mode: "transpile" or "ingest" (see SourceWriteMode).
Typed as string for the reason given on SourceSummaryDto.mode.
sourceId
Section titled “sourceId”sourceId:
string
Defined in: src/types/sources.ts:369
Source identifier.
sourceType
Section titled “sourceType”sourceType:
string
Defined in: src/types/sources.ts:371
Source type.
supportedModes
Section titled “supportedModes”supportedModes:
string[]
Defined in: src/types/sources.ts:395
The write-path modes this source’s adapter can actually serve (#71).
Always contains 'ingest' — every adapter can materialize. Contains
'transpile' only when the adapter executes transpiled SQL, which is what
a live view requires. A client rendering a mode selector should offer
exactly these, rather than hard-coding a list of source types: the set is
derived from the adapter’s declared capability, so it stays correct as
adapters gain the ability.