Temporal Timing Format Reference

Status: STUB Priority: P1 Document ID: eda-001 Canonical Path: docs/eda/TTF_Reference.md Related Module: docs/post-ASML_era/module.json

About This Document#

This document is a planned stub. It has been registered in the TriadicFrameworks documentation graph and is referenced by five canonical post-ASML era documents. It is a P1 priority deliverable required by EDA tool integration workflows and PDK delivery.

Purpose#

The Temporal Timing Format (TTF) Reference provides the complete specification for the TTF arc encoding system used throughout the TRS-aware EDA toolchain. TTF arcs represent temporal causality paths in the logic graph, replacing or augmenting traditional static timing arcs with zone-relative temporal transition descriptors. This reference is the normative authority for arc type definitions, encoding syntax, EDA integration interfaces, and timing engine consumption rules.

Citing Documents#

Expected Content#

When authored, this document is expected to cover:

1. TTF Overview — Design goals; relationship to Liberty (.lib) and Verilog timing models; TTF as a superset or companion format.
2. Arc Type Definitions
   • CSA (Coherence-Sensitive Arc) — Arcs whose delay is a function of local SC_eff; encoding of SC class dependency.
   • ZBA (Zone Boundary Arc) — Arcs that cross SCR zone boundaries; inter-zone handoff latency encoding; ZBI parameter embedding.
   • APA (Adaptive Phase Arc) — Arcs whose phase can shift under dynamic coherence conditions; phase adaptation range encoding.
   • TCA (Temporal Commit Arc) — Arcs terminating at a Temporal Register commit point; L4 Commit coupling; SLF reference encoding.
   • DDA (Deferred Delivery Arc) — Arcs with intentional temporal delay for pipeline fold stages; fold depth parameter encoding.
3. Encoding Syntax — File format (text-based, line-oriented); arc record structure; field types and units; example arc records for each type.
4. Arc Composition Rules — How multiple TTF arcs combine at a cell output; precedence rules; degenerate arc handling.
5. SC Class Annotation — Embedding SC class constraints in arc records; runtime SC class checking by timing engine.
6. EDA Tool Integration
   • Timing engine ingestion API; arc discovery and loading sequence.
   • Static timing analysis (STA) extensions for TTF; slack computation with temporal arcs.
   • Required tool certification for TTF consumption (cross-reference to PDK Specification Section 8).
7. Mapping from Metrology Data — How RWDL and CLG maps from TGI Metrology are converted to TTF SC class annotations; toolchain scripts and format conversion.
8. Versioning — TTF format version field; backward compatibility rules; deprecation policy for arc types.
9. Quick Reference — Table of all arc types, required fields, optional fields, and units.

Dependencies#

When authored, this document is expected to reference:

• docs/post-ASML_era/The_TRS-Aware_PDK_Specification.md — PDK arc library definitions that instantiate TTF arc types
• docs/post-ASML_era/The_Logic_Folding_Architecture_Guide.md — Logic fold context for ZBA and DDA arc usage
• docs/post-ASML_era/The_TGI_Metrology_Standard.md — Metrology data that feeds into TTF arc SC annotations
• docs/fab/SCR_Zone_Config.md — Zone topology parameters embedded in ZBA arc records

Authoring Notes#

• This document MUST use normative language with R-prefix identifiers (R-TTF-NN format recommended).
• Arc encoding syntax MUST be specified with sufficient precision that a conforming parser can be implemented from this document alone (no ambiguous fields).
• All five arc types defined in The_TRS-Aware_PDK_Specification.md (CSA, ZBA, APA, TCA, DDA) must be explicitly covered and cross-referenced.
• Format version numbering must be defined before first public release.

Related Documents#

This stub was scaffolded from the TriadicFrameworks post-ASML era documentation suite. See docs/post-ASML_era/README.md for the full document graph.