What we are building
Three efforts, with the date we would stop each one.
One is live with a public demo; the others are not products yet. Each has a written problem, an intended operator, and a kill date — the day we archive it if the one thing it must prove has not happened. Publishing the kill date is the point: it is what stops an idea outliving its evidence.
LegalEngineering
Day zeroA durable index and chronology for document-heavy case work, so exhibits and timelines are found rather than rebuilt.
- Intended for
- Ourselves first, on one real matter. Chambers only after internal use has proved it.
- State today
- Day zero. A written definition and a first task list exist. No software has been built.
- We stop it on
- 19 October 2026if the index and chronology are not in weekly use on that matter by then.
UrjaOps
LiveA register that shows which solar site is blocked on which filing or document, without ten folders and a message thread.
- Intended for
- Operations leads at EPCs and aggregators, who track this today in spreadsheets, shared drives and field calls.
- State today
- Live at urjaops.com: lifecycle tracking for all four PM-KUSUM components, a responsibility directory, a deadline register with reminders, seven registers and 28 AI drafting actions. A public demo runs on a fictional sample project. No paying operator yet.
- We stop it on
- 19 November 2026if no operator has put a real site list into the register and confirmed it does the job of their weekly spreadsheet.
EduOS
Day zeroA way for cohort operators to prove completion with evidence, instead of reconstructing it from spreadsheets afterwards.
- Intended for
- Training leads and small education teams, who chase this today through spreadsheets and messages.
- State today
- Day zero, and deliberately parked: no build work begins until a named design partner exists. Attention is finite and two other efforts rank ahead of it.
- We stop it on
- 19 November 2026if no design partner has committed by then.