Project Uploads
Manage the files uploaded to this project.
Evidence detailsChecking
Not assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protectedProject Uploads content
Counts describe inventory. Hashes establish file identity. Classification routes the file. None of these facts is a schedule-quality score.
Identity only
Choose a project, then inspect or re-check the schedule files that belong to it. Upload identity, dates, hashes, format, parser provenance, and bounded TASK field coverage stay together here; raw schedule bodies stay hidden.
Select one immutable review to inspect present, blank, invalid, and absent TASK fields.
No review selected. Missing values remain unknown and are never rendered as zero.
This page uses metadata-only server JSON. It shows filenames, classifications, byte counts, hashes, parser coverage, and provenance summaries; it never returns raw XER/XML bodies or server source paths.
Only reading order changes. Values, citations, authority, and review provenance stay fixed.
Reactions are observations; they never change the champion by themselves.
Review status and evidence steps
Steps update from visible page evidence. Blocked and withheld states name the boundary; no completion percentage is inferred.
Discussion questions and talking points
Observed → derived → withheld remains explicit. These talking points stay tied to the selected evidence; they are not an unrestricted database question box.
Unavailable context remains explicitly not supplied.
This talking point preserves the page’s evidence and authority boundary.
