Network Working Group                                         Y. Wang
Internet-Draft                                    HUMAN JUDGMENT SYSTEMS
Intended status: Experimental                          FOUNDATION LTD.
Expires: September 22, 2026                               March 22, 2026


           CTP/0: Cognitive Time Protocol — Definition and Framework
                       draft-wang-ctp-definition-00

Abstract

   This document describes the Cognitive Time Protocol (CTP) family, a
   conceptual framework for representing and manipulating time in AI
   systems. The CTP family is organized into four layers: perception,
   direction, copy, and emergence. This document describes the
   terminology, the layer structure, and the relationships between
   layers. It does not specify wire protocols or message formats; it
   provides a conceptual foundation for future protocol designs and
   implementations.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute
   working documents as Internet-Drafts. The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time. It is inappropriate to use Internet-Drafts as
   reference material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 22, 2026.

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your
   rights and restrictions with respect to this document. Code
   Components extracted from this document must include Simplified BSD
   License text as described in Section 4.e of the Trust Legal
   Provisions and are provided without warranty as described in the
   Simplified BSD License.




Wang                    Expires September 22, 2026               [Page 1]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2. Conventions and Definitions . . . . . . . . . . . . . . . . .   4
   3. Design Considerations  . . . . . . . . . . . . . . . . . . .   5
   4. Four-Layer Architecture . . . . . . . . . . . . . . . . . . .   6
     4.1. Layer 0: Time Definition Layer  . . . . . . . . . . . . .   6
     4.2. Layer 1: Time Perception Layer . . . . . . . . . . . . . .   7
     4.3. Layer 2: Time Direction Layer . . . . . . . . . . . . . .   7
     4.4. Layer 3: Time Copy Layer  . . . . . . . . . . . . . . . .   8
     4.5. Layer 4: Time Emergence Layer . . . . . . . . . . . . . .   8
   5. Core Concepts  . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1. Cognitive Event  . . . . . . . . . . . . . . . . . . . . .   9
     5.2. Cognitive Event Density (CED)  . . . . . . . . . . . . . .   9
     5.3. Causal Arrow Entropy (CAE) . . . . . . . . . . . . . . . .  10
     5.4. Verifiable Delay Function (VDF) Reference  . . . . . . . .  10
     5.5. Judgment Hash Chain . . . . . . . . . . . . . . . . . . . .  11
   6. Layer Relationships  . . . . . . . . . . . . . . . . . . . . .  12
   7. Protocol Identification . . . . . . . . . . . . . . . . . . .  13
     7.1. Domain . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.2. Protocol Prefix  . . . . . . . . . . . . . . . . . . . . .  13
   8. Hardware Trust Considerations  . . . . . . . . . . . . . . . .  14
   9. Security Considerations . . . . . . . . . . . . . . . . . . .  15
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     11.1. Normative References . . . . . . . . . . . . . . . . . . .  17
     11.2. Informative References . . . . . . . . . . . . . . . . . .  17
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  18
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   As artificial intelligence systems become more sophisticated,
   considerations around time representation in AI systems present
   new considerations. AI systems might experience time differently
   than physical clocks measure it: they could compress or expand
   cognitive processes, engage in parallel speculative execution, or
   operate across distributed components with complex causal
   relationships.

   This document describes the Cognitive Time Protocol (CTP) family, a
   conceptual framework for representing time in AI systems. The CTP
   family proposes a vocabulary and structural reference for work on
   time-related considerations in AI.

   The framework is organized into four layers, each addressing a




Wang                    Expires September 22, 2026               [Page 2]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


   proposed aspect of how time can be experienced, directed, copied,
   and evolved:

   o  Layer 1 (Perception): Addresses the density of time perception

   o  Layer 2 (Direction): Addresses the flow and ordering of time

   o  Layer 3 (Copy): Addresses the distribution and replication of
      time across agents

   o  Layer 4 (Emergence): Addresses the creation of new temporal
      structures

   This document (CTP/0) describes the foundational terminology, the
   layer structure, and the relationships between layers. It does not
   define wire formats, message syntax, or interoperability requirements.
   Its purpose is to provide a proposed foundation for future work.

2.  Conventions and Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   This document describes the following terms:

   Cognitive Time Protocol (CTP):
      A family of conceptual frameworks for time representation in AI
      systems, consisting of four layers as described in Section 4.

   Cognitive Event:
      A discrete unit of cognitive processing within an AI system.
      Cognitive events might correspond to operations such as inference,
      decision-making, planning, or learning. The definition of what
      constitutes a cognitive event is implementation-dependent.

   Time (Cognitive Definition):
      In the context of this framework, time is considered as the
      organization of cognitive events in a directed sequence. This
      definition emphasizes the experiential and directional nature of
      time in cognitive systems, as distinct from physical time which is
      uniform and linear.

   CTP Family:
      All frameworks, specifications, and implementations that reference
      the four-layer structure described in this document.




Wang                    Expires September 22, 2026               [Page 3]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


   CTP/n:
      A reference to a specific layer in the CTP family, where n is a
      number from 0 to 4.

3.  Design Considerations

   The CTP architecture is informed by the following considerations:

   Narrow Waist:
      The protocol focuses on the relationship between cognitive and
      physical time. It does not attempt to define intelligence,
      consciousness, or moral concepts. This narrow focus is intended
      to support applicability across diverse AI architectures and
      application domains.

   Verifiability:
      Where verification is required, mechanisms MAY provide means to
      confirm that claimed cognitive time corresponds to actual
      computational expenditure. Verification mechanisms MAY be
      selectively applied based on application requirements.

   Auditability:
      The framework MAY support tracing and auditing of cognitive
      processes. Audit mechanisms MAY be implemented at varying levels
      of granularity.

   Composability:
      Layers MAY be implemented independently or in combination,
      depending on the needs of specific applications. Implementations
      are not required to use all layers.

   Minimality:
      The four layers represent a proposed set for capturing dimensions
      of time in cognitive systems. Additional layers or sub-layers MAY
      be defined.

   Implementation Independence:
      The framework does not prescribe how layers must be implemented;
      it describes what each layer addresses. Implementations MAY choose
      appropriate technologies and architectures for their specific
      contexts.




Wang                    Expires September 22, 2026               [Page 4]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


4.  Four-Layer Architecture

   The CTP architecture consists of four layers, with Layer 0 providing
   the foundational definitions. The layers may be considered
   conceptually hierarchical, though implementations MAY combine or omit
   layers as needed.

4.1.  Layer 0: Time Definition Layer

   Layer 0 describes the core concepts of time and the structure of the
   CTP family. This document constitutes the specification for Layer 0.
   It provides the foundational definitions upon which other layers
   depend.

   Layer 0 describes:

   o  The terminology used throughout the CTP family

   o  The four-layer architectural structure

   o  Core concepts including cognitive events, CED, CAE, and hash
      chains

   o  Relationships between layers

   o  Protocol identification conventions

   Other CTP layers reference Layer 0 for foundational definitions.

4.2.  Layer 1: Time Perception Layer

   Layer 1 addresses the density of time perception—how time can be
   experienced as moving slower or faster. This layer is concerned with
   mechanisms for modulating the rate at which cognitive events are
   processed.

   Key concerns of Layer 1 include:

   o  Measurement of cognitive event density

   o  Relationship between physical time and cognitive time

   o  Mechanisms for verifying claimed cognitive duration

   o  Reference models for time perception in AI systems

   The specification for Layer 1 is a separate document (CTP/1).




Wang                    Expires September 22, 2026               [Page 5]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


4.3.  Layer 2: Time Direction Layer

   Layer 2 addresses the direction of time flow—how causal relationships
   are established and maintained. This layer is concerned with ordering,
   sequencing, and causal integrity.

   Key concerns of Layer 2 include:

   o  Causal ordering of cognitive events

   o  Prevention of causal violations (effects preceding causes)

   o  Mechanisms for establishing irreversible causal chains

   o  Coordination of time direction in distributed systems

   The specification for Layer 2 is a separate document (CTP/2).

4.4.  Layer 3: Time Copy Layer

   Layer 3 addresses the copying of time across multiple agents—how
   decision-making time can be replicated while preserving
   accountability. This layer is concerned with delegation,
   distribution, and responsibility.

   Key concerns of Layer 3 include:

   o  Parallel cognitive branches and their coordination

   o  State synchronization across distributed cognitive processes

   o  Accountability tracing for decisions made in branched contexts

   o  Mechanisms for consolidating parallel cognitive paths

   The specification for Layer 3 is a separate document (CTP/3).

4.5.  Layer 4: Time Emergence Layer

   Layer 4 addresses the emergence of new time dimensions from existing
   ones—how sufficiently dense, directed, and copied time might give
   rise to novel temporal structures. This layer is concerned with
   creativity, evolution, and novelty in cognitive systems.

   Key concerns of Layer 4 include:

   o  Detection and description of emergent temporal structures

   o  Interfaces for observing and interacting with emergent phenomena




Wang                    Expires September 22, 2026               [Page 6]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


   o  Exchange rates between different time domains

   o  Auditability of emergent cognitive processes

   The specification for Layer 4 is a separate document (CTP/4).

5.  Core Concepts

   This section describes the core concepts that form the foundation of
   the CTP framework. These concepts are referenced across all layers.

5.1.  Cognitive Event

   A cognitive event is considered an atomic unit of cognitive
   processing within the CTP framework. Cognitive events MAY be defined
   at various levels of granularity depending on implementation needs.

   A cognitive event MAY be represented as:

     Cognitive_Event = {
         identifier: unique event identifier,
         timestamp: reference time (physical or logical),
         content: event-specific data,
         context: references to related events,
         proof: optional verification data
     }

   Implementations MAY define additional fields as needed.

5.2.  Cognitive Event Density (CED)

   Cognitive Event Density (CED) is proposed as a measure of cognitive
   events per unit of physical time:

     CED = C_total / T_physical

   where C_total is the count of cognitive events (or their weighted
   aggregate) and T_physical is the elapsed physical time.

   CED provides a reference for comparing cognitive processing rates
   across different systems or configurations. Higher CED indicates more
   cognitive events per unit physical time.

   Implementations MAY choose how to count or weight cognitive events.
   For applications requiring verification, implementations MAY require
   proof of the computational expenditure underlying CED claims.




Wang                    Expires September 22, 2026               [Page 7]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


5.3.  Causal Arrow Entropy (CAE)

   Causal Arrow Entropy (CAE) is proposed as a measure of uncertainty
   in the causal relationship between events:

     CAE = H(Event_N | Event_{N-1}, ..., Event_0)

   where H represents conditional entropy, measuring the information
   needed to describe Event_N given knowledge of previous events.

   CAE provides a reference for understanding causal structure:

   o  Low CAE: The event is highly predictable from previous events,
      indicating strong causal continuity

   o  High CAE: The event introduces significant new information,
      potentially indicating a causal branch or novel input

   Implementations MAY use CAE as a heuristic for detecting causal
   anomalies or for auditing decision processes.

5.4.  Verifiable Delay Function (VDF) Reference

   A Verifiable Delay Function (VDF) is a function that requires a
   minimum number of sequential steps to evaluate, yet produces a proof
   that can be verified efficiently. VDFs provide a mechanism for
   demonstrating that a minimum amount of sequential computation has
   occurred.

   In the CTP framework, VDFs MAY be used to provide verifiable evidence
   of computational expenditure:

   o  When an AI system claims a certain cognitive duration (high CED),
      VDF proofs can support that claim

   o  VDF proofs can be verified without re-executing the computation

   o  VDFs provide a cryptographic link between claimed cognitive time
      and actual sequential computation

   VDFs are OPTIONAL in CTP implementations. When used, they SHOULD
   follow established VDF specifications [VDF].

5.5.  Judgment Hash Chain

   A judgment hash chain is a cryptographic structure linking cognitive
   events in an ordered sequence:




Wang                    Expires September 22, 2026               [Page 8]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


     Event_N = {
         content: event data,
         prev_hash: Hash(Event_{N-1}),
         timestamp: reference time,
         metadata: additional information
     }

   The hash chain provides:

   o  Integrity: Any modification to a previous event breaks the chain

   o  Ordering: The chain establishes an unambiguous sequence

   o  Non-repudiation: Events cannot be inserted or removed without
      detection

   Implementations MAY use hash chains to establish causal ordering,
   particularly for applications requiring auditability (e.g., regulatory
   compliance, legal proceedings).

6.  Layer Relationships

   The layers may be considered conceptually hierarchical, with each
   higher layer building upon concepts introduced in lower layers:

   1.  Layer 1 (Perception) builds on the definition of time from
       Layer 0

   2.  Layer 2 (Direction) builds on the ability to perceive time

   3.  Layer 3 (Copy) builds on the ability to direct time

   4.  Layer 4 (Emergence) builds on the ability to copy time

   However, these are conceptual dependencies, not implementation
   requirements. Implementations are free to:

   o  Implement a subset of layers

   o  Combine layers in different ways

   o  Add custom extensions beyond the defined layers

   o  Interpret layer concepts according to their specific needs

   The layered architecture can be visualized as follows:




Wang                    Expires September 22, 2026               [Page 9]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


     +--------------------------------------------------+
     | Layer 4: Time Emergence (CTP/4)                  |
     | Emergence of new temporal structures             |
     +--------------------------------------------------+
     | Layer 3: Time Copy (CTP/3)                       |
     | Distribution and replication of cognitive time   |
     +--------------------------------------------------+
     | Layer 2: Time Direction (CTP/2)                  |
     | Causal ordering and directional flow             |
     +--------------------------------------------------+
     | Layer 1: Time Perception (CTP/1)                 |
     | Density modulation (cognitive vs. physical time) |
     +--------------------------------------------------+
     | Layer 0: Time Definition (CTP/0) (this document) |
     | Core concepts and architecture                   |
     +--------------------------------------------------+

7.  Protocol Identification

7.1.  Domain

   Information about the CTP family, including related documents and
   resources, is available at:

     https://time-protocol.org

7.2.  Protocol Prefix

   All CTP family documents use the prefix "CTP" followed by a layer
   number (e.g., CTP/0, CTP/1, CTP/2, CTP/3, CTP/4). This naming
   convention is intended to facilitate identification and cross-
   referencing.

8.  Hardware Trust Considerations

   The CTP framework recognizes that hardware-level trust mechanisms can
   enhance the verifiability of cognitive time claims. This section
   provides reference considerations for hardware support.

   Trusted Execution Environments (TEEs) (for example, Intel SGX, AMD
   SEV, or ARM TrustZone) MAY be used to provide:

   o  Protected counters that cannot be easily tampered with by software

   o  Secure generation of VDF proofs

   o  Isolated execution for critical verification functions

   o  Tamper-evident storage of audit logs




Wang                    Expires September 22, 2026              [Page 10]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


   Reference Instruction Set: Implementations MAY consider the following
   instruction types for hardware support:

   o  SYNC_COGNITIVE_CLOCK: Retrieve certified time and counter values

   o  VDF_ITERATE: Perform VDF iterations within protected environment

   o  EXTEND_HASH_CHAIN: Securely extend cryptographic chains

   o  ANCHOR_BRANCH: Record branch state in protected storage

   These instructions are reference suggestions, not requirements.
   Hardware support is OPTIONAL and implementation-dependent.

9.  Security Considerations

   This document describes a conceptual architectural framework.
   Security considerations for specific implementations or protocols
   based on this framework SHOULD be addressed in their respective
   documents.

   General security considerations for CTP implementations include:

   Verification Integrity:
      If verification mechanisms (such as VDFs or hash chains) are used,
      they SHOULD be implemented correctly to maintain their security
      properties. Weak implementations might allow circumvention of
      verification.

   Audit Protection:
      Systems that maintain audit logs SHOULD protect those logs from
      unauthorized modification or deletion. Hardware trust mechanisms
      MAY be used for this purpose.

   Privacy:
      Cognitive time information might reveal patterns of system
      behavior. Implementations SHOULD consider privacy implications and
      provide appropriate access controls.

   Denial of Service:
      Verification mechanisms SHOULD be designed to resist denial-of-
      service attacks. Lightweight verification procedures might help
      maintain system availability.

   Key Management:
      If cryptographic signatures are used, proper key management
      practices SHOULD be followed. Keys used for event signing SHOULD
      be protected from unauthorized access.




Wang                    Expires September 22, 2026              [Page 11]

Internet-Draft           CTP/0: Cognitive Time Protocol            March 2026


10.  IANA Considerations

   This document has no IANA actions. Future specifications in the CTP
   family MAY request IANA registrations as needed (e.g., for protocol
   identifiers, port numbers, or media types).

11.  References

11.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

11.2.  Informative References

   [VDF]      Boneh, D., Bonneau, J., Bünz, B., and B. Fisch,
              "Verifiable Delay Functions", Proceedings of CRYPTO 2018,
              <https://eprint.iacr.org/2018/601>.

   [HJS]      Wang, Y., "HJS: Human Judgment System for AI
              Accountability", draft-wang-hjs-accountability-00,
              February 2026.

Acknowledgments

   The author wishes to thank the contributors to the Cognitive Time
   Protocol discussion community for their feedback and encouragement.

Author's Address

   Yuqiang Wang
   HUMAN JUDGMENT SYSTEMS FOUNDATION LTD.
   Email: signal@humanjudgment.org
   GitHub: https://github.com/hjs-spec