Coding workflows and cooperative AI.
Integration in developmentExplore CodeProject repository · GitHub

VOLPAROSSA CORE
Connecting devices, sharing resources and building intelligence together.
Development preview
Different places. Many participants. A connected whole.

Useful parallel routes connect participants through different relays. Each normal Internet path keeps one relay between the client and exit.
Network documentationReuse verified public content when its source and permissions allow sharing. Private files and arbitrary encrypted web traffic do not become shared cache entries.
Cache documentationApplications encrypt files before sharing fragments and recovery copies. Owners keep their recovery keys; providers hold ciphertext. Complete maintenance and application recovery remain in development.
Storage documentationDivide suitable tasks, combine results and reuse permitted models. Confidential execution of private work on other participants’ devices remains unfinished.
Compute documentationExplore authorized transfers and durable accounting with fictitious test value. This is not a live banking or payment service.
Transactions documentationArchitecture in development. Individual milestones have been tested; these are not yet five released services. The harbour connections are illustrative.
Built on existing projects. Extended through a shared foundation.
Designed around one compatible background Core per device, shared by multiple applications. Other participants run their own Core, with their own resources and permissions.

VOLPAROSSA is being developed to let devices share suitable work, reuse models and learn from measured outcomes. The aim is to make a modest device an entry point to shared capabilities.
In development
Explore cooperative computeThe design divides suitable tasks and combines their results. Shared learning uses permitted data, with evaluation and correction as part of development. Private prompts, files and results are not automatically shared training material.
Confidential execution of private tasks on other participants’ devices remains unfinished. A local coding result does not establish protected distributed execution.

DPS — Decentralized Positioning System
Privacy-preserving positioning
DPS is being developed to combine satellite signals, nearby devices and local sensors, with explicit permissions and clear uncertainty. The goal is to improve positioning while keeping precise locations and movement history private.
Explore complementary satellite, local and sensor-based measurements.
Make confidence, conflicts and unavailable information clear.
Keep access, sharing and retention under separate permissions.
Research & development
The current prototype assesses supplied position claims. Real sensor fusion, navigation and measured accuracy remain in development. Relative position does not establish an absolute location, and agreeing or signed claims do not prove geographic truth.
Receiving positioning help, accessing sensors, contributing measurements, retaining history and training models each need separate permission. Joining the network does not authorize sharing your precise location or movement history.
DPS uses the five Core layers. Privacy is a design goal, not a guarantee of anonymity. This page requests no location or sensor access; the illustrated points are fictional.

Open infrastructure grows through shared effort. Explore the design, test a milestone or help build the next part.
Start contributingParticipation is voluntary. Joining the network means accepting its resource-sharing responsibilities.
Participation requires explicit activation. Your own device use takes priority. Shared storage calls for a matching usable contribution, including recovery copies and overhead. No payment is required to participate.
Participants contribute according to available capabilities. Devices with an independent Internet connection also provide authorized exit service; local-only devices contribute local links and relay capacity.