LL.M International Business Law (Distinction) · LL.B (Hons) · Reading for the Sri Lanka Bar · Colombo
From law into systems.
I work on the legal-technology side: document workflows, correspondence automation, mandate tracking, and contract review - built so a human is always the one accountable for whatever leaves the firm. Four years of background across corporate, intellectual property, and structured-finance matters.
Case studies show control logic without exposing client matter detail, templates, rules, or live operating records.
Outputs are shaped around source discipline, sign-off, and decision records rather than unsupervised generation.
The portfolio sits between legal training, document control, cross-border mandates, and AI evaluation work.
Case studies
What I've built.
Three system architectures from live matters, plus two longer notes on how I think about the work. Each is shown at a level of abstraction that doesn't expose any client matter; the implementation stays with the firm.
Formal documents - opinions, advice notes, demand letters, internal memoranda - drafted under firm voice and standing instructions, then routed through a human reviewer before anything is dispatched. The architecture is on the public side; the rules and templates stay private.
Open the case studyMandate facts, authority checks, document sequencing, and the next action sit in a single operating record. Source-of-truth pattern from cross-border structured-finance work.
Open the case study The document execution workflowA document only reaches signing once version, signer authority, attachments, submission route, and audit trail have all been checked. Self-hosted infrastructure.
Open the case studyDrafting examples, clause taxonomies, reviewer edits, and rejection reasons curated into reference material that AI tools can lean on without inventing facts. Out of the LL.M thesis on copyright and generative AI.
Read the note Regulation, AI accountability, and the human layerWhy the duty has to stay with the human - recent sanctions cases (Mata v. Avianca, Park v. Kim), the EU AI Act, GDPR Article 22, ABA Formal Opinion 512, and where Sri Lanka's professional-conduct apparatus fits in.
Read the noteOperating principles
Four rules I keep across every system here.
Spelling them out lets you check whether the work actually delivers on them, instead of taking the claim at face value.
- Source discipline
Don't invent facts.
The system never makes up a figure, an authority, a right, or a governing law. If it isn't on the matter record, the output flags the gap in brackets. The reviewer fills the bracket or kills the draft.
Older than the technology - the same discipline that separates settled advice from speculation.
- Human review
A human always signs off.
Every output that's ready to go out sits behind a human signature. The system's job is to surface what the reviewer needs to see, in the order they need to see it - never to step in front of them.
Where the AI helps, it helps the reviewer think; it doesn't replace the thinking.
- Execution control
No signing without the checks.
Nothing reaches signature until the version's locked, the attachments are complete, the signer authority is verified, and the audit trail is being kept. A confident-looking draft is not the same as a document that should leave the firm.
The signing infrastructure is self-hosted because final execution shouldn't sit behind someone else's product.
- Disclosure boundary
Public site, private firm.
The pages here show architecture and how decisions get made. Client matters, implementation detail, and the live operating register don't appear on the open web - they get walked through inside a proper review setting.
The site is the demonstration; the firm is where the work actually happens.
Get in touch.
Email is the fastest route. I keep reply windows short, and any walkthrough at firm-level detail happens off the public site by design.
Use email for the current CV, a walkthrough of any case study at firm-level detail, or a dummy-data demonstration where that's the right context. Project work, collaboration, and technical inquiries are all welcome.