Protection contracts
Capability definitions, threat and protection semantics, execution-state rules, quarantine boundaries, and evidence structures make security claims machine-reviewable instead of decorative.
Wardveil Security by GoreeCloud
Wardveil Security is GoreeCloud's platform-wide security and protection authority. Version 2.0.0 is currently at Seal under Platform Contract 2.0; deployment remains Development, and Anchor/Stable qualification is blocked on the remaining non-deferrable gates. Its source foundation covers shared security contracts, authorization, execution state, quarantine, evidence, and scanner integration while keeping production acceptance bound to the exact capability and environment.
Security authority
Wardveil provides shared security meaning and governed coordination. The component that actually executes an action keeps its own local authorization, safety, and readback responsibilities.
Capability definitions, threat and protection semantics, execution-state rules, quarantine boundaries, and evidence structures make security claims machine-reviewable instead of decorative.
Identity and authentication establish who is acting. Consequential security actions still require scoped authorization, exact targets, and executor-side enforcement.
Security posture should be supported by current provenance, execution state, diagnostics, receipts, and scope-specific acceptance rather than inferred from installation alone.
Execution path
Platform relationships
Owns privacy, consent, minimization, data-use, and privacy-status authority. Security evidence may inform privacy decisions without replacing them.
Open Privacy →Owns accounts, authentication, sessions, claims, and identity context. Authentication alone is not universal permission for a security action.
Transports approved security signals and evidence across authorized paths while Wardveil retains security semantics and the executor retains local action authority.
Owns continuity, preservation, backup, and recovery. Wardveil can provide security evidence for restore decisions without becoming the recovery authority.
Defines how security state is presented without manufacturing that state.
Open Design →Claim discipline
The Wardveil name, icon, dashboard, source code, scanner availability, or neighboring platform status is not proof that a workload is protected. The represented control must actually be implemented, authorized, enforced, verified, and accepted for the scope being claimed.