You can read every word in a legal document and still not understand what it means for your life.
A notice. A contract. A court order. A property document passed down through a family.
Recognising the words isn't the same as understanding their implications.
That gap is one reason we're building aidhar, a legal workspace from 123sudo.
It has now moved from research and design into development. For our team, that's a milestone. For me, it's personal.
My connection to law came before this product
I'm KAT, co-founder of 123sudo.
I studied law through a three-year LLB and have worked in High Courts and district courts. My relationship with the legal system comes from education and experience, not just an interest in building a product for it.
The last couple of years have left me questioning the distance between what people expect from justice and what they experience.
I feel frustrated. But I also feel a responsibility to contribute.
I don't believe an app can fix the judiciary. I don't want to promise that software will clear pending cases or resolve problems much bigger than our team.
But I keep returning to a question we can work on:
What if more people could understand the legal language that shapes their lives?
Understanding is a starting point, not a verdict
Understanding a document doesn't resolve a dispute.
It doesn't establish that someone's interpretation is correct. It doesn't replace advice from a qualified lawyer.
But clearer explanations can give someone a starting point for asking questions.
- What does this term mean?
- Which part of this document needs professional attention?
- What information should I bring to a conversation with a lawyer?
- What am I still uncertain about?
I want us to build for that moment: when someone is looking at something important and doesn't know where to begin.
Why our team is taking this on now
At 123sudo, we've been building and improving practical software, including 9xchat, our multi-model AI workspace.
That experience has given us more confidence to take on a problem with a different kind of responsibility.
A confusing interface is frustrating. A confident but misleading legal explanation can have more serious consequences.
So this isn't a case of taking a general-purpose chat interface, changing its name, and calling the problem solved.
We're at the beginning of development. There are questions we need to work through carefully.
The design questions I'm carrying into development
These are principles I want us to explore, not a list of features we're claiming to have shipped.
1. Can we make language clearer without changing its meaning?
Simplifying language is not the same as removing nuance.
A short explanation can become misleading if it leaves out a condition, exception, or limitation that matters.
The goal should be understandable language, not simplicity at any cost.
2. Can people distinguish an explanation from legal advice?
A user shouldn't need to read between the lines to understand the limits of a tool.
I want us to be clear about what an explanation does, what it doesn't establish, and when someone needs professional help.
That distinction belongs in the experience, not only in a disclaimer at the bottom.
3. How should uncertainty appear?
An answer that sounds confident isn't necessarily reliable.
We need to think carefully about how the workspace communicates missing information, ambiguity, and points that need verification.
Sometimes the useful response may be a question or an explicit limit, rather than a polished answer.
4. How do we keep the original document in view?
An explanation should help people engage with the source, not encourage them to forget it exists.
I want to explore ways of keeping the relationship between a document and its explanation understandable.
Again, that's a design goal, not an announcement of a completed capability.
Built with people working in law
aidhar began as a personal initiative, but it isn't mine alone.
It's being built by the aidhar team and shaped by conversations with lawyers and the people we hope to support.
I want to contribute something useful to my colleagues in law. I also want someone outside the profession to feel less lost when they encounter unfamiliar legal language.
Those audiences have different needs.
A lawyer working through documents and a person trying to understand a notice shouldn't automatically receive the same experience.
Listening to both matters. So does being honest about what we can build well first.
Language shouldn't become another locked door
India's linguistic diversity is central to how I'm thinking about aidhar.
Understanding a legal concept in one language doesn't necessarily mean someone can understand it equally well in another.
Our ambition is to support more languages over time.
But multilingual support can't just mean adding a language selector. Legal meaning, terminology, and nuance need careful evaluation.
We haven't announced a launch-language list yet. I'd rather start with a scope we can assess properly than promise every language before we're ready.
Why I keep thinking about the next generation
I hope more young people grow up understanding their rights and the institutions around them.
Maybe one day practical legal literacy and fundamental rights will have a stronger place in every student's education.
Until then, there is room for tools that help people begin learning and asking informed questions.
Technology can't create equality before the law on its own.
But we can try to make understanding less intimidating and more accessible.
Where we are today
aidhar is in development. It isn't publicly launched yet.
We're not announcing completed features, a release date, or a promise to replace professional legal work.
We're sharing the problem we care about and the direction we're taking.
For me, this project sits at the intersection of three things: my legal background, our team's experience building software, and a belief that people deserve a clearer understanding of the systems that affect their lives.
From our small team in Uttarakhand, this is the beginning of something we hope will be useful.
aidhar, a legal workspace from 123sudo. Coming soon.
Disclosure: I'm a co-founder of 123sudo, the team developing aidhar. This article shares our motivation and development goals, not legal advice or a description of completed product capabilities.
Written with help from 9xchat, our multi-model AI workspace, and my 123sudo Head of Growth agent. The experiences, views, and direction are my own.
Whether you're a lawyer, developer, or someone who has struggled with legal language, what is one thing a workspace like this must get right?
Top comments (0)