habitable Alpha · synthetic evaluation only

A tenant-held repair record

Your landlord has the work orders. Keep your own.

A photo is only the first entry. Keep the condition, repair request, proof it arrived, response, repair visit, and what happened afterward in one record stored on your device.

Walk the Unit 4B sample Open the packet it produced Check the evidence method

Current boundary: Habitable Evidence is not independently audited or proven in court. Do not rely on it for a real legal matter yet.

Tenant copy Unit 4B · Bathroom

Sample case · synthetic data

Condition

Black mold on bathroom ceiling

4 recorded events

ReportedRepair trailAdded to record

The left date is when the tenant says it happened. The right date is when the entry joined this record.

Condition photographedDark spotting above the shower
What was reported
Spots were visible above the shower on 2 January.
What can be checked
The file joined the record on 4 January. Original sealed; content fingerprint recorded.
Repair request savedEmail copy attached to the condition

“Dark spotting is spreading above the bathroom shower. Please inspect and repair.”

What was reported
The tenant says this request was sent on 3 January.
What can be checked
The saved message bytes and their later handling.
Delivery confirmation attachedEmail receipt linked to the request

Delivered03 Jan · 9:42 AM

What was reported
The receipt is described as confirmation of delivery.
What can be checked
The receipt joined the record on 4 January, sealed and linked to the saved request.
Condition documented againDark spotting still visible
What was reported
The condition remained visible after notice.
What can be checked
The follow-up file joined the record on 19 January, separately sealed and linked.

No response or repair visit is recorded in this sample trail.

Sharing is a separate action

One record. Two deliberately different copies.

Habitable keeps the complete tenant-held record on the device. Creating a review copy is a separate step with its own contents and disclosures.

Canary · tenant copy

Kept here

  • Sealed originals
  • Original photo metadata
  • Complete local custody details
Pink · review copy

Leaves only when created

  • Whole-unit record in the current alpha
  • Photo metadata removed by default
  • Bundle a recipient can verify independently

Current limits

The project’s claims have a status, too.

Claim Current evidence Status
The app detects changes to sealed files and custody records. Automated fixity, custody, packet, and verifier tests. Implemented and test-gated
The security and cryptography have been independently reviewed. An independent security and cryptography audit. Not completed
The packet workflow fits housing-law practice. Housing-law review of the legal framing and packet workflow. Not completed
The workflow works for tenant organizations. A real tenant-union or legal-aid pilot with documented outcomes. Not completed
The interface works with major screen readers. A recorded human NVDA and VoiceOver pass, plus signed native distribution. Still open

Integrity checks cannot prove what a photo depicts, who created it, or whether a particular court or agency will admit it. Habitable produces a verifiable, court-organized alpha packet—not a promise about a legal outcome.

Ways to inspect the work

Start with the artifact you need.

Evaluate the supplied case—not a tenant’s case.

The review hub separates public technical feedback from private organization contact. It accepts no evidence uploads; every evaluation starts with the supplied synthetic case.

Follow one condition through the evidence method.

Run the alpha locally

There is no hosted case app. The local interface requires uv and Python (3.14).

git clone https://github.com/ChelseaKR/habitable
cd habitable
uv sync
uv run habitable demo
uv run habitable app

AGPL-3.0; the standalone verifier also carries Apache-2.0 permission.

For a current housing problem, use a tenant resource.

Habitable is not legal advice, an emergency service, or a place to post evidence. Do not put tenant names, addresses, photos, or case details in GitHub issues.