1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
|
%% ============================================================
%% Academic Journal Paper Template
%% Compatible with: IEEE, ACM, Elsevier, Springer conventions
%% ============================================================
\documentclass[10pt, twocolumn]{article}
%% ---- Core Packages ----------------------------------------
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{lmodern}
\usepackage{microtype} % Microtypographic refinements
%% ---- Page Geometry ----------------------------------------
\usepackage[
top=1in, bottom=1in,
left=0.75in, right=0.75in,
columnsep=0.25in
]{geometry}
%% ---- Mathematics ------------------------------------------
\usepackage{amsmath, amssymb, amsthm}
\usepackage{mathtools}
\usepackage{bm} % Bold math symbols
%% ---- Figures & Tables -------------------------------------
\usepackage{graphicx}
\usepackage{booktabs} % Professional table rules
\usepackage{multirow}
\usepackage{array}
\usepackage{caption}
\usepackage{subcaption}
\usepackage{float}
%% ---- Algorithms -------------------------------------------
\usepackage[ruled, vlined, linesnumbered]{algorithm2e}
%% ---- Code Listings ----------------------------------------
\usepackage{listings}
\usepackage{xcolor}
\lstdefinestyle{codestyle}{
backgroundcolor=\color{gray!8},
basicstyle=\ttfamily\footnotesize,
breakatwhitespace=false,
breaklines=true,
captionpos=b,
commentstyle=\color{green!50!black},
keywordstyle=\color{blue}\bfseries,
stringstyle=\color{orange!70!black},
numberstyle=\tiny\color{gray},
numbers=left,
numbersep=5pt,
showstringspaces=false,
frame=single,
rulecolor=\color{gray!40},
tabsize=2
}
\lstset{style=codestyle}
%% ---- Hyperlinks -------------------------------------------
\usepackage[
colorlinks=true,
linkcolor=blue!70!black,
citecolor=green!50!black,
urlcolor=blue!60!black
]{hyperref}
\usepackage{url}
%% ---- Bibliography -----------------------------------------
\usepackage[numbers, sort&compress]{natbib}
%% ---- Miscellaneous ----------------------------------------
\usepackage{lipsum} % Lorem ipsum filler — remove in production
\usepackage{enumitem}
\usepackage{siunitx} % SI units: \SI{3.14}{\mega\hertz}
\usepackage{cleveref} % Smart cross-references: \cref{fig:foo}
%% ---- Theorem Environments ---------------------------------
\theoremstyle{plain}
\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{corollary}[theorem]{Corollary}
\newtheorem{proposition}[theorem]{Proposition}
\theoremstyle{definition}
\newtheorem{definition}[theorem]{Definition}
\newtheorem{example}[theorem]{Example}
\theoremstyle{remark}
\newtheorem{remark}[theorem]{Remark}
%% ---- Custom Commands --------------------------------------
\newcommand{\R}{\mathbb{R}}
\newcommand{\N}{\mathbb{N}}
\newcommand{\Z}{\mathbb{Z}}
\newcommand{\E}{\mathbb{E}}
\newcommand{\Prob}{\mathbb{P}}
\newcommand{\norm}[1]{\left\lVert #1 \right\rVert}
\newcommand{\abs}[1]{\left\lvert #1 \right\rvert}
\newcommand{\inner}[2]{\left\langle #1,\, #2 \right\rangle}
\newcommand{\ie}{\textit{i.e.}\xspace}
\newcommand{\eg}{\textit{e.g.}\xspace}
\newcommand{\etal}{\textit{et al.}\xspace}
%% ---- Caption Formatting -----------------------------------
\captionsetup{
font=small,
labelfont=bf,
format=hang,
justification=justified
}
%% ---- Header / Footer --------------------------------------
\usepackage{fancyhdr}
\pagestyle{fancy}
\fancyhf{}
\fancyhead[L]{\small\itshape Ne.org, Vol.~2, No.~1, March 2026}
\fancyhead[R]{\small\thepage}
\renewcommand{\headrulewidth}{0.4pt}
%% ============================================================
%% FRONT MATTER
%% ============================================================
\title{%
\vspace{-1.5em}%
\large\textbf{The 'Context Language' System.}%
}
\author{%
\textbf{Amlal El Mahrouss}$^{1}$\thanks{Corresponding author. Email: amlal@nekernel.org}
\\amlal@nekernel.org, amlalelmahrouss@icloud.com\\[0.4em]
\small $^{1}$Ne.org Journal
}
\date{%
\small 3 March 2026
}
%% ============================================================
\begin{document}
%% ============================================================
\twocolumn[{%
\maketitle
\vspace{-0.5em}
\rule{\linewidth}{0.4pt}
%% ---- Abstract -------------------------------------------
\begin{center}
\begin{minipage}{0.92\linewidth}
\small
\textbf{Abstract.}\enspace
This development presents a systems language[1] in which we'll name 'Context Language' (CL).
We propose a method of programming language design in which Execution is separated from Data, alongside trait rules.
\medskip
\textbf{Keywords:}\enspace
Computer Science; Software Engineering;
\end{minipage}
\end{center}
\vspace{0.8em}
\rule{\linewidth}{0.4pt}
\vspace{1em}
}]
%% ============================================================
\section{Denoting CL Execution}
\label{sec:cl-introduction}
We propose the following approach to represent the CL execution flow, as execution context a way to mathematically present:
\begin{equation}
\Theta(\operatorname{C}) \coloneqq\frac{d\operatorname{Prog}(\operatorname{\lambda C})}{d\operatorname{C}}
\end{equation}
Such that an execution context (denoted as $\operatorname{C}$) is a program currently running with rules (denoted as $\operatorname{Trait}(\operatorname{C})$) and domains. We derive the program by its context in this formula, as we depend on $\operatorname{C}$, the $\operatorname{C}$ variable must be valid and computable in a domain $\operatorname{D}$.
\section{Syntax}
\label{sec:cl-syntax}
The syntax of a Context Language may consist of traits, and implementations. The traits can be expressed as defined in Nectar. One way to represent it mathematically is:
\begin{equation}
\operatorname{Trait}(\operatorname{C}) \coloneqq \operatorname{Rules}(\operatorname{C}) \in \operatorname{C}
\end{equation}
Traits and such must be valid in $\operatorname{C} \And$ $\Theta(\operatorname{C})$.
\section{Example: The Nectar 'CL'}
\label{sec:cl-example-nectar}
Developing such languages would benefit Software Engineering as we noticed a much faster cycle of software development when using the CL approach rather than the classic CL approach. We also notice that Nectar programs tends to be shorter and more expressive than average.
\section{Conclusion}
\label{sec:cl-conclusion}
We can conclude by theorizing that the CL could benefit software engineering by enabling secure systems and engineering, and making them much more accessible than we had previously. However more development will come after this development for additional reports on this approach.
\end{document}
|
