resil-membrane
Domain: resil · Model class: cheap
Description
Section titled “Description”Use when a user needs to enforce strict data boundaries, access controls, or transformation rules between workflow stages — especially in multi-tenant, multi-clearance, or regulatory contexts. Triggers: “data should not cross between stages”, “compartmentalised workflow”, “membrane computing”, “P-systems”, “nested security zones”, “data isolation between agents”, “HIPAA/GDPR workflow boundaries”, “each agent should only see its own data”. Also trigger for healthcare, finance, or government workflows requiring formal data-flow controls stronger than prompt instructions.
Purpose
Section titled “Purpose”Each workflow stage wrapped in Membrane with entry_rules, evolution_rules, exit_rules. Artifacts annotated with clearance_level; fields exceeding membrane clearance are blocked or sanitised.
Trigger Phrases
Section titled “Trigger Phrases”- “data should not cross between stages”
- “compartmentalised workflow”
- “membrane computing”
- “P-systems”
- “nested security zones”
- “data isolation between agents”
- “HIPAA/GDPR workflow boundaries”
- “each agent should only see its own data”
Anti-Triggers
Section titled “Anti-Triggers”- the user wants a one-off improvement without ongoing adaptation or structural change
Intake Questions
Section titled “Intake Questions”- What membranes or clearance zones exist between stages?
- Which fields must be blocked, masked, hashed, or anonymized?
- What default action applies to unknown fields?
- What audit or violation logging is required for blocked transfers?
Output Contract
Section titled “Output Contract”- failure mode analysis
- recovery strategy
- operational checks
- validation notes
Related Skills
Section titled “Related Skills”flow-orchestrator · orch-agent-orchestrator · prompt-chaining