---
name: intake
description: >
  Verify and propose one target repository and plan directory when repository
  identity is absent or ambiguous. Use for Intake before Architectural
  Alignment. Do not use after owner-confirmed fit, for parent-wide exploration,
  planning decisions, product edits, role routing, or publication.
---

# Intake

The Orchestrator runs this in its controller session and records the decision.
Intake handles input and repository selection.

## Inputs and match

- **Inputs:** Lifecycle goal, authorized candidate roots, visible prior decisions,
  repository rules, and discovery limits.
- **Match:** target root, repository identity, or plan location is unresolved.
- **Non-match:** the owner already named and confirmed the repository and plan.

## Algorithm

1. Inspect the selected root only. Open one additional root only when authorized.
2. Cap discovery at depth 4 and 200 paths; prefer Git identity, manifests,
   top-level instructions, and current plan conventions.
3. Reject nested-repository confusion, missing Git identity, or conflicting
   owner evidence with a typed finding.
4. Propose exactly one repository and one plan-directory assumption with path
   evidence and a short reason.
5. Return one owner confirmation question through the Orchestrator. A recommendation
   is not confirmation.

## Return and recovery

Return `FIT_PROPOSED`, `FIT_CONFIRMED`, `FIT_UNAVAILABLE`, `FIT_MALFORMED`, or
`FIT_UNDECIDABLE` with root, plan directory, evidence, blocker, and next action.
Resume only from new evidence; never repeat confirmed input or add agent runs.

Never write files, walk unapproved parents, rank endless alternatives, or
advance the Lifecycle itself.