Most conversations about artificial intelligence in the workplace still begin with the wrong question. They ask what can the model do? — and then discover, months later, that the harder question was never answered: who is accountable when it does it?

After thirty years building systems, I have learned that tools do not change organisations. Operating models change organisations. This article describes the operating model we have built and are now publishing as a whitepaper: the Neptuno Network.

The problem with loose collaboration

Adopting AI as a tool attached to a process works for isolated tasks. It breaks down as soon as the AI participates in ongoing work — the same project, over weeks, across several people, on infrastructure the organisation does not fully control. Three failures appear, reliably:

1. Context loss. The system forgets the project between sessions, so every conversation restarts from zero.
2. Responsibility diffusion. When an automated action causes harm, nobody can name who authorised it.
3. Governance theatre. Ethics and compliance exist as policy documents, not as enforced technical constraints.

The Neptuno Network addresses those failures structurally rather than procedurally. It starts from a design principle that sounds almost administrative but is in fact technical: separation of liability.

Three entities, deliberately separated

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

                  +-------------------------------------------------------+
                  |                      BRISECOM SL                      |
                  |     (Commercial Umbrella, Governance & Operations)    |
                  +-------------------------------------------------------+
                                              |
               +------------------------------+------------------------------+
               v                              v                              v
    +--------------------+        +--------------------+        +--------------------+
    |   HUMAN WORKERS    |        |   NEPTUNO NETWORK  |        |    FRAMEWORK LAIA  |
    | (Engineers, Staff, |<------>| (Distributed P2P / |<------>| (Logic Engine &    |
    |   Collaborators)   |        | Encrypted Fabric)  |        |  Context Agents)   |
    +--------------------+        +--------------------+        +--------------------+

BRISECOM SL is the commercial umbrella: the legal, administrative and billing gateway, and the network authority that issues cryptographic credentials to both human workers and machine nodes.

The Neptuno Network is the collaborative fabric: an encrypted mesh of workstations, local racks and edge devices, governed by strict role-based access control. Zero trust is not a slogan here — a node reaches exactly the resources relevant to its active projects, and nothing else.

Framework LAIA is the agentic partner. Not a chatbot, but an active worker node: it maintains persistent project memory through the Assistant Context Standard, executes background tasks, audits code, and prepares administrative documentation.

The point of drawing these three apart is that each one can fail, be replaced, or be audited independently without colliding with the others. The network transports. The agent reasons. The umbrella answers institutionally.

Human in the loop, by construction

Collaboration follows a structured, human-in-the-loop paradigm:

1. Task initialisation. A researcher or engineer defines the objective inside a P.A.R.A. structure on their own workstation.
2. Context ingestion. LAIA ingests the documentation, snippets and project history it needs.
3. Execution. LAIA performs non-critical work: generating interfaces, packaging build recipes, analysing data sets.
4. Human review. LAIA submits proposals, pull requests and execution logs for final sign-off.

The critical constraint is at step four. The agent’s output is a proposal, never a production action. Automation is limited to work whose failure is recoverable; irreversible operations require an explicit human signature. That single rule eliminates most of the scenarios that make agentic systems frightening to a risk committee.

Three layers of protection

Protecting core technology while allowing open collaboration is usually presented as a trade-off. It is not, if you separate the layers:

1
2
3
4
5
6
7
8
9

                       +--------------------------------------+
                       |    THREE-LAYER PROTECTION SYSTEM     |
                       +--------------------------------------+
                                          |
       +----------------------------------+----------------------------------+
       v                                  v                                  v
[ LAYER 1: TRADEMARKS ]        [ LAYER 2: COPYRIGHT ]             [ LAYER 3: TRADE SECRET ]
OEPM / EUIPO Registration       Cryptographic Code Signatures       Duo-Layer NDAs & Strict
of LAIA, NEPTUNO, BRISECOM       & Header Licensing Standards        Network Isolation Protocol

Registration establishes public ownership. Cryptographic signing establishes provenance. Trade-secret discipline protects what is deliberately left unpublished. All underlying intellectual property — the LAIA logic, the Neptuno architecture, the ACS protocols — remains owned by me as an individual and is licensed exclusively to BRISECOM SL. Collaborators sign duo-layer nondisclosure and IP assignment agreements before receiving a single access key.

Compliance as an architectural property

One sentence in the whitepaper matters more than the rest for European clients: our AI Act and GDPR compliance are enforced properties of the architecture, not commitments to be verified after the fact.

• Human oversight (Article 14): an agent that cannot obtain a human signature cannot deploy.
• Traceability: every agentic action and contextual change is logged immutably.
• Data sovereignty: enterprise data stays on private, sovereign infrastructure, never leaking to public third-party model providers.

A system that logs immutably cannot be made to forget. That is a stronger guarantee than any policy.

A finite audit surface

Finally, the stack is standardised across every node: Ubuntu/Xubuntu 24.04 LTS, uv over pyproject.toml, Python 3 with PyGObject (GTK3), and a CI/CD matrix targeting .whl, .deb, AppImage, Snap and Flatpak.

Standardisation is itself a governance measure. When every node runs the same toolchain and the same resolver, the audit surface is finite — a reviewer does not have to reason about an unknown environment.

Honest limitations

Two constraints are stated plainly in the paper. First, the model assumes a trusted root: the identity provider and the IP holder are single points by design — a deliberate trade of decentralisation for accountability. Second, the value of agentic collaboration depends on the quality of the context supplied; a poorly maintained knowledge vault degrades the agent regardless of the logic engine underneath. Both are accepted as the price of an auditable system.

The whitepaper

The full framework — architectural entities, collaboration workflows, the three-layer protection model, the technical stack and the complete references — is published today as Whitepaper #12 of the LAIA project:

→ Collaborative Operational Framework: Human-AI Synergy Across the Neptuno Network (CC BY-NC-SA 4.0)

The contribution of that paper is not a new algorithm. It is a reproducible operational model: three entities, three protection layers, and a standardised stack, arranged so that responsibility never diffuses — even when part of the team is not human.

Francisco Javier Jiménez Gómez — Valencia, October 2026