The one-sentence version. What it is, why it matters, and what goes wrong without it.
Golden Rule of Software Engineering — live
See how technology really works.
Axiom turns technology principles into short explanations and live simulators. Break the system on purpose, watch what fails, then watch the fix save it. No jargon walls — just clarity.
👑 Rule 1 track: Software Engineering
·
6 principles free
·
no credit card
● 44 Golden Engineering Rules
Scroll to explore
👑 Section 01 — The Golden Rule · Software Engineering
“Anything can happen twice, concurrently, partially, slowly or not at all.”
This single assumption is the constitution of software engineering. Duplicates, concurrency, partial failure and delay are not edge cases — they are the normal weather of a real system. Every rule that follows exists to keep a system correct, safe and recoverable in spite of them.
↻ Happens twice→ idempotency keys
⇉ Concurrently→ constraints & locking
◐ Partially→ transactions & state
◷ Slowly / never→ timeouts, queues, retries
Match each “what if” to a control — then prove the control works. That is the whole job.
Section 02 — Live simulators
Concepts you can actually touch
Not videos. Not slides. Real, interactive models of the principles behind the Golden Rule. Flip a safeguard off to see the failure, on to see the fix. Every one has a ↺ Reset.
Section 03 — The curriculum
The 44 Golden Engineering Rules
Forty-four principles across ten areas, each explained at three depths plus a quick check. The first six are free forever; the rest are part of Pro.
44Principles
6Free forever
10Topic areas
3Reading levels
Foundations3
Resilience7
Data Integrity7
Interfaces2
Security4
Scale & Performance3
Operations6
Engineering Practice4
Governance2
Mindset3
Where most systems actually break
Build for Production, Not Just for DemoA demo works once. A product works every time.
IdempotencyAnything can happen twice — charge once.
AtomicityAll of it happens, or none of it does.
Let the Database Guard the RulesConstraints are the final authority.
State MachinesOnly legal states, only legal moves.
Nothing Fails SilentlyIf it breaks, it says so — loudly.
Section 04 — How the lessons work
Every principle, explained three ways
Flip the reading level and the same lesson rewrites itself — from a first sentence to the engineering detail.
How to apply it day to day, with the trade-offs and the common pitfalls spelled out.
The engineering detail — the failure modes, the edge cases, and how it holds under load.
Simple by design
Every principle has a plain-language explanation plus a deeper one. Start easy, go deep when you are ready.
Play with it
Simulators let you double-tap a payment, race two requests, or flood a database — and see why it matters.
Learn together
Join the community: ask questions, explain a concept your way, and help others get it.
Section 05 — What is coming next
One platform, every technology domain
Software Engineering is the first track because it is the foundation. The same engine — short lessons, three depths, live simulators — is being extended to the rest of the technology landscape.
GRC
Governance, Risk & Compliance, made operational instead of theoretical.
- Risk registers & controls
- Policy, audit & evidence
- Frameworks without the fog
CyberSecurity
Zero trust, least privilege and defence in depth you can actually see working.
- Threat models & attack paths
- Identity, secrets & access
- Incident response patterns
Digital Transformation
Business analysis and process optimisation turned into principles and simulators.
- Business analysis & requirements
- Process optimisation & automation
- Operating-model design
Start with the rules that keep systems alive.
Create a free account to unlock the first six principles, save your progress, earn badges, and join the community. No credit card.