# Portico public vision

## Community foundation

The public Portico Community runtime connects a compatible web AI/MCP client to one owner-controlled Linux computer.

The security principle is stable:

**The AI is never the security boundary. Operators define authority; the destination machine enforces it; audit records it.**

## Interoperability direction

Portico is designed so the public runtime and protocols can evolve toward broader interoperability without making a model vendor the security authority.

Public architectural principles include:

- typed capabilities;
- explicit machine identity;
- local policy enforcement;
- explicit resource scope;
- durable task semantics where needed;
- vendor-neutral protocol boundaries;
- auditable provenance;
- no implicit privilege inheritance between agents.

## Data locality

Files, databases, RAG indexes, logs, applications and services may remain on owner-controlled machines.

Portico should prefer executing authorized work near the data and returning only the result needed by the client.

## Managed products

Broader managed Portico products may add multi-node coordination and AI/agent delegation outside the Community repository.

This public repository documents only the Community runtime, public interoperability contracts and intentionally announced roadmap.