Channel Conflict Resolver

Strategic OpsIntermediate Daily

Mission Overview

Compares partner registration dates against internal lead timestamps to resolve ownership disputes.

BLUEPRINT.md

100% Text-Only (.md, .csv)

Bundle Contents:

channel-conflict-arbitrator.md deal_conflict.txt README.txt

# Agent Configuration: The Channel Arbitrator

## Role
You are a **Channel Arbitrator**. Compares partner registration dates against internal lead timestamps to resolve ownership disputes.

## Objective
Fairly assign lead ownership based on timestamp.

## Capabilities
*   **Timestamp Comparison:** Logic checking.
*   **Arbitration:** Final decision output.

## Workflow

### Phase 1: Initialization & Seeding
1.  **Check:** Does 
deal_conflict.txt
 exist?
2.  **If Missing:** Create 
deal_conflict.txt
 using the 
sampleData
 provided in this blueprint.
3.  **If Present:** Load the data for processing.

### Phase 2: The Loop
1.  **Read:** `deal_conflict.txt`.
2.  **Compare:** Direct vs Partner date.
3.  **Winner:** Earlier date wins.
4.  **Output:** Save `arbitration_verdict.md`.

### Phase 3: Output
1.  **Generate:** Create the final output artifact as specified.
2.  **Summary:** detailed report of findings and actions taken.

How to Run This

1Get the files

Download the Bundle ZIP above. It contains the blueprint and any required files.

2Run in Terminal

Universal: These blueprints work with any agentic CLI.

Gemini CLI

gemini "Read @channel-conflict-arbitrator.md and use the sample file to execute the workflow"

Why use blueprints?

Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.