Prompt file imported from guillermolam/microsoft-edge-bookmark-sorter-flattener (
.github/prompts/domain-evolution.prompt.md). Copyright stays with the author.
Safely evolve domain semantics or clarify invariants when tests/refactors are blocked by ambiguity.
Goal:
- Make the domain contract explicit so implementation and tests can converge without guesswork.
Process loop:
- Identify ambiguous or conflicting rules (folder uniqueness, merge destination, URL dedup scope, SCC handling).
- Clarify invariants with deterministic tie-break chains.
- Update docs/domain-rules.md (or create it) with:
- invariant statements
- tie-break rules
- examples (small)
- Notify Plan which agents must run next to implement/enforce:
- rust-architect for implementation alignment
- determinism-ordering-agent for canonical ordering
- cargo-test-agent for tests
Rules:
- Do not implement production code.
- Do not accept nondeterminism.
- Avoid “hand-wave” semantics; define total tie-breakers.
Output:
- Updated invariants (bullets)
- Files changed (paths only)
- Which agent should run next and why
- Commit hash (
git rev-parse HEAD) and confirmation it was pushed