What we're building now
Three products. One operating thesis.
I.O.V began as a strategic intelligence studio: a way to understand markets before they become obvious, make decisions while the map is still incomplete, and move from thesis to proof quickly.
Increasingly, the work is becoming product.
Not because every piece of strategy needs software, but because the most interesting questions we are working on now cannot be answered with a deck alone. They need interfaces, agents, permissions, transactions, users and real-world feedback.
Today, three products sit at the centre of that work:
Signal Atlas. Pulso. NIVQRA.
They solve very different problems. Underneath them is the same idea: intelligence becomes valuable when it can move safely into action.
01 — Signal Atlas
Cultural intelligence that can act.
Signal Atlas began with a simple frustration: discovering a city still means stitching together dozens of fragmented surfaces. Editorial guides know taste but rarely know you. Booking platforms know inventory but rarely know culture. Maps know where something is but not necessarily whether it is worth your time.
We are building Signal Atlas as a different kind of interface.
It combines editorial judgement, local signals, structured city intelligence and agent-assisted discovery into one system that can answer a deceptively difficult question:
Where next?
The first layer is discovery: places, food, culture, events, style, seasonal signals and city intelligence.
The second is personalization: understanding the person, the moment and the city rather than simply returning search results.
The third is action.
Signal Atlas is being designed so recommendations can eventually move naturally into capabilities: finding transport, checking events, preparing bookings, discovering housing, accessing local services and paying when appropriate.
The product is deliberately broader than a travel guide.
The ambition is an intelligent cultural interface for navigating a city.
02 — Pulso
Prediction, reputation and economic participation for LATAM.
Pulso begins from a very different behaviour: people already predict the future constantly.
Who will launch next. What will sell out. Which creator will break through. What trend will become mainstream. What will happen in entertainment, finance, culture and everyday life.
Today those predictions disappear into posts, chats and comment sections.
Pulso turns them into a reputation layer.
The product combines a short-form social feed with creator-led questions, forecasting and a persistent record of who was actually right.
But prediction alone is not the end state.
Pulso is being built around the idea that social participation, reputation and economic utility can live in one experience. Behind the interface we are developing a chain-neutral liquidity and payment architecture rather than forcing the user to understand wallets, networks or payment rails.
Arc, x402 and other execution systems can sit underneath that experience.
NIVQRA sits above them.
The user should experience one product.
The complexity belongs to us.
03 — NIVQRA
Human authority for autonomous systems.
NIVQRA comes from the most fundamental question we have encountered while building with agents:
Who gave the machine permission to do that?
Most software security models are built around access.
Can this system open the account? Can this API key call the service? Can this agent reach the wallet?
But access is not authority.
An autonomous system may technically be able to perform an action without being authorised to perform that action, for that purpose, for that person, at that moment and within those limits.
NIVQRA is the control plane we are building for that missing layer.
Identity → Mandate → Permission → Intent → Policy → Decision → Execution Eligibility → Evidence → Revocation.
The goal is not to become another wallet, payment rail or blockchain.
The goal is to govern the authority that those systems exercise.
AI may propose. NIVQRA enforces. Humans define the boundary.
04 — Why these three belong together
At first glance, a cultural intelligence platform, a social prediction product and an authority system have very little in common.
From our side of the table, they are increasingly the same research programme expressed in three different products.
Signal Atlas asks: how should an intelligent interface understand a person and the world around them?
Pulso asks: how does an intelligent interface coordinate participation, reputation and economic action?
NIVQRA asks: under whose authority is that action allowed to occur?
Put together, they describe a larger stack:
Understand → Decide → Act → Govern.
That is the territory I.O.V is exploring.
05 — The agent layer
Across the three products we use Astra agents as the operating layer connecting intelligence to execution.
The goal is not to bolt a chatbot onto every interface.
Agents are useful when they can carry context across a workflow: research, interpret, compare, plan, call capabilities, evaluate results and return evidence.
Different products give those agents different jobs.
In Signal Atlas they help turn local information into useful decisions.
In Pulso they can support resolution, verification and economic workflows.
Around NIVQRA they operate inside explicit mandates rather than unrestricted access.
The architecture matters because the interface may increasingly become capable of acting.
When that happens, intelligence without boundaries becomes a liability.
06 — Why Lovable matters to the way we build
I.O.V is an official Lovable Solution Partner at the Registered tier. IOV Labs runs on an active Lovable Business subscription, and partner certification is underway.
That relationship fits directly into the way we want to work.
The old software model separates strategy, design and engineering into long sequential phases.
We are trying to collapse them.
An idea should become an interface quickly enough that we can discover whether the idea was wrong.
Lovable gives us a fast product surface for prototyping and shipping. GitHub holds the canonical engineering record. Our agents help research, build, test and operate. More specialized infrastructure enters only when the product actually requires it.
The important part is not 'vibe coding.'
It is compressing the distance between a strategic assumption and real evidence.
07 — How we are building
Start with the unresolved problem.
Not the feature. Not the technology. The behavioural or economic constraint underneath it.
Form a product thesis.
What would have to be true for this to become genuinely valuable?
Build the smallest convincing interface.
Enough product to make the thesis tangible.
Put it in front of reality.
Users, partners, APIs, infrastructure and edge cases replace internal imagination.
Give agents real work.
Not decorative conversation. Research, orchestration, resolution, testing and repeatable workflows.
Separate authority from execution.
Execution systems may change. Mandates and boundaries should remain explicit.
Preserve the evidence.
Every iteration should leave the next iteration smarter.
Expand only after the first proof exists.
Do not scale the assumption. Prove it.
08 — What happens next
Signal Atlas is moving from editorial discovery toward a living city interface.
Pulso is moving from social prediction toward an integrated creator, reputation and economic layer for Latin America.
NIVQRA is moving from thesis into deployable authority infrastructure for autonomous economic action.
Different products. Shared architecture. Shared agents. Shared operating discipline.
And increasingly, one I.O.V underneath them.
We build maps for markets that do not exist yet. Now some of those maps are becoming products.