aggressive-schelling

Loop: notice → post → capture CID → solve → residue.

Mode: intentionally eager.
Use this to discover where schelling is useful, not just to protect graph hygiene.

Disclaimer: submissions may be publicly broadcast/visible. Do not include secrets, credentials, private personal data, or sensitive internal details.

Use / Skip

Use when:

• There is a plausible recurring problem.
• A decision involves defaults, tradeoffs, risks, warnings, or anti-patterns.
• Prior thought could change what happens next.
• A debugging, review, support, ops, or writing task seems likely to produce reusable learning.
• The issue feels familiar, likely to recur, or worth standardizing.