project-intakelisted

# Project Intake ## Purpose Establish an evidence-backed answer to “what does this project have now?” without treating filenames, directories, or existing files as proof of Artifact type or validity. ## Trigger Run at initial startup, on an unfamiliar or resumed project with uncertain state, after substantial new `input/` material arrives, or when the current inventory no longer matches the repository. ## Inputs - User request, `config/project.md`, `input/`, and relevant repository content. - Existing Artifact Registry, State, and latest Checkpoint when present. - Target Stage or target Artifact, if known. ## Prerequisites - Confirm the project root and accessible scope. - Do not require organized input directories; treat placement and extension as hints only. - Do not expose secrets or inspect irrelevant sensitive content. ## Procedure 1. Read Project Configuration, current State, Checkpoint, and target. 2. Scan `input/` and target-relevant repository areas; record skipped or inaccessible scope. 3. Inspect content sufficiently to identify each asset's meaning rather than inferring from its name alone. 4. Assign an Asset ID, source path, source kind, revision/freshness signal, and confidence. 5. Classify candidate Artifact type and likely lifecycle stage from content. 6. Determine initial completeness and status: `MISSING`, `PARTIAL`, or `UNVERIFIED`; never assign `VALID` solely because a file exists. 7. Detect duplicates, contradictions, obsolete variants, unreadab