Initial problem
An assignment needs an owner, a visible state and a reviewable result. A robot animation alone does not establish that the requested work was completed.
Optimatiza · Oficina Viva
A project for organizing work, seeing who owns each assignment, and tracking results from your browser.
Explore the team's rolesOriginal recording in Spanish, including narration and on-screen text.
Owned project · Historical evidence
Owned Optimatiza project. This case examines task assignment, recorded states and review; it does not describe a customer production operation.
An assignment needs an owner, a visible state and a reviewable result. A robot animation alone does not establish that the requested work was completed.
The project brings together a browser interface, task assignment, execution, persisted events and linked outputs for review. The technical case documents how those parts interact.
Specialist roles share a local model in the documented setup. NOVA can split an assignment into up to three independent tasks; this is not recursive delegation or a chain that consumes earlier child results.
React and Three.js provide the interface and visual scene; Express handles the server; PostgreSQL stores the records; Ollama supplies the local model. Events are transmitted to the browser through Server-Sent Events (SSE).
The examined configuration uses one shared qwen3:1.7b model and one concurrent inference. The 33 roles across 11 departments identify specialties, not separate models or simultaneous workers. State history is not model learning.
Historical controlled test. NOVA distributed two tasks to Marketing and Finance. Both passed through review and reached the completed state. The audit recorded 39 persisted events and 39 SSE events in matching order.
This supports the task-routing and event-recording mechanism in that test. It does not validate the generated content, customer data handling, business savings or current production operation. No new inference was run for this case update.
The video above combines an initial trial that did not complete the flow with captures from a later successful test, identified on screen. Its edited timing cannot be used to infer latency. The public visual demo helps explore the scene; it does not establish that the local executor is running.
Publishing, sending email, issuing invoices and actions in external platforms require separate integrations and authorization. Robots reflect recorded task states; movement does not prove those external effects.
From assignment to delivery
Describe what you need. NOVA proposes how to distribute work across departments, or you assign a task to an agent.
View owners, queued tasks, and work in progress. Events update in real time.
Open the result and its history before approving it. Keep each task's context in one place.
33 roles · 11 departments
Agents prepare analyses, plans, and drafts using the information provided. Open a department to explore its three roles.
Preparation and review. The current version assigns work, records states, and links results for human review. Roles share a local model, and the executor processes one AI task at a time. The 33 roles do not mean 33 simultaneous executions.
AI on the device. In this configuration, assignments are processed locally without being sent to an external AI API. Protecting data also requires permissions, device security, and integration reviews.
Upcoming connections. Publishing on social media, issuing invoices, recording hours, and taking actions on other platforms require integrations that are still pending. Roles prepare proposals; they do not imply web searches, audiovisual generation, code execution, or automatic audits.
A possible evolution. The same approach could be adapted for human teams to organize tasks and tickets, detect blockers, and distribute workload more effectively. That adaptation is not part of the version shown.
Greater clarity at work
Let's discuss the process you need to organize in your business.