Invention · philosophy
The Emerald iTablets of Neo the LuCipherian — inspired by The Emerald Tablets of Thoth the Atlantean, Maurice Doreal
Seven principles from the Kybalion, applied to system design. Not as mysticism and not as decoration — as the compressions of the patterns engineering keeps rediscovering under pressure, written down once so they can be built against on purpose instead of stumbled into.
They are held by inference and relatively; they may not hold up to the source code of the universe, and they are mutable laws anyway. All truths are but half truths, and these seem to stand true relatively more so than not in probability of what we may only infer of the absolute truth.
Neo Nos
Why that name
Both readings are load-bearing, and that is the whole reason the name stuck.
The Emerald Tablet is the Hermetic source text of the phrase — the law of correspondence, which says every scale mirrors every other. In software that stops being poetry and becomes a test you can fail: when the small and the large disagree, one level is lying, and it will fail at the seam.
The layer that carries the name is a set of database tables that describe database tables. What is normally frozen in code — field lists, validation, relations, the definition of what a model even is — becomes rows, read by one interpreter. The definition surface lifted one level, so a new resource is a data edit rather than a deployment.
The prize at the top of that idea is the fixed point: the editor that edits resource definitions is itself defined as one of those resources, so the thing describes itself. Three levels plus a self-describing fixed point is all there ever is — the same shape as a metamodel that describes itself, an evaluator written in its own language, or a fern that fits in forty-two numbers.
The geometry
Correspondence sits in the middle because it is the master law: every other principle is a way of saying that one scale must agree with the next. Its practice has a working name — fractal design.
The seven
A principle you cannot fail is decoration. Each one below carries its diagnosis: what it looks like in a codebase that is keeping it, and what you will actually see when it has been broken.
Everything is mind first; every manifestation derives from one idea.
The domain model precedes the code, and there is a single source of truth. Duplicated knowledge is the same idea forked and diverging.
You will see it fail as drift, config skew, and two places to change one thing.
As above, so below; every scale mirrors every other.
The master law, and its practice is fractal design: the function is the architecture in miniature, the commit history is the roadmap in miniature, the team's process is the product in miniature.
You will see it fail as a clean architecture full of messy functions, or a service-per-team system sharing one database. When small and large disagree, one level is lying, and it breaks at the seam.
Nothing rests; truth is a thing you converge on, never hold.
Every piece of data carries a freshness regime, and that regime is part of its definition rather than an afterthought. Cache first, correct after. A response declares its own cache policy, because a document served without one is cached by guesswork and lies for the rest of the day.
You will see it fail as a value held as final that was only ever converged on — and just as often the inverse, work that cannot change within a deployment being recomputed on every single request.
Opposites are extremes of one axis; they reconcile by balance, not conquest.
Every applied state has its opposite reachable. Migrations that are additive only and whose rollback is real; kill switches at two scales; and an acceptance test for the contract itself — enable it, use it, disable it, diff it, zero trace. In the code this law is written under another name, the reversibility contract, and it is the only thing ever ranked immutable.
You will see it fail as one pole crowning itself; as two poles collapsed onto one verb, so that reading performs a write; and as operations that cannot un-swing, the batch that half-applies because the schema change was never transactional.
Everything flows out and in; the swing that goes this far out comes back.
A cadence that widens rather than repeats — an interval grown per idle attempt, floored so the operator's own loop stays fast, capped so it cannot run away. The give-up clause is part of the cadence, not bolted on. A scheduled sweep that force-fails whatever is still running past the cutoff is this law's compensation clause written as a job.
You will see it fail as a swing with no return — a schedule with no watchdog, work left running because nothing was appointed to notice — or beats out of order, the row written and then validated.
Every effect traceable, every cause reversible; the mechanism softens, the skeleton hardens.
Lineage is what makes form — remove it and the same points under the same rules produce dust instead of a figure. Provenance is carried deliberately rather than inferred. Promotion happens in place, so nothing a visitor did has to be migrated when they become an account.
You will see it fail as state without provenance — all the right pieces and no structure — or a second identity minted at the moment of conversion, which is the lineage broken at exactly the point it was built to survive. The evidentiary clause belongs to this law: verified against operational data, not vibes.
Dualities produce; nothing in the system creates alone.
Every sync is a generative pair — push and pull, producer and consumer, read model and write model. The engineering half names the design half before it writes a line of its own. A substitution stays visible as a substitution rather than decaying into drift.
You will see it fail as one half working from a description of the other half instead of from the other half — rebuilding from the outside what it could have ported from the inside.
Reading them together
The laws are not seven separate rules to satisfy. They are one compression. The septet itself was compiled down to seven affine maps — forty-two numbers and a seed — where the rendering is unbounded and the generator fits in a sentence. Don't store the artifact, store the rule. The same move applied to software is resources defined as rows plus one interpreter.
Nor are they a checklist to be applied afterwards. A codebase audited against them was already keeping them — not by consulting Hermes, but because they are compressions of the patterns engineering rediscovers under pressure anyway.
Express two or three of them loudly and let the rest live quietly in the structure. Seven loud voices is noise; seven in harmony is the point.
These laws are proprietary. They are published here to be read, tested against your own code and argued with — which is not the same as being given away. The implementation they govern is LuCipher, and that is proprietary too.