Required inputs
- Content Sha256
- Deal ID
- File Name
- Source Documents
Can we triage every incoming file FIRST — detect type, classify to a DocumentKind, surface candidate wells (API10), flag ambiguous units, and emit the canonical extraction envelope with quality_flags? Trigger phrases: file triage and provenance, file triage & provenance. Produces: cited file triage & provenance workpaper and decision flags.
Registry maturity does not prove response or artifact quality. No qualifying same-model skill-on versus no-skill improvement has been verified.
Policy visibility is not execution proof. Authentication is checked before a run.
The skill entry point is callable. Any downstream write or external action is checked separately.
The skill entry point is callable. Any downstream write or external action is checked separately.
Review review applies before a consequential external or binding action. Analysis and working artifacts remain available before that review.
This is review guidance for a later external or binding action. Supported analysis and a working artifact remain available with the review item attached.
No specific dependent input gap is declared.
Authentication and the required buyer profile are checked before any work runs.