Define chat, party, trade, commerce, and community contracts

[zoeyrose]

Outcome

Provide bounded social/economy/property messages with exact authorization, revisions, privacy, and transactional outcomes.

Scope and normative requirements

• Chat channels/messages/system events with stable sender/session context, authored/localized text distinction, timestamps where required, rate/error states, and moderation/redaction constraints.
• Party identity/membership/roles/invites and lifecycle revisions.
• Trade offers/revisions/confirm/cancel/settlement plus structured item/currency summaries.
• Merchant/bank/repair/seller/mail/auction quote/list/action/result paging and idempotency.
• Guild/property/apartment/storage/ownership/access/fee state visible to the authorized viewer, including typed apartment owner presentation.

Acceptance criteria

• Fixtures cover stale/duplicate/replayed requests, privacy filtering, disconnect, membership/ownership changes, transactional settlement, large/paged lists, and unknown fields.
• No protocol message lets a client claim role/price/ownership/settlement result.
• Private data is absent—not merely hidden by the UI—from unauthorized messages.
• Client can render/log permitted chat and commerce/community state without parsing service prose.
• Bounds prevent chat/list/search abuse and unbounded telemetry strings.

Dependencies and parallelization

Coordinates with Go social/commerce/property services and Rust UI. Domain message groups can develop in parallel under common identity/request patterns.

Licensing and scope boundary

Protocol schemas, specifications, fixtures, and generators are MIT. Verified original past work by an approved MIT provenance grantor may be migrated under the recorded provenance grant. Compiled content artifacts are specified by content-toolkit; this repository owns network contracts only.