-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathPT-CHN_schema.qmd
172 lines (153 loc) · 4.65 KB
/
PT-CHN_schema.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
---
title: "Plain-Text Chronological Hierarchical Notation (PT-CHN)"
subtitle: "A Comprehensive Schema for LLM Conversation Management"
author: "Generated by Perplexity AI"
date: "2024-11-08"
format:
html:
toc: true
toc-depth: 3
number-sections: true
pdf:
toc: true
number-sections: true
---
# Introduction
This Quarto document provides a comprehensive guide to the PT-CHN schema. It can be rendered to HTML, PDF, or other formats while maintaining consistent formatting and structure. The document is designed to serve both as a reference guide and as training material for new users.
The Plain-Text Chronological Hierarchical Notation (PT-CHN) is a robust naming convention designed for managing Large Language Model (LLM) conversations. This schema optimizes for searchability, readability, and maintainability while using only ASCII characters.
## Core Format
The base format follows this structure:
@YYMMDD-[CAT]-{TAG1.TAG2}-#ID-<V00>-!P-*S: Title
Schema Components
Temporal Marker (@YYMMDD)
Format: @YYMMDD
Example: @241107
Purpose: Chronological organization and temporal search
Rules:
YY: Two-digit year
MM: Two-digit month
DD: Two-digit day
Category Code ([CAT])
Primary classification codes:
Code Description Use Case
DEV Development Technical development tasks
RES Research Investigation and research
PRJ Project Project management
EXP Experiment Testing and experimentation
STD Study Learning and analysis
ANA Analysis Detailed examination
Tag System ({TAG1.TAG2})
Tags use dot notation for hierarchical organization:
{DOMAIN.SUBDOMAIN}
Common tag combinations:
Tag Combination Description
PROMPT.FUNC Functional prompting
AI.ARCH AI architecture
SYS.OPT System optimization
Identifier (#ID)
Format: #XNN where:
X: Alpha character (A-Z)
NN: Two-digit number (01-99)
Examples:
#A01 - First series, first item
#B01 - Second series, first item
#Z99 - Final series, last item
Version Control (<V00>)
Version notation follows semantic principles:
Notation Meaning Usage
<V01> Initial First version
<V02> Revision Subsequent updates
<VXX> Experimental Testing versions
Priority Indicator (!P)
Priority levels and their meanings:
Code Priority Description
!C Critical Immediate attention required
!H High Important, time-sensitive
!M Medium Standard priority
!L Low Can be deferred
!X None No priority assigned
Status Marker (*S)
Current state of the conversation:
Code Status Description
*IP In Progress Active development
*DN Done Completed
*RV Review Needs review
*BL Blocked Cannot proceed
*AR Archived Completed and stored
*HL Hold Temporarily paused
*XX Unknown Status unclear
Implementation Guidelines
Search Patterns
Basic Searches
@24 - All entries from 2024
[DEV] - All development entries
{PROMPT - All prompt-related entries
#A01 - Specific identifier
<V02> - All version 2 items
!H - All high priority items
*IP - All in-progress items
Combined Searches
@24.*IP - In-progress items from 2024
[DEV].*RV - Development items needing review
!H.*IP - High-priority in-progress items
Best Practices
Version Control Management
Version Incrementing Rules:
Increment for substantial changes
Use VXX for experiments
Document changes in description
Priority Management
Priority Assignment:
Default to !X when unclear
Review priorities weekly
Reserve !C for genuine emergencies
Status Tracking
Status Update Rules:
Update with each interaction
Document status changes
Regular status audits
Example Workflows
Development Cycle
// Initial Creation
@241107-[DEV]-{PROMPT.FUNC}-#A01-<V01>-!H-*IP: Initial design
// Review Phase
@241107-[DEV]-{PROMPT.FUNC}-#A01-<V02>-!H-*RV: Added features
// Completion
@241107-[DEV]-{PROMPT.FUNC}-#A01-<V03>-!M-*DN: Implementation complete
Research Cycle
// Initial Research
@241107-[RES]-{AI.ARCH}-#B01-<V01>-!M-*IP: Initial research
// Findings Review
@241107-[RES]-{AI.ARCH}-#B01-<V02>-!M-*RV: Preliminary findings
// Conclusion
@241107-[RES]-{AI.ARCH}-#B01-<V03>-!L-*DN: Research concluded
Maintenance and Governance
Schema Evolution
Modification Guidelines:
Document all schema changes
Maintain backward compatibility
Version the schema itself
Quality Control
Regular Audits:
Check for consistency
Update outdated entries
Archive completed items
Training and Adoption
New User Guidelines:
Start with basic format
Graduate to full schema
Regular usage reviews
Appendix
Quick Reference
Format: @YYMMDD-[CAT]-{TAG1.TAG2}-#ID-<V00>-!P-*S: Title
Categories: DEV, RES, PRJ, EXP, STD, ANA
Priorities: !C, !H, !M, !L, !X
Statuses: *IP, *DN, *RV, *BL, *AR, *HL, *XX
Change Log
Version Date Changes
1.0.0 2024-11-08 Initial release
1.1.0 2024-11-08 Added status codes
References
ISO 8601 Date Format
Semantic Versioning 2.0.0
ASCII Character Set Standards