| name | constraint-engine |
| version | 1.2.0 |
| description | Learn from consequences, not instructions — generate and enforce constraints from experience |
| author | Live Neon <contact@liveneon.dev> |
| homepage | https://github.com/live-neon/skills/tree/main/agentic/constraint-engine |
| repository | leegitw/constraint-engine |
| license | MIT |
| tags | ["agentic","constraint","enforcement","circuit-breaker","lifecycle"] |
| layer | core |
| status | active |
| alias | ce |
| disable-model-invocation | true |
| metadata | {"openclaw":{"requires":{"config":[".openclaw/constraint-engine.yaml",".claude/constraint-engine.yaml"],"workspace":["output/constraints/","output/hooks/"]}}} |
constraint-engine (制約)
Unified skill for constraint generation, pre-action checking, circuit breaker management,
and constraint lifecycle. Consolidates 7 granular skills into a single enforcement system.
Trigger: 行動前∨閾値到達 (pre-action or threshold reached)
Source skills: constraint-generator, circuit-breaker, emergency-override, constraint-lifecycle, constraint-versioning, positive-framer (partial), contextual-injection (partial)
Installation
openclaw install leegitw/constraint-engine
Dependencies: leegitw/failure-memory (for eligibility data)
openclaw install leegitw/context-verifier
openclaw install leegitw/failure-memory
openclaw install leegitw/constraint-engine
Standalone usage: Requires failure-memory for constraint generation from observations.
For full lifecycle management, install the complete suite (see Neon Agentic Suite).
Data handling: This skill is instruction-only (disable-model-invocation: true).
It provides constraint templates and enforcement logic but does NOT invoke AI models itself.
No external APIs or third-party services are called. Results are written to output/constraints/
in your workspace. The skill only accesses paths declared in its metadata.
What This Solves
Instructions get ignored. Rules get forgotten. Documentation goes unread. This skill takes a different approach — constraints generated from actual failures:
- Generate constraints from observations that meet the eligibility threshold (
R≥3 ∧ C≥2)
- Enforce constraints at runtime with a circuit breaker (CLOSED → OPEN → HALF-OPEN)
- Manage lifecycle from proposal through adoption to retirement
The insight: A constraint born from "this actually broke" carries more weight than "this might break." Consequences teach better than instructions.
Usage
/ce <sub-command> [arguments]
Sub-Commands
| Command | CJK | Logic | Trigger |
|---|
/ce check | 検査 | action→constraints[]→pass∨block |