Home /Modules/docs/README.IE.md

README.IE.md

docs/i18n/README.IE.md · 812 line(s) · markdown

<img align="right" src="../../images/sleela/sleela-medium-profile-permanent-icon-002.jpg" width="45" height="45" alt="SLeeLa">

SLeeLa 3.0 — Ireland (IE)

International country edition. This file groups the language editions selected for Ireland in one country-specific README.

English

SLeeLa is a native systems programming language, compiler, runtime, and virtual-machine ecosystem. This edition is for readers in Ireland.

Gaeilge

Is teanga ríomhchláraithe córas dúchasach í SLeeLa, lena n-áirítear tiomsaitheoir, timpeallacht rite agus éiceachóras meaisíní fíorúla.


Treoir theicniúil i nGaeilge

A. Tógáil agus tástáil

Is é SLEELA.syntax an príomhthagairt do chomhréir na teanga. Ba cheart d’fhorbróirí an leagan den tiomsaitheoir agus an leagan den chomhréir foinseach a idirdhealú: ní hionann iad, agus ní gá go mbeadh gach gné de chuid na sonraíochta ar fáil i ngach leagan den tiomsaitheoir.

Ó fhréamh an stórtha, úsáid na horduithe seo de réir mar is cuí:

make
make -C impl all
bash ./test-suites/run-all.sh --all

Is féidir le spriocanna coitianta Make cabhrú le tógáil agus glanadh:

make all
make registry
make tests
make ballum
make help
make clean

Ní chruthaíonn tógáil rathúil aon chomhpháirte amháin go bhfuil gach leabharlann nó gach ardán réidh le heisiúint. Ba cheart torthaí na dtástálacha a cheangal leis an tiomantas Git, leis an gcóras oibriúcháin agus leis an slabhra uirlisí a úsáideadh. Níor cheart tástálacha a scipeáladh ná tástálacha nár ritheadh a thuairisciú mar thástálacha rathúla.

B. Suiteáil

Tacaíonn an tionscadal le suiteáil ar fud an chórais, le suiteáil faoi chuntas úsáideora agus le fréamh ullmhúcháin do phacáistí:

sudo make install
make install PREFIX="$HOME/.local"
make install DESTDIR="$PWD/package-root"
make install-check

Is gnách go n-úsáideann suiteáil chórais /usr/local/bin, /usr/local/lib/sleela agus /usr/local/share/sleela. Le PREFIX="$HOME/.local", suiteáiltear faoi eolaire an úsáideora agus ní bhíonn sudo riachtanach de ghnáth. Cruthaíonn DESTDIR crann comhad sealadach le haghaidh pacáistithe; ní hionann é agus suiteáil dhíreach ar an gcóras óstach.

Lean an treoir suiteála agus na treoracha don ardán ar leith. Ná bain comhaid nach bhfuil cláraithe ag an suiteálaí mar chuid den tsuiteáil.

C. Teanga, tiomsaitheoir agus timpeallacht rite

Cuimsíonn SLeeLa tiomsaitheoir, timpeallacht rite, meaisíní fíorúla, leabharlanna agus uirlisí doiciméadaithe. Tá cód dúchasach C agus C++ sa stór chomh maith le modúil SLeeLa. Nuair a thrasnaíonn glao teorainn idir cód dúchasach agus an timpeallacht rite, ní mór conradh ABI na comhpháirte a leanúint.

Is iad na céimeanna tipiciúla sa phíblíne ná anailís foclóireachta, parsáil, anailís shéimeantach, ísliú go hionadaíocht idirmheánach, giniúint cód agus forghníomhú ar an meaisín fíorúil. Ba cheart tástálacha a dhearadh do gach céim agus do na teorainneacha eatarthu; ní leor tástáil a dhéanann seiceáil ar chomhréir amháin chun cruinneas an chláir iomláin a dhearbhú.

D. Conarthaí API agus modúil

Ba cheart do gach API poiblí na hionchuir a nglacann sé leo, na haschuir a thugann sé ar ais, na hearráidí a d’fhéadfadh tarlú, rialacha úinéireachta cuimhne agus fo-iarmhairtí a shonrú. Ba cheart doiciméadú modúil na réamhriachtanais, na hiar-choinníollacha agus na srianta ardáin a lua go soiléir.

Ní hionann ainm siombail ná tagairt do mhodúl agus údarú chun cód a fhorghníomhú. Caithfear údarú agus teorainneacha forghníomhaithe a sheiceáil ag an teorainn chuí. Ba cheart go dteipfeadh ar oibríocht go sábháilte má bhíonn ionchur neamhbhailí, acmhainn ar iarraidh nó comhpháirt neamhthacaithe aici.

E. Tástáil athchéimnithe agus in-atáirgtheacht

Ba cheart don tsraith tástála cásanna dearfacha agus diúltacha a chlúdach: comhaid fhoinseacha bhailí, earráidí parsála, sárú rialacha cineáil, teipeanna ísliúcháin, aschur cód agus torthaí forghníomhaithe. I gcás comhtháthaithe dúchasaigh, ba cheart comhaontú ABI, láimhseáil earráidí agus glanadh acmhainní a thástáil freisin.

Taifead an t-ardán, leagan an tiomsaitheora, leagan na n-uirlisí agus an tiomantas Git a úsáideadh. Ba cheart go mbeadh torthaí athdhéanta inchomparáide agus go mbeadh aon tástáil scipeáilte le feiceáil sa tuairisc. Féach ar bheartas tástála agus ar mhaitrís tacaíochta ardán.

F. Logánú agus cothabháil na Gaeilge

Coinnigh ainmneacha comhad, aitheantóirí, orduithe, cosáin, URLanna, samplaí cód agus ainmneacha API mar atá siad sa bhunleagan. Aistrigh an míniú timpeall orthu, ní na teaghráin a chaithfidh an tiomsaitheoir nó an bhlaosc a aithint. Úsáid téarmaíocht chomhsheasmhach do “compiler”, “runtime”, “virtual machine”, “module” agus “API”; nuair nach bhfuil téarma Gaeilge soiléir nó cobhsaí ann, tabhair an téarma teicniúil Béarla idir lúibíní ar an gcéad úsáid.

Is cuid den obair leanúnach í an t-aistriúchán. Nuair a athraítear an README canónach, déan comparáid idir na hailt chomhfhreagracha agus nuashonraigh an leagan Gaeilge. Níor cheart an leagan seo a mheas mar athbhreithniú teanga deiridh: moltar athbhreithniú ó chainteoir líofa Gaeilge agus athbhreithniú teicniúil ar leith.


Full English technical reference

SLeeLa 3.0 — Ireland (IE)

<p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>

<p align="center"><strong>A native systems language, compiler, runtime, and virtual-machine ecosystem.</strong></p>

Complete English technical edition for readers in Ireland. The full project documentation, code examples, build and installation instructions, API references, and release notes are reproduced. Technical identifiers and repository-relative links are unchanged.

<p align="center"><a href="https://github.com/mearvk/SLeeLa/actions"><img alt="GitHub Actions" src="https://img.shields.io/github/actions/workflow/status/mearvk/SLeeLa/test-suite.yml?branch=main&label=test%20suite"></a> <a href="../../docs/PLATFORM-SUPPORT.md"><img alt="Platform matrix" src="https://img.shields.io/badge/platforms-Linux%20%7C%20macOS%20%7C%20Windows-273238"></a></p>

The Now. The Ingredient. A language is more than syntax: it is the compiler, runtime, libraries, tools, and platform contracts that make software usable.

What SLeeLa is involved in. SLeeLa is involved in Math, Object, Science, and Reach — the four faces of its work: the calculable (Math), the settled thing standing in the catalogue of what is (Object), the disciplined study of the true (Science), and the extension of a system's hand to other systems and people (Reach). National Interests remain — they are not set aside by any of the four; where a subject bears on a nation's interest, that standing is kept (recorded faithfully, e.g. in each class's Metadata metaOrigin / metaNationalSchedule), never dissolved.

I. Start Here

II. News

Recent additions to the language, drivers, and standard library:

III. Build and Test

Prerequisites: a C/C++ toolchain (GCC or Clang) and GNU Make; Python 3 for the manifest/flow tooling; on Linux the X11/Xrandr development packages for the display products (a module's make deps reports/installs what it needs). The impl/ build is fail-closed on a trusted SHA-256 manifest, which the root Makefile points at automatically.

From a clean checkout, the quickest start:

make                                  # build everything from the repo root

Or build and test just the native core:

make -C impl all                      # build the core compiler/runtime only
bash ./test-suites/run-all.sh --all   # run the full test suite

The repo-root make builds every product (core, VM, codecs, churn, antivirus, …) and ends by building the registry and materializing its baseline table — so a built tree ships a reviewable registry out of the box. The essential targets:

make                     # build everything (alias of `make all`; registry runs last)
make all                 # the same full build, named explicitly
sudo make install        # install commands + runtime support (see §IV)
make clean               # remove build outputs from every dispatched build system
make help                # list every target the root Makefile provides

Other useful targets:

make registry            # just the registry: build + materialize the table
./build-registry.sh      # same thing, invoked directly
make tests               # build and run the test suite
make ballum              # build the Ballum display library for this OS (see ballum/)
bin/install-modules      # paced install/build of each module over ~10-20 min (see bin/)

The registry target runs build-registry.sh: it builds the registry core, seeds the baseline table into the portable text store registry/build/sleela.sleelareg, and exports the MySQL table script registry/build/registry.sql (via sleela registry export). Review it with sleela registry or registry/build/sleela-registry review. See the registry guide and Registry 3.0 architecture.

Consult the build and testing guides for prerequisites and platform-specific steps. A successful build of one component does not prove every library or platform is release-ready.

IV. Install

After building the native products, install the commands and runtime support files:

sudo make install
make install PREFIX="$HOME/.local"       # user-local install, no sudo
make install DESTDIR="$PWD/package-root" # staged package install
make install-check

The conventional installer uses /usr/local/bin, /usr/local/lib/sleela, and /usr/local/share/sleela by default. It preserves an existing startup configuration and refuses to overwrite untracked existing commands. Uninstall removes only files recorded by the installer, preserving configuration and untracked runtime data.

For a focused, guided deployment of just the main package — the sleela, sleelvac, and nordshrift binaries, the standard library, protocols, and support modules — use the clean installer:

make clean-install       # guided install of the main package only

It makes one primary decision (install the main package), then a scope choice, then on success an optional picker for curated enhancement modules. For the interactive deployment workflow and all installation options, see Quick and Safe Install.

V. Language and Runtime

The authoritative grammar is SLEELA.syntax. The current repository documents syntax 3.0; compiler/tool version and source syntax version are distinct. The 3.0 surface adds the pure and gasoline document markers (§30) — a pair of bare, contextual, declarative-only Preonems that mean nearly the same thing, each marking the document’s standing by its own honesty. Syntax 3.0 consolidates the 1.0–2.9 language surface into the current normative edition, preserving all feature-specific minimum gates. The prior 2.9 surface adds @mix consequent fields (§28) — a class may declare multiple same-named instance fields when each carries @mix, understood as one indexed group (top-down 1,2,3,… or manual @mix(1,2,3,...) whose index count must match the group). It carries forward the base-2 signed/unsigned wide-integer families int32..int16777216 (§24) and uint32..uint16777216 (§25) over the earlier long/int64/int128 (§21); keyword supporter documents (§22); and the Preonems — the declarative-only document markers author/authorial (§18), material/memory (§19–§20), determine (§23), object/field (§26), pure/gasoline (§30), and artifact (§35, legislature-grade standing graded unto time and space), collectively titled the Preonems (§26.1). Constructor overload resolution and this(...)/base-constructor delegation are explicitly outside the verified syntax 1.8 contract. Consult the grammar and implementation notes before relying on a feature. SleelaDoc's nine source units now declare #sleela 3.0; the shared compiler gate accepts source syntax 1.0–3.0. The new API build is produced by make api-docs.

The repository includes a native C/C++ implementation, SLVM generation references, standard-library modules, tests, examples, and platform integrations. Implementation and validation status varies by module; consult its specification and current CI results rather than assuming uniform completeness.

VI. Engineering Principles

VII. Antivirus Build and Integrity

The Sleelavirin antivirus package includes a native SHA-256 scanner, an optional ClamAV adapter, source/index integrity manifests, and platform-package checksums. Build and test the package from the repository root:

make antivirus
make antivirus-test
make antivirus-integrity
make antivirus-integrity-check MANIFEST=build/INTEGRITY-MANIFEST.json

The integrity manifest is generated under antivirus/build/; it covers tracked source and documentation inputs plus protected signature-index files, while excluding generated output and the mutable ClamAV cache. ClamAV database snapshots have their own manifests. Release ZIPs include INTEGRITY-MANIFEST.json, SHA256SUMS, and a .sha256 sidecar. Verify downloaded archive hashes against a trusted value obtained independently: a checksum stored beside an archive is not a publisher signature. See the Sleelavirin guide, security checklist, and antivirus build workflow.

A release is not considered verified until the relevant CI jobs pass on the exact release commit and the resulting artifacts have been checked.

VIII. SLeeLa Editor Themes — Vim and Emacs

SLeeLa includes a coordinated set of professional dark color schemes for Vim and Emacs, plus a native C/C++ palette utility. The original American Professional scheme remains the default. Ten companion palettes are available for different cultural and institutional design inspirations; these are interpretive design palettes, not official representations of any nation, culture, court, or institution.

The Eleven Schemes and Their Colors

SchemeBackgroundForegroundKeywordsTypesStringsComments
American Professional<span style="display:inline-block;width:1em;height:1em;background:#101820;border:1px solid #888"></span> #101820<span style="display:inline-block;width:1em;height:1em;background:#F4F7FA;border:1px solid #888"></span> #F4F7FA<span style="display:inline-block;width:1em;height:1em;background:#7FB3FF;border:1px solid #888"></span> #7FB3FF<span style="display:inline-block;width:1em;height:1em;background:#73DACA;border:1px solid #888"></span> #73DACA<span style="display:inline-block;width:1em;height:1em;background:#F2C078;border:1px solid #888"></span> #F2C078<span style="display:inline-block;width:1em;height:1em;background:#8A96A3;border:1px solid #888"></span> #8A96A3
Pan-Eurasian<span style="display:inline-block;width:1em;height:1em;background:#111827;border:1px solid #888"></span> #111827<span style="display:inline-block;width:1em;height:1em;background:#F0F2F5;border:1px solid #888"></span> #F0F2F5<span style="display:inline-block;width:1em;height:1em;background:#7AA7E8;border:1px solid #888"></span> #7AA7E8<span style="display:inline-block;width:1em;height:1em;background:#69C9B3;border:1px solid #888"></span> #69C9B3<span style="display:inline-block;width:1em;height:1em;background:#D7B56D;border:1px solid #888"></span> #D7B56D<span style="display:inline-block;width:1em;height:1em;background:#8995A5;border:1px solid #888"></span> #8995A5
Russian and Slavic — Medium<span style="display:inline-block;width:1em;height:1em;background:#202733;border:1px solid #888"></span> #202733<span style="display:inline-block;width:1em;height:1em;background:#E8EAF0;border:1px solid #888"></span> #E8EAF0<span style="display:inline-block;width:1em;height:1em;background:#A9C0DD;border:1px solid #888"></span> #A9C0DD<span style="display:inline-block;width:1em;height:1em;background:#8FC4B2;border:1px solid #888"></span> #8FC4B2<span style="display:inline-block;width:1em;height:1em;background:#D6BD8B;border:1px solid #888"></span> #D6BD8B<span style="display:inline-block;width:1em;height:1em;background:#9AA3AF;border:1px solid #888"></span> #9AA3AF
Central Asian / Silk Road<span style="display:inline-block;width:1em;height:1em;background:#1C2529;border:1px solid #888"></span> #1C2529<span style="display:inline-block;width:1em;height:1em;background:#F5F0E5;border:1px solid #888"></span> #F5F0E5<span style="display:inline-block;width:1em;height:1em;background:#7FADE0;border:1px solid #888"></span> #7FADE0<span style="display:inline-block;width:1em;height:1em;background:#45C6C2;border:1px solid #888"></span> #45C6C2<span style="display:inline-block;width:1em;height:1em;background:#D9B56D;border:1px solid #888"></span> #D9B56D<span style="display:inline-block;width:1em;height:1em;background:#92A3A0;border:1px solid #888"></span> #92A3A0
East Asian<span style="display:inline-block;width:1em;height:1em;background:#171A1C;border:1px solid #888"></span> #171A1C<span style="display:inline-block;width:1em;height:1em;background:#F2EFE7;border:1px solid #888"></span> #F2EFE7<span style="display:inline-block;width:1em;height:1em;background:#D97878;border:1px solid #888"></span> #D97878<span style="display:inline-block;width:1em;height:1em;background:#72C7A5;border:1px solid #888"></span> #72C7A5<span style="display:inline-block;width:1em;height:1em;background:#D8B76A;border:1px solid #888"></span> #D8B76A<span style="display:inline-block;width:1em;height:1em;background:#969F9B;border:1px solid #888"></span> #969F9B
ICC — International Criminal Court<span style="display:inline-block;width:1em;height:1em;background:#0E1A2B;border:1px solid #888"></span> #0E1A2B<span style="display:inline-block;width:1em;height:1em;background:#EAF0F7;border:1px solid #888"></span> #EAF0F7<span style="display:inline-block;width:1em;height:1em;background:#5B8FD6;border:1px solid #888"></span> #5B8FD6<span style="display:inline-block;width:1em;height:1em;background:#7FB7C9;border:1px solid #888"></span> #7FB7C9<span style="display:inline-block;width:1em;height:1em;background:#D9B25A;border:1px solid #888"></span> #D9B25A<span style="display:inline-block;width:1em;height:1em;background:#7E8CA0;border:1px solid #888"></span> #7E8CA0
SCOTUS — U.S. Supreme Court<span style="display:inline-block;width:1em;height:1em;background:#1A1416;border:1px solid #888"></span> #1A1416<span style="display:inline-block;width:1em;height:1em;background:#F3EEE6;border:1px solid #888"></span> #F3EEE6<span style="display:inline-block;width:1em;height:1em;background:#9E2B35;border:1px solid #888"></span> #9E2B35<span style="display:inline-block;width:1em;height:1em;background:#8FA9B8;border:1px solid #888"></span> #8FA9B8<span style="display:inline-block;width:1em;height:1em;background:#C9A24B;border:1px solid #888"></span> #C9A24B<span style="display:inline-block;width:1em;height:1em;background:#8C8178;border:1px solid #888"></span> #8C8178
Greek (Hellenic)<span style="display:inline-block;width:1em;height:1em;background:#0A1A30;border:1px solid #888"></span> #0A1A30<span style="display:inline-block;width:1em;height:1em;background:#FFFFFF;border:1px solid #888"></span> #FFFFFF<span style="display:inline-block;width:1em;height:1em;background:#2E7BD6;border:1px solid #888"></span> #2E7BD6<span style="display:inline-block;width:1em;height:1em;background:#5E9FE0;border:1px solid #888"></span> #5E9FE0<span style="display:inline-block;width:1em;height:1em;background:#9FC3EC;border:1px solid #888"></span> #9FC3EC<span style="display:inline-block;width:1em;height:1em;background:#6E86A6;border:1px solid #888"></span> #6E86A6
Turkish (Al Bayrak)<span style="display:inline-block;width:1em;height:1em;background:#2A0609;border:1px solid #888"></span> #2A0609<span style="display:inline-block;width:1em;height:1em;background:#FFFFFF;border:1px solid #888"></span> #FFFFFF<span style="display:inline-block;width:1em;height:1em;background:#F23D48;border:1px solid #888"></span> #F23D48<span style="display:inline-block;width:1em;height:1em;background:#F0A9AE;border:1px solid #888"></span> #F0A9AE<span style="display:inline-block;width:1em;height:1em;background:#F0C9A9;border:1px solid #888"></span> #F0C9A9<span style="display:inline-block;width:1em;height:1em;background:#A8767A;border:1px solid #888"></span> #A8767A
Kiro<span style="display:inline-block;width:1em;height:1em;background:#0B0B12;border:1px solid #888"></span> #0B0B12<span style="display:inline-block;width:1em;height:1em;background:#F5F5FA;border:1px solid #888"></span> #F5F5FA<span style="display:inline-block;width:1em;height:1em;background:#A98EDA;border:1px solid #888"></span> #A98EDA<span style="display:inline-block;width:1em;height:1em;background:#6E8BE0;border:1px solid #888"></span> #6E8BE0<span style="display:inline-block;width:1em;height:1em;background:#E8C547;border:1px solid #888"></span> #E8C547<span style="display:inline-block;width:1em;height:1em;background:#6A6482;border:1px solid #888"></span> #6A6482
SLeeLa<span style="display:inline-block;width:1em;height:1em;background:#08080E;border:1px solid #888"></span> #08080E<span style="display:inline-block;width:1em;height:1em;background:#FFFFFF;border:1px solid #888"></span> #FFFFFF<span style="display:inline-block;width:1em;height:1em;background:#B07CFF;border:1px solid #888"></span> #B07CFF<span style="display:inline-block;width:1em;height:1em;background:#5A7CFF;border:1px solid #888"></span> #5A7CFF<span style="display:inline-block;width:1em;height:1em;background:#FFD21E;border:1px solid #888"></span> #FFD21E<span style="display:inline-block;width:1em;height:1em;background:#6E5F9E;border:1px solid #888"></span> #6E5F9E

National flag colours (source palette)

The Greek and Turkish schemes are derived from the two countries' official national flag colours, shown here with their exact published hex values. The scheme backgrounds/accents above are darkened, editor-friendly interpretations of these source colours — the table below is the "colors as nationally exposed" reference.

NationColourHexBasis and meaning
GreeceBlue<span style="display:inline-block;width:1em;height:1em;background:#0D5EAF;border:1px solid #888"></span> #0D5EAFNational flag blue (Law 851/1978). The sky and the seas; blazoned heraldically as azure.
GreeceWhite<span style="display:inline-block;width:1em;height:1em;background:#FFFFFF;border:1px solid #888"></span> #FFFFFFNational flag white. Purity of the independence struggle; the cross denotes Eastern Orthodox Christianity.
TürkiyeRed (al bayrak)<span style="display:inline-block;width:1em;height:1em;background:#E30A17;border:1px solid #888"></span> #E30A17National flag red (Turkish Flag Law). The field; by tradition the blood of martyrs and Ottoman sovereignty.
TürkiyeWhite<span style="display:inline-block;width:1em;height:1em;background:#FFFFFF;border:1px solid #888"></span> #FFFFFFNational flag white. The crescent and star — peace, purity, and the Turkic/Islamic heritage symbol.

The schemes anchor each editor's foreground on the national white and its keywords, cursor, selection, and status line on the exact national blue (#0D5EAF) or red (#E30A17), so the colours that matter are literally the national colours. These are interpretive design palettes; the flag-colour reference is provided for provenance and is not an official representation of either state. Colour meanings follow the Hellenic Republic MFA state-symbols description and the Turkish Flag Law tradition.

Color Swatch Table

The palette cells below use SVG swatches, so GitHub renders the actual colors rather than empty HTML color cells. Each strip shows the six colors in this order: background, foreground, keywords, types, strings, and comments. The exact hex codes are listed beside each swatch, in the same scheme order as the reference table above.

SchemeRendered palette colorsHex codes (background · foreground · keywords · types · strings · comments)
American ProfessionalAmerican Professional palette: background, foreground, keywords, types, strings, comments#101820 · #F4F7FA · #7FB3FF · #73DACA · #F2C078 · #8A96A3
Pan-EurasianPan-Eurasian palette: background, foreground, keywords, types, strings, comments#111827 · #F0F2F5 · #7AA7E8 · #69C9B3 · #D7B56D · #8995A5
Russian and Slavic — MediumRussian and Slavic Medium palette: background, foreground, keywords, types, strings, comments#202733 · #E8EAF0 · #A9C0DD · #8FC4B2 · #D6BD8B · #9AA3AF
Central Asian / Silk RoadCentral Asian Silk Road palette: background, foreground, keywords, types, strings, comments#1C2529 · #F5F0E5 · #7FADE0 · #45C6C2 · #D9B56D · #92A3A0
East AsianEast Asian palette: background, foreground, keywords, types, strings, comments#171A1C · #F2EFE7 · #D97878 · #72C7A5 · #D8B76A · #969F9B
ICC — International Criminal CourtICC palette: background, foreground, keywords, types, strings, comments#0E1A2B · #EAF0F7 · #5B8FD6 · #7FB7C9 · #D9B25A · #7E8CA0
SCOTUS — U.S. Supreme CourtSCOTUS palette: background, foreground, keywords, types, strings, comments#1A1416 · #F3EEE6 · #9E2B35 · #8FA9B8 · #C9A24B · #8C8178
Greek (Hellenic)Greek Hellenic palette: background, foreground, keywords, types, strings, comments#0A1A30 · #FFFFFF · #2E7BD6 · #5E9FE0 · #9FC3EC · #6E86A6
Turkish (Al Bayrak)Turkish Al Bayrak palette: background, foreground, keywords, types, strings, comments#2A0609 · #FFFFFF · #F23D48 · #F0A9AE · #F0C9A9 · #A8767A
KiroKiro palette: background, foreground, keywords, types, strings, comments#0B0B12 · #F5F5FA · #A98EDA · #6E8BE0 · #E8C547 · #6A6482
SLeeLaSLeeLa palette: background, foreground, keywords, types, strings, comments#08080E · #FFFFFF · #B07CFF · #5A7CFF · #FFD21E · #6E5F9E

Additional accent colors are used for functions, constants, selections, diagnostics, and preprocessor directives. The Russian and Slavic palette intentionally uses medium-intensity slate, blue, sage, ruby, and antique gold for a calmer professional appearance.

Install the Vim Schemes

From the repository root:

mkdir -p ~/.vim/{syntax,ftdetect,colors}
cp lib/linux-editors/vim/syntax/sleela.vim ~/.vim/syntax/
cp lib/linux-editors/vim/ftdetect/sleela.vim ~/.vim/ftdetect/
cp lib/linux-editors/vim/colors/sleela-*.vim ~/.vim/colors/

Add the following to ~/.vimrc to enable SLeeLa syntax highlighting and choose a scheme:

syntax enable
set background=dark
colorscheme sleela-american

Choose exactly one of these colorscheme names:

For example, use colorscheme sleela-russian-slavic for the medium Russian and Slavic palette, or colorscheme sleela-greek / colorscheme sleela-turkish for the Hellenic and Al Bayrak palettes. Restart Vim or source your configuration with :source $MYVIMRC.

Install the Emacs Schemes

Create a local theme directory and copy the mode and theme files from the repository root:

mkdir -p ~/.emacs.d/sleela
cp lib/linux-editors/emacs/sleela-mode.el ~/.emacs.d/sleela/
cp lib/linux-editors/emacs/sleela-*-theme.el ~/.emacs.d/sleela/

Add this to ~/.emacs or ~/.emacs.d/init.el:

(add-to-list 'load-path (expand-file-name "~/.emacs.d/sleela"))
(add-to-list 'custom-theme-load-path (expand-file-name "~/.emacs.d/sleela"))
(require 'sleela-mode)
(load-theme 'sleela-american t)

Replace sleela-american with sleela-eurasia, sleela-russian-slavic, sleela-silk-road, sleela-east-asian, sleela-greek, sleela-turkish, sleela-kiro, or sleela-sleela to select another scheme. If Emacs asks whether to trust the theme, inspect the local theme file before accepting it.

Preview the Native C/C++ Palettes

The small native palette utility can list schemes, print their terminal colors, and look up an individual color:

make -C linux-editors
./linux-editors/build/sleela-editor-theme --themes
./linux-editors/build/sleela-editor-theme --theme eurasia --palette
./linux-editors/build/sleela-editor-theme --theme russian-slavic --hex keyword
make -C linux-editors test

For backward compatibility, --palette and --hex COLOR without --theme select American Professional. Build and test results should be checked on the target system and CI; documentation of a command is not itself evidence that it passed.

See the editor integration guide for the full palette descriptions and utility details.

IX. Contributing

  1. Read the documentation index and testing policy.
  2. Make focused changes with positive and negative tests.
  3. Run targeted tests, then the broad suite.
  4. Report OS/toolchain details; do not describe skipped checks as passing.

SLeeLa is developed by MEARVK LLC. Historical landing-page material is preserved in docs/README-LEGACY.md.

X. AE6E66 — Round Public Email Levy Expectation

For the AE6E66 initiative, the project's stated expectation is $300,000,000.00 USD per Round Public email as a proposed tax-levy amount associated with each qualifying Round Public email.

This statement records a project expectation only. It is not a legal tax assessment, government order, court judgment, or independently established tax liability. Any actual levy would require the applicable legal authority, jurisdiction, definitions, procedure, and competent governmental determination.

XI. Alphabet and Character-set Runtime

SLeeLa's alphabet documentation and native character runtime are maintained in alphabet/sleela/ and lib/alphabet/native/. The native C++17 tests cover strict UTF-8 scalar decoding/encoding, C<n> capacity signatures, and bounded character-set membership:

make -C lib/alphabet/native test

The experimental UTF-4088 catalogue and its SLeeLa lookup adapter are documented in utf-4088/SLeeLa-ALPHABET-INTEGRATION.md. UTF-4088 IDs are a separate namespace, not Unicode scalar values. Compiler and SLVM binding work is explicitly tracked separately from these native foundations.

XII. AutoCAD Creator™

The AutoCAD Creator™ is an interactive 2D CAD application written entirely in SLeeLa. Where the sibling AutoCAD Renderer turns a plan into a drawing in one shot, the Creator lets you create and alter a 2D AutoCAD document live — add walls, rooms, dimensions and notes, then move, relabel, re-layer, delete, and undo what you placed — and save the result as a real AutoCAD DXF drawing (R12 text, opens in AutoCAD / LibreCAD).

Its graphical interface is built on SleelaUI™, SLeeLa's own cross-platform UI toolkit (under lib/user-interface) — not JavaFX — raising a real native window on X11 / Cocoa / Win32. The design follows one rule, "SleelaUI presents; SLeeLa decides": the GUI never computes geometry or writes DXF. Every tool issues a create / alter / delete / undo / save intent to the authoritative SLCadCreator, which owns the editable document and a reversible command history, while the canvas only previews the geometry the Creator holds.

The reusable editing engine lives in lib/autocad — SLCadEntity, SLCadDocument, SLCadCommand, and SLCadCreator — and runs end to end headless. The GUI shell and demo live under autocad/creator:

make creator          # from autocad/: run the Creator demo -> out/altered.dxf

On a display this opens the live editing window; on a headless host it builds the drawing in memory, prints a report plus the DXF, and exits cleanly.

XIII. UTF-4088 Input-map Ordering

The specialized UTF-4088 catalogue defines its spatial input-map traversal and abstract pressure iterations in utf-4088/INPUT-MAP-AND-PRESSURE.md. The National Lien subject-index policy is in utf-4088/NATIONAL-LIEN-REGISTER.md. Map coordinates, pressure levels (1–50), permanent catalogue IDs, and alphabetic ranks are independent fields; none should be silently substituted for another. Pressure is an algorithmic iteration level, not a physical quantity.

XIV. Recent and Expanded Package Index

This appended index highlights recently expanded packages, domain libraries, and source collections. Entries are grouped alphabetically by package name or topic. Descriptions identify the repository location; implementation and validation status should be checked in each package's own documentation and tests.

A–C

D–G

H–I

O–S

U–W

Package-index Maintenance

When a package is added or materially expanded, add its entry here in the appropriate alphabetical group, link to its canonical directory and README, and describe only capabilities supported by the checked-in sources. Keep this index additive: do not remove or rewrite the existing README sections as part of package-index updates.


<img src="https://github.com/mearvk/SLeeLa/blob/master/images/debian-logo.png" width="25" height="25" alt="Debian"> XV. Bitcoin Conjegeum

CremeOak

bc1qs6v4q9zsw70t0umk3m0quhvf9dr6cdeskl28dh :: ⠝⠇⠼⠁⠟⠎⠼⠋⠧⠼⠙⠟⠼⠊⠵⠎⠺⠼⠛⠼⠚⠞⠼⠚⠥⠍⠦⠼⠉⠍⠼⠚⠟⠥⠓⠧⠦⠼⠊⠙⠫⠼⠋⠉⠙⠑⠎⠅⠇⠼⠼⠃⠼⠗⠙⠓

bc1qx33vma553gddsjkq372l3xlm8e8huv2vzad3cc :: ⠃⠉⠼⠁⠟⠭⠼⠉⠼⠉⠪⠍⠁⠼⠑⠑⠛⠙⠙⠎⠚⠅⠟⠼⠉⠼⠛⠼⠝⠇⠼⠉⠼⠭⠇⠍⠼⠨e⠼⠨a⠓⠥⠪⠼⠪⠼⠪⠵⠁⠙⠼⠉⠉

US Democratic and US Policy.


XVI. National Science Brand Imagery

<p align="center"><img src="https://raw.githubusercontent.com/mearvk/SLeeLa/master/brand/national-sleela-science-004.jpg" alt="National SLeeLa Science" width="560"></p>

<p align="center"><img src="https://raw.githubusercontent.com/mearvk/SLeeLa/master/brand/national-sleela-nsf-001.jpg" alt="National SLeeLa NSF" width="560"></p>

XVII. UTF-4088 Million-Entry Experimental Catalogue

The UTF-4088 catalogue generator deterministically builds a 1,048,576-entry experimental symbol catalogue. The documented compact format is described in utf-4088/FORMAT.md; the generation and validation contract is in utf-4088/GENERATION-RESULTS.md.

Run the generator with Python 3:

python3 utf-4088/tools/generate_catalogue.py \
  --output utf4088-million.bin \
  --summary utf4088-million.summary.json

The generated binary is 16,777,244 bytes and is designed to remain below 20,000,000 bytes. Unit tests and a GitHub Actions workflow verify entry count, glyph uniqueness, size, and SHA-256; successful runs publish the binary and summary as the utf4088-million-catalogue workflow artifact. The generated binary is deliberately kept out of Git history. UTF-4088 remains experimental and is not Unicode-compatible.


SLeeLa

<p align="center"><img src="../../images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>


XVIII. Recent Additions — Pi Constant, Modium/Registry Startup, sleelactl Math, and @native

This section records features added during the 2026-11 work, newest groups first. The linked source files and their validation status are authoritative; changes under review are not described as merged until they reach master.

The 100,000,000-digit Pi catalog constant

The repository ships a verified one-hundred-million-digit value of π at pi-generator/pi.100000000.digits (a well-formed decimal, 3.14159…), alongside a 57,344-digit value pi-generator/pi.57344.digits. Both are independently verified genuine π — see pi-generator/VERIFIED.md, which documents the checks (textbook prefix, the Feynman point at fractional position 762, the famous one-millionth digit, agreement with lib/math/SLPiReference.sleela, and a whole-file digit-frequency analysis) and a one-shot reproduction script.

Modium™ / Registry™ load the Pi constant at subsystem startup

On the dedicated subsystem entry points — sleela registry and sleela modium (and the installer first run), not on every sleela run — the Modium and Registry subsystems load the large π catalog constant. On an interactive terminal they print a transient red Loading Modium™ / Loading Registry™ line that is then erased in place before normal output begins; the effect is strictly TTY-gated, so piped and test output stay byte-for-byte unchanged. The locator (not the bytes) is seeded as the registry Math key defaults piReferenceLargePath and piReferenceLargeDigits, in both the SLeeLa model (lib/registry/SLRegistry.sleela) and the native seeder (registry/sleela_registry.c); lib/math/SLPiReference.sleela exposes largePath() / largeDigits(). The π constant is installed into the OS SLeeLa location (<data>/pi/) by both the standard make installer and the guided "beautiful" installer. Details: pi-generator/MODIUM-REGISTRY-PI-STARTUP.md.

sleelactl — the beautiful installer and a native-backed math subject

@native, Native Drive, and multi-language execution

A new @native method annotation requests ahead-of-time native compilation of a hot method. The new sleela aot command finds @native methods, verifies each is within a supported offloadable subset, and emits C/C++ — failing closed (refusing, with a precise reason) on any construct it cannot yet translate, so a half-translated method is never produced.

sleela aot --list <file.sleela>    # per-method verdict: ok / REFUSED (reason)
sleela aot --emit <file.sleela>    # emit C/C++ (stdout) for an in-subset program

@native remains a request for AOT treatment, with unsupported constructs rejected before emission. The Native Drive supports multi-unit C/C++ executable and shared-library builds through host compilers (including MSVC), supported SLeeLa AOT output, symbol inspection against the native-loader ABI, shell-free process execution, stdin/stdout/stderr handling, multi-stage piping, and XClass delegation to the production loader. sleelactl exposes its build/run commands and routes XClass inspection and explicit systemd unit rendering/installation through inspect native-drive. The VM owns a bounded native-module handle table with mandatory host authorization and generation-checked handles. Syntax 3.0 now adds nativeOpen, nativeCall, and nativeClose: append-only bytecode dispatch crosses a separately versioned null/bool/int64/double/UTF-8 ABI, while VM-owned arrays, structs, and other composite values stay inside the interpreter and may use same-name bytecode fallback. Plugins can optionally receive a versioned host callback table to invoke exact SLeeLa functions through nested VM execution, with suspended-stack GC rooting, an explicit host callback-name allowlist, and recursive native API calls rejected. Native code remains trusted in-process code, not a sandbox. Source process-policy annotations have a versioned schema but are not yet parsed/enforced. Details, security boundaries, and the seven-workstream ledger: Native Drive and pi-generator/AT-NATIVE.md.

XIX. International README Editions

SLeeLa provides country-specific README entry points for the 50 markets in its international edition. Each country has one file named README.<CC>.md; where multiple languages are relevant, they are grouped within that country's file.

Translation policy: These files are initial localized country entry points. Their introductions and language headings are localized, while the complete technical reference remains in the canonical English README.md. A country file must not be described as a complete translation until every section has been translated, technical identifiers and links have been checked, and the edition has received language review. Language coverage in this first pass is representative and is not a claim that every constitutionally recognized, regional, indigenous, or sign language has been fully translated.