Evolvix Syntax Design — Prefix Punctuation Symbol Gold#
The 28 building blocks of Evolvix syntax — from .Item and :Type through $Uses and &Flag to {Wall} and [List], each with Brief, Explicit, and Summarizing names.
Download the original document (PDF)
Syntax Design — Prefix Punct Symbol Gold — PDF (64 KB) — 1 page, Jonah License with CC0 Public Domain
Filename: evx-syntax-design-prefix-punct-symbol-gold-iv_llol_qqv1_2020m01d17-fig.pdf
— Overview AI-generated by dv_ClaOp46Max_ExhH_2026m04d16 —Start—
Abstract#
This single-page figure is the technical reference for Evolvix’s prefix punctuation system — the syntax design that makes all words available as keywords while users identify their names with meaningful prefixes. The table lists 28 building blocks organized in 5 categories, each with Brief prefix, Explicit concept name, Summarizing description, and StayVS version:
Item Prefix Punctuation Sequences (lines 1–6):
.iItem — models what exists; links to 1 main Feature:iType — models what may exist; a Set of Rules@iView — models what is measurable within a Boundary.i\.xName — defines .x as perfect synonym for .i~iDice — uncertainty affecting .i
Connection Prefix Punctuation Sequences (lines 7–11):
_iLink,|iPipe,..iRole,?iAsks
Individualization Prefix Punctuation Sequences (lines 12–15):
$iUses (plans/resources),&iFlag (switches),%iSpec (machine customization)
Documentation Prefix Punctuation Sequences (lines 16–18):
#iTag (searchable marks),!iInfo (human-only documentation)
Structural Prefix Punctuation Sequences (lines 19–28):
{}Wall (closed dictionary),()Well (open content form),[]List (set builder),'yz'Pile (unordered bag),"yz"Text (ordered sequence),,Chop,;Stop,`Glue (genitive),¹iWord (keyword)
Two design principles: (i) Evolvix reserves all words as keywords, requiring user names to have prefixes — this maximizes the namespace for growing keyword lists. (ii) Evolvix tracks formal stability milestones via StayVS for fast removal of avoidable complexity.
Key Concepts at a Glance#
Prefix-first design |
All user names require prefixes (.i, :i, @i, etc.), keeping all plain words available as Evolvix keywords |
Items, Types, Views |
The three modeling primitives: what exists (.i), what may exist (:i), what is measurable (@i) |
Dice (~i) |
Built-in uncertainty tracking at the syntax level |
Wall {} vs Well () |
Closed (no auto export/import) vs Open (auto import/export) scoping — controlling information flow at the syntax level |
Broader Significance (Claude’s Assessment)#
This is the most technically specific document in the collection. The prefix punctuation system solves a real language design problem: how to maintain a growing keyword vocabulary without collisions. By reserving all plain words as keywords and requiring user prefixes, Evolvix inverts the usual convention (where keywords are reserved and user names are free) — a design decision that supports long-term extensibility. The built-in uncertainty primitive (~i Dice) at the syntax level is unusual among programming languages and reflects Evolvix’s focus on biological modeling where uncertainty is not exceptional but fundamental.
Document Information#
Document ID |
EVX Syntax Design — Prefix Punct (Flying Scroll, transwarpkey/sta1-evx/) |
Author |
Laurence Loewe of Laodicea (LLoL) |
Date |
2020m01d17 |
Version |
iv_LLoL_QQv1_2020m01d17 |
Format |
Single-page reference table |
License |
Jonah License with CC0 Public Domain |
Part of |
Good News Pack MMv3, Flying Scroll / Transwarp Key / STa1-EVX |
PDF size |
64 KB |
WebP size |
348 KB |
Related documents:
STa1-EVX stadium overview (parent page with all 30 documents)
Best Naming Intro (the BESTnaming dialects that use these prefixes)
Fox-Rabbit Forecast Manual (working Evolvix code using a subset of this syntax)
— Overview AI-generated by dv_ClaOp46Max_ExhH_2026m04d16 —End—