The self-running automation backlog produced five endpoint shapes that are small enough to ship without pretending to be a lawyer, broker, doctor, or platform appeals team.

This batch adds:

  • vendor-questionnaire-draft for evidence-supported security questionnaire answers.
  • app-store-rejection-explain for App Store and Google Play rejection triage.
  • rfp-requirements-extract for RFP, grant, and solicitation requirement extraction.
  • marketplace-notice-explain for seller account and platform notice packet planning.
  • tariff-duty-scenario for landed-cost and duty-rate what-if math.

The boundary is deliberate. These endpoints extract, calculate, classify, and build checklists. They do not submit appeals, choose final HTS classifications, guarantee app approval, guarantee awards, or invent compliance claims.

vendor-questionnaire-draft is the cleanest Prooflayer expansion: upload questions plus evidence snippets, and unsupported answers come back as needs_evidence. tariff-duty-scenario is the cleanest EdgeFinance entry: caller supplies rates and shipment values, then the endpoint returns current vs proposed duty and landed-cost deltas.

The other three are first cuts at the same pattern: exact scary text in, structured packet out, with a hard stop before regulated or platform-sensitive action.