Secretary of State filings
Formations, amendments, dissolutions, member updates, reg-agent changes.
METH-ENT · ENTITY RESOLUTION v3.2
Entity resolution, defensibly.
How Acren resolves LLCs, partnerships, trusts, and operator personas across Secretary-of-State filings, recorder activity, registered-agent history, and signal corroboration — and how it surfaces ambiguity rather than hiding it. Designed to be reviewable by an analyst, not just trusted by a UI.
Inputs.
Recorder activity
Grantor / grantee chains; entity names as they appear at recording.
Registered-agent history
Switch dates; reg-agent clustering for serial-shell detection.
Signal corroboration
Acquisition, refi, and transfer events used to corroborate entity edges.
Address normalization
Filing and recording addresses normalized cross-source.
Entity matches are graph edges, not hidden assumptions.
Acren stores relationship confidence, supporting records, conflicting evidence, and review status so owner/entity context can be shown, summarized, withheld, or rejected.
- Blocking
Multi-pass blocking on name, address, agent, jurisdiction.
- Pairwise scoring
Deterministic + probabilistic match with feature weights.
- Cluster build
Edges built; conflicts surfaced not silenced.
- Persona layer
Cross-entity operator persona derived above legal entities.
- Review gate
Promotion to customer-facing requires reviewed thresholds.
- Feedback loop
Customer feedback flows back to scoring weights and QA.
Confidence labels and what they mean.
| Label | Threshold | Customer visibility | Use in ranking |
|---|---|---|---|
| Source-backed | Multi-source agreement | Visible | Full weight |
| Appears connected | Single source · partial corroboration | Visible · labeled | Partial weight |
| Needs review | Weak match or contested | Internal only | Excluded |
| Rejected | Contradicting evidence | Suppressed · retained for audit | Excluded |
Edge cases.
Series LLCs
Parent and protected series treated as distinct nodes with linkage labels.
Nominee trusts
Disclosed beneficiaries surfaced; undisclosed parties stay as labeled gaps.
Jurisdictional aliases
Same operator across states is clustered, not silently merged.
Common-name collisions
Disambiguated by filing trail; weak matches stay internal-only.
Foreign registrations
Foreign-state registrations preserved with state-of-formation primacy.
Dissolved entities
Retained with status and date — historical research depends on this.
Opportunity memo preview
conf · 0.91 · source-backed
Entity match · Resolved owner entity → operator persona Resolved operator persona.
- Match basis
- Reg-agent overlap (3 entities) · members of record overlap · address cluster
- Supporting filings
- SOS-FRM ×3 · SOS-AMD ×4 · SOS-AGT ×2
- Confidence
- Source-backed (0.91)
- Open questions
- One candidate entity (Candidate related entity) awaiting QA.
- Rejected candidates
- Rejected candidate entity · contradicting reg-agent history
- Review status
- Promoted · reviewer signoff 2026-05-22
- Display posture
- Customer-facing · labeled
Next action
- →Review packetInspect every supporting record
- →Save to universeAdd to reviewed acquisition set
- →Move to needs researchFlag open questions
- →Assign analystRoute to team workflow
- →MonitorWatch for source updates
Why surface ambiguity instead of picking a winner?+
Because a wrong silent merge is harder to recover from than a labeled uncertainty. Analysts can act on a known gap. They cannot act on a hidden mistake.
Can the same entity appear in two personas?+
Yes, with explicit notes. Personas are evidence-derived, not authoritative — they help research, support research judgment.
How often is the model re-trained?+
Weights are reviewed quarterly. Edge-level decisions are reviewable per packet; nothing relies on opaque seasonal drift.
Responsible use
Responsible boundary
Responsible boundary. Not for FCRA-regulated use. Acren organizes commercial-property and business-entity records and ranks research priority from recorded evidence. It does not predict intent, provide valuation or underwriting, or support consumer-eligibility decisions.
Responsible use
Source trail required
Every recommendation must carry source trails, field-level rights status, and open questions.
Responsible use
Review before action
Customers are responsible for verifying records before outreach, capital, or workflow decisions.
Responsible use
Display rules built in
Customer-facing, summarized, internal-only, and withheld fields stay visible as product controls.
Entity methodology
See entity resolution in your jurisdictions.
Access reviews include entity-resolution readiness for the entity or property context you bring.
Next step
Start with your market and buy box.
Responsible boundary. Not for FCRA-regulated use. Acren organizes commercial-property and business-entity records and ranks research priority from recorded evidence. It does not predict intent, provide valuation or underwriting, or support consumer-eligibility decisions.