01 / The product in the design

Product shape

Terra is a guided property marketplace with three role-specific workspaces: buyer, seller and organization. The organization controls the initial introduction and coordinates the first meeting; messenger is the central operational surface.

USER_CONFIRMED

One property inquiry, a coordinated introduction

Matt confirmed this operating direction. Buyers and sellers initially speak privately with the organization, not directly with each other. The organization decides when to introduce them and authorize a shared conversation.

Discover and shortlist a property while preserving buyer context.
Open one property inquiry linking the property, buyer, seller, assigned representative, messages and meeting state.
Coordinate privately through separate buyer ↔ organization and seller ↔ organization threads.
Introduce deliberately: open an organization-authorized shared conversation and coordinate the first meeting.

OPEN DECISIONS

The transitions still to design

The confirmed organization-mediated introduction remains the spine of Terra. The v14 audit exposes missing rules between private inquiry, participant introduction, meeting agreement, structured offer, reservation and externally completed closing. These are distinct transitions, not a single “closed” state. The pages that follow now carry the open choices and recommended safeguards; the audit does not approve policies or implement the application.

Source anchors

Coverage audit A01, A05, A09 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OBSERVED PROTOTYPE

What v14 actually gives us

One mobile HTML application, with buyer, seller and agency views over shared in-memory fixture data. The location vocabulary is Playa Venao, Pedasí and Panama City; property types are Land, Apartment, House and House with land. English, Spanish, Swedish and Hebrew dictionaries exist; Hebrew switches the document to RTL. This is design evidence, not a confirmed launch geography, customer segment or production localization guarantee.

Source anchors

state; render; renderTopbar; renderBottomNav · CLUSTERS; properties; T

Open unchanged v14 source

USER_CONFIRMED

Three connected workspaces

Buyer

Discover properties, keep personal context and talk privately with the organization.

A named representative guides the inquiry before any buyer–seller introduction.

Seller

Maintain inventory and discuss buyer interest privately with the organization.

Direct buyer access starts only when the organization authorizes the introduction.

Organization

Own inquiry coordination, participant introduction and the first meeting.

Messenger is core operations, not optional Ask agent help attached to an offer.

OPEN DECISIONS

Promises that are not yet product facts

The source advertises a fixed 4.5% commission, confidentiality, team verification, email/SMS updates and help with contracts. Those are prototype copy, not approved pricing, operational capacity, implemented privacy controls or legal assurances. Market-demand language and area price ranges are hardcoded content, not researched market evidence.

Are we building a single agency's operating marketplace or a platform for many agencies?
What ongoing support and direct communication should follow the organization-controlled introduction and first meeting?
Who supplies and maintains the initial trustworthy inventory?

Journeys & roles →

02 / One journey, different responsibilities

Journeys & roles

The confirmed target has buyer, seller and organization workspaces. Separate private conversations precede an explicit organization-authorized introduction. The v14 role switch remains a simulation, not permission enforcement.

OBSERVED PROTOTYPE

Buyer: discovery to next step

Browse map or list → open property → save a favorite or custom collection → add a private-looking note.
Set preferences → inspect deterministic matches → explore or watch an area.
Request a showing with date, time and translator preference, or submit an offer with price, deposit, closing days, conditions and a message.
Read offer-history bubbles and directly respond to a seller counter; optional Ask agent support and a fixed transaction-progress illustration are demo behaviors, not the confirmed communication model.

Source anchors

renderBuyerMatches; renderPropertyNotes; renderOfferForm; renderNegotiationThread; renderTxProgress

Open unchanged v14 source

OBSERVED PROTOTYPE

Seller: draft to reviewed inventory

The listing wizard traverses type, location, details, legal status, access, photos, pricing, offer settings, review, preview and submission. Submission adds a pending property to the local array; the seller view filters by demoSeller. A seller can accept, decline or counter an offer on the demo path.

The photos/documents step is presentation, not a file uploader.
Submission copies only core fields. Legal, access, tags, offer rules and financing terms collected by the wizard are not carried into the new property record.
The authorization checkbox is displayed, but wizValid does not require it to advance.

Source anchors

WIZ_STEPS; wizValid; wizStepBody; bindScreenEvents lines 2213–2223

Open unchanged v14 source

OBSERVED PROTOTYPE

Agency: review and coordination

Agency screens show counts, approvals, offers, a showing calendar and a buyer/seller directory. Approval changes a property status to active; rejection changes it to rejected. Bulk approval promotes every pending property without qualification checks. Agency offer view is observational: the negotiation response predicate only grants response buttons to buyer/seller roles. The showing flow displays confirmation without real participant approval. Neither these screens nor the optional Ask agent affordance implement organization-controlled introductions.

Source anchors

renderAgencyOverview; renderAgencyApprovals; renderAgencyDirectory; renderNegotiationThread

Open unchanged v14 source

USER_CONFIRMED

The confirmed introduction journey

Buyer → organization

Buyer opens a property inquiry and a private thread with the organization.

No direct seller conversation is opened automatically.

Seller → organization

Organization coordinates seller interest and availability in a separate private thread.

The buyer cannot see this thread or organization internal notes.

Organization → introduction

An explicitly identified representative authorizes the introduction and opens a shared conversation.

Display participants and organization visibility; no silent impersonation of buyer or seller.

Private → shared

The shared room is a new audience boundary, not a merger of private histories.

Earlier private messages and internal notes must not automatically become visible.

Organization → first meeting

Coordinate a requested meeting through participant agreement before confirming it.

Request is not confirmation; record completed, rescheduled or cancelled outcomes.

OPEN DECISIONS

Offers on either side of introduction

Confirmed: first contact and introduction remain organization-mediated. Observed v14 direct buyer/seller offer responses are not the adopted routing model. OPEN: before introduction, are offers unavailable or privately routed through staff? After introduction, should a versioned structured offer be posted into the shared room, and which participants may respond? Preserve the existing private histories in either choice.

Source anchors

Coverage audit A01 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

USER_CONFIRMED

First-meeting lifecycle

Requested → coordinating → participant agreement → confirmed → completed / rescheduled / cancelled. The organization coordinates the first meeting; no requested slot or sent message alone establishes confirmation.

OPEN DECISIONS

Agreement, rescheduling and preparation

PROPOSED: a meeting is confirmed only when the defined parties agree to an explicit date, time, timezone and required preparation. OPEN: who must agree, cancellation/no-show rules and what requires renewed approval. Rescheduling should invalidate affected agreement rather than silently carry it forward. v14 defaults missing date/time and treats an unanswered interpreter choice as false; these are observed shortcuts, not approved requirements.

Interpreter handoff

Capture requested language pair, request/message, assigned interpreter and availability in the staff preparation view.

OPEN: supportable language pairs, required approvers and confirmation prerequisites. Spanish–English copy does not prove every UI language has interpretation.

Unknown is unanswered

A blank interpreter answer remains unknown; proposed explicit request/decline replaces a false default.

Show preparation context to authorized participants only; exact sharing policy remains OPEN.

Source anchors

Coverage audit A06, A07 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OPEN DECISIONS

Still open after this decision

Ongoing direct communication after introduction, contact-detail release, staff roles and authority granularity, meeting modality and translator participation, and response expectations remain OPEN. Whether a person can be both buyer and seller and whether an organization represents both sides also remain unresolved.

OPEN DECISIONS

After acceptance: someone still owns the next step

PROPOSED: retain an accountable organization contact after acceptance or decline and track externally performed documentation, due diligence, agreement, deposit and closing milestones. v14 removes “Ask agent” at acceptance/decline despite promising closing help. OPEN: who owns progress, failed-deal follow-up and closing-evidence collection, and what makes each milestone complete. This is operational tracking, not execution of legal work, escrow or payments.

Source anchors

Coverage audit A09 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

← Product shape Domain & system model →

03 / The records underneath the screens

Domain & system model

A property inquiry is the connective record across property, buyer, seller, assigned representative, messages and meeting state. The communication direction is user-confirmed; these entities and enforcement mechanisms are proposed implementation.

PROPOSED PRODUCT

Proposed entity relationships

Person ↔ Organization membership

Buyer, seller and organization workspaces have authenticated, scoped participants.

Exact staff roles remain open; a role toggle does not grant access.

Property → Listing → Review

A physical property may have a listing history; each submission has a review result.

Separate physical identity from marketing and publication state.

Buyer → Preferences / Collections / Notes

Collections contain listing references; notes have an author and audience.

A note is not public listing copy.

Property / Listing → Inquiry → Meeting

One inquiry links property, buyer, seller, assigned representative, thread references and meeting state.

Requested → coordinating → participant agreement → confirmed → completed / rescheduled / cancelled.

Listing → Offer → Term revision / Event

Each offer belongs to a buyer; counters preserve prior terms and actor history.

Accepted offer is not automatically a completed sale.

Accepted intent → Coordination case

A case can track externally verified milestones and responsible people.

No payment, title transfer or legal completion is inferred from a checkbox.

Listing / Case → Restricted evidence

Documents have provenance, access policy and review status.

A legal-status declaration is not verification of title.

USER_CONFIRMED

Inquiry and conversation boundaries

Private buyer thread

Participants: buyer and organization.

Seller has no automatic access, even after introduction.

Private seller thread

Participants: seller and organization.

Buyer has no automatic access, even after introduction.

Authorized shared conversation

Organization explicitly authorizes the buyer–seller introduction; participants and organization visibility are shown.

No copying private history or internal notes into the shared room.

Internal organization notes

Remain separate from participant messages and shared-room history.

Organization actions have their actual actor identity; no silent impersonation.

OPEN DECISIONS

Information audiences are separate contracts

PROPOSED audience model—not blanket permission for every staff member. Agent-authored content is not automatically public or shared.

Private buyer notes

Buyer-owned planning and notes remain distinct from room messages and staff advice.

Private organization notes are a separate staff-only category with organization/assignment scope.

Deliberately shared advice

An explicit buyer-visible advice category has an intentional audience, separate from confidential staff notes.

v14’s buyer-visible “Agent notes” include seller-flexibility fixtures. Do not automatically disclose confidential negotiating information.

Buyer budget: OPEN audience

Decide whether maximum budget is private buyer planning or intentionally disclosed to scoped staff.

Also decide how seller-representing staff may use it. Nationality is not a language requirement; messenger privacy alone does not protect negotiating position.

Source anchors

Coverage audit A02, A08 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OPEN DECISIONS

Membership, consent and staff changes

Confirmed introduction authority does not imply undisclosed access. OPEN: whether a party can decline introduction; who may add participants; what staff reassignment changes; whether access can be revoked; and what removed participants may retain from already shared history. Preserve pre-introduction private histories regardless. Explicit membership and access records are proposed; retention/revocation policy is not chosen.

Source anchors

Coverage audit A03, A12 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OPEN DECISIONS

Separate lifecycles, explicit links

PROPOSED: model and audit these states independently. The following are conceptual state families, not approved enums or implemented automation.

Inquiry and introduction

Private inquiry → organization review → offered/declined/agreed introduction → shared-room membership.

Exact consent, routing and membership transitions OPEN.

Listing and offer

Listing draft/review/published/reserved/sold/withdrawn is separate from offer draft/submitted/countered/accepted/declined/expired/withdrawn.

v14 labels accepted and declined offers “Closed”; acceptance does not change inventory or competing offers. Reservation, backups and expiry policy OPEN.

Meeting and closing

Meeting request/proposal/agreement/reschedule/cancel/no-show is distinct from tracked closing milestones and failed-deal return to market.

Accepted ≠ reserved ≠ sold ≠ verified public sale. Sold evidence and publication remain governed by the existing Sold Properties page.

Source anchors

Coverage audit A05, A06, A09 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OBSERVED PROTOTYPE

What is real in the demo, and what is staged

Search and matches

Local filters on fixtures are implemented.

Radius is stored but not used in match filtering; missing dimension fields can pass minimum filters.

Maps and nearby

SVG shapes, fixed area clusters and generated pin positions.

Near me selects Playa Venao; no geolocation or geocoding integration.

Accounts and persistence

Nonempty email/password dismiss the sign-in form; state lives in memory.

No authentication service, durable storage or cross-user synchronization found.

Offers and showings

Buttons append objects and mutate local status/history.

No remote delivery, conflict protection, calendar reservation or notification transport.

AI pricing

An on-click range is calculated from up to two same-location active fixture listings.

A simple ±8% range around their average; no model call or valuation evidence.

Transaction and live tracking

Fixed milestone presentation, fixed ETA/distance and drawn route.

No escrow, payments, signatures, title workflow or location sharing.

Content and imagery

Area narratives and price ranges are embedded; Picsum images overlay SVG fallback scenes.

Remote placeholder photos are not evidence of the advertised properties.

Source anchors

renderBuyerMatches lines 1330–1345 · bindAuthEvents lines 2024–2040 · renderTxProgress; renderLiveShowing; wizStepBody pricing

Open unchanged v14 source

PROPOSED PRODUCT

System boundaries, without choosing a stack

The uploaded file uses vanilla HTML/CSS/JavaScript. That describes the prototype, not an approved production stack. Provider choices and infrastructure are intentionally unselected.

Presentation: responsive browsing and role-specific workspaces, with explicit language and direction support.
Identity and policy: authenticated people, memberships and record-level permissions.
Application records: durable listings, reviews, property inquiries, audience-bound conversations, introduction authorizations, meeting states and immutable offer events.
Restricted evidence: private media/document custody, independent of public listing delivery.
Delivery adapters: maps, media, notifications and calendars only after their contracts and providers are selected.

PROPOSED PRODUCT

Integrity rules worth carrying forward

Never lose the legal/access/offer-setting fields between wizard review and submission.
Preserve exact prior terms when countering; reject stale responses against superseded terms.
Handle more than one interested buyer without silently selling the same listing twice.
Escape user-entered text. The demo interpolates form values into innerHTML and is not a safe production rendering pattern.
Prove private notes and documents cannot leak through public listing, agency directory or notification views.
Review translations and RTL interactions end-to-end; dictionary presence is not full coverage (approval detail lacks Swedish spec labels).
Enforce thread audiences on the server for message reads, writes, search, exports and notifications; a hidden UI tab is not a privacy control.
Opening a shared room must not expand access to existing private messages or internal notes.
Bind introduction authorization to the inquiry and actual organization actor; display all participants and organization visibility.
A meeting request cannot transition directly to confirmed without recorded participant agreement. These are proposed acceptance constraints, not verified implementation.

← Journeys & roles Listing Matrix →

Fields · actions · account boundaries

Listing Matrix

A proposed permission map for buyer, seller and organization workspaces. These defaults describe a product design to review—not permissions implemented by the v14 prototype or blanket-approved policy.

PROPOSED PRODUCT

Read the scopes first

Public means the published listing only. Buyer access means that buyer’s own saved collections and inquiries; seller editing means that seller’s own listings. Organization access means authorized staff within their assigned organization and record scope—not unrestricted platform-wide access.

View is not edit authority. Private buyer notes, private threads, verification files and internal records are separate from the public listing.
Proposed control: the organization reviews and publishes a listing version. Exact staff roles and authority to rewrite seller facts remain open.
Property is the underlying asset; Listing is a market-facing offer/version for that property. Buyer annotations never edit either seller inventory or the published listing.

PROPOSED PRODUCT

Listing fields: who sees and changes what?

Read each cell as visibility / editability. Published values are visible to public visitors as well as buyers. Seller and organization access below is always ownership- or assignment-scoped.

Scroll within the table on small screens →

Proposed listing-field visibility and editability
Field / record	Buyer	Seller · own listing	Organization · scoped staff
Public listing essentials	View published type, size and summary; no inventory edits.	View own draft; create/edit submitted facts before review.	View/review assigned listing; publish approved version. Fact rewriting policy open.
Location / exact address	View published area. Exact address release: OPEN policy; not automatic on inquiry.	Supply location/address privately; propose public granularity.	Review location; exact-address disclosure requires resolved policy, not assumed access release.
Seller identity / contact	View only identity approved for public display. Direct contact release: OPEN.	Maintain own identity/contact privately; propose public identity.	Use necessary contact for assigned coordination; public display and release policy OPEN.
Media	View published photos/media; no changes.	Upload, replace or remove own draft media with rights to use it.	Review for quality/privacy and publication; substantive alteration rights OPEN.
Descriptions / features	View published version; no changes.	Create/edit own factual claims; respond to correction requests.	Review/request changes; unilateral edits to seller facts OPEN.
Asking price	View published asking price; an offer is a separate record, not a price edit.	Propose own asking price and revisions.	Review price revision; publish approved version. Authority to set seller price OPEN.
Availability / status	View published availability; inquiry does not reserve a property.	Report availability; request pause or status change.	Review and apply approved public state; exact emergency pause authority OPEN.
Verification / documents	View approved verification summary only; private originals not public by default.	Provide own supporting documents; see own submission and review outcome.	Scoped reviewer access only; approve summary. Document-sharing and retention policy OPEN.
Internal notes / private records	Own private collection notes only; no seller or organization internal notes.	Own private notes only; no buyer notes or organization internal records.	Own scoped organization records only; no blanket right to buyer or seller private notes.

PROPOSED PRODUCT

A field dictionary, not just a listing form

PROPOSED expansion of the listing contract. Source controls establish capture concepts, not verified property facts. For each field below decide type-specific requirement, owner/editor, public versus private audience, review status and evidence. Unknown values remain unknown; required fields may block progression rather than invent data.

Scroll within the table on small screens →

Source-grounded field families and unresolved contract
Field family	Capture / source coverage	Proposed validation and open scope
Dimensions by property type	Land and built-area dimensions, bedrooms and bathrooms where applicable; unit conversion.	Retain original unit and normalized basis. OPEN: required fields by type, precision and conversion presentation. Do not infer bathrooms.
Topography and legal status	Topography; legal categories titled / rights of possession / concession / other.	Legal category is a declared value until reviewed, not legal assurance. OPEN: type requirements, public visibility and supporting evidence. Missing is not titled.
Access, utilities and lifestyle	Access conditions, utilities and lifestyle/amenity/tag selections; evidence upload placeholders.	Define separate field keys and allowed values from source during implementation, plus available/unavailable/unknown states. OPEN: evidence, review and disclosure by type. Upload UI is not storage.
Owner financing	Down payment, term, interest and minimum terms.	OPEN: units, currency, required conditions, visibility and negotiable terms. Capturing terms does not service financing.
Negotiation controls	Offer-button and negotiation switches; offer thresholds.	OPEN: do thresholds reject, warn or flag staff review? Specify disabled-button meaning, threshold audience and minimum-terms behavior; do not silently select a policy.

Source anchors

Coverage audit A10, A11 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OBSERVED PROTOTYPE

Source defects that must not become facts

OBSERVED v14: submission discards legal status (2217–2219); agency approval falls back to Titled (1930). Wizard state defaults to two bathrooms (1088/2227) without a matching bathroom input (1783–1798). RECOMMENDED requirement: preserve submitted legal values and represent absent legal/bathroom data as unknown, never titled or two bathrooms. This recommendation is not a human-confirmed policy or a claim that the demo is fixed.

Source anchors

Coverage audit A11 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OBSERVED PROTOTYPE

Detailed source options · field review ledger

OBSERVED source options (1783–1816, 1830–1844). These are the v14 vocabulary to review, not a claim that each attribute is present on a real property or that these are approved final enums.

Type-specific dimensions

Apartment, House and House with land show living area and bedrooms. Land and House with land show plot size. Living units: m² / sq ft; land entry: hectares / acres.

OPEN: applicability and requirements for other property types; retain unit provenance. Bathrooms lack an input despite a stored default.

Topography and legal

Topography choices: flat, hilly, ocean view, mountain view, jungle. Legal: titled, rights of possession, concession, other.

View descriptors mixed with terrain need a deliberate final taxonomy. Legal evidence and unknown/reviewed status remain separate.

Access and utilities

Paved road, gravel road, 4×4 access; electricity, water, solar and well.

Each needs explicit present/absent/unknown semantics, evidence and public/private/review decisions.

Location and lifestyle options

River, ocean, mountain, town, restaurants, beaches, horses, supermarket, schools, gas, surf and trails.

Define whether each means access, proximity or a feature; do not collapse them into verified amenities.

Evidence placeholders

Photos, title document, survey and ID appear as upload/document placeholders.

Private document custody and review must be specified; placeholder controls do not prove uploaded evidence.

Offer and financing vocabulary

Source thresholds: any offer or 30% / 20% / 10% below ask; negotiation, offer-button and owner-financing switches. Financing term choices: 5 / 10 / 15 / 20 years, down payment, interest and minimum-terms text.

These are source choices, not approved minima or underwriting. Threshold reject-versus-flag behavior, currencies, rate basis and negotiability remain OPEN.

Source anchors

Coverage audit A10 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

PROPOSED PRODUCT

Listing lifecycle and buyer actions

Defaults below are PROPOSED. Submission is not approval; approval is not publication. A published listing is a reviewed snapshot, not a live mirror of an editable draft.

Scroll within the table on small screens →

Proposed listing lifecycle and buyer-action permissions
Action	Buyer	Seller · own listing	Organization · scoped staff
Create / save draft	No seller-inventory creation.	Create and save own listing draft.	Assisted creation on seller’s behalf: OPEN authority and attribution policy.
Edit / revise	No edits to seller inventory.	Edit own draft; propose a revision to published facts.	Review/request corrections; authority to rewrite seller facts OPEN.
Submit for review	No.	Submit own complete version.	Receive and route assigned submission.
Request changes	May flag an issue via inquiry; not a review decision.	Receive and respond to review feedback.	Return specific corrections to seller.
Approve	No.	No self-approval for publication.	Authorized reviewer approves an exact version; staff-role split OPEN.
Publish	No.	Request publication; no direct publish under this proposal.	Authorized publisher releases reviewed version. Proposed control, not confirmed policy.
Unpublish / pause	No.	Request pause or withdrawal of own listing.	Apply scoped unpublish; urgent self-pause and staff authority remain OPEN.
Archive	Archive own inquiry/collection only, not inventory.	Archive own unpublished draft; request archive of published listing.	Archive assigned listing through agreed lifecycle; retention policy OPEN.
Inquire	Open own property inquiry with organization.	Receive seller-side organization coordination, not buyer private thread.	Receive/assign inquiry and coordinate each side.
Save / annotate	Save in own private collection; edit own private notes.	No access to buyer saves or notes.	No blanket access to buyer private collections or annotations.

USER_CONFIRMED

Meetings, introductions and contact

Confirmed direction: organization-controlled initial communication, separate buyer ↔ organization and seller ↔ organization threads, then an organization-authorized shared room and coordinated first meeting. The action mapping is proposed where it adds detail.

Scroll within the table on small screens →

Confirmed communication boundaries with proposed action mapping and open disclosure policy
Action / boundary	Buyer	Seller	Organization · scoped staff
Request showing · proposed mapping	Request a meeting through own inquiry; request is not confirmation.	Propose availability through own organization thread.	Receive request and coordinate the first meeting.
Coordinate first meeting · confirmed direction	Discuss own needs privately with organization.	Discuss availability privately with organization.	Coordinate separate parties; modality and translator arrangements remain OPEN.
Confirm meeting · proposed mapping	Agree to time/details; cannot bind seller alone.	Agree to time/details; cannot bind buyer alone.	Record confirmation after participant agreement; never treat request alone as confirmed.
Authorize introduction / shared room · confirmed direction	Join only the authorized shared audience.	Join only the authorized shared audience.	Authorize introduction and open new shared room with visible participants.
Prior private messages / internal notes · confirmed boundary	No access to seller private thread or organization internal notes.	No access to buyer private thread or organization internal notes.	Do not expose prior private histories or internal notes when creating shared room.
Release contact / exact address · OPEN policy	No automatic entitlement from inquiry, shared room or meeting request.	Consent/release conditions require policy decision.	Introduction authority is not blanket contact/address disclosure authority.

PROPOSED PRODUCT

Sold evidence, public summaries and market releases

PROPOSED additions. Marking a listing sold is not verification or publication. These controls preserve the organization-mediated messenger and first-meeting decisions above.

Scroll within the table on small screens →

Proposed sold-sale evidence and publication permissions
Record / action	Buyer · public read	Seller · own listing	Organization · authorized scoped staff
Private closing record / evidence	No access to private evidence, identities or closing documents.	May privately submit evidence for own listing: PROPOSED. No self-verification.	Assigned evidence access only; capture provenance and actual closing price.
Verify actual closing price	No verification authority.	No self-verification or Terra Verified badge assignment.	Authorized verifier checks closing evidence; advertised price and sold status insufficient.
Privacy approval / public summary	Read only released restricted summary.	Read public summary; may flag issues with own sale. No privacy self-approval.	Review explicit whitelist and reidentification risk. No private data in public API/client payload.
Publish Terra Verified summary	Read released summary; no publish rights.	Request publication, not directly publish.	Authorized publisher releases evidence-verified and privacy-approved version; duties split OPEN.
Correction / withdrawal	Report an issue; no direct edit.	Request correction/withdrawal of own sale summary.	Review and apply scoped correction/withdrawal; rerun gates and recompute aggregates.
Area market intelligence	Read released privacy-safe aggregates only.	Same public read; no private cohort records.	Aggregate eligible verified sales with count/window/cohort; sparse-cohort policy OPEN.

OPEN DECISIONS

Decisions still needed

These are unresolved policy choices, not gaps to fill silently.

When, to whom and with what consent may exact address and seller contact details be released? Does first-meeting coordination need a limited disclosure rule?
Can staff alter seller-provided facts, media or price—or only request changes? If assisted editing is allowed, whose confirmation and actor attribution are required?
Which scoped staff can review, approve, publish, pause and archive? Can a seller immediately pause a live listing? What records must be retained?
Proposed post-publication rule: substantive changes to price, location, availability, features or material media return for review. Keep the prior approved public version until replacement or withdrawal; emergency handling and minor-edit exceptions remain open.

← Domain & system model Sold Properties & Market Intelligence →

Closed sales · private evidence · public insight

Sold Properties & Market Intelligence

A sold layer that earns trust without exposing the people behind a transaction. Partner-requested direction; the publication workflow, metrics and privacy controls below are proposed product design—not implemented Terra functionality or real transaction data.

PROPOSED PRODUCT

Two layers, one map

Proposed public control: Active listings | Sold properties. Active shows published offers; Sold shows only privacy-approved public sale summaries. Selecting a sold marker opens a restricted card, never a private closing record. No fabricated sale markers or measured market inventory are presented here.

A listing marked sold is not automatically a verified sale and must not automatically appear in the public sold layer.
Terra Verified Sales means the actual closing price has been verified by authorized Terra staff from closing evidence. An advertised price or self-reported sold status is insufficient. This is not title, legal or ownership assurance.
Exact versus approximate map location remains OPEN. The prototype should not imply precise public coordinates have been approved.

PROPOSED PRODUCT

An illustrative sold card

AFIK’S EXAMPLE · NOT AN ACTUAL VERIFIED SALE. Property type was not supplied; it must not be inferred from bedroom counts. Currency is shown as the supplied $ symbol; its currency code remains unspecified.

Sold for $425,000

Original asking: $450,000 · Difference: −5.6%

Closed: August 2026 · public month/year only

3 bed · 3 bath · 220 m²

Land: 8,000 m² · Property type: not supplied

Building-area basis for 220 m² must be confirmed before computing building price per m².

Sold price / land m²: $53.13

Days on Terra: 94

Days on market is not established by this example. No Terra Verified badge is earned by illustrative numbers.

PROPOSED PRODUCT

From private closing to public summary

Proposed organization-controlled publication chain. Each step concerns an exact version and leaves a private audit trail; a status edit cannot skip the chain.

Private closing record: scoped organization staff capture closing price, currency, dates, asking-price history and evidence linked to the property/listing. Seller submission for their own listing is PROPOSED, not approval authority.
Evidence verification: an authorized organization-scoped verifier checks actual closing price and metric provenance. Ordinary buyers and sellers cannot self-verify. Missing or disputed evidence remains unpublished.
Privacy review: evaluate the explicit public-field whitelist and combinations of location, photos, dimensions and timing for reidentification risk. Suppress or generalize according to the chosen policy; policy choices remain open.
Public restricted summary: an authorized publisher releases only the approved projection/version through a separate public API. Verify and publish duties may be split; the exact role split is OPEN.
Correction or withdrawal: re-review material corrections; withdraw unsafe or invalid summaries and recompute affected aggregates. Public endpoints must cease serving withdrawn versions; cache invalidation, retention and audit policy remain OPEN.

PROPOSED PRODUCT

Privacy is a boundary, not a hidden panel

Partner requirement: sensitive information remains private. Never include buyer/seller names, phone numbers, IDs, finca numbers, documents or other identifying details in the public sale payload. Private data must not be embedded in client JSON, hidden DOM, public downloads or map metadata.

Separate PrivateClosingRecord from an explicit whitelist PublicSaleSummary projection/API. Access to private evidence is organization- and assignment-scoped, with least-privilege permissions.
Candidate summary fields: approved map granularity, final sale price, original asking price, signed difference, closing month/year, property type, approved sizes, separate per-m² ratios and evidenced duration. Each is still subject to privacy review.
An allowed field can still identify a transaction when combined with other fields. Identifiable photos, unusually precise dimensions and timing may need suppression or generalization. Do not promise absolute anonymization.
Underlying public sale cards and aggregate releases must share a coherent disclosure policy; withholding names alone does not prevent reconstruction or linkage.

PROPOSED PRODUCT

Metrics ledger

Proposed definitions distinguish price history, denominator and observable duration. Missing or zero denominators produce null / unavailable, never zero-valued performance.

Scroll within the table on small screens →

Proposed sale and area-statistic definitions
Metric	Definition / basis	Publication or decision boundary
Original versus final asking	Original = first recorded asking price for the defined listing episode. Final asking = last asking price before closing; store separately.	Listing episode and relist rules OPEN. Label which asking price each comparison uses.
Signed difference	(sale − original asking) / original asking × 100. Example: −5.6%.	Negative = sold below original ask. Null if asking absent/zero.
Asking-to-sale discount	(original asking − sale) / original asking × 100. Example: +5.6%.	Positive discount is not the signed difference; sales above ask yield negative discount.
Building price per m²	Sale price / evidenced building area.	Building area basis must be confirmed. Do not infer a building valuation or mix with land ratios.
Land price per m²	Sale price / land area. Example: $53.13/m², half-up rounding.	For improved property this is a whole-sale ratio, not a separate land valuation.
Median sale price	Median of eligible verified sale prices in the selected area, period and property cohort.	Currency normalization and treatment of incomparable cohorts/outliers OPEN.
Average price per m²	PROPOSED: arithmetic mean of eligible per-sale ratios, separately for building and land.	Ratio of sums is an alternative, not the same measure; aggregation choice OPEN.
Average discount / duration	Arithmetic mean of eligible per-sale original-ask discounts; separate mean of evidenced duration days.	Use metric-specific eligible counts. No unverified durations or missing values treated as zero.
Days on Terra versus days on market	Days on Terra is platform-observed exposure. Total days on market needs separate external evidence.	Start/end clock, pauses and relists OPEN. Example supplies only Days on Terra: 94.

PROPOSED PRODUCT

Area intelligence without invented certainty

Area statistics use eligible Terra Verified Sales only and display sample count, date window, area definition and property cohort alongside each metric. Terra’s observed sales are not necessarily representative of the whole market.

No measured statistics supplied: show “No verified dataset supplied” in this workbook, not invented averages or a fake market trend.
Minimum cohort size and suppression rules are OPEN. Until an approved privacy policy permits release, sparse or insufficient data must show “Insufficient data” rather than statistics. No invented approved threshold.
Define the closing-period window, property cohort, geography, outlier treatment and currency normalization before comparing areas. Publish metric-specific sample counts and coverage limitations.
Corrections and withdrawals must flow into eligible samples and aggregates; assess overlapping filters and repeated queries for inference risk.

PROPOSED PRODUCT

A small data model, with a hard public boundary

Property is the underlying asset. Listing is a market offer/version tied to it. PrivateClosingRecord links the relevant property/listing episode to privately held closing evidence. An approved PublicSaleSummary is a versioned whitelist projection—not the private record serialized with a few fields hidden.

Property → Listing

One asset may have multiple listing episodes or versions.

Preserve original and final asking-price provenance.

PrivateClosingRecord → PublicSaleSummary

Private evidence → verification → privacy approval → publication.

Internal identifiers and evidence references stay private; public linkage must follow disclosure policy.

Eligible summaries → Area aggregate

Cohort + window + metric basis + eligible count + revision lineage.

An aggregate must not release suppressed private fields or silently mix incompatible denominators.

OPEN DECISIONS

Decisions still needed

Matt authorized this workbook addition, not silent closure of these product-policy choices.

Exact versus approximate map location; permitted photo/detail granularity; public price/size/time combinations and suppression/generalization policy.
Minimum cohort count, overlapping-filter protections and alignment between public sale cards and aggregate privacy.
Verifier/publisher duties, scoped evidence access, correction/withdrawal procedure and retention.
Original-ask episode definition; currency normalization; outlier and cohort policy; arithmetic-mean ratios versus ratio of sums; clock and relist definitions.

PROPOSED PRODUCT

Partner source · preserved as supplied

Afik’s messages were forwarded by Matt. The first message ends mid-phrase at “average days o…”; missing words are unknown and have not been completed. The second message is illustrative, not closing evidence.

Add a “Sold Properties” layer to the map. Users should be able to toggle between active listings and sold properties, and when they tap a sold property it should show the final sale price, original asking price, percentage difference, closing month/year, property type, size, land size, price per m², and days on market. All sensitive information must remain completely private — no buyer/seller names, phone numbers, IDs, finca numbers, documents, or other identifying details. For properties sold through Terra, we can treat them as “Terra Verified Sales” because we know the actual closing price. I also want area-level market stats based on these verified sales, such as median sale price, average price per m², average asking-to-sale discount, and average days o…
Something like this: Sold for: $425,000; Original asking: $450,000; Difference: −5.6%; Closed: August 2026; Property: 3 bed · 3 bath · 220 m²; Land: 8,000 m²; Sold price / land m²: $53.13; Days on Terra: 94

← Listing Matrix Build boundary & decisions →

04 / A coherent first product

Build boundary & decisions

Confirmed product direction: organization-controlled initial communication and introduction, with a coordinated first meeting. Proposed build slice: connect a reviewed property to one durable inquiry, its private threads, authorized shared room and truthful meeting lifecycle.

PROPOSED PRODUCT

The proposed first real loop

The communication and introduction model is USER_CONFIRMED. This implementation slice remains proposed, unbuilt and untested; it does not approve a technology stack or release.

Seller saves a complete durable listing; an authorized reviewer publishes the approved version.
Buyer opens a property inquiry; organization assigns a representative and connects the buyer, seller and property records.
Buyer and seller each communicate privately with the organization in separate threads.
The organization authorizes their introduction and opens a shared room with visible participants and organization participation/visibility.
No private prior messages or internal notes are automatically copied or revealed.
Organization coordinates requested → coordinating → participant agreement → confirmed; capture completed, rescheduled or cancelled outcomes.

PROPOSED PRODUCT

Keep next, not automatically now

Next coherent extension

Structured offers and counters with versioned terms.

Add once participant authority and the legal meaning of acceptance are settled.

Useful supporting depth

Preferences, collections, private notes, locale coverage and area content.

Include only the depth needed by the chosen first customer path.

Separate high-risk scope

Payments, escrow, signatures, legal closing and owner-financing servicing.

Do not imply these follow from displaying transaction milestones.

Separate validation work

AI valuations, actual geolocation/live tracking, automated alerts and content services.

Select evidence sources, consent model and delivery providers before promising them.

OPEN DECISIONS

Decisions that change the product

Operating model

Single agency or multi-agency marketplace?

Changes data isolation, onboarding, permissions and who owns review.

Initial customer path

The initial introduction and first-meeting coordination are organization-controlled. Local/remote emphasis and any later offer-first expansion remain open.

Do not substitute the demo direct-counter flow for the confirmed target.

Launch boundary

Which geography, property types and languages must be complete first?

The source's three areas and four dictionaries are not launch commitments.

Verification promise

What does reviewed or verified mean, who performs it, and with what evidence?

Avoid implying title or identity assurance from a status badge.

Commercial model

Is the displayed 4.5% commission intentional? Who charges whom and when?

Requires an explicit business decision; no pricing is approved here.

Offer authority

Nonbinding intent or a legally consequential action? Can agents act for principals?

Requires local professional advice and clear authority before implementation.

Information and communication policy

Post-introduction ongoing direct communication, contact-detail release and retention remain OPEN.

The confirmed boundary is no automatic disclosure of prior private messages or internal notes.

Inventory and operations

Who supplies initial listings, reviews changes and responds to requests?

A useful product needs accountable operators, not just UI states.

Staff and meeting operations

Exact staff roles, meeting modality/translator arrangements and response expectations remain OPEN.

Do not invent a service-level promise, assigned staff hierarchy or meeting venue.

OPEN DECISIONS

Decision register: agreement and inventory

These grouped questions remain OPEN. They supplement—not replace—prior recorded decisions. Confirmed organization-mediated introduction is unchanged.

Communication and access

Decide pre/post-introduction offer routing; explicit advice audiences; budget visibility/use; consent, participant addition, staff reassignment and revocation/history retention.

Audiences and membership are product decisions, not implications of organization ownership.

Exact offer accepted

Decide which financing, deposit, closing interval and condition terms can be negotiated. Proposed acceptance shows the full exact version: price, cash/mortgage, deposit, interval and conditions.

v14 decision view omits full terms; counters change only price/message. Define the anchor for “45 days”; hidden preserved data is not informed agreement.

Inventory after acceptance

Decide reservation, continued showings, competing/backup offers, expiry/withdrawal and failed-deal return to market.

Offer acceptance alone proves neither a reservation nor a closed sale. Assign a post-acceptance operational owner and required closing evidence.

Meeting prerequisites

Decide agreeing parties, timezone, reschedule re-approval, cancellation/no-show and interpreter availability/preparation acceptance.

UI languages and supported interpreter language pairs are separate capabilities.

Source anchors

Coverage audit A01, A03, A04, A05, A06, A07, A08, A09 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

OPEN DECISIONS

Decision register: identity, measurement and discovery

The remaining source behaviors need explicit retain / alter / defer decisions before they become implementation requirements.

Accounts and staff access · A12

OPEN: one real identity with multiple roles, organization membership, scoped staff access and guest access. Buyer Profile is search preferences, not complete settings.

OBSERVED: role switching follows fake auth; seller S1 is separate from account name; sign-out retains shared demo state and offer lookup uses display name. Do not reuse those as identity/security rules.

Matching · A13

OBSERVED: ALL selected amenities, ANY selected tags; missing dimensions may pass; hidden type-specific preferences persist after a type change.

OPEN: strict filtering versus ranked recommendations, missing-data behavior and clearing/revalidating stale type preferences. Radius and Near me remain staged.

Saved browsing · A14

OBSERVED: recently viewed updates from list browsing; Favorites and custom collections are independent. Heart removal inside a collection changes Favorites, not its membership; membership uses a picker.

OPEN: consistent controls plus collection rename/delete/share, private-note editing/deletion and recently-viewed scope. Do not treat undemonstrated actions as implemented.

Locale and content · A15

OBSERVED: four UI dictionaries / Hebrew RTL, but no language selector at initial auth; descriptions and fixture notes remain untranslated and money ignores chosen locale.

OPEN: auth locale, units and money formatting; separate UI, listing and message translation from interpreter services.

True lead measurements · A16

OBSERVED: “New leads” counts offers; “Registered buyers” counts fixture buyers; “Recent activity” takes first four offers. Directory segmentation is nationality/region.

OPEN: define genuine inquiry/lead/event metrics, identity, deduplication and time windows for the organization-mediated journey; demo counts are not business definitions.

Inventory and area exploration · A17

OBSERVED: seller cards open first associated offer or are inert; general inventory editing is not implemented. Area tabs are Overview / Map / Lifestyle / Prices.

OPEN: retain, alter or defer these behaviors. Map pins select and scroll to cards rather than opening detail; choose deliberately, do not infer a general editing workflow.

Source anchors

Coverage audit A12, A13, A14, A15, A16, A17 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

PROPOSED PRODUCT

What would count as a working first slice

These are proposed acceptance tests; none has been run against a production implementation.

Buyer, seller and organization use separately authenticated workspaces and see the same durable inquiry state after reload.
Before authorized introduction, buyer and seller cannot message each other directly through this inquiry.
Private buyer ↔ organization and seller ↔ organization histories and internal notes remain inaccessible to the other side after shared-room creation.
Shared-room membership, organization visibility and actual message sender are explicit; no silent impersonation.
A meeting request remains requested until coordination and participant agreement support confirmation; retries do not duplicate inquiries or meetings.
Unreviewed listings stay out of public browse, and approved facts survive submission; narrow-screen, keyboard and selected locale flows work without the demo role switch.

PROPOSED PRODUCT

Preservation and acceptance requirements to discuss

RECOMMENDED acceptance coverage for a future build—not tests claimed to pass in Terra today. The original v14 source and all earlier Foldy revisions stay immutable. Existing sold-market partner provenance, illustrative example, private-evidence boundary and release gates are preserved.

Verify full versioned offer terms at acceptance and explicit closing-interval anchor; prove accepted, reserved, sold, expired and failed-deal states do not collapse into one another.
Verify private buyer notes, confidential organization notes and deliberately shared advice have distinct audiences; budget, membership/revocation and staff reassignment tests await explicit policy decisions.
Verify meeting confirmation and reschedule agreement, timezone and interpreter preparation; unanswered inputs remain unknown rather than invented defaults.
Round-trip legal status, bathrooms, type-specific dimensions, access/utilities, financing terms and negotiation controls. Exercise unknown data, missing evidence and threshold decisions without guessing policy.
Test multi-role identity and staff scoping without demo IDs/name matching; true inquiry metrics, ALL amenities / ANY tags decisions, missing dimensions and stale type preferences.
Test collection versus Favorites membership, recently viewed, locale/content/interpretation boundaries, area tabs and map pin behavior against the chosen retain/alter/defer decisions.

Source anchors

Coverage audit A02, A04, A05, A06, A07, A10, A11, A12, A13, A14, A15, A16, A17 · source v14 line anchors in canonical coverage register

Open unchanged v14 source

← Sold Properties & Market Intelligence Original interactive prototype →