Legal judgment engine
data/build-014-engine-v1.jsonSeven work layers, four allocation states, inherited human and AI controls, leak detection and jurisdictional boundary.
BUILD 014
Legal Judgment Architecture
A tool may produce legal text, but responsibility does not move with the text. Research, interpretation, inference, strategy, approval, professional judgment and client authority require distinct allocations.
QUESTIONWho owns each layer of legal judgment?
STRUCTURED PUBLIC BUILD ARCHIVE
Research, creation, decisions, audits and plans are publicly structured without claiming that every release gate is complete.
This page exists so the durable record does not depend on conversation history. Research, decisions, generated artifacts, audits, limitations, media metadata, plans and canonical source paths are retained here as part of the build itself. A listed repository path proves that an implementation record was retained; it does not independently support a real-world factual claim.
5 of 5 listed retained paths have a public reader link on this archive page. Unlinked paths remain named for traceability but are not represented as publicly inspectable evidence.
What informed the build
ABA Formal Opinion 512
Official guidance on competence, confidentiality, communication, supervision, candor and fees when lawyers use generative AI.
ABA Model Rule 2.1
Grounds the lawyer’s independent professional judgment and candid advice.
ABA Model Rule 5.3
Grounds reasonable measures, supervision and responsibility for nonlawyer assistance.
What exists because we built it
014-A Legal Judgment Architecture
Audit seven legal-work layers, expose judgment leakage and export locally.
014-B The Answer Has Layers
An interactive responsibility stack separates assistance from owned judgment.
Legal Judgment Engine v1
Reusable legal-work allocation and supervision assessment.
Why it works this way
Builds 001 and 012 are concrete dependencies
The engine directly calls the human-review primitives and assessAIUseControls.
Generated text does not transfer responsibility
Strategy, final approval and professional judgment cannot be silently assigned to AI assistance.
Client authority remains distinct
Decisions allocated to the client are not relabeled lawyer or tool decisions.
No universal UPL claim
The architecture defers to jurisdictional law, adopted rules, court orders, agreements and supervising counsel.
How the work was checked
Machine-readable archive
data/build-014-archive-v1.jsonRoutes, lineage, privacy and consumers.
Privacy/support
data/build-014-privacy-support-v1.jsonClient-local state and jurisdictional support boundary.
Freshness/performance
data/build-014-freshness-performance-v1.jsonCurrent official ABA sources and offline operation.
Browser fixtures
tests/build014.spec.tsSupervised, leak, reset, export, lifecycle, 320px and B-layer coverage.
What this build intentionally leaves forward
Release path
Complete static gates, Chromium/WebKit matrix, media, preview and exact-head certification.
Future consumers
015, 016, 044 and 093 consume cap:014.
Take the social artifact with you
B-LINKEDIN / CANONICAL FILM
720×900 · 4:5 MP4 · 24 fps · silent-first
CURRENT VERIFIED MEDIA / 30-second film · 358.5 KB
FINAL PROPOSITION / RESPONSIBILITY DOES NOT MOVE WITH THE TEXT.
SHA-256 3d23136849cbc05d50e496b0a5b0bbc0d4197f66ce941b27abcc718910780b5cReproducible from data/linkedin-film-specs-v1.json with scripts/render-linkedin-films.py. The website—not a chat attachment—is the canonical media source.
The repository files that preserve the implementation record
apps/web/app/100-builds/014/a/LegalJudgmentLab.tsxapps/web/app/100-builds/014/b/JudgmentLayers.tsxpackages/release/src/decision-engines.tsdata/build-014-engine-v1.jsondata/build-014-archive-v1.jsondocs/builds/014/SPEC.mddocs/builds/014/ARCHIVE.mdtests/build014.spec.tsThese paths preserve the implementation record. Only items with an explicit public reader link are publicly inspectable here. A file path, working interface or internal engine is not independent support for a real-world claim; synthetic propositions and design reasoning remain labeled within the retained record.