Explicit authority at every boundary.
Runfabric separates product access, process state and external execution. These are the current boundaries of the development release.
Project access
Passkeys identify the person signing in. Project membership determines permitted operations. CLI and MCP grants are scoped to a selected project and resource. Machine keys can be limited to operations and activity kinds and revoked independently.
A Runfabric Project is independent of a Sentient or HOS Organization. Composition requires an explicit authority mapping; sharing an identifier does not grant access.
Credential custody
Hosted integration secrets and origin service credentials are encrypted at rest. Their values are not returned by profile listing or placed in workflow definitions. Run inputs and tool outputs can contain business data, so give each operation only the data it needs.
On a private worker, credentials stay in your environment or secret manager. The hosted service stores the operation's result and evidence, not the private process environment.
Durability and external effects
PostgreSQL owns published workflows, run state and activity receipts. The Cloudflare control plane owns login, integration and trigger records. Queue messages carry identifiers rather than secrets. Fenced activity leases reject stale worker completions.
An external provider can accept a write even if its response is lost. Runfabric records ambiguity and exposes reconciliation. Exactly-once business effects depend on provider idempotency support and workflow configuration.
Execution boundaries
Hosted profiles constrain destinations, tool names, output sizes and execution windows. They do not execute arbitrary shell commands. Local command profiles use fixed executables and argument mapping without shell interpolation.
Agent activities cannot add tools or credentials to their allowlist. Broker, model and execution limits are controlled by the project operator.
Development environment
Cloudflare hosts the website, control plane and integration runner. The Coralbeat2 dev GCP project hosts the durable workflow origin. This is a bounded development environment, not a production SLA or compliance certification.
Use test accounts and development credentials. Requests to model and tool providers remain subject to those providers' retention, permissions and limits.