CaseTalk currently supports temporal modeling on Object-Fact Types with a fixed set of temporal axes (valid time, transaction time, decision time) and hardcoded column names. This is insufficient for real-world data pipeline projects where different target systems use their own naming conventions for the same temporal concepts (e.g. a Data Vault satellite uses LOAD_DTS/LOAD_END_DTS, SQL Server Temporal uses SysStartTime/SysEndTime, regulatory systems use EFFECTIVE_DATE/EXPIRY_DATE).

The following capabilities are missing:

1. Users cannot configure the column names that are generated for each temporal axis. The names are fixed and cannot be adapted to a target system conventions.
2. An OFType can only be assigned a single temporal topology (e.g. valid + transaction time). There is no way to independently name the two axes or assign them separately.
3. When mapping source system columns to a model in the data catalog alignment view, temporal system columns (load dates, valid-from/to etc.) are invisible and cannot be mapped to their source counterparts.

The request is to introduce a named timeline set registry where users can define reusable templates (name, axis type, start/end/indicator column names) and assign any combination of these to an OFType. Configured timeline columns should also appear as mappable entries in the role-path mapping view so source system catalogs can document how their timestamp columns align to the modeled temporal axes.