← All screens |2.10 Client-ready gate + export ← Prev Next: System states →

2.10 · Client-ready gate & export 4C preview

Addendum §3 (controlling): the gate is server-computed API-NEW and means "no unresolved unsafe state remains in the included output" — not "the user clicked past the warnings". The UI may render the gate but is not the source of truth. Export (CSV/XLSX/HTML with citations + audit) is new API-NEW.

4C preview
Not in the 4A first slice. The server-computed client-ready gate and export (CSV/XLSX/HTML with citations + audit) are Phase 4C. In 4A the Client-ready control is shown disabled; this screen previews the gate and export that arrive later. Note client_ready is a matter/export gate state, never a per-cell gutter.

Not ready Gate blocked

5 included cells block export. The gate blocks if any included cell/claim has:

  • review_status ∈ {draft, needs_source, needs_lawyer_review, escalated, stale}
  • support_status ∈ {unsupported, not_registered, stale}
  • failed or running generation / extraction / refresh jobs
  • blocker-severity warning codes
  • missing required authority checks for legal-rule / regulatory / procedural / application claims
✗ 1 unsupported blocker
~ 2 stale blocker
2 needs lawyer review blocker

rejected cells are excluded from output by default, but their decision record remains available in the audit export if requested.

Ready 0 blockers

Pre-export summary
Included cells
18
Supports
31
Unsupported
0
Rejected (excluded)
2 — in audit only
Include citations (quote + locator + version)
Include audit trail (reviewer, time, decisions)
Apply privilege / PII redaction (review before sending to a client)

An client_ready audit event is emitted. A careless export is a confidentiality incident — the redaction option intersects the privilege/PII and retention ADRs (blueprint §7.8).

Honesty. Any later internal/working export must be visually and semantically distinct from a client-ready export, so an unfinished review is never mistaken for a defensible deliverable.