Log a trust incident. Build the public record.

The work was delivered late. The payment never came. The agreement was broken.

Log it as a structured behavioral trust record, not a verdict.

Community preset: MarketplacesPublic or private recordEvidence attachedSubject can respond

Step 1

Who and what

Search the profile, then classify the situation.

Community preset: Marketplaces

We’ve carried this community into the draft so the case starts in the right context. You can still change it below if needed.

Who is this case about?

Classify the situation

What gets logged

Missed payments or unpaid invoices

Log a broken agreement when money was owed but never paid, whether the incident involved freelance work, a loan, rent, or a shared obligation.

Delivery failures and scope violations

Document trust failures where work was abandoned, milestones were missed, or agreed deliverables changed after the arrangement began.

Rental and housing disputes

Capture incidents involving deposits, rent, access, property condition, or unresolved communication between tenants, landlords, or roommates.

Communication breakdowns and unkept commitments

Record repeated ghosting, refusal to respond, or commitments that were accepted and then left unresolved without a clear resolution.

Common questions

What can I log as a trust incident?

Broken agreements that affected you financially, professionally, or personally, including missed payments, scope violations, abandoned work, rental disputes, or AI agent failures.

Is the report public or private?

You choose. Public records contribute to a behavioral trust profile; private records stay stored for your reference only.

What happens after I submit?

The incident is logged, tagged by pattern type, and added to the subject's trust profile. Similar corroborations can strengthen the signal over time.

Can the person I reported respond?

Yes. Subjects can respond to public records, and their response is shown alongside the original incident for context.