DEV Community: Sercan Koç

Beyond the PDF: Law as an Architectural Layer in the Modern Tech Stack

Sercan Koç — Sat, 20 Dec 2025 08:05:57 +0000

In the world of software development, law is often seen as limited to static PDF documents like "Terms of Service" or "Privacy Policy" that come into play only after the system is built.

However, with the rise of Web3, AI, and RegTech, we are entering an era where treating law merely as a documentation layer is insufficient—and can even lead to system failure. In this new reality, law must become an architectural layer embedded into the DNA of the code during the design phase.

## Why is Law No Longer Just a "Document"?

Traditional compliance models are reactive; the system is built, and then lawyers check if it complies with existing rules. In fields where speed and irreversible transactions are fundamental, such as Web3 and Decentralized Finance (DeFi), this approach creates "regulatory-induced technical debt." This forces expensive and time-consuming redesigns later to meet legal requirements.

The "Legal by Design" approach reverses this process. In this model, lawyers, developers, and UI/UX designers sit at the same table from the prototype phase. The goal is to use legal constraints not as blockers, but as fundamental parameters that shape design decisions.

## Legal Constraints Shaping Architecture

Here are a few concrete examples of how legal requirements directly influence system architecture:

### 1. Zero-Knowledge Proofs (ZKP) and Data Privacy
Centralized databases require data to be "seen"; however, data protection regimes like GDPR, KVKK, and others limit the sharing of sensitive data. Zero-Knowledge Proof (ZKP) technology solves this paradox with the principle of "proving without revealing." If a system can mathematically verify a user is over 18 without ever seeing their actual birth date, this implements the principle of "data minimization" at the code level.

### 2. Programmable Compliance: The ERC-3643 Example
Traditional token standards (like ERC-20) are permissionless and allow for anonymous transfers, which often conflicts with securities regulations. Standards like ERC-3643 move compliance to the "smart contract" level. This architecture allows only pre-verified (whitelisted) wallets to hold tokens, executing investor eligibility checks autonomously.

### 3. Digital Identity (DID) and Sovereignty
Self-Sovereign Identity (SSI) models shift identity management from centralized institutions to the individual. This architectural choice radically changes the concept of the "data controller," minimizing the legal liabilities and risks developers face regarding the storage of unnecessary PII (Personally Identifiable Information).

## Governance in a World Where Code is Law

Treating law as an architectural layer also affects governance processes. A DAO (Decentralized Autonomous Organization) constitution isn't just text; it is a logic sequence defining voting mechanisms and fund distribution rules.

However, as seen in the Tornado Cash case, relying solely on decentralization provides no legal shield; building systems with "compliance-oriented design" has become inevitable.

With the Tokenized Compliance approach, transfer limits or geographic restrictions can be coded directly at the protocol level. This stops compliance from being an external audit mechanism and turns it into the system's operating principle.

## Conclusion: Why Now?

Digital sovereignty, AI ethics, and digital asset laws (like MiCA) are now integral parts of the tech world. Future successful systems will be built by architects who view legal requirements not as a "patch" added post-launch, but as a fundamental engineering input.

The intersection of law and code is one of the most critical layers of the modern software stack. For those who want to dive deeper into this architectural approach, methodologies, and technical-legal frameworks, GenesisHukuk’s public knowledge repository is here:

Genesis Hukuk

If you are building systems where law, code, and governance intersect, you may find it useful.

Road Accident Report - AI Assistant

Sercan Koç — Sat, 13 Sep 2025 14:18:46 +0000

This is a submission for the Google AI Studio Multimodal Challenge

What I Built

I built the AI Accident Assistant, a sophisticated web application designed to solve a major real-world problem: the stress, confusion, and error-prone process of creating a vehicle accident report at the roadside.

An accident is a chaotic event. The last thing anyone wants is to manually copy information while trying to recall details under pressure. My application transforms this experience.

A user simply:

Takes photos of official documents (driver's license, insurance policy).
Captures the scene with photos or videos.
Records a brief voice memo describing what happened.

The AI assistant takes over, processing this multimedia evidence to generate a complete, accurate, and pre-filled accident report. The final output is a secure and organized Evidence Package (.zip) containing a formal HTML report, the AI-generated sketch, and all original media files, ready for submission to an insurance company.

Demo

Deployed Applet: https://road-accident-report-ai-assistant-121419357176.us-west1.run.app

The demo showcases the full, end-to-end user journey:

Setup: The user is greeted by a clean landing page and then selects the report's jurisdiction (e.g., UK, California) and language.

Upload: The user uploads all their evidence—documents, scene photos, and audio statements for each driver involved. They can also use their device's GPS to log the accident location.

AI-Powered Verification: The user reviews the AI-generated draft report. If the AI has questions due to missing or conflicting data, it presents a conversational chat interface for clarification. The user can also visually adjust the AI-generated SVG diagram and review a separate AI-generated artistic sketch of the scene.

Download: After signing digitally and providing consent, the user downloads the final Evidence Package.

How I Used Google AI Studio

The core of this application is powered by a chain of sophisticated multimodal prompts sent to Google's Gemini 2.5 Flash and Imagen 4.0 models.

I engineered a multi-step AI workflow within the application:

Data Extraction (Gemini): The first call sends all media files (images, audio) along with contextual data (like GPS location) to Gemini. I leveraged Gemini's native JSON output mode by providing a strict schema, ensuring a reliable and structured data response that populates the report draft.

Interactive Diagram Generation (Gemini): A second, targeted prompt asks Gemini to analyze the scene photos and extracted data to generate a clean, interactive SVG diagram of the accident. The prompt explicitly instructs the model to use specific group IDs () to make the diagram elements draggable in the UI.

Sketch Generation (Imagen): A third call sends a descriptive prompt to Imagen, which generates a top-down, black-and-white schematic sketch of the accident, providing an alternative visual representation for the final report.

Conversational Clarification (Gemini): If information is missing, the application initiates a conversational loop. The user's text answers are sent back to Gemini with the current report data, and the model intelligently updates the JSON with the new information.

Multimodal Features

The multimodal capabilities of Google's AI models are the foundation of this app's user experience.

Image Understanding (Documents & Scene)

What it does: Gemini analyzes official documents to extract key details and simultaneously interprets scene photos to understand road conditions, vehicle positions, and impact points.

Why it's better: This eliminates manual data entry, reduces human error, and saves critical time. The AI is even prompted to detect and flag unreadable or blurry documents, giving the user a chance to re-upload for better accuracy.

Audio Intelligence (Voice Memos)

What it does: The user can record a voice memo describing the accident. Gemini transcribes the statement and cross-references the narrative with visual evidence from the photos.

Why it's better: This offers a natural way for users to provide their statement while events are fresh. The AI’s ability to check for contradictions is a powerful validation feature that ensures a more truthful report.

Intelligent Generation (SVG Diagram & PNG Sketch)

What it does: The app leverages both Gemini and Imagen to generate two distinct visual aids: a clean, interactive SVG diagram for precise adjustments, and a simple, easy-to-understand PNG sketch.

Why it's better: This provides users with multiple ways to visualize the incident. The interactive SVG diagram, in particular, empowers the user to fine-tune the AI's output, creating a collaborative report-building process that leads to a highly accurate final document.