.. meta::
   :description: AI overview of the Evolvix Syntax Design figure — prefix punctuation sequences forming the building blocks of the Evolvix language (Items, Types, Views, Links, Pipes, Flags, Tags, Walls, Wells, Lists).
   :keywords: STa1-EVX, Evolvix, syntax, prefix, punctuation, language design, Item, Type, View, Link, Pipe, Flag, Tag, Wall, Well, List, StayVS, LLoL, Good News Pack, MMv3
   :og:card:title: Syntax Design<br>Prefix Punct Symbol Gold
   :og:card:description: Core concepts for building Prefix Punctuation Sequences in Evolvix — 28 building blocks from Items and Types to Walls and Lists.


.. title:: EVX Syntax Design — Prefix Punct


****************************************************************************************************
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.*


.. admonition:: Download the original document (PDF)
   :class: note

   `Syntax Design — Prefix Punct Symbol Gold — PDF (64 KB) </_file/pdf/gnp/mmv3/flyingscroll/transwarpkey/sta1-evx/evx-syntax-design-prefix-punct-symbol-gold-iv_llol_qqv1_2020m01d17-fig.pdf>`__
   — 1 page, :doc:`Jonah License with CC0 Public Domain </license/joli/index>`

   Filename: ``evx-syntax-design-prefix-punct-symbol-gold-iv_llol_qqv1_2020m01d17-fig.pdf``

   `WebP preview (348 KB) </_file/pdf/gnp/mmv3/flyingscroll/transwarpkey/sta1-evx/evx-syntax-design-prefix-punct-symbol-gold-iv_llol_qqv1_2020m01d17-fig.webp>`__


.. image:: /_file/pdf/gnp/mmv3/flyingscroll/transwarpkey/sta1-evx/evx-syntax-design-prefix-punct-symbol-gold-iv_llol_qqv1_2020m01d17-fig.webp
   :alt: Evolvix Syntax Design — Prefix Punctuation Sequences building blocks
   :width: 100%
   :align: center


|


--- 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):**

- ``.i`` **Item** --- models what exists; links to 1 main Feature
- ``:i`` **Type** --- models what *may* exist; a Set of Rules
- ``@i`` **View** --- models what is measurable within a Boundary
- ``.i\.x`` **Name** --- defines .x as perfect synonym for .i
- ``~i`` **Dice** --- uncertainty affecting .i

**Connection Prefix Punctuation Sequences (lines 7--11):**

- ``_i`` **Link**, ``|i`` **Pipe**, ``..i`` **Role**, ``?i`` **Asks**

**Individualization Prefix Punctuation Sequences (lines 12--15):**

- ``$i`` **Uses** (plans/resources), ``&i`` **Flag** (switches), ``%i`` **Spec** (machine customization)

**Documentation Prefix Punctuation Sequences (lines 16--18):**

- ``#i`` **Tag** (searchable marks), ``!i`` **Info** (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**,
  :literal:`\`` **Glue** (genitive), ``¹i`` **Word** (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
==========================

.. list-table::
   :widths: 30 70
   :header-rows: 0

   * - **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
=====================

.. list-table::
   :widths: 30 70
   :header-rows: 0

   * - **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**
     - :doc:`Jonah License with CC0 Public Domain </license/joli/index>`
   * - **Part of**
     - Good News Pack MMv3, Flying Scroll / Transwarp Key / STa1-EVX
   * - **PDF size**
     - 64 KB
   * - **WebP size**
     - 348 KB

Related documents:

- :doc:`STa1-EVX stadium overview <../sta1-evx>` (parent page with all 30 documents)
- :doc:`Best Naming Intro <evx-naming-intro>` (the BESTnaming dialects that use these prefixes)
- :doc:`Fox-Rabbit Forecast Manual <evx-forecast-manual>` (working Evolvix code using a subset of this syntax)


--- Overview AI-generated by dv_ClaOp46Max_ExhH_2026m04d16 ---End---


.. ----- FOOTER FORM dv_ClaOp46Max_ExhH ----- type open-std ----- START -----

.. |content-vvn| replace:: dv_ClaOp46Max_ExhH_2026m04d16

.. include:: /_templates/include-file/footer/separator/tidal-gradient.rst

.. dropdown:: Notes
   :class-container: page-footer-form-notes
   :class-title: page-footer-form-title

   .. include:: /_templates/include-file/footer/page-footer-stability.rst


.. only:: html

   .. include:: /_templates/include-file/footer/cta/gnp-mmv3-review.rst

   .. dropdown:: FF FeedbackFlow to improve this page: How you can contribute
      :class-container: page-footer-form-feedbackflow
      :class-title: page-footer-form-title

      .. include:: /_templates/include-file/footer/form-open-std/prelink.rst

      .. ----- PAGE-SPECIFIC FF (ff-email MailForm=OOv2r0p0) ----- START -----

      .. raw:: html

         <a class="ff-email-preview-link" href="mailto:FF+mmv3-twk-sta1-evx-syntax-design@balospe.com?cc=FF%2BCompleteFeedbackFlow%40balospe.com&amp;subject=FF%20k2%20s2%20AIMS%20for%20%5Bmmv3-twk-sta1-evx-syntax-design%5D%20Replace_by_OneLineSummary_of_proposed_FF_improvement&amp;body=To%20make%20this%20page%20%5Bmmv3-twk-sta1-evx-syntax-design%5D%0D%0Amore%20gentle%20kind%20reasonable%0D%0Afor%20beginners%2C%20producers%2C%20andOr%20experts%0D%0Awith%20a%20background%20in%20xyz%3A%0D%0A%0D%0APlease%20consider%20improving%20this%3A%0D%0A%0D%0A%0D%0A--%0D%0ABy%20sending%20this%20email%2C%20I%20agree%20that%20its%20content%20may%20be%20published%0D%0Aunder%20the%20Jonah%20License%20(balospe.com%2Fen%2Flicense%2Fjoli%2F)%0D%0Aunless%20I%20state%20otherwise%20above.%20MailForm%3DOOv2r0p0">To:      FF+mmv3-twk-sta1-evx-syntax-design@balospe.com
         CC:      FF+CompleteFeedbackFlow@balospe.com
         Subject: FF k2 s2 AIMS for [mmv3-twk-sta1-evx-syntax-design] Replace_by_OneLineSummary
         Body:    To make this page [mmv3-twk-sta1-evx-syntax-design]
                  more gentle kind reasonable
                  for beginners, producers, andOr experts
                  with a background in xyz:

                  Please consider improving this:

                  --
                  By sending this email, I agree that its content may be published
                  under the Jonah License (balospe.com/en/license/joli/)
                  unless I state otherwise above. MailForm=OOv2r0p0</a>

      .. ----- PAGE-SPECIFIC FF ----- END -----

      .. include:: /_templates/include-file/footer/form-open-std/postlink.rst


.. ----- FOOTER FORM dv_ClaOp46Max_ExhH ----- END -----