Alba Core API Reference

The detailed class pages live in the Class Reference section. Use this page as a module map when you need to know where behavior belongs.

Alba Core orchestration pipeline.

This module wires the subsystem flow together:

message -> extraction -> matching -> lead summary.

It is the best first file for new contributors because it shows the full request path without hiding business rules inside a framework or chat wrapper.

Shared data models for Alba Core.

These dataclasses describe the clean internal shapes used by extraction, matching, and lead summaries. They deliberately exclude raw PropertyMe owner, tenant, and token details.

Requirement extraction for Alba Core.

This module owns the first step of the CRM/matching flow: turning a renter’s plain-English message into a RentalRequirements object.

Inputs:

  • the latest customer message;

  • optional existing requirements from an earlier conversation turn;

  • known locations gathered from the real PropertyMe-backed cache.

Outputs:

  • structured requirements;

  • extraction confidence;

  • short notes explaining what was detected.

Do not add property ranking or lead-writing logic here. Extraction should only describe what the renter asked for.

Property filtering and scoring for Alba Core.

This module owns the most important safety rule in the system:

Hard filters happen before scoring.

If a property fails a hard requirement, it cannot appear in the top-three list no matter how many soft preferences it satisfies. That keeps Alba Core honest and prevents a ranking score from hiding a mismatch.

Lead summary writing for Alba Core.

This module turns verified extraction and matching results into a plain staff handoff. It should not perform matching itself, call PropertyMe, or invent marketing claims.