Platform

Probability is fenced. Compliance is computed.

Tasaab is built around a clean split: deterministic code owns facts and decisions; a language model, when used, can only describe results already established by the engine.

The module contract

The same four steps, in every jurisdiction.

A failed source is not treated as an empty result. It marks the evidence incomplete and suppresses the compliance matrix.

  1. 01
    Deterministic

    Gather evidence

    Query government GIS and registries, normalize geometry, and preserve feature IDs and source dates.

  2. 02
    Deterministic

    Build obligations

    Apply transcribed statutory rules. Every obligation must carry the evidence identifiers it rests on.

  3. 03
    Bounded

    Draft and audit

    Optional model-generated prose passes through a deterministic critic. Three failed attempts lock the section.

  4. 04
    Reviewable

    Compile the pack

    Produce unsealed DOCX, XLSX, PDF, spatial data, and a manifest for qualified professional review.

Formal verification

Wrong and impossible are different findings.

Geometry and thresholds are expressed as a satisfiability problem. Fixed measurements stay pinned; negotiable design choices remain free. Exact rationals keep boundary cases exact.

Z3 proof kernelcompleted · 018 ms
assert footprint ≤ 0.15 × parcel
pin parcel = 43,560 ft²
pin footprint = 5,880 ft²

PROVEN_COMPLIANT
headroom = 654 ft²

From desk to field and back

Missing facts become a field brief—not an invented answer.

Pre-field

Find what the data cannot know

Desk assessment turns each refusal into coordinates and a required measurement.

On site

Observe the physical world

The qualified professional records only what the field brief identified.

Post-field

Re-run the same engine

Measurements resolve existing rules. No second arithmetic pipeline can drift.

Six enforced invariants

Trust is an architectural property.

These are tested boundaries, not product principles left to convention.

01

Determinism over probability

Code owns every number, geometry, and threshold. Models may draft prose; they never decide compliance.

02

Professional reliance stays intact

The engine prepares unsealed drafts. A qualified professional reviews, decides, and signs.

03

Every obligation has evidence

An obligation cannot exist without the spatial features, registry records, or statutory citations supporting it.

04

Repair loops are bounded

After three failed drafting attempts, the section locks and requires qualified professional action.

05

Jurisdictions stay isolated

Modules depend on a shared core, never on one another. Import boundaries are enforced in tests.

06

Licensing remains clean

The engine excludes GPL and AGPL dependencies and records third-party licensing.

Evaluate before you licence

Test the boundary, not the pitch.

Bring a known parcel or approved filing and compare Tasaab’s evidence, arithmetic, refusals, and output pack against professional ground truth.

Start an evaluation