Skip to content
Luiz Hogrefe

AnyImob

An earlier applied implementation: an AI assistant for real-estate brokerage

Applied implementation · historical lineage

How does an assistant stay inside what the project data supports, and recognise when a person has to take over?

AnyImob on anylai.eu

Overview

AnyImob is an AI assistant for real-estate brokerage in Brazil, built before the current AnyLAI research. It answers questions about property developments, checks its answers against project data, refuses advice it may not give and opens a handoff to a human broker when a guardrail fires.

It is a technical lineage, not an application of today's frameworks: it implements neither COADF nor ERQYO. Several of its patterns, such as grounding, confidence after generation and handoff, were later generalised in AnyLAI's research.

Guardrails, first hit wins

Guardrails, first hit wins
  1. Question
  2. Retrieve project data
  3. Draft answer
Answer with confidence

An answer is shown only if no guardrail fires. Otherwise it is rewritten, refused or handed over.

Text description of the diagram

A question enters, relevant project data is retrieved and a draft answer is generated. The draft passes an ordered list of guardrails: request for a human, contradiction between sources, low retrieval confidence, identity questions, advice outside scope such as financing, legal or valuation, urgency pressure and grounding against project data. The first guardrail that fires decides: hand over to a broker, block, or rewrite. If none fires, the answer is shown with its confidence.

Building blocks

  • Grounding check

    Claims in an answer are compared as canonical values, such as amounts, areas and dates, against the project data.

  • Answer confidence

    Computed after generation and after the guardrails, and kept separate from retrieval similarity. A refusal is always low confidence.

  • Guardrails

    An ordered list of checks where the first hit wins, from a request for a human to out-of-scope advice.

  • Handoff ticket

    A persisted ticket that gives the conversation to a broker, with the reason.

  • Audit log

    A record of what the assistant decided and why.

One conversation

  1. 1

    A visitor asks for the price and size of an apartment.

  2. 2

    The answer's amount and area are compared with the project data and match.

  3. 3

    The visitor then asks whether the apartment is a good investment.

  4. 4

    The advice guardrail fires: the assistant declines to advise and opens a handoff ticket for a broker.

How it differs

  • AnyImob ≠ ERQYOReference implementation · not deployed

    ERQYO is a later, general runtime architecture. AnyImob predates it and does not use it.

    ERQYO

  • AnyImob ≠ COADFPublished framework

    COADF formalises governance principles. AnyImob is an earlier implementation and is not presented as applying them.

    COADF

Status

Applied implementation · historical lineage

An existing applied implementation and historical lineage. Its assistant features sit behind a feature flag that is off by default, and it is not publicly accessible.

It was built during an earlier entrepreneurial phase that is separate from AnyLAI's non-commercial research.

Limitations

  • The chat is stateless on the server; conversation history is held by the client, and only handoff tickets store a thread.
  • Grounding covers values that exist in the project data; it cannot check what the data does not contain.
  • Not presented as implementing COADF or ERQYO.

← Back to Projects