Acren's methodology exists so an opportunity does not become a black-box score. Every surfaced property should show why it appeared, what records support it, what confidence label applies, what is still unknown, and what diligence step should happen next.
Each spec exists to keep a surfaced property inspectable before a team routes it to broker calls, comps, lease research, expense review, underwriting, watchlist, outreach, or pass.
How Acren supports owner/entity context for opportunities without overstating ownership relationships, control, operators, agents, or related-property signals.
How Acren reconciles parcels, APNs, buildings, addresses, and ownership-of-record context before a property appears in a acquisition agenda.
How displayed recommendation reasons and packet fields are gated by source support, recency, corroboration, and confidence labels.
How Acren keeps public-record research separate from seller-intent prediction, consumer eligibility, investment advice, and unsupported claims.
Relationships between properties, parcels, owners, entities, records, and sources are confidence-labeled and reviewable. A relationship can be source-backed, appears-connected, needs-review, rejected, internal-only, generalized, or suppressed depending on the available evidence and display posture.
Sources per rendered claim. No exceptions.
Validators run on every entity update.
Public, versioned, changelogged specifications.
How a target market becomes a ranked queue and packet.
How methods render at the lead and field level.
Score a research workflow by evidence, coverage, confidence, and gaps.
Use guardrails, rights, and posture.