skill-007-ecosystem-conflict-resolution

Apply a tiered precedence ladder that ranks explicit founder orders (T0) above permission rules, open incidents, and convenience workflows. Before the first disk edit, parse the founder message for explicit authorization and block all writes until the highest-tier rule is identified.

A precedence ladder is an ordered ranking of rule sources so the highest tier wins any conflict. This Skill uses six tiers from T0 (explicit founder commands like SAVE TO or EDIT ALLOWED) down to T5 (convenience rules like plan.json that never self-start).

An agent should refuse disk writes when a workflow rule demands action but no explicit founder order exists, when a save request lacks a resolvable path, or when the target path belongs to another lane. It then presents A/B/C options and waits for founder approval.

Valid T0 triggers include SAVE TO with a path, EDIT ALLOWED plus ACTION, ASF phrases, WORK assignments, or a direct yes to an agent's question. Prior session context, plan.json files, and mandatory paste instructions alone do not qualify.

The agent runs a filing registry resolver script to map the request to a route_id and path. If the registry returns no match or an ambiguous match, the agent asks only for the category or scope, never the exact path.