# Separate task creator from delivery owner

Illustrative planning brief; no automatic product import.

Illustrative request: “show tasks I created.” Several of those tasks are owned by colleagues, while other tasks assigned to the requester were created elsewhere.

## Decision

Use the creator constraint for origin questions and the owner constraint for delivery responsibility.

## Owned work

- Identify the subject
  - Owner role: Analyst
  - Acceptance evidence: The question explicitly distinguishes created by from assigned to.
- Choose the matching filter
  - Owner role: CLI user
  - Acceptance evidence: The read uses --creator me or --owner me according to that subject.
- Explain the result boundary
  - Owner role: Reviewer
  - Acceptance evidence: The answer states which relationship was filtered and its pagination coverage.

## Workflow

1. Ask whether the requester means tasks they created, tasks they own, or the intersection; write that subject in the review brief.
2. Inspect the installed creator and owner filter contracts, resolve the subject in the intended organization, and preserve the requested project restrictions.
3. Label the returned list with the relationship and pagination covered; do not describe created work as assigned work.

## Judgment

Creator and owner are not interchangeable, even when the same person fills both roles on some tasks.


## Filled illustrative planning example

Synthetic records: W-17 was created by Morgan and is owned by Lee; W-18 was created by Lee and is owned by Morgan. For Morgan, a creator query concerns W-17 and an owner query concerns W-18. These are illustrative relationships, not live records.


## Before / after

Before: List tasks owned by me and call them “tasks I created.”

After: Use the creator filter and state that the result concerns task origin, not current ownership.


## Workflow questions

### Is creator a responsibility assignment?

No. It records origin; ownership concerns responsibility for moving the work forward.

### Can a task have different people in these roles?

Yes. Read the actual fields rather than inferring one from the other.

## Product connection

This manual brief helps an authorized TeamBoost CLI user keep identity, query scope and review evidence explicit. Check the installed interface and account access before using a source-backed command.

Confirm account availability before adopting this manual outline.