01
Authorized records enter
Single accounts or encrypted batches are normalized across identity anchors, contact data, addresses, restrictions, and supporting documents. First-party records establish a hypothesis; they do not corroborate themselves.
Collections adjudication infrastructure
Your data is not the decision.
Gallus Resolve turns fragmented recovery-file evidence into one documented operating outcome, a registered reason, and the next allowed step.
The decision is the product. The audit makes it defensible.
What to expect
Controls before claims.
Customer-owned providers
Masked-by-default packets
Deterministic, replayable results
How Gallus Resolve works
One complete file. One result per record.
A six-stage operating pipeline preserves evidence lineage from authorized input through a sealed, reproducible determination.
02
Customer-owned evidence is connected
Approved providers are checked for configuration, contract readiness, permitted use, and live-input capability. Calls are bounded, traced, and aimed at material evidence gaps; credentials stay encrypted and provider data is never resold.
03
The account is investigated
An append-only ledger preserves identity hypotheses, collisions, address history, relationships, life events, restrictions, lawful paths, channel policy, lineage, contradictions, and negative evidence.
04
CAS-1 applies fixed gates
Run integrity → Restrictions → Permissible use → Identity → Selected contact-path support → Evidence-family independence → Final decision. Advisory automation cannot create evidence, change policy, or override the result.
05
One canonical outcome returns
Every accepted record reaches Proceed, Review, Block, No Result, or Run Failure. No Result means permitted investigation lacked usable support; Run Failure means execution integrity failed and no substantive decision is claimed.
06
A sealed decision packet is produced
The packet records outcome, reason, next allowed step, evidence basis, restrictions, execution trace, masking state, hashes, and version history. Exports are masked by default and sealed determinations can be replayed.
CAS-1 gate order
Run integrity → Restrictions → Permissible use → Identity → Selected contact-path support → Evidence-family independence → Final decision
Proprietary thresholds and internal adjudication formulas are not published.
PROCEED
Required identity, path, restriction, policy, and independence gates pass.
REVIEW
A named ambiguity, conflict, attribution issue, or policy question remains.
BLOCK
A controlling restriction or prohibited path prevents ordinary treatment.
NO RESULT
The permitted investigation completed without enough usable support.
RUN FAILURE
Technical or execution integrity failed; no substantive decision is claimed.
Viral adoption canvas
Controlled organizational adoption.
Here, “viral” means trusted expansion inside a regulated B2B market—not public sharing of sensitive consumer records.
01
Category idea
Collections adjudication infrastructure between retrieving recovery-file data and taking agency action.
02
Memorable message
Your data is not the decision. Provider count is not source independence.
03
First buyer
Recovery-operations leaders accountable for routing, exception queues, provider performance, and risk.
04
Internal champions
Compliance, legal, audit, agency leadership, client success, creditors, and portfolio owners.
05
Aha moment
One complete file becomes one terminal result per record, with a reason and next step.
06
Shareable proof
A privacy-safe CAS-1 summary—not raw account packets—with outcomes, drivers, coverage, conformance, and hashes.
07
Entry wedge
A controlled evaluation converts an authorized, undifferentiated portfolio into five named queues.
08
Spread loop
Operations reviews → compliance validates → leadership sees results → an adjacent stakeholder requests another file.
09
Success metrics
Production conversion, portfolios added, terminal-state rate, Run Failure rate, Review resolution time, and referrals.
What does the evidence support, why, and what is allowed next?
Engagement model
Start with the file, not a seat count.
Pricing is scoped to record volume, provider configuration, policy requirements, export controls, and deployment needs.
Controlled evaluation
Authorized-file assessment
A bounded evaluation with five outcome queues, a privacy-safe summary, conformance results, and an implementation review.
Production portfolio
Volume-based scope
Ongoing adjudication, approved provider connections, account-level decision exports, sealed packets, and operational review queues.
Enterprise program
Custom deployment
Multiple portfolios or workflows, governance support, tailored integrations, access controls, and organization-wide rollout planning.
Product boundaries
What Gallus does not do.
- Contact consumers or turn Proceed into an outreach command.
- Provide legal advice or guarantee accuracy, recovery, or liquidation.
- Treat provider quantity as independent corroboration.
- Allow AI or provider output to authorize the final decision.
- Present synthetic acceptance results as live production performance.
- Export unmasked decision packets without approval, scope, and operator attribution.
Operating questions
The decision is the product.
Turn an authorized file into defensible operating queues.
Begin with a controlled evaluation. Give operations, compliance, leadership, and clients the same documented answer.