OAB Sets Guardrails Requiring Human Lawyer Oversight of AI in Legal Services

·1 views

A DEV Community article outlines technical and ethical guardrails meant to limit how artificial intelligence is used in Brazilian legal work. It says the Brazilian Bar Association (OAB) requires that any AI-assisted legal output be directly supervised and signed off by a registered lawyer, and that responsibility for AI-driven errors rests with the lawyer rather than the technology provider. The piece cites the Estatuto da Advocacia, OAB opinions and resolutions, and reported court practice, noting courts tend to reject filings whose authorship cannot be clearly attributed to a qualified professional. Suggested safeguards include blocking unsigned AI outputs, mandatory warnings on sensitive topics, immutable logs of AI interactions, and disabling automated drafting of complex documents. The article presents these as current expectations in the profession rather than a new regulatory announcement.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Glimpse Developer Adds Live Note-Taking to Meeting App After Using It in Lectures

A developer spent a year building Glimpse, a dictation and meeting app, largely on their own. After matching the features users expect from dictation tools, they focused on meeting mode, drawing inspiration from MacWhisper. When MacWhisper launched live transcripts, the developer added a similar feature to Glimpse. Using it during lectures revealed shortcomings, such as the app listening for too long or too short a time and not indicating which model was processing the live notes. The developer's takeaways are to copy what users expect, scrutinize what you dislike even in copied features, and use your own product constantly to catch problems before others do.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Setting Up External DNS with Cloudflare on a Local Kubernetes Cluster

This installment of a Kubernetes series explains how to deploy External DNS to automate DNS record management on a local cluster. The author uses Cloudflare as the DNS provider and follows declarative GitOps practices with Flux. The process starts by generating a zone-scoped Cloudflare API token and storing its credentials in a Kubernetes secret, which is encrypted with SOPS before being committed to Git. The External DNS deployment is then defined through a ServiceAccount, a read-only ClusterRole and binding, and a Deployment that watches ingresses and syncs records to Cloudflare. The article notes that the setup builds on earlier steps for routing external traffic to the cluster so it can be reached via a public IP.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

DEV community asks which single fix users would make to the platform

A DEV Community post invites readers to name the one thing they would fix on the platform if given a magic wand. The author asks for a single answer, which can be a feature, rule, bug, or aspect of how the feed works. The author gives an example: a way to understand why a post received few views, which would especially help new writers who get no initial readers. The post notes that, without such insight, writers can only guess at the reason. The author states they will read every reply.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Rails 8 Tutorial Part 2 Covers Built-in Authentication Generator for Study Flow

The second part of a Rails 8 tutorial series builds user accounts for a sample app called Study Flow. It explains that Rails 8 includes its own authentication generator, which writes readable Ruby code into the app instead of relying on a gem such as Devise. The guide walks through how login works, with a session record stored in the database and an identifier kept in a cookie so the browser can be recognized across requests. It also covers the generated models, the use of password digests rather than stored passwords, and the rate limiting and access controls applied to the controllers. A signup page, which the generator does not create, is added manually at the end.

0 comments Read more at DEV Community