31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
# KTT Rail (Placeholder)
|
|
|
|
## Status
|
|
|
|
KTT is a **rail plugin slot** until sector-specific definition. The name is used in different sectors for different systems; this document reserves the slot and describes placeholder behavior.
|
|
|
|
## Identifier Types
|
|
|
|
- **ktt.id** — Generic KTT identifier; format: alphanumeric, optional `.` `_` `-`.
|
|
- **ktt.participantId** — Same validation as ktt.id.
|
|
|
|
Validation is in `@as4-411/core` (validation.ts). A valid `ktt.*` identifier can be stored and resolved to a RouteDirective like any other identifier once directory data exists.
|
|
|
|
## Endpoints
|
|
|
|
To be defined when the rail is specified. Use standard protocol values (https, mq, etc.) and a profile name indicating the KTT channel.
|
|
|
|
## Trust and Directory Source
|
|
|
|
- **Authoritative directory source(s):** TBD per sector.
|
|
- **Trust constraints:** TBD. Prefer tenant scoping and explicit allow/deny.
|
|
|
|
## Connector
|
|
|
|
- **packages/connectors/ktt**: Placeholder adapter with `ingestFromFile` and `ingestFromApi` stubs. When the rail is defined, implement ingest that maps external participants/identifiers/endpoints into the core directory model.
|
|
|
|
## Acceptance
|
|
|
|
- A valid `ktt.*` identifier resolves to at least one RouteDirective when directory data is present.
|
|
- Adapter supports ingest (file + API modes) as stubs; full implementation when KTT is clarified.
|