Invisibility

1. Restate the target, the success condition, and any no-touch boundaries before taking action.
2. Inventory what is currently exposed through logs, alerts, interfaces, metadata, or temporary artifacts.
3. Trim nonessential exposure while preserving the traces operators, auditors, and debuggers actually need.
4. Return the quieter operating pattern and the visibility that intentionally remains.
5. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

• A reduced-footprint operating plan.
• A list of traces to suppress, minimize, or relocate.
• A list of audit and debugging surfaces that must remain.

Pitfalls / Guardrails

• Keep the metaphor anchored to a real mechanism instead of drifting into lore.
• Do not delete or suppress records required for security review, compliance, or incident response.
• If the request is really about hiding wrongdoing, this is the wrong spell.

Verification

• Check that the result includes every deliverable promised above.
• Check that confirmed facts, assumptions, and inferences are visibly separated.
• Check that the metaphor still maps cleanly to a real operational mechanism.

Example Invocation

/invisibility reduce the unnecessary noise and exposure around this workflow while preserving the traces we are obliged to keep