GitHub - resendizkarlakaren/HEX: Lambda Nested Environments · GitHub
/" data-turbo-transient="true" />
Skip to content
Search/
Sign in<br>Sign upAppearance settings
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
resendizkarlakaren
HEX
Public template
Notifications<br>You must be signed in to change notification settings
Fork
Star
HEX
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>16 Commits<br>16 Commits
.github
.github
000-FLUX
000-FLUX
000-LIVE
000-LIVE
000-RUN
000-RUN
.gitignore
.gitignore
README.md
README.md
View all files
Repository files navigation
HEX
Experimental framework for formalizing, modeling, and executing transformations. HEX is an experimental environment for developing a formal system in which distinctions, relations, transformations, and their observable traces can be represented, manipulated, tested, and eventually executed.
❦ Status
Early development / conceptual architecture HEX is currently in an exploratory stage. Conceptual clarity takes precedence over implementation volume.
❦ What is HEX?
HEX is an attempt to build a system capable of moving between:
Concepts ➜ Representation ➜ Operation ➜ Traceability ➜ Model ➜ Evidence
The objective is not merely to create another programming language or simulation framework. HEX explores whether a minimal formal vocabulary can describe how configurations become different configurations while remaining:
➜ representable<br>➜ composable<br>➜ executable<br>➜ observable<br>➜ testable<br>➜ comparable
❦ Branch Structure & Workflow
HEX is organized into multiple branches, each representing a distinct experimental channel:
HEX 𖣂 Stable nucleus, consolidated version.
RUN ➜ Laboratory of performative execution.<br>LIVE ➜ Laboratory of real-time interaction.<br>FLUX ➜ Laboratory of dynamic change.
Workflow: RUN / LIVE / FLUX → HEX
This modular branching structure allows experimentation without compromising stability. Each branch embodies a conceptual role, while HEX remains the reference point for consolidated work.
❦ Languages & Tools
Each branch is associated with a language or tool that reinforces its conceptual role. This is of course Optional.
HEX ➜ TypeScript + Markdown (solidity, documentation clarity).<br>RUN ➜ Rust (secure, performant execution).<br>LIVE ➜ p5.js / Processing (interactive visualization).<br>FLUX ➜ Go (efficient handling of dynamic processes).
Note: These associations are conceptual guidelines rather than strict requirements. Branches may use different languages or tools depending on the experiment.
Note: These associations are conceptual guidelines rather than strict requirements.
Branches may use different languages or tools depending on the experiment.
❦ Development Conventions
-Commits must be descriptive and traceable.<br>-Merges into HEX require prior validation through testing.<br>-Experimental branches should be periodically synchronized to avoid divergence.<br>-Documentation accompanies code to preserve conceptual clarity.
❦ Architecture
𒄆 HEX 𒄆
╭──────────────┴──────────────╮<br>│ │<br>▼ ▼<br>ᡕᠵデᡁ᠊╾━ Λ ᡕᠵデᡁ᠊╾━ FLUX<br>foundations concepts / patterns<br>│ 𓂃<br>Sequences / Inspo<br>│ 𓍼<br>ᡕᠵデᡁ᠊╾━ RUN<br>execution<br>│ ╰┈➤ 𒄆𓁹✞𒀱✞𓁹𒄆<br>ᡕᠵデᡁ᠊╾━ Src<br>implementation
ᡕᠵデᡁ᠊╾━ LIVE<br>perception
❦ Design Philosophy
The minimum criterion of the system is its capacity for simplification.
A useful formalism should allow a phenomenon to be represented with fewer arbitrary assumptions while preserving the distinctions necessary for its transformation.
❦ Development Possible Stages
-Phase I — Conceptualization
-Phase II — Formalization
-Phase III — Minimal Runtime
-Phase IV — Composition
-Phase V — Simulation
-Phase VI — Validation
-Phase VII — Expansion
❦ Current Priority
The immediate priority is not to maximize functionality , but to determine whether the conceptual core can be reduced to a sufficiently small set of coherent operations.
❦ License
License and contribution guidelines will be established as the project reaches a stable public-development stage.
❦ Project Status
Experimental. Conceptual architecture in development.
HEX begins.
Welcome! 𒄆 HEX 𒄆 Is Happy To Say Hello!
This repository currently shows a complete flow~
➜ Fragments ➜ raw material (texts, narratives, seeds)
➜ RUN ➜ execution/interpretation (scripts, notebooks, symbolic translations)
➜ Λ ➜ formalization (axioms, foundational principles)
➜ Root ➜ minimal essentials (README, license, index)
For now, the material will remain in Fragments as examples.
Later, the Binder will be updated to integrate these pieces more systematically.
Collaborators can explore the cycle
~ write ➜ interpret ➜ formalize ➜ run~
About<br>Lambda Nested...