[ LOCAL-FIRST ] •
[ EVIDENCE-LED ] •
[ REVERSIBLE ] •
[ SOVEREIGN BY DESIGN ] •
[ FRUGAL ] •
[ PORTABLE ] •
[ INTERACTIVE ] •
[ USER-FRIENDLY ]
NullaLabs is the personal research and engineering identity behind Ethernium: local-first software, bounded automation, explicit authority and claims that remain proportional to reproducible evidence.
The profile deliberately separates three things:
| Surface | Meaning | Evidence boundary |
|---|---|---|
| Public software | Repositories and packages that can be inspected now | Source, tests and releases are linked below |
| Private engineering | Active ecosystem components under controlled development | A name or diagram is not a public release |
| Visual research | Interface language, shaders and interaction studies | Visual artifacts are not physical or scientific proof |
| FRUGAL local cognitive kernel |
CHRONOLITH integrity evidence |
SENESCHAL consultative preflight |
| INVICTVS visual control surface |
THESTRAL IDE / control plane |
EXEKUTION controlled execution research |
These labels describe the intended separation of responsibilities. Components without a linked public repository and reproducible release remain private or in development. Internal screenshots, simulations and unit tests do not prove deployment in a physical or hostile environment.
Evidence rule: latency, bypass ratio, CPU/GPU use, frame rate, security efficacy and external anchoring apply only to the exact artifact, hardware and procedure recorded with the measurement.
| Principle | Operational consequence |
|---|---|
| Frugal routing | Deterministic and symbolic paths precede neural/cloud escalation |
| Controlled authority | A UI, model or advisory component has no hidden mutation power |
| Promotion gates | External input moves through source → mapped → adapter → tested → promoted |
| Release hygiene | Source, release, evidence and cold archive remain distinct |
| Honest limits | Missing physical or external proof is recorded, never simulated as success |
| Rollback | Meaningful changes remain reviewable, reconstructable and reversible |
Build useful local-first systems whose components remain understandable on their own, whose integrations are contractual, and whose claims can be tested without trusting the presentation.











