Runtime and data boundaries
An enterprise first decides where the Harness runs and which systems handle models, files, logs, and secrets. Private deployment is more than placing a service on an internal network. Egress, retention, backup, recovery, and release paths between environments all need explicit design.
Identity, permissions, and connectors
An Agent is defined by what it can call. CRM, ERP, database, and internal API connections need separate designs for user identity, service credentials, and tool permissions. MCP can be a connection protocol, while the enterprise outcome is a governable business connector.
From PoC to sustained operation
A PoC validates a use case. Production must cover monitoring, incident handling, upgrades, execution traces, and ownership. Delivery should include a running Harness, enterprise connectors, custom Agents, deployment documentation, and an upgrade path, not only a proposal.