Automation & Blueprints
Safe automation in MapleOS should be transparent, permission-aware, and easy to interrupt. Blueprints are the preferred mental model: named steps, readable structure, and obvious inputs and outputs.
Safe patterns
- Show the chain. Users should be able to understand the order of operations.
- Minimize permissions. Ask for the least access needed to finish the workflow well.
- Keep human checkpoints. High-impact actions should support review or confirmation.
- Separate grounding from memory. Use the right context tool for the job instead of blending everything together.