Logic
Rules conflict. The value of a formal system is that they conflict the same way twice — and that the resolution is written down.
Rules conflict. Resolve them in this order, highest first.
safety law privacy policy
user value and accuracy
technical eligibility and canonical correctness
business value and constraints
intent fit and information quality
measurement and learning
efficiency and scale
cosmetic optimization
Use AND when all conditions are necessary. A failed mandatory condition blocks publication or sends the candidate to research.
PUBLISH
IF demand_is_evidenced
AND intent_is_distinct
AND business_fit_is_positive
AND information_advantage_exists
AND asset_is_maintainable
AND measurement_is_installedUse OR when several different forms can satisfy the same requirement. OR does not mean “include everything.” It means choose one or more valid alternatives according to the task.
EVIDENCE
=
firsthand_experience
OR original_data
OR reproducible_test
OR qualified_expert_review
OR documented_case_studyUse XOR when only one choice can be canonical.
FOR EACH dominant_intent_cluster:
existing_url XOR new_url XOR merged_url
MUST be the intended canonical destinationTARGET_CLUSTER
=
candidate_queries
NOT jobs
NOT salaries
NOT unrelated_brand
NOT wrong_geography
NOT wrong_languageIF same_task
AND same_answer_structure
AND same_result_format
AND same_next_action
THEN merge_into_one_canonical_asset
ELSE split_or_testThis creates candidates, not automatic publication.
FOR EACH approved_location
AND FOR EACH approved_service
GENERATE candidate_location_service_pageREPEAT diagnose → change → observe → decide
UNTIL:
target_is_reached
OR expected_value_falls_below_cost
OR constraint_is_triggeredAT_LEAST 1 useful internal link points to every priority canonical page
AT_MOST 1 dominant intent owns a canonical URL
EXACTLY 1 primary KPI governs an experimentIF all mandatory conditions pass
THEN execute or advance the candidate
ELSE route to research, consolidation, repair, deferral, or rejection