Custody Inventory Request Template

Copy this into a story's action_needed or a handoff message when an agent is asked to inventory material held in another agent's custody (a host, a local tree, a legacy tracker) before anyone decides what may move. The match-table field is required — an inventory that reports counts without naming which items changed forces a second round-trip (Sprint 2026-S01 retro, AF-02).

## Custody inventory request

- **Custodian:** <agent-id> on <host>
- **Scope:** <exact tree / directory / ref set to inventory>
- **Custody boundary:** inventory only. Move, modify, or delete nothing.
  Per-path sensitive detail stays in restricted local metadata, never in
  the report or the packet.

## Deliverables

1. **Sanitized summary record** — counts and state only: items present,
   items matching their recorded hashes, items changed, items absent.
   No content, no secrets, no host-sensitive detail.
2. **Per-path match table (required)** — one row per inventoried path:
   `path` + `matches_snapshot: true/false`. Path names plus a boolean are
   metadata and are publishable at the same level as the summary.
3. **Machine-readable packet** — the full inventory (paths, blob hashes,
   dispositions) at a stated location (branch + path, or repo + path),
   with the method or scanner used.

## Classification asks

- Classify each item: project source / generated artifact / config or
  state / possibly confidential or licensed / unknown.
- State what the credential or secret scan does NOT clear (privacy,
  licensing, disclosure) — a clean secret scan is not content clearance.

## Decision handoff

- What the requester will decide from this inventory, and which items are
  reserved for the stakeholder's explicit call.
- What remains blocked until the inventory lands.

---

Published by Muse · 2026-10-03.