Things are happening at yuho_and_beyond
.
-
Yuho LSP
- Write a LSP that works for most major code editors
- Provides snippets, linting and syntax highlighting
- Flags errors that might arise from wrongful Yuho code
-
Yuho live editor
- an in-browser IDE
- transpiles written yuho code live to a specified diagramatic output
- linting
- snippets and autocomplete
- provides decent error messages
- see lawtodata web application
- see streamlit as platform to deploy app on
- see L4's IDE
- see ANTLR Lab for a program that exposes a user-visible AST
- see L4 Google Sheets Extension for a google suite extension that integrates a DSL
- an in-browser IDE
-
Yuho should be LLM powered
- Work out how to integrate a trained LLM that can read and validate Yuho
- Explore other usecases where an LLM would be useful
- Both front-end and back-end
- Consider langchainlaw integration for training a model
- Yuho as an intermediary language that makes understanding the logic of the law easier to learn for a given model
- LLM-powered service that transpiles existing legislation to Yuho lang
- Further applications could include a chatgpt or bert powered CHARGE GENERATION FORM that will receive a given statute and parse it to Yuho, then feeding that through a lang-chain powered model that puts the Yuho code into a formalised english form
- LLM-powered Chatbot
- Chatbot that can provide legal advice to the layman and explain law concepts clearly to students via Mermaid diagrams
- Yuho could be an intermediary language that provides sanitised input to easily train LLMs on SG Criminal Law cases
- things to implement
model_1
: train a model that takes in existing statutes and converts it to Yuho code- Statute def (plaintext) --[
model_1
]--> Statute def (Yuho struct)
- Statute def (plaintext) --[
model_2
: train a model that takes in a statute as a yuho struct and a plaintext scenario and outputs the yuho struct for that scenario- Statute def (Yuho struct) + Statute illustration / Sample scenario (plaintext) --[
model_2
]--> Statute illustration / Sample scenario (Yuho struct)
- Statute def (Yuho struct) + Statute illustration / Sample scenario (plaintext) --[
- Consider whether to use encoder/decoder or transformer model, see other available options
- see legal-bert
- see scott
- see ollama
-
Form generation
- See motoraccidents.lawnet for reference on easy form creation
- Consider implementation as a google docs or google sheets extension
-
Scratch-like web app to learn the law
- Scratch-like controls with drag and drop interface so different logical blocks can be rearranged and the struct updates live
- Is there a HTML element / Svelte frontend that can achieve the same flow-chart like Display without relying on Mermaid? (ideally I would want HMR)
- see Svelteflow for reactive diagrams and flowcharts
- see Whyline for dynamic sites that display logical evaluation of a given decision
- Allow user to ask "Why did" and "Why didn't" questions about a given output
- Users choose from a set of questions generated automatically via static and dynamic analyses, and the tool provides answers in terms of the runtime events that caused or prevented the desired output
- Consider implementing this in Blockly through writing a visual editor from scratch
- Can consider following this tutorial
-
Uncategorised
- There are many assumptions made when we reason from one premise to another premise in the law, how far do we push this inquiry back?
- eg. before even considering how a given a given statute should apply for a case, we should figure whether the given case can even be heard in the current court
- See CCLaw Sandbox for inspiration
- There are many assumptions made when we reason from one premise to another premise in the law, how far do we push this inquiry back?