execution-domain-core

name	execution-domain-core
description	Scoped execution environment, task policy, and exit criteria system for Yuri OS / Yuri. Inspired by Domain Expansion, translated into enterprise-safe system behavior. Use when the user says 'scope this task', 'set boundaries', 'define exit criteria', 'create a domain', or 'contain this work'.
version	1.0.0
status	active
enterprise_ready	true
non_destructive_default	true
triggers	["/yuri domain","/domain","/edc"]
requires	["enterprise-control-plane","audit-events","rollback-policy"]
scope	harness
invocation	workflow

Execution Domain Core Skill

When to use

Use this skill when the user asks Yuri OS / Yuri to perform work involving:

• user_goal
• target_paths
• constraints
• allowed_tools
• risk_tolerance
• deadline_or_budget
• enterprise_requirements

Also use it when the active task matches this operating principle:

Create a bounded task environment with explicit rules, allowed tools, target files, risk limits, evidence requirements, and exit criteria before serious work begins.

When not to use

Do not use this skill when:

• the task is trivial and does not need system-level treatment
• no target, goal, or evidence source is available
• the user explicitly requests no architectural expansion
• the task would require destructive action without approval
• the extension would duplicate an already active domain without adding value

Trigger phrases

• "run execution-domain-core"
• "use Execution Domain Core"
• "turn this into Yuri OS DNA"
• "analyze and integrate this safely"
• "enterprise-ready extension"
• "non-destructive implementation plan"
• "bake this into the system"

Required inputs

input:
  goal: string
  artifact_type: user_goal | target_paths | constraints | allowed_tools | risk_tolerance | deadline_or_budget | enterprise_requirements
  target: string
  constraints:
    enterprise_mode: true
    destructive_actions_allowed: false
    require_audit_trail: 
     
  
       
     []