It starts with the map.Then the map puts things to work.
Sinopia grows in layers, like a fresco: each one rests on the one beneath, and comes in once the previous one has done its job.
Three layers, one at a time.
The next one is paid for by whoever already paid for the previous one. Scroll: it builds from the bottom up.
The map
Code, data, pipelines, jobs and infrastructure in a graph with the code index, served via MCP to any agent. And an agent that answers questions about how the system works.
The recipes
The skills marketplace: how to use the map and how to build by your rules. You publish yours there too.
The hands
Connectors to Git, ticketing, cloud and email: the agent acts with the person's permissions, preview first, then confirmation.
It starts with one system.
The map of one repository
On one of your repositories, with the connector for your agent: you try it on your own code, at no cost.
The map of one system
You get the map, the documentation that comes out of it, the agent that answers how it works, and three presentations. Fixed price: half at signing, half at delivery.
The living map
Every night the harvesting jobs reread code, data and jobs, and the map updates itself. Served to your developers and their agents: a monthly fee, never by the hour.
You provide a read-only copy and a contact person for one hour a week. The agents do the rest.
The map is yours: the graph stays with you, even the day you leave.