OSC (OConnector SentinelCloud)

0. Canonical name

The canonical pillar name is OSC — OConnector SentinelCloud.

1. Classification in the ecosystem

Cloud and execution-governance sentinel.

OSC is positioned as the Heptagon component responsible for evaluating macro execution boundaries before cloud-facing or cost-sensitive actions proceed.

2. What this project is

OSC acts as a guardrail layer for cloud, cost, and policy-aware execution decisions. In the ABS ecosystem, it is the component consulted before actions that may create financial exposure, resource misuse, or policy violations in infrastructure-facing workflows.

3. What the current integration shows

The current hub integration exposes an evaluation path with fields such as agent_id, action_type, estimated_cost, resource, and policy_pack, which indicates a service that evaluates execution context before selected actions continue.

4. Functional role

OSC should be understood as:

• a pre-execution evaluation layer for cloud and cost-sensitive actions,
• a macro guardrail against unacceptable resource or policy exposure,
• and a governance input to runtime decisions in controlled environments.

5. What it is not

OSC should not be described as a generic secret vault, a public cloud KMS replacement, or a public SaaS console. Those positions blur the role of the pillar and create confusion with other security or policy components.

6. Intended deployment posture

OSC fits the broader ABS model of self-hosted, private, or customer-controlled deployment. It should be presented as infrastructure that supports governed execution paths rather than as a mass-market cloud service.

7. Documentation discipline

When documenting this pillar, use the name OSC consistently. Use OConnector SentinelCloud on first mention when expansion is helpful, and avoid alternate names that redefine the component.