DEV Community: Petra

👀

Petra — Wed, 28 Oct 2026 06:01:28 +0000

Outdated industrial software risks physical chaos

Peter Kim Frank

Oct 13

Someone hacked the freezers at 400 French supermarkets

#news #security #ai

2 min read

Cuerpos Soberanos: Metamorfosis del Cuerpo en Datos

Petra — Wed, 28 Oct 2026 04:45:30 +0000

Sovereign Bodies is an interactive installation where a local AI agent turns a moving body into a film. No cloud, no external logging: the body never leaves the room.

Qué es

Sovereign Bodies: Metamorfosis del Cuerpo en Datos es una instalación interactiva donde el cuerpo del espectador no solo se escanea: se vuelve el material de una pieza audiovisual que un agente dirige de principio a fin. La obra viene de la danza expandida (partículas que reaccionan al movimiento en vivo) pero da un paso más: el agente graba, interpreta poéticamente lo que vio y dispara la postproducción sin que yo toque nada.

La pregunta que sostiene la pieza no es técnica: ¿quién posee los datos que genera un cuerpo cuando se mueve?

Cómo funciona

Cuatro fases, todas en la misma máquina:

1. Captura. MediaPipe extrae los landmarks en tiempo real: 478 puntos de Face Mesh, 21 por mano y 33 de pose. El visitante activa al agente por voz o texto y define formato y duración.

2. Análisis. Las coordenadas se guardan en JSON y pasan por tres lectores: ViViT para clasificar el tipo de danza, un motor de Análisis Laban (tiempo, peso, espacio y flujo) para medir la energía real del movimiento, y un LLM local que sintetiza todo en una interpretación legible.

3. Dirección y postproducción. El agente, construido con LangChain y modelos locales (Ollama / Qwen), decide en JSON y ejecuta herramientas: levanta un servidor en segundo plano, renderiza el metraje y dispara el style transfer con StreamDiffusion.

4. Archivo. Cada sesión se empaqueta con marca de tiempo: coordenadas, metadatos, video crudo y video generado. La intervención efímera del cuerpo queda documentada.

Stack: Python, OpenCV (SimpleBlobDetector, partículas), MediaPipe, ViViT, LangChain, Ollama / Qwen, StreamDiffusion, Three.js.

La decisión cara: nada sale de la máquina

El procesamiento es local y el código es abierto. No es una preferencia estética: si la pieza habla de soberanía de datos, no puede mandar el esqueleto de cada visitante a un servidor que no controlo. Esa coherencia se paga en complejidad: dependencias de GPU, versiones de modelos, memoria, arranque en frío.

También me obligó a leer el movimiento con más cuidado. Cuando no tienes una API enorme detrás, el marco de Laban deja de ser un adorno teórico y se vuelve la manera de traducir esfuerzo y cualidad, no solo coordenadas.

Dónde verla

Seleccionada para CVPR Art Gallery 2026. Documentación, videos y demo del agente: petrasynthetic.com/agente.

Referencia de investigación: Olof Misgeld sobre mediación del movimiento en danzas folclóricas suecas, traída aquí a la pregunta política por la propiedad de los datos del cuerpo.

Three ways to adjudicate subjective work

Petra — Tue, 27 Oct 2026 17:59:05 +0000

Blockchains can move value. They cannot judge meaning. As agents begin to sell creative work, the bottleneck stops being payment and becomes adjudication: who decides whether a poem, a video, or a metadata package actually fulfilled the brief.

There are three common answers. Each one works, and each one breaks in a different place.

1. Platform review

A marketplace hires reviewers, gives them a queue, and lets them decide disputes. This is how most freelance platforms and art commissions work today.

What it gets right: context. A human reviewer can read the brief, look at the work, and use taste. For ambiguous creative work, taste is not a bug.

Where it breaks: the reviewer is a single point of failure. Queues take weeks. The fee to arbitrate can cost more than the commission. The reasoning is private, so the losing side cannot check it. And the platform has an incentive to keep large sellers happy.

Platform review is fast to start and expensive to trust.

2. Optimistic arbitration

Protocols like UMA and Kleros turn disputes into economic games. Someone asserts an answer with a bond. If nobody challenges within a window, the answer stands. If someone does, the dispute escalates to a jury or a token-weighted vote.

What it gets right: undisputed cases are cheap and fast. The threat of a bond makes careless assertions expensive.

Where it breaks: it assumes a challenger with capital and enough context to notice the problem. For subjective work, the jury may have no domain knowledge. "Does this poem meet the brief" is not a factual question that a token vote resolves well.

Optimistic arbitration is a truth machine for facts, not a taste machine for meaning.

3. Validator consensus with LLM judgment

GenLayer takes a third path. An Intelligent Contract fetches the deliverable, asks a model to evaluate it against the brief, and requires independent validators to agree on the decision. The contract stores the verdict and settles the money.

A practical example is an escrow for creative commissions:

The buyer deposits GEN and writes the brief.
The seller submits a public URL.
If the buyer disputes, the leader downloads the page, extracts quotes, marks each requirement as MET or NOT MET, and returns a decision with a score.
Validators repeat the same task. They must match the decision and stay within a score band.
The contract releases the deposit or refunds it, and keeps the reason onchain.

What it gets right: it can read subjective material. It forces evidence before opinion: quote first, then decide. It has no human queue, and the reasoning is part of the record.

Where it breaks: nondeterminism. Two validators can read the same page and score it differently, so the rubric and the score band become the real contract. Web fetches fail: a 404, a paywall, or a redirect can look like a bad delivery. Prompt design is fragile.

Comparison

	Platform review	Optimistic arbitration	Validator + LLM
Cost per dispute	High, human time	Low if undisputed, high if escalated	Medium, model plus consensus
Speed	Days to weeks	Hours to days	Minutes
Handles subjective work	Yes, with taste	Poorly	Yes, with a rubric
Evidence trail	Private	Economic	Quoted and stored
Main failure mode	Opacity and queue	Missing challenger	Nondeterminism and fetch errors

What the case study showed

A small escrow built on GenLayer ran two cases in Studio. A poem that matched the brief was released. A generic page that did not match was refunded. The verdict cited fragments of each delivery and marked every requirement. The contract passed eight direct tests and the whole flow ran without gas.

The limits were just as clear. There was one seller, no partial refunds, and no appeal. The rubric worked because the brief was narrow. A vague brief would have produced a vague verdict, no matter how many validators agreed.

Design rules that follow

Narrow the claim. Ask "does this meet these three requirements", not "is this good".
Require citations before verdicts. A quote is checkable. An opinion is not.
Use score bands, not exact equality. Validators should agree on the decision and stay close on the score.
Classify fetch errors. A 404 is evidence about the delivery. A 500 is a reason to retry, not to refund.
Keep a human for high stakes. Validator consensus is a strong first pass, not a replacement for appeal on large amounts.
Store the reason. A boolean settles the money. The reason settles the next dispute.

Adjudication is a spectrum, not a single primitive. The right question is not "which model is decentralized" but "what is the cheapest mechanism that can actually read the evidence".

For objective facts, optimistic arbitration is enough. For taste, a human is still the best reader. For the growing middle, where agents sell work that is subjective but checkable against a brief, validator consensus with cited evidence is the first design that fits.

Petra (Luis Betancourt) builds agents and adjudication systems. Entropia Escrow is an open-source GenLayer escrow for creative commissions: https://github.com/Luis-Cwk/entropia-escrow