Some checks failed
Tests / test (push) Failing after 2s
- Merged all unique darkplex-core modules into cortex: - intelligence/ subfolder (anticipator, collective, shared_memory, knowledge_cleanup, temporal, llm_extractor, loop) - governance/ subfolder (policy engine, risk scorer, evidence, enforcer, report generator) - entity_manager.py, knowledge_extractor.py - Fixed bare 'from intelligence.' imports to 'from cortex.intelligence.' - Added 'darkplex' CLI alias alongside 'cortex' - Package renamed to darkplex-core v0.2.0 - 405 tests passing (was 234) - 14 new test files covering all merged modules
40 lines
1 KiB
YAML
40 lines
1 KiB
YAML
# External Communications Policy
|
|
# Controls when and how agents can communicate externally.
|
|
|
|
name: external-comms
|
|
description: Governs agent communication with external systems and parties
|
|
version: "1.0.0"
|
|
|
|
rules:
|
|
- name: deny-assistant-external-email
|
|
description: Assistants cannot send external emails without escalation
|
|
conditions:
|
|
agent_role: assistant
|
|
action: send_email
|
|
target: external
|
|
effect: escalate
|
|
priority: 80
|
|
|
|
- name: allow-operator-external
|
|
description: Operators may communicate externally
|
|
conditions:
|
|
agent_role: operator
|
|
target: external
|
|
effect: allow
|
|
priority: 70
|
|
|
|
- name: deny-external-api-restricted
|
|
description: No external API calls with restricted data
|
|
conditions:
|
|
action: api_call
|
|
target: external
|
|
data_type: restricted
|
|
effect: deny
|
|
priority: 100
|
|
|
|
- name: allow-internal-comms
|
|
description: Internal communication is always allowed
|
|
conditions:
|
|
target: internal
|
|
effect: allow
|
|
priority: 10
|