RTT Badge Suffix Convention 🏷️
(Fork‑Safe Lineage Signaling)
The RTT Baseline badge may be extended with suffixes to indicate how a fork extends or specializes RTT concepts.
Suffixes are descriptive, not evaluative.
They signal direction, not authority.
Core Rule#
All suffixes follow this pattern:
RTT-baseline+<suffix>The RTT-baseline prefix must remain intact.
Approved Suffix Categories#
🔬 Simulation & Modeling#
Used when RTT is extended into simulation, replay, or modeling domains.
| Suffix | Meaning |
|---|---|
+sim |
Simulation‑focused fork |
+rsm |
Resonance Substrate Modeling integration |
+vst |
validated Spacetime integration |
+replay |
System behavior replay / analysis |
Example:
RTT-baseline+vst🧠 Systems & OS Extensions#
Used when RTT is extended deeper into system behavior.
| Suffix | Meaning |
|---|---|
+kernel |
Deeper kernel instrumentation |
+sched |
Scheduler‑focused exploration |
+memory |
Memory corridor specialization |
+io |
I/O or boundary‑focused work |
Example:
RTT-baseline+kernel🎓 Education & Teaching#
Used for learning‑oriented forks.
| Suffix | Meaning |
|---|---|
+edu |
Teaching / classroom fork |
+lab |
Guided experiments |
+sandbox |
Safe exploration environment |
Example:
RTT-baseline+edu🧪 Experimental Directions#
Used for speculative or exploratory work.
| Suffix | Meaning |
|---|---|
+exp |
Experimental concepts |
+proto |
Early prototype |
+alt |
Alternative interpretation |
Example:
RTT-baseline+expMultiple Suffixes 🔗#
Multiple suffixes may be chained sparingly:
RTT-baseline+vst+eduRules:
- Maximum of two suffixes recommended
- Order from structural → contextual
- Avoid novelty stacking
If it starts to look clever, simplify 😄
What Suffixes Must Not Do 🚫#
Suffixes must not:
- imply correctness or superiority
- redefine RTT itself
- obscure lineage
- replace the
RTT-baselineprefix
Examples to avoid:
RTT-advancedRTT-certifiedRTT-officialRTT-true
RTT has no “official” forks — only honest ones.
Visual Style (Optional)#
Suffixes may:
- use a lighter accent color
- appear after a
+ - remain visually subordinate to
RTT-baseline
The baseline always leads.
Why This Convention Works#
- Preserves RTT as the anchor
- Encourages exploration without fragmentation
- Makes forks legible at a glance
- Avoids governance or gatekeeping
- Scales across repos and time
It answers:
What direction did this fork take?
without answering: Which one is better?