Home /Modules/bin/SUPPOSITIONS.md

SUPPOSITIONS.md

bin/SUPPOSITIONS.md · 145 line(s) · markdown

bin/ — Suppositions

Status: suppositions, not a contract. This document records a working model of what the SLeeLa bin/ directory is supposed to hold and how it is supposed to behave. Items marked (shipped) exist today; items marked (supposed) are the intended direction and are not yet all wired. Treat the build system and bin/README.md as authoritative where they disagree.

1. The premise

Historically bin/ held only the POSIX launcher scripts. The premise here widens it: bin/ is the collection point for SLeeLa's runnable products — both

  1. the launcher/entry scripts (shipped today), and
  2. the compiled binaries produced when SLeeLa's C and C++ sources are built — whether an individual module is compiled, or the whole main SLeeLa program is built.

This is in addition to, not instead of, the normal binary-install locations a conventional install already uses:

ScopeLocation (example)Owner
User-local~/.local/bin, $XDG_BIN_HOMEthe user
System/usr/local/bin, /usr/binroot/admin
Repo profilethis bin/the SLeeLa tree

So a product can land in the repo's bin/ (for in-tree use and as the launcher's resolution target) and be installed to a user/system/local bin by the installer. The two are complementary: bin/ is the build/staging profile; the profile locations are the deployment targets.

2. How bin/ accepts C/C++ compilation output (supposed)

When a C/C++ build runs — a single module or the whole program — its linked executable is staged into bin/ under a stable name, so the launcher and the OS shell can find it next to the scripts:

Objects (.o) and static archives (.a) are not staged into bin/ — only final linked executables. Libraries/headers go to lib//include/ (or the pkg-config path), per the Ballum install pattern.

3. Supposed binaries in bin/

Grounded in what the build actually produces (see each Makefile). "Source" names the build that emits it.

3.1 Launcher / entry scripts — (shipped)

NameKindSourcePurpose
SLeeLaPOSIX shin-treeOS-terminal launcher: run a .sleela object/artifact, forward toolchain subcommands, set the catalog + SHA-256 gate
OSsupportPOSIX shin-treeOS Defender / native-support provisioning front end (sleela defender ...)
install-modulesPOSIX shin-treepaced iterative installer: walk every module and run its install/all, spread over ~10-20 min (drives bin/Makefile.modules)
Makefile.modulesMakefilein-treethe module-walk build logic the install-modules launcher drives
install-modules.shPOSIX shin-treethe paced-walk runner invoked by bin/Makefile.modules

3.2 Core toolchain binaries (whole-program C/C++ build) — (shipped as impl/build/*; supposed to stage into bin/)

Supposed bin/ nameBuilt asSourcePurpose
sleelaimpl/build/sleelamake -C implthe authoritative compiler/runtime (SLeeLa™ Language/Runtime; historically "Sleelvac™"), source syntax 1.0 – 3.1 — check/run/compile/native/vm/nordshrift/…
nordshriftimpl/build/nordshriftmake -C implthe Nordshrift .sst transpiler driver (NS-SST-0001 spec 2.2; check/build/objects/relevance). The SLeeLa→Nordshrift→back round-trip is sleela nordshrift.
sleelvacimpl/build/sleelvac (SLEELAVC_BIN)make -C implthe Sleelvac driver variant
sleela.exe / nordshrift.exeMinGW buildbuild-windows.ps1the Windows variants (the launcher already probes .exe)

3.3 Per-module native products — (supposed to stage into bin/ on build)

Supposed bin/ nameBuilt asSourcePurpose
ballum-demoballum/build/ballum-demomake -C ballum demolinked Ballum display demo (links the OS display libs — X11/Xrandr, Cocoa/CoreGraphics, or gdi32)
slvm-01 … slvm-11sleela-virtual-machine/0NN/vm-build/slvm-NNmake premium-vmsthe eleven premium SLVM generation runners
sleela-audio-nativeaudio buildmake -C audio (native)native audio bridge runner
sleela-gov-nativegov buildgovernance native buildnative governance runner
regex-*regex/build/*make -C regexregex engine C/C++ self-test/demo runners

3.4 OS Defender native backends (compiled C/C++, per host OS) — (supposed; provisioned by OSsupport)

These are the privileged native-support artifacts OSsupport/sleela defender fetches, builds, and installs. They are OS-native driver/module products, so they install into the OS's own privileged location rather than a plain bin/, but they are catalogued here as SLeeLa products of a C/C++ build.

Host OSBackend productBuildInstall target
Windows 10+Windows.Admin.Defender (signed WDK driver)WDK/MSVCdriver store (elevated)
LinuxLinux.Admin.Defender (kernel module)make installkernel module path (privileged)
macOSMacOS.Admin.Defender—detect only; no privileged backend

4. Resolution order (how the launcher finds a product) — (shipped)

bin/SLeeLa and bin/OSsupport resolve the sleela binary in this order:

  1. SLEELA_BIN (explicit override), if executable;
  2. bin/sleela / bin/sleela.exe (a staged copy next to the script);
  3. impl/build/sleela / impl/build/sleela.exe (the in-tree build).

This is exactly why staging compiled output into bin/ (step 2) is the supposed mechanism: it makes a freshly built product the one the launcher runs, without touching the user/system install.

5. Per-OS linking note

Compiled products that touch the display or the OS integrate the OS-centric libraries at link time (see ballum/ and GROFF.md-adjacent build notes):

The .pc (pkg-config) manifests that modules install record these in Libs.private, so a downstream link of a staged bin/ product picks them up.

6. Open questions (to resolve before promoting any of this to a contract)


Suppositions recorded for the bin/ profile. See bin/README.md for the shipped launcher behavior and each module's Makefile for what it actually builds.