Corroboration
Number of independent sources that agree on the claim.
Claim validation for opportunity memos.
Validation is the quality gate behind the ranked acquisition agenda. It is not the product promise; it is why a recommendation reason is reviewable. Recommendation reasons need source support, weak owner/entity links are labeled or withheld, unsupported fields become open questions, and missing data is not filled with model guesses.
Inputs.
Source posture
Review state, rights posture, and field readiness for the source class.
Source weight
Recorder > derived index; primary > scraped derivative.
Graph resolution quality
Confidence of underlying entity / property edges.
QA review
Reviewer signoff for promotion to customer-visible.
Graph relationships are validated before promotion.
Acren validates graph relationships before promoting them into customer-visible opportunity memos. Reviewed coverage, field quality, display posture, source posture, and QA state determine whether a graph edge can be used, generalized, suppressed, or routed for review.
Confidence bands and behavior.
| Band | Score | Customer visibility | Behavior |
|---|---|---|---|
| Source-backed | ≥ 0.85 | Visible | Full weight in ranking |
| Likely | 0.65–0.85 | Visible · labeled | Reduced weight in ranking |
| Appears connected | 0.40–0.65 | Visible · labeled | Excluded from auto-actions |
| Needs review | < 0.40 | Internal only | Excluded from customer surfaces |
| Rejected | Contradicted | Suppressed | Retained for audit |
- Score
Compute confidence from inputs.
- Threshold
Apply band thresholds and promotion gates.
- Surface gaps
Render missing fields and conflicts explicitly.
- QA review
Reviewed promotion to customer-visible.
- Replay
Reproduce any claim end to end from sources.
- Feedback
Customer feedback flows back to scoring weights.
Failure modes Acren refuses.
Single-source unlabeled inference
Never surfaced as source-backed.
Silent merges
Disagreements are retained on the node and labeled.
Implied readiness
Source posture is shown per field, not implied per page.
Black-box ranking
Inputs and weights ship in the packet; nothing is opaque.
Coverage halo
A claim from a not-customer-ready cell never appears in customer ranking.
Why ship every input with the claim?+
Because replay is the only honest test of validation. If a third party cannot reproduce the score from the inputs, the score is not reviewable.
How are weights chosen?+
Weights are reviewed with input from QA, customer feedback, and source-class behavior. Changes are versioned and reflected in the packet.
What about conflicting records?+
Both records are retained. The packet shows the disagreement, the responsible sources, and the resolution status. Analysts choose how to act.
Responsible use
Research priority, not seller intent
Acren ranks commercial property research priority. It does not infer disposition, hardship, or willingness to transact.
Responsible use
Source evidence required
Every recommendation must carry supporting records, field-level rights status, and verification gaps.
Responsible use
Verification before action
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Responsible use
Display rules built in
Customer-visible, generalized, internal-only, and suppressed fields stay visible as product controls.
Validation
See claim validation inside an opportunity memo.
Sample-packet reviews include source, field, display, and QA posture for the asset class and markets you bring.
Continue
See how each opportunity keeps the source trail attached.