/**
 * The pre-authorization surface. Fixed by #23 decision 4.
 *
 * Lives OUTSIDE the authenticated shell and needs its own minimal entry point:
 * it renders for an actor with no org, no capability and no subscription.
 *
 * The invitation shows issuer, category and deadline — and nothing else.
 * Scope, volume band and terms are RFP content and stay behind the wall.
 *
 * The full vendor sequence:
 *   invited -> subscribe -> teaser -> acknowledgement -> full RFP
 *   (a billing gate, then a confidentiality gate, doing different jobs)
 */
export interface InvitationView {
  issuerName: string
  categoryLabel: string
  responsesDueAt: Date
  invitedAs: string
}
