Who builds this, and why
Mert Efe Şensoy
I am a software engineer in Turkey. Ephesus is mine, and at the time of writing it is the work of one person — every commit on this repository is authored by me, which is a deliberate policy rather than an accident of scale.
The projects I care about have one property in common, and I did not notice it until someone pointed it out: they are all instruments for telling whether something is actually true. A decoder that validates a memory module beyond its checksum. A conformance suite that has to pass on every backend. A rescue simulation whose verdicts are deterministic. Ephesus is the same instinct pointed at software construction itself — a company of agents that cannot claim work is done without producing the evidence.
Related projects
motus
A transport-agnostic messaging seam for C++17, with a per-backend conformance suite
aftershock
A command-and-control system for a post-earthquake search-and-rescue exercise, with deterministic mission verdicts
MÜŞAHİT
A single laptop that watches 37 Turkish news sources overnight and tells you what mattered by morning
CASSANDRA
Can useful language-model behaviour be formed on consumer hardware without brute-force gradient training?
Names cut into the wall
Ancient cities inscribed the names of the people who paid for the aqueduct, the library, the colonnade. Ephesus did it more than most — the stones of the real city are covered in them. This is that wall.
Anyone whose contribution is merged is named here: code, a bug report that found something real, a documentation fix, a build report from a platform nobody had tested. Not sponsors — contributors. The wall records work.
THIS WALL IS EMPTY
No contribution has been merged from anyone but the architect yet.
The first name cut here will be the first person who is not me.
The wall is written by hand from merged pull requests and closed issues, not generated from a contributor count. If you are on it, someone read your work.
Built in the open, under rules
Everything about how Ephesus is built is public: the requirements, the decision records, the design document, the milestone-by-milestone progress with its evidence, and the implementation record for every change. When those documents disagree with the code, the code is wrong.
It is MIT licensed. It is pre-alpha and says so everywhere rather than only in the small print. If it interests you, the fastest way in is a first issue, and the fastest way to understand it is the post about checks that cannot fail.