Jurisdiction-aware by design

Clarity where the rules
change from place to place.

No tenant or property team should have to become a housing-law expert just to understand why a bond can proceed. Huddle checks whether an enabled ruleset exists, prepares the configured information when it does, and stops or brings a person in when authority or judgment is missing.

The rules stay in the background. The reasoning stays visible.

Operating Controls and Evidence

Huddle records the inputs, ruleset version, disclosures, reviewer state, and operating evidence used for each enabled workflow. The platform does not rely on a regulator endorsement or a general digital-asset safe harbor.

Ruleset and Human Review Layer

The mesh separates bond mechanics from jurisdiction-specific tenancy requirements. An enabled ruleset evaluates configured deposit limits, disclosures, timelines, interest treatment, and documentation. Missing or uncertain authority pauses the workflow for review instead of assuming approval.

A note on legal advice: Huddle provides compliance-support automation, documentation, and evidence trails. It does not certify that a transaction is lawful, does not replace legal advice, and does not make an unavailable jurisdiction or asset available. Parties should use qualified counsel for legal interpretation and jurisdiction-specific guidance.

TRAIGA audit architecture

Every automated action has an evidence trail.

Compliance Mesh is not just rule matching. It records the inputs, decision path, reviewer state, generated document set, and on-chain assent references so operators and counsel can reconstruct why a bond proceeded or paused.

Inputs

Property address, tenancy facts, lease type, deposit amount

Ruleset

Enabled state or provincial requirements, or a missing-source status

Decision

Proceed, block, or route for manual review

Evidence

Disclosure packet, signatures, hashes, reviewer notes

Bond state

Selected denomination, custody, fees, risk disclosures, settlement status, and on-chain references where applicable

Agent-assisted actions are logged with timestamps and decision metadata so a reviewer can audit the difference between automated handling and human exception review.

What enabled workflows check

For an enabled jurisdiction, the Compliance Mesh runs the configured preflight and determines whether the bond can proceed or requires review. Unsupported jurisdictions stop with a missing-source status; they are not treated as approved.

Deposit Caps

For an enabled ruleset, the mesh checks configured deposit limits and blocks or flags an amount that requires review.

Disclosure Requirements

For an enabled ruleset, the mesh prepares configured notice language and evidence requirements for the tenancy facts it is given.

Return Timelines

For an enabled ruleset, HuddleSentinel tracks configured tenancy-end dates, notices, and handoff timing for operator review.

Interest Requirements

Where an enabled ruleset identifies deposit-interest or fund-treatment requirements, the mesh connects them with the selected asset and the matching disclosure or review path. Huddle does not substitute a promotional yield for a statutory obligation.

Mutual Assent Verification

Every Deposit Assignment and HuddleBond creation requires verifiable mutual assent from both parties. The mesh records that election and preserves the evidence trail tied to the tenancy.

British Columbia Workflow

The current Canadian launch ruleset supports British Columbia. Other provinces and territories remain unavailable until their sources, workflows, and approvals are complete.

Launch availability is intentionally specific.

HuddleBond v1 currently has enabled compliance preflight rulesets for Texas, Florida, and British Columbia. A ruleset catalog, research file, or manual-review path does not make another jurisdiction available.

US-TX

Texas

Enabled ruleset

US-FL

Florida

Enabled ruleset

CA-BC

British Columbia

Enabled ruleset

Every other jurisdiction: not currently enabled for HuddleBond v1. Huddle must complete source verification, workflow configuration, product and asset review, and any required counsel approval before availability is stated.

The right information for each side

The Compliance Mesh keeps the bond relationship legible. Tenants see the selected asset, custody, fees, settlement terms, material risks, and portability. Landlords and property managers see deadlines, documentation, and bond-specific terms in one place.

No more deposit account management

The bond relationship is tracked in one place with explicit records for deposit amount, elections, timelines, and settlement evidence. That reduces administrative drag and makes handoffs cleaner.

Automatic settlement documentation

When a tenancy ends, the mesh prepares the jurisdiction-aware settlement packet, evidence trail, and next required action so both sides can review the same operating record.

Dispute-resistant by design

Recorded assent, structured evidence, and on-chain events where applicable reduce disputes about timing, election, release, and settlement history. Both sides can point to the same shared record.

Asset terms stay explicit

The bond terms show the denomination, custody, fees, settlement rules, and material risks from day one. Only approved configurations are offered, and no yield or return is promised.

Trust needs more than a static checklist.

Three enabled launch rulesets. One evidence-driven workflow.

Wider participation depends on verified legal sources, an enabled ruleset, required disclosures, product and asset approval, and any counsel or manual review required before a bond proceeds.

Availability model aware50-state ruleset coverage13 Canadian province/territory rulesets