/ai-approval-packet · download
UNAVAILABLE
variant: v0.1
snapshot

Forwardable · downloadable · pilot-bound packet.

A creditor-side reviewer can hand this pilot-bound packet to a compliance officer, a partner, or a board. No login required, no tenant data, no attestation implied.

Forwardable posture

PILOT — forwardable with no login required, no tenant data, and no attestation implied. Each row carries a [shipped] / [planned] / [unknown] / [not shipped] honesty tag.

Renders as a single PDF. Mirrors the page mirror at /ai-approval-packet — the page is the textual mirror; the PDF is the canonical artifact.

filename: settleup-collections-ai-approval-packet-v0.1.pdf

UNAVAILABLE
UNAVAILABLE
§ AI approval packet
UNAVAILABLE

The pilot-bound bundle your partner can inspect before approval.

PILOT — citation-anchored evidence, gate-state taxonomy, supervised-pilot covenant, and export guarantee for a creditor-side firm to inspect before any separately approved production workflow.

Every row on this page is one click from the artifact that backs it. The five terminal states below are deterministic — replay the same input six months from now and the state re-derives identically. The export guarantee is the last line of the packet.

  • № 01 · Proof

    Codification

    UNAVAILABLE

    Every codified statute has a source and scope.

    Plain-English summaries, citation anchors, scope, version, and dated revisions sit on the codified registry so each rule can be inspected before it is used.

    In packet:Rule worksheet with citation, scope, version, and evidence boundary per statute.

    Open proof
  • № 02 · Proof

    Dated rule changelog

    UNAVAILABLE

    Fail-closed stops the action.

    Five terminal states — Permitted · Human Review Required · Blocked · Missing Evidence · Waiting for Approval. Unresolved rules, missing evidence, and low-confidence results block the draft and surface the seven required fields.

    In packet:Dated changelog excerpt + the five-state gate taxonomy.

    Open proof
  • № 03 · Proof

    Methodology

    UNAVAILABLE

    Decisions are explainable.

    Each review decision carries a cited source, a bounded scope, and a human approval checkpoint. Bundle includes a worked review example plus the methodology doc.

    In packet:Methodology doc + worked decision-hash example.

    Open proof
  • № 04 · Proof

    Pilot-bound connectors

    UNAVAILABLE

    Pilot-bound integration.

    Documented connector rows publish their data boundary, permissions model, failure behavior, and testing-evidence log for pilot evaluation. This packet does not evidence a production vendor round trip.

    In packet:Documented connector taxonomy + data-boundary table, per vendor; no production round trip is evidenced.

    Open proof
  • № 05 · Proof

    Data-use boundary

    UNAVAILABLE

    Consumer PII is not a feature.

    Reads the matter file and keeps proposed dispatch artifacts inside the supervised pilot boundary; production system-of-record write-back is not evidenced. The packet carries the full WILL / WILL NOT band plus the pilot boundary pinned to date and tenant.

    In packet:Full WILL / WILL NOT band + supervised-pilot boundary; no production system-of-record write-back is evidenced.

    Open proof
  • № 06 · Proof

    Labor + capacity math

    UNAVAILABLE

    Every delta anchors to your baseline labor.

    Worksheet spec — volume × baseline minutes × corrections × turnaround × fully-loaded cost → staff/attorney freed + capacity gain + price / matter — anchored to YOUR baseline labor. Directional — not a vendor heuristic, not law.

    In packet:Worksheet spec — labor + capacity math, directionally anchored to your inputs.

    Open proof

§ Gate state taxonomy

UNAVAILABLE

Five terminal states. Every compliance decision ends in one — and only one. Pair this list with the worked review example in the methodology bundle.

  • Permitted
    UNAVAILABLE
    State

    Compliance decision cleared.

    When it fires:
    Every codified rule fired true; required evidence satisfied; policy ceiling respected.
    What the system does next:
    Draft queued under role-guarded scope; any dispatch step remains outside this packet and requires separately approved pilot scope.

    log: rule_version + policy_version + triggered_rule + decision_hash + dispatch_audit_row

  • Human review required
    UNAVAILABLE
    State

    Statutory pre-condition needs a partner eyes-on.

    When it fires:
    Presentment pre-condition — assignment chain, balance reconciliation, hardship claim — could not clear without attorney review.
    What the system does next:
    Draft is QUEUED, not DISPATCHED. A partner approval row opens in the matter's audit.

    log: blocked_rule + required_approval_role + partner_review_window

  • Blocked
    UNAVAILABLE
    State

    Fail-closed: the rule did not match anything in the codified registry.

    When it fires:
    An inbound action mapped to no rule row — ambiguous claim, missing jurisdiction scope, signature drift.
    What the system does next:
    No draft. Review reference logged; partner exception row is visible in the audit trail.

    log: no_rule_match + decision_hash + partner_exception_audit_row

  • Missing evidence
    UNAVAILABLE
    State

    Eight required evidence fields absent.

    When it fires:
    Matter file is incomplete relative to the eight required fields the codified rule table enforces.
    What the system does next:
    Draft is BLOCKED. UI surfaces the seven required field tiles; a single attachment re-runs the evaluation.

    log: missing_field_set + decision_hash + re_run_required_flag

  • Waiting for approval
    UNAVAILABLE
    State

    Draft built and previewed. Dispatch held.

    When it fires:
    Draft was permitted, previewed in the matter's audit row, but no user has clicked Approve & Dispatch yet.
    What the system does next:
    Dispatch stays held. A partner approval row records the decision; this packet does not open a production dispatch path.

    log: draft_ready + dispatched_at + dispatcher_user_id

§ Supervised-pilot data-use boundary

UNAVAILABLE

We WILL

  • Read from the matter file the matter file gave us — no other source.
  • PILOT — Keep proposed dispatch artifacts in the isolated audit vault; production system-of-record write-back is not evidenced.
  • Log every decision with rule version + policy version + review reference.
  • Expose the codified rule table, every review reference, and every audit row on demand.
  • Bound the supervised pilot to the matter file scope the underwriter review record pins.
  • aiApprovalPacket.supervisedPilot.will.5
  • aiApprovalPacket.supervisedPilot.will.6
  • aiApprovalPacket.supervisedPilot.will.7
  • aiApprovalPacket.supervisedPilot.will.8
  • aiApprovalPacket.supervisedPilot.will.9
  • aiApprovalPacket.supervisedPilot.will.10
  • aiApprovalPacket.supervisedPilot.will.11

We WILL NOT

  • Auto-dispatch during the supervised-pilot window. Every send waits for human approval.
  • Enrich, score, broker, resell, or otherwise syndicate consumer PII — to anyone.
  • Train or fine-tune any model on consumer PII — ours, yours, or a third party's.
  • Move consumer PII across firm boundaries. Each row stays in the tenant of origin.
  • Hold consumer PII past the export-date in the export guarantee below.
  • aiApprovalPacket.supervisedPilot.wont.5
  • aiApprovalPacket.supervisedPilot.wont.6
  • aiApprovalPacket.supervisedPilot.wont.7
  • aiApprovalPacket.supervisedPilot.wont.8
  • aiApprovalPacket.supervisedPilot.wont.9
  • aiApprovalPacket.supervisedPilot.wont.10
  • aiApprovalPacket.supervisedPilot.wont.11

§ Request the full packet

UNAVAILABLE

Request the pilot-bound packet.

We'll mail the pilot-bound packet — review worksheet, gate-state taxonomy, supervised-pilot covenant, ROI worksheet spec — within one business day. Page-turnable, not slides.