Public demo

Scheduling should be connected to readiness.

A hearing slot is only useful when the packet, service/proof posture, timeline, evidence, and correction state are clear enough for meaningful review.

SurfaceScheduling and readiness
GoalReduce not-ready hearings
SignalPacket-ready status

Scheduling as operations

Scheduling should not be isolated from the state of the record. ProSe can help show which matters are awaiting slots, which are not ready, and which have service, proof, or packet gaps.

Readiness signals

Packet readiness

Show whether the required documents and review steps are complete.

Service/proof posture

Surface exceptions that may prevent meaningful movement.

Correction status

Keep returned packets visible until issues are resolved.

Calendar placement

Connect slotting to operational readiness rather than simple date selection.

Public value

When readiness is visible, the public can better understand why delay happens and what process improvement should measure.