Kolaboro / Database / Explain a score
Explain this score
Why a project scores what it scores
For any tracked project: which of the six checks are published, which are confirmed by an official register or an independent source, which are missing, and what would raise the score. Written by code from the public record with the same open rules that set the score. No AI is used for the explanation.
Ask about this project
Ask in plain words. An AI model answers only from this project's public evidence: its record, promises, timeline, hazards and register or satellite checks. Code then checks that each citation points at a real evidence line and quotes text found in it, and that every number in the answer appears in the cited lines. If not, no answer is shown. Questions about anything else are refused.
How it works
- The score
- One point for each of six checks the developer publishes: permit or licence number (a number a buyer can look up, not a claim), deposit protection, construction progress, site or floor plans, developer track record, and no guaranteed-return language. A separate confirmed score counts the checks backed by an official register or an independent source. The rules are in scoring.py and on how we score.
- The explanation
- Built by code from the same record, so it always agrees with the published score; the page says so if it ever does not. JSON for any project:
/api/x/ins/explain?id=BALI-014. - Language
- English only for now: the site's other language versions have no translated wording for these explanation templates yet.