didi.sh — the three services get a platform: one login, one agent, and an identity-service spec
We bought didi.sh and decided what converges on it: exactly two shared planes — a central identity service (one account, SSO via a .didi.sh cookie) and a shared agent named didi that loads skills per task. The identity service is specced to implementation depth, on an Elixir/Phoenix stack, with augment-it and its two waiting client teams as the first consumer.