CURRENT MVI · OWNER CORRECTION

Beta scope · read with the MVI

The dedicated Minimum viable implementation page governs current beta depth: separate buyer–Terra and seller–Terra coordination, structured negotiation before or after showings, mandatory Terra-verified representative attendance at the first viewing, optional temporary opt-in meetup geolocation, and thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING. General direct buyer–seller rooms are not approved beta scope. Owner financing is deferred beyond beta; structured negotiation remains core. Qualification stays invisible internal admin, never an entry gate. Advanced analytics/AI valuation remain later depth; no application implementation is claimed.

PRODUCT DIRECTION

From discovery to a completed sale

Owners list directly with Terra. Buyers can inquire, request a showing or make an offer from a property; a showing is not a prerequisite to an offer. Terra stays involved as the transaction progresses.

1. Discover → property → inquiry, showing request or offer → negotiation → agreement → due diligence and closing → sold → market data.
2. Use structured offers, counters, acceptance and decline in the initial product, with the exact terms and participants visible.
3. Keep separate private buyer ↔ Terra and seller ↔ Terra conversations before a Terra-authorized introduction; preserve their private histories afterward.
4. Let buyers and sellers negotiate within Terra with the team involved. Messenger supports the transaction; it is not the whole product.
5. Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.

TRANSACTION MODEL

The transitions still to design

The complete transaction journey is the product scope. Its records distinguish offer acceptance, agreement, due diligence, closing, sold status and public market-data release. The exact reservation, competing-offer, contact-release and post-acceptance rules still need decisions. Earlier audit recommendations that narrowed the first product to introductions or deferred structured offers are superseded by this feedback; the prototype gaps they documented remain real.

PRODUCT DIRECTION

Three connected workspaces

PRODUCT TERMS

Commercial model, verification and remaining choices

The owner pays a fixed 4.5% commission and accepts the commission agreement on listing submission. Terra does not automatically inflate the asking price to cover the fee. Verification is fundamental: owners supply property and ownership documents for Terra review. Owner financing is deferred beyond beta by owner decision. Beta excludes owner-financing listing controls, financing-specific offer fields and financing-specific acceptance requirements; structured offers, counters, acceptance and decline on agreed transaction terms remain core. Historical prototype financing is retained as source evidence only. Any later financing capability requires a separate scope decision; no servicing, underwriting or funds custody is included.

1. Still to define: commission payment timing, legal drafting and exceptions.
2. Still to define: exact verification evidence, reviewer access, retention and what any verification badge certifies. A reviewed listing is not a guarantee of title.
3. A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined. Translator language pairs and professional AML/KYC triggers remain open.
4. The agreed first-beta target is roughly 100 Playa Venao / Cañas listings with a four-person operation. This fixes the beta geography and planning scale; it does not claim that reviewed inventory, staffing or operating capacity already exists. Verify actual readiness before launch. Property-type and language coverage still need definition. Prototype email/SMS and contract-help copy is not evidence of delivered services; hardcoded market claims are not research.

PRODUCT DIRECTION

One marketplace, including Projects and Presale

One marketplace, one map and one listing system serve individual sellers and Project accounts. Project and Presale are normal search/map filters or categories, not separate marketplaces, maps or listing systems; Projects receive no promoted/featured section or preferential placement.

1. Project is a seller/account type inside the existing seller workspace, not a fourth administrative role or a physical property type. A verified Project profile can sell multiple ordinary listings or units. Finca Vida is an illustrative profile name only, not an actual verified seller. Project verification does not verify its units, their ownership or Presale eligibility.
2. Presale is an optional listing selection available to any individual seller or Project account. Terra must verify the listing for Presale before it is published as Presale. Existing listing and property/ownership review still applies; Project verification is not a substitute and no self-publication fallback is authorized.

PRODUCT DIRECTION

Social discovery without public discussion

Thin beta includes Like, Save, Follow, Share, PRIVATE Comment/Question, Inquire and TRENDING. A private Comment/Question can reuse the listing-linked buyer–Terra inquiry path: no direct buyer–seller chat or public Q&A. Follow/unfollow supports individual sellers and Project accounts and public new-listing/price-change updates. TRENDING uses ordinary Project treatment with no paid/featured Project preference; its ranking rule is OPEN. Buyer identities, saved collections, follower rosters and private questions stay private across counts, notifications, APIs, exports and shares; public-only share payloads and approved anonymous aggregate counts do not grant access to operational cases. Count definitions, privacy safeguards and notification details remain open.

1. Share externally through WhatsApp, social platforms or copy link using only public listing data. Shared links, previews and payloads must never expose private seller contact information, private inquiries, conversations or documents. There are no public comments or public Q&A.
2. Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.
3. Each individual seller or Project dashboard covers its own listings/account: views, likes/saves, followers, inquiries, viewing requests and offers. Engagement is aggregate and anonymous, not a buyer roster. Operational inquiries, viewing requests and offers remain legitimate private, participant/assignment-scoped records, not public analytics or automatic access to buyer-private threads. Counting rules, unique versus repeat events and reporting windows remain open; prototype fixtures are not real analytics.

OWNER-CONFIRMED DIRECTION · OPEN DETAILS REMAIN

Current beta boundaries · evidence and privacy

1. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
2. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct.
3. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined.

CURRENT MVI · OWNER CORRECTION

Beta scope · read with the MVI

The dedicated Minimum viable implementation page governs current beta depth: separate buyer–Terra and seller–Terra coordination, structured negotiation before or after showings, mandatory Terra-verified representative attendance at the first viewing, optional temporary opt-in meetup geolocation, and thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING. General direct buyer–seller rooms are not approved beta scope. Owner financing is deferred beyond beta; structured negotiation remains core. Qualification stays invisible internal admin, never an entry gate. Advanced analytics/AI valuation remain later depth; no application implementation is claimed.

PRODUCT DIRECTION

Buyer: choose the next step

Discover and compare properties, open a property and choose an inquiry, a showing request or an offer. Negotiate exact terms, reach agreement and work with Terra through due diligence and closing.

1. A showing is optional, never a prerequisite for making an offer.
2. Structured offer → counter / accept / decline is core initial scope, not a later expansion.
3. Private notes and both private Terra conversations stay separate after an introduction; an introduction grants no new room audience.
4. Buyers can Like/Save listings and Follow individual sellers or Project accounts. Sellers see aggregate anonymous engagement counts, not the identities of buyers who liked/saved or a follower roster. Following supports updates such as new listings and price changes; notification channel, cadence and the full event set remain unspecified.
5. Share externally through WhatsApp, social platforms or copy link using only public listing data. Shared links, previews and payloads must never expose private seller contact information, private inquiries, conversations or documents. There are no public comments or public Q&A.
6. Filter the existing marketplace/map for Project listings or verified Presale listings while retaining the ordinary property-type filters. Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.

PRODUCT DIRECTION

Owner: submit, negotiate and complete

List directly with Terra, supply property and ownership documents for review, and accept the owner-paid fixed 4.5% commission agreement on submission. The asking price is not automatically increased to fund the commission.

1. Respond to review requests and publish reviewed listing facts through Terra’s workflow.
2. Negotiate exact structured offers; accept, decline or counter within Terra with the team involved. Owner financing is deferred beyond beta; ordinary structured negotiation remains included.
3. Cooperate on agreement, due diligence and closing. Payment timing, legal wording and fee exceptions remain unresolved.
4. Project is a seller/account type inside the existing seller workspace, not a fourth administrative role or a physical property type. A verified Project profile can sell multiple ordinary listings or units. Finca Vida is an illustrative profile name only, not an actual verified seller. Project verification does not verify its units, their ownership or Presale eligibility.
5. Presale is an optional listing selection available to any individual seller or Project account. Terra must verify the listing for Presale before it is published as Presale. Existing listing and property/ownership review still applies; Project verification is not a substitute and no self-publication fallback is authorized.
6. Each individual seller or Project dashboard covers its own listings/account: views, likes/saves, followers, inquiries, viewing requests and offers. Engagement is aggregate and anonymous, not a buyer roster. Operational inquiries, viewing requests and offers remain legitimate private, participant/assignment-scoped records, not public analytics or automatic access to buyer-private threads. Counting rules, unique versus repeat events and reporting windows remain open; prototype fixtures are not real analytics.

PRODUCT DIRECTION

Terra: the beta intermediary

Terra’s operating team verifies listings and coordinates introductions, showings, offers, negotiation and the transaction. Messenger supports those responsibilities; it does not replace structured offer or closing records. Review Project profiles and Presale eligibility separately from ordinary listing/property-ownership evidence; neither account verification nor social engagement grants publication or introduction authority.

COMMUNICATION BOUNDARIES

The confirmed introduction journey

CORE INITIAL PRODUCT

Offers on either side of introduction

A buyer can submit a structured offer without requesting or completing a showing. Buyers and owners can counter, accept or decline and negotiate inside Terra with the team involved. Terra controls the introduction, not whether offers belong in the product. Before introduction, Terra coordinates each side privately; the exact delivery and response permissions for offers around that transition still need definition. Introduction creates no general direct buyer–seller room; private histories stay separate and no technical prevention of off-platform bypass is promised.

SHOWING COORDINATION

First-meeting lifecycle

A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer.

SHOWING PREPARATION

Agreement, rescheduling and preparation

Record date, time, timezone, meeting point and translator needs. A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer. Prototype defaults for unanswered date/time/interpreter inputs are not product rules.

DECISIONS TO RESOLVE

Remaining operating choices

Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct. Staff permissions, contact disclosure, translator language pairs and applicable AML/KYC responsibilities remain unresolved.

TRANSACTION COORDINATION

After acceptance: someone still owns the next step

Terra remains involved after acceptance: agreement → due diligence and closing → sold → eligible market data. The team coordinates the transaction; acceptance is not proof of a completed sale. Exact task ownership, milestone evidence, reservation, deposit handling, failed-deal follow-up and closing rules remain to be defined. This does not promise legal execution, escrow, payments or financing servicing. v14 removes Ask agent at acceptance/decline despite promising closing help: that remains an implementation gap, not the desired endpoint.

PRODUCT DIRECTION

Follow, share and return to the same listing

Thin beta includes Like, Save, Follow, Share, PRIVATE Comment/Question, Inquire and TRENDING. A private Comment/Question can reuse the listing-linked buyer–Terra inquiry path: no direct buyer–seller chat or public Q&A. Follow/unfollow supports individual sellers and Project accounts and public new-listing/price-change updates. TRENDING uses ordinary Project treatment with no paid/featured Project preference; its ranking rule is OPEN. Buyer identities, saved collections, follower rosters and private questions stay private across counts, notifications, APIs, exports and shares; public-only share payloads and approved anonymous aggregate counts do not grant access to operational cases. Count definitions, privacy safeguards and notification details remain open.

1. Buyers can Like/Save listings and Follow individual sellers or Project accounts. Sellers see aggregate anonymous engagement counts, not the identities of buyers who liked/saved or a follower roster. Following supports updates such as new listings and price changes; notification channel, cadence and the full event set remain unspecified.
2. Share externally through WhatsApp, social platforms or copy link using only public listing data. Shared links, previews and payloads must never expose private seller contact information, private inquiries, conversations or documents. There are no public comments or public Q&A.
3. One marketplace, one map and one listing system serve individual sellers and Project accounts. Project and Presale are normal search/map filters or categories, not separate marketplaces, maps or listing systems; Projects receive no promoted/featured section or preferential placement.
4. Notification transport and cadence remain open. Do not turn Follow or Share into seller-contact release or imply an operational notification service exists.

OWNER-CONFIRMED DIRECTION · OPEN DETAILS REMAIN

Current beta boundaries · evidence and privacy

1. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
2. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct.
3. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined.

CURRENT MVI · OWNER CORRECTION

Beta scope · read with the MVI

The dedicated Minimum viable implementation page governs current beta depth: separate buyer–Terra and seller–Terra coordination, structured negotiation before or after showings, mandatory Terra-verified representative attendance at the first viewing, optional temporary opt-in meetup geolocation, and thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING. General direct buyer–seller rooms are not approved beta scope. Owner financing is deferred beyond beta; structured negotiation remains core. Qualification stays invisible internal admin, never an entry gate. Advanced analytics/AI valuation remain later depth; no application implementation is claimed.

DOMAIN DESIGN

Entity relationships

COMMUNICATION BOUNDARIES

Inquiry and conversation boundaries

Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.

INFORMATION BOUNDARIES

Information audiences are separate contracts

Private buyer notes, confidential Terra notes and intentionally shared advice have different audiences. Authorship by a Terra representative does not make information public or grant blanket staff access. Budget visibility and use still need an explicit policy.

DECISIONS TO RESOLVE

Membership, consent and staff changes

Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate. Define Project signatory authority, staff assignment, revocation and retention for the approved private threads and structured terms; no off-platform bypass-prevention guarantee.

LIFECYCLE DESIGN

Separate lifecycles, explicit links

Discovery → property → inquiry/showing/offer → negotiation → agreement → due diligence/closing → sold → market data. Track these related lifecycles separately: neither a showing nor an accepted offer substitutes for the evidence and decisions required at later stages. Exact enums and automation remain implementation design.

SYSTEM DESIGN

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.

1. Presentation: responsive browsing and role-specific workspaces, with explicit language and direction support.
2. Identity and policy: authenticated people, memberships and record-level permissions.
3. Application records: durable listings, reviews, commission acceptance, linked cases, separate private threads, introduction evidence, first-viewing resources/actual attendance, revocable expiring meetup shares, versioned offers and transaction milestones. Owner-financing records and controls are deferred beyond beta.
4. Restricted evidence: private media/document custody, independent of public listing delivery.
5. Delivery adapters: maps, media, notifications and calendars only after their contracts and providers are selected.
6. Seller account and discovery: individual/Project type and Presale selection feed the same listings, marketplace and map; no preferential Project placement.
7. Thin beta includes Like, Save, Follow, Share, PRIVATE Comment/Question, Inquire and TRENDING. A private Comment/Question can reuse the listing-linked buyer–Terra inquiry path: no direct buyer–seller chat or public Q&A. Follow/unfollow supports individual sellers and Project accounts and public new-listing/price-change updates. TRENDING uses ordinary Project treatment with no paid/featured Project preference; its ranking rule is OPEN. Buyer identities, saved collections, follower rosters and private questions stay private across counts, notifications, APIs, exports and shares; public-only share payloads and approved anonymous aggregate counts do not grant access to operational cases. Count definitions, privacy safeguards and notification details remain open.

IMPLEMENTATION ACCEPTANCE

Integrity rules worth carrying forward

1. Never lose the legal/access/offer-setting fields between wizard review and submission.
2. Preserve exact prior terms when countering; reject stale responses against superseded terms.
3. Handle more than one interested buyer without silently selling the same listing twice.
4. Escape user-entered text. The demo interpolates form values into innerHTML and is not a safe production rendering pattern.
5. Prove private notes and documents cannot leak through public listing, agency directory or notification views.
6. Review translations and RTL interactions end-to-end; dictionary presence is not full coverage (approval detail lacks Swedish spec labels).
7. Enforce thread audiences on the server for message reads, writes, search, exports and notifications; a hidden UI tab is not a privacy control.
8. Introduction does not create a shared room or expand access to private messages or internal notes.
9. Bind introduction authorization to the inquiry and actual organization actor; display all participants and organization visibility.
10. A first-viewing request cannot become confirmed without buyer/seller agreement and available assigned Terra-verified representative; resource loss forces re-coordination/rescheduling; actual attendance is recorded. Translator availability must match agreed needs.
11. Require owner acceptance of the commission agreement on submission; retain a fixed 4.5% owner fee without automatically changing the asking price.
12. Prove offers can be submitted without a showing and that counter/accept/decline uses the exact current terms with Terra’s participation visible.
13. Keep verification evidence private under its eventual access and retention policy; never turn a badge or sold flag into proof of title, closing or public-release permission.
14. Verify individual sellers and Project accounts use one marketplace, one map and one listing system; Project/Presale filters do not create duplicate inventory or preferential Project placement.
15. Verify Project is a seller-account type, not a fourth admin role or physical property type; a verified Project can hold multiple ordinary listings but does not auto-verify units, ownership or Presale.
16. Verify either seller-account type can select Presale and that publication AS PRESALE fails until the listing-level Presale verification is complete, while ordinary listing/property-ownership review remains required. No self-publication fallback.
17. Verify Like/Save and Follow preserve buyer privacy in seller dashboards, APIs, exports and notifications: aggregate anonymous counts only, never engagement identities or a follower roster.
18. Verify external WhatsApp/social/copy-link sharing and previews expose only public listing data, never private seller contact, inquiry history or documents; no public comments or Q&A.
19. Verify inquiry and viewing-first requests use private buyer–Terra coordination and separate seller–Terra threads. Introduction does not create direct chat; no general buyer–seller room is assumed approved. Preserve exact structured terms and prior-private-history separation.
20. Verify Follow supports individual sellers and Project accounts with new-listing/price-change updates; channel/cadence tests await explicit decisions and unpublished/private data cannot leak.
21. Verify own seller/Project dashboards cover views, likes/saves, followers, inquiries, viewing requests and offers, while private operational records retain their distinct participant/assignment scope. Exact counts, unique/repeat logic and windows await definitions; fixtures are not measured analytics.
22. Verify the linked inquiry/case record does not impose a new manual Inquire prerequisite on showing requests or offers, and showings remain optional for offers.

CURRENT MVI · OWNER CORRECTION

Beta scope · read with the MVI

The dedicated Minimum viable implementation page governs current beta depth: separate buyer–Terra and seller–Terra coordination, structured negotiation before or after showings, mandatory Terra-verified representative attendance at the first viewing, optional temporary opt-in meetup geolocation, and thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING. General direct buyer–seller rooms are not approved beta scope. Owner financing is deferred beyond beta; structured negotiation remains core. Qualification stays invisible internal admin, never an entry gate. Advanced analytics/AI valuation remain later depth; no application implementation is claimed.

ACCESS DESIGN

Read the scopes first

Public means the published listing only. Buyer access concerns that buyer’s own saved collections, inquiries and offers; owner editing concerns that owner’s listings. Organization means Terra’s operating team during beta. Staff access is assignment- and record-scoped, not unrestricted platform access.

1. View is not edit authority. Private buyer notes, private threads, verification files and internal records are separate from the public listing.
2. Terra reviews owner-supplied property and ownership documents and listing facts before publication. Exact reviewer/publisher roles, evidence standards and authority to rewrite owner facts remain open.
3. 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.
4. One marketplace, one map and one listing system serve individual sellers and Project accounts. Project and Presale are normal search/map filters or categories, not separate marketplaces, maps or listing systems; Projects receive no promoted/featured section or preferential placement.
5. Project is a seller/account type inside the existing seller workspace, not a fourth administrative role or a physical property type. A verified Project profile can sell multiple ordinary listings or units. Finca Vida is an illustrative profile name only, not an actual verified seller. Project verification does not verify its units, their ownership or Presale eligibility.
6. Seller columns include individual sellers and Project accounts acting only on their own listings/account. Public profile fields do not grant access to private seller contact data.

LISTING CONTRACT

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 table horizontally on narrow screens →

FIELD CONTRACT

A field dictionary, not just a listing form

Capture the listing’s factual and commercial terms without losing them between draft, review and publication. Owner financing is deferred beyond beta by owner decision. Beta excludes owner-financing listing controls, financing-specific offer fields and financing-specific acceptance requirements; structured offers, counters, acceptance and decline on agreed transaction terms remain core. Historical prototype financing is retained as source evidence only. Any later financing capability requires a separate scope decision; no servicing, underwriting or funds custody is included. Source controls provide vocabulary, not verified property facts or final enums. Type-specific requirements, public/private audiences and evidence rules still need specification; missing values remain unknown.

Scroll table horizontally on narrow screens →

LISTING LIFECYCLE

Listing lifecycle and buyer actions

The owner supplies listing facts and property/ownership evidence and accepts the fixed 4.5% commission agreement at submission. Terra reviews the listing; submission alone does not publish it. A published listing is a reviewed snapshot, not an unchecked mirror of its editable draft. Exact staff-role separation remains to be defined.

Scroll table horizontally on narrow screens →

TRANSACTION COMMUNICATION

Meetings, introductions and contact

Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate. A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.

Scroll table horizontally on narrow screens →

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 →

DECISIONS TO RESOLVE

Decisions still needed

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

1. 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?
2. 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?
3. Which scoped staff can review, approve, publish, pause and archive? Can a seller immediately pause a live listing? What records must be retained?
4. 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.
5. What exact property/ownership evidence is required; who may access it; how long is it retained; and what does any verification badge certify? Terra’s responsibility to verify is established.
6. How are commission payment timing, legal wording and exceptions handled? The owner-paid fixed 4.5%, acceptance at submission and no automatic price inflation are established.
7. Decide structured-term audiences, contact disclosure, translator arrangements, optional meetup geolocation private audience/duration/retention and professional AML/KYC triggers. No assumed general direct chat room; owner financing is deferred beyond beta.
8. Define Project-profile and Presale verification evidence, badge meaning and review handling; verification of one subject does not automatically verify an account, unit/listing or Presale.
9. Specify Follow notification channel/cadence and exact event coverage. Define counts, unique/repeat events and reporting windows for own-dashboard statistics; private operational case access is distinct from anonymous engagement.
10. Like/Save and Follow are established direction; their detailed relationship to Favorites/custom collections and collection sharing remains to be designed. External public-listing sharing is not permission to share private collections or notes.

OWNER-CONFIRMED DIRECTION · OPEN DETAILS REMAIN

Current beta boundaries · evidence and privacy

1. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
2. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct.
3. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined.

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.

1. A listing marked sold is not automatically a verified sale and must not automatically appear in the public sold layer.
2. 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.
3. 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.

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.

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.

1. Separate PrivateClosingRecord from an explicit whitelist PublicSaleSummary projection/API. Access to private evidence is organization- and assignment-scoped, with least-privilege permissions.
2. 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.
3. 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.
4. 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 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.

1. No measured statistics supplied: show “No verified dataset supplied” in this workbook, not invented averages or a fake market trend.
2. 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.
3. Define the closing-period window, property cohort, geography, outlier treatment and currency normalization before comparing areas. Publish metric-specific sample counts and coverage limitations.
4. 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.

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.

1. 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…
2. 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

CURRENT MVI · OWNER CORRECTION

Beta scope · read with the MVI

The dedicated Minimum viable implementation page governs current beta depth: separate buyer–Terra and seller–Terra coordination, structured negotiation before or after showings, mandatory Terra-verified representative attendance at the first viewing, optional temporary opt-in meetup geolocation, and thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING. General direct buyer–seller rooms are not approved beta scope. Owner financing is deferred beyond beta; structured negotiation remains core. Qualification stays invisible internal admin, never an entry gate. Advanced analytics/AI valuation remain later depth; no application implementation is claimed.

CORE INITIAL PRODUCT

The initial product loop

A working product must connect the commercial transaction, not stop after an introduction. The earlier introduction-only slice and deferred-offer recommendation are superseded. Technical architecture, release and operational execution are not authorized by this content revision.

1. Owner supplies durable listing facts and property/ownership documents; submission requires acceptance of the fixed 4.5% owner-paid commission agreement, without automatic asking-price inflation.
2. Terra verifies the listing and coordinates publication of reviewed facts under the eventual evidence and access rules.
3. Buyer discovers a property and chooses an inquiry, a showing request or a structured offer. A showing is never an offer prerequisite.
4. Terra coordinates private conversations and authorizes introductions without exposing prior private histories or internal notes.
5. Buyer and owner negotiate inside Terra with the team involved: structured offer, counter, acceptance or decline on exact terms. Owner financing is deferred beyond beta by owner decision. Beta excludes owner-financing listing controls, financing-specific offer fields and financing-specific acceptance requirements; structured offers, counters, acceptance and decline on agreed transaction terms remain core. Historical prototype financing is retained as source evidence only. Any later financing capability requires a separate scope decision; no servicing, underwriting or funds custody is included.
6. Terra coordinates agreement, due diligence and closing. Acceptance is not sold status, and marking sold does not publish private evidence or market data.
7. Eligible sold summaries and market intelligence follow the existing verification, privacy and release boundaries on Sold Properties & Market Intelligence.
8. One marketplace, one map and one listing system serve individual sellers and Project accounts. Project and Presale are normal search/map filters or categories, not separate marketplaces, maps or listing systems; Projects receive no promoted/featured section or preferential placement.
9. Project is a seller/account type inside the existing seller workspace, not a fourth administrative role or a physical property type. A verified Project profile can sell multiple ordinary listings or units. Finca Vida is an illustrative profile name only, not an actual verified seller. Project verification does not verify its units, their ownership or Presale eligibility.
10. Presale is an optional listing selection available to any individual seller or Project account. Terra must verify the listing for Presale before it is published as Presale. Existing listing and property/ownership review still applies; Project verification is not a substitute and no self-publication fallback is authorized.
11. Buyers can Like/Save listings and Follow individual sellers or Project accounts. Sellers see aggregate anonymous engagement counts, not the identities of buyers who liked/saved or a follower roster. Following supports updates such as new listings and price changes; notification channel, cadence and the full event set remain unspecified.
12. Share externally through WhatsApp, social platforms or copy link using only public listing data. Shared links, previews and payloads must never expose private seller contact information, private inquiries, conversations or documents. There are no public comments or public Q&A.
13. Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.
14. Each individual seller or Project dashboard covers its own listings/account: views, likes/saves, followers, inquiries, viewing requests and offers. Engagement is aggregate and anonymous, not a buyer roster. Operational inquiries, viewing requests and offers remain legitimate private, participant/assignment-scoped records, not public analytics or automatic access to buyer-private threads. Counting rules, unique versus repeat events and reporting windows remain open; prototype fixtures are not real analytics.

SCOPE BOUNDARIES

Supporting depth and separate execution scope

DECISION REGISTER

Decided direction and remaining decisions

DECISIONS TO RESOLVE

Decision register: agreement and inventory

The operating model, initial structured-offer scope and continued Terra transaction coordination are established. The questions below concern detailed rules, not whether those capabilities belong in the product. The earlier audit’s deferred-offer and introduction-only recommendations no longer govern the current scope.

DECISIONS TO RESOLVE

Decision register: identity, measurement and discovery

Current direction establishes thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING alongside ordinary Project accounts and distinct Presale verification. Internal qualification is invisible admin, not a buyer-facing ladder or entry gate. Unresolved ranking, count, privacy and notification details are decisions, not permission to silently omit approved thin capabilities.

ACCEPTANCE TO VERIFY

What would count as a working initial product

These are acceptance requirements for implementation. They have not been demonstrated by the v14 prototype or tested against a production service.

1. Buyer, seller and organization use separately authenticated workspaces and see the same durable inquiry state after reload.
2. Buyer and seller use separate Terra threads; direct buyer–seller chat is not approved beta scope merely because an introduction is authorized.
3. Private buyer ↔ Terra and seller ↔ Terra histories and internal notes remain inaccessible to the other side after introduction.
4. Private-thread audiences, Terra visibility and actual actor identity are explicit; no silent impersonation or assumed shared-room creation.
5. A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer.
6. 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.
7. Submission captures property/ownership documents and affirmative commission-agreement acceptance. The owner fee remains fixed at 4.5%, and submitting does not automatically inflate the asking price.
8. A buyer can submit an offer without a requested or completed showing. Buyer and owner can counter, accept and decline exact versioned terms inside Terra with its team involved.
9. Owner financing is deferred beyond beta: its controls, fields and workflows are excluded from beta acceptance. Structured negotiation and exact term-history preservation remain required.
10. Terra can coordinate agreement, due diligence and closing after acceptance; accepted, reserved, sold and public-market release remain distinct. Exact rule-dependent tests must await the remaining decisions.
11. Verify individual sellers and Project accounts use one marketplace, one map and one listing system; Project/Presale filters do not create duplicate inventory or preferential Project placement.
12. Verify Project is a seller-account type, not a fourth admin role or physical property type; a verified Project can hold multiple ordinary listings but does not auto-verify units, ownership or Presale.
13. Verify either seller-account type can select Presale and that publication AS PRESALE fails until the listing-level Presale verification is complete, while ordinary listing/property-ownership review remains required. No self-publication fallback.
14. Verify Like/Save and Follow preserve buyer privacy in seller dashboards, APIs, exports and notifications: aggregate anonymous counts only, never engagement identities or a follower roster.
15. Verify external WhatsApp/social/copy-link sharing and previews expose only public listing data, never private seller contact, inquiry history or documents; no public comments or Q&A.
16. Verify inquiry and viewing-first requests use private buyer–Terra coordination and separate seller–Terra threads. Introduction does not create direct chat; no general buyer–seller room is assumed approved. Preserve exact structured terms and prior-private-history separation.
17. Verify Follow supports individual sellers and Project accounts with new-listing/price-change updates; channel/cadence tests await explicit decisions and unpublished/private data cannot leak.
18. Verify own seller/Project dashboards cover views, likes/saves, followers, inquiries, viewing requests and offers, while private operational records retain their distinct participant/assignment scope. Exact counts, unique/repeat logic and windows await definitions; fixtures are not measured analytics.
19. Verify the linked inquiry/case record does not impose a new manual Inquire prerequisite on showing requests or offers, and showings remain optional for offers.

ACCEPTANCE TO VERIFY

Preservation and acceptance requirements to discuss

Acceptance coverage for implementation—not tests passed by Terra today. The original v14 source and earlier revisions remain immutable; their observed gaps are retained. Current product direction supersedes the audit’s introduction-only or deferred-offer recommendations. Existing sold-market partner provenance, illustrative example, private-evidence boundary and release gates are preserved. This round adds social actions, Project seller accounts and Presale to the existing marketplace. Sold-market and original-prototype content remain unchanged.

1. 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.
2. 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.
3. Verify meeting confirmation and reschedule agreement, timezone and interpreter preparation; unanswered inputs remain unknown rather than invented defaults.
4. Round-trip legal status, bathrooms, type-specific dimensions, access/utilities and approved negotiation controls. Owner-financing-specific fields and workflows are deferred beyond beta. Exercise unknown data, missing evidence and threshold decisions without guessing policy.
5. 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.
6. Test collection versus Favorites membership, recently viewed, locale/content/interpretation boundaries, area tabs and map pin behavior against the chosen retain/alter/defer decisions.

OWNER-CONFIRMED DIRECTION · OPEN DETAILS REMAIN

Current beta boundaries · evidence and privacy

1. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
2. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct.
3. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined.

IMPLEMENTATION GAP

How the prototype relates to the intended product

The unchanged demo is implementation-gap evidence, not the current product contract. Its local offer/counter/accept/decline interactions illustrate core initial scope; its optional Ask agent and staged transaction progress do not deliver Terra’s full intermediary role. The intended owner-direct product includes document verification, submission acceptance of the owner-paid fixed 4.5% commission agreement, optional showings, structured negotiation and continuing coordination through closing. Owner financing is a real feature to implement, not a promise of servicing.

1. The non-enforced authorization checkbox and document placeholders do not satisfy submission agreement or owner-document verification requirements.
2. The apparent tracking screen does not establish GPS tracking, location-sharing consent or contact release.
3. No change to this workbook repairs, secures or implements the original prototype.

APPROVED DIRECTION · NOT IMPLEMENTATION

The beta we are trying to prove

Can verified owners list, can Terra generate suitable buyer interest, and can its team coordinate valued transactions, document introductions and collect the agreed commission? Success is an evidenced service and transaction loop—not a guarantee of zero bypass.

1. The agreed first-beta target is roughly 100 Playa Venao / Cañas listings with a four-person operation. This fixes the beta geography and planning scale; it does not claim that reviewed inventory, staffing or operating capacity already exists. Verify actual readiness before launch. Property-type and language coverage still need definition.
2. Accounts remain buyer, seller and Terra. Project is a seller/account type, never a fourth role. One marketplace, one map/search and one listing system; Project and Presale are ordinary filters with no preferential Project placement.
3. Inquiry, viewing request and offer are alternative entry paths. An offer can arrive before or after a viewing; a linked coordination case must not impose an extra manual inquiry prerequisite.

MUST BUILD

1 · Verified supply and useful discovery

Build a durable create/edit listing flow with photos, asking price, property type, location, size, access and basic legal description. Owners provide identity, Title / ROP and ownership/property evidence.

1. Licensed PJ / Terra review is required before listing publication. Confirm PJ’s actual license, authority and responsibilities before relying on that arrangement; no verified legal authority or title guarantee is asserted here.
2. Presale is selectable on each listing by any seller or Project. Publish AS PRESALE only after distinct Presale verification, in addition to ordinary seller/property/ownership review. A verified Project profile cannot approve its units automatically.
3. Thin beta includes Like, Save, Follow, Share, PRIVATE Comment/Question, Inquire and TRENDING. A private Comment/Question can reuse the listing-linked buyer–Terra inquiry path: no direct buyer–seller chat or public Q&A. Follow/unfollow supports individual sellers and Project accounts and public new-listing/price-change updates. TRENDING uses ordinary Project treatment with no paid/featured Project preference; its ranking rule is OPEN. Buyer identities, saved collections, follower rosters and private questions stay private across counts, notifications, APIs, exports and shares; public-only share payloads and approved anonymous aggregate counts do not grant access to operational cases. Count definitions, privacy safeguards and notification details remain open.
4. At listing submission, capture the seller’s acceptance of the 4.5% agreement with version, acceptor and timestamp. Do not artificially increase the asking price to cover commission. Terra-generated buyer attribution is governed by the contract, not merely by a database link.

MUST BUILD

2 · Terra-first coordination and introductions

Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.

1. Record the authorized introduction at the authorization event—not after attendance—with listing/property, buyer, seller, representative, timestamp, relevant agreement version and evidence. Protected Introduction eligibility follows lawyer-approved terms; an event record does not automatically create a legal fee entitlement.
2. Viewing states include requested, coordinating, confirmed, completed, cancelled, rescheduled and no-show. A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer. Retain time/timezone, meeting point, directions and confirmation evidence.
3. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
4. Retain translator request, language pair and manual assignment subject to actual availability and explicit confirmation. No universal language or machine-translation promise. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined.

MUST BUILD

3 · Negotiate exact terms inside Terra

Build versioned structured offers and counters with accept/decline, actual actor and timestamps before or after a showing. Show exact price, agreed payment terms, deposit, closing interval and conditions being acted upon; preserve each prior version. No direct-chat or showing prerequisite.

1. Owner financing is deferred beyond beta by owner decision. Beta excludes owner-financing listing controls, financing-specific offer fields and financing-specific acceptance requirements; structured offers, counters, acceptance and decline on agreed transaction terms remain core. Historical prototype financing is retained as source evidence only. Any later financing capability requires a separate scope decision; no servicing, underwriting or funds custody is included.
2. Track Negotiating → Accepted → Due diligence → Contract → External deposit / closing → Sold. Deposit and closing happen externally; Terra has no funds custody.
3. Accepted is not sold. Record withdrawal, expiry, cancellation or failed due diligence and preserve the attempt and history. Restore market availability only when the controlling transaction ends and the approved inventory policy permits it; a failed individual offer must not override another active accepted or reserved transaction. Reservation, competing/backup offers and the legal effect of acceptance still need explicit rules.
4. Record actual closing evidence, final outcome and commission as expected / due / collected / disputed / waived. The fee base, due event and exclusions remain commercial/legal launch gates. Distinguish expected income from actual collected commission.
5. Retain the sold record and verified actual closing facts, with private evidence separate from the whitelisted public projection. The existing Sold Properties & Market Intelligence release/privacy gates remain unchanged; advanced area analytics and AI valuation are later depth, not beta blockers.

MUST BUILD

4 · The operating console and safety floor

Build scoped Terra administration for verification, assignments, introductions, offers, KYC, transactions and flags. Audit who changed what and when; private records are participant/assignment scoped, not globally visible to sellers.

1. Notify the relevant audience for inquiry, viewing, offer, counter, acceptance, verification and transaction-stage events. Record delivery failures for manual follow-up; advanced delivery automation can wait.
2. Compliance is core, even when checks are manual or provider-assisted. A licensed professional/local counsel must confirm exact triggers, responsibilities and blocking rules before each relevant stage. Do not assume AML/KYC can always wait until an offer is accepted.
3. By product design, anonymous browsing does not itself trigger screening; this remains subject to applicable duties. Listing ownership review is not a substitute for required participant or transaction checks.
4. Keep account access, consent, document retention, private-history separation and public projections explicit. The prototype’s role switch and fixtures are not a security model or proof of a working service.
5. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct.

DELIVERY SPLIT

Must build · manual operations · later

Use the smallest implementation that can carry the full transaction loop, with accountable manual operations rather than pretending automation already exists.

1. MUST BUILD: authenticated roles; durable listings and review gates; ordinary map/search; thin Like/Save/Follow/Share/PRIVATE Comment/Question/Inquire/TRENDING; separate Terra threads; introduction evidence; first-viewing mandatory representative availability and attendance records; optional temporary opt-in/revocable/expiring private meetup geolocation; structured versioned negotiation; closing and commission records; scoped internal admin, audit and notifications. Open ranking/privacy details gate only their affected behavior.
2. MANUAL OPERATIONS: review ownership/Presale evidence; qualify buyers invisibly inside Terra admin without an entry gate; verify and assign representatives, confirm buyer/seller and agreed translator availability; perform professional compliance checks; coordinate external counsel/deposits/closing; reconcile introduction attribution and commission collection. Record accountable owner, actual outcome and next action.
3. LATER DEPTH: owner financing (explicitly deferred beyond beta); advanced social/network experiences, recommendations and notification automation; advanced area analytics and AI valuation. Optional temporary meetup geolocation and thin social/TRENDING remain beta scope, with their narrow unresolved policies explicit.
4. OUTSIDE THIS MVI: escrow or funds custody, payments/servicing/underwriting, machine translation, public discussion feeds, separate Project marketplaces, preferential Project placement and guaranteed bypass prevention.

REMAINING LAUNCH GATES

Launch gates, not hidden assumptions

Resolve these before the relevant capability is used. The MVI direction is approved; the unresolved professional and operational details are not.

1. Licensed professional/local counsel: confirm PJ authority, listing/Presale review standard, AML/KYC trigger and blocking matrix, acceptance effect and contract execution responsibilities.
2. Commercial/legal: settle 4.5% fee base, due event and exclusions; Terra-generated buyer attribution. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
3. Operator: confirm actual staffing/inventory, Terra-verified representative capacity and agreed translator resources. The first viewing requires representative attendance with no unaccompanied exception; missing resources block confirmation and resource loss requires re-coordination/rescheduling. Confirm response ownership, language pairs, cancellation/no-show records and external closing evidence.
4. Product/implementation: settle exact role/membership rules, privacy and retention, approved-fact edit/re-review handling, backup-offer/reservation policy, notification transport and event/count definitions. No invented launch thresholds or guaranteed deal count.
5. Affected product decisions: exact optional geolocation private audience/duration/retention; TRENDING ranking and privacy-safe count rules; any future general direct buyer–seller room. Owner financing is settled as deferred beyond beta. Do not infer these from introduction, prototype UI or prior narrative.

ACCEPTANCE TO VERIFY · NO TESTED PRODUCT CLAIM

Beta acceptance and closeout readout

Run real end-to-end cases and report outcomes, including failure and cost—not just listings and introductions.

1. Acceptance: an unreviewed listing and unverified Presale cannot publish; agreement acceptance retains exact version/actor/time; Project uses ordinary discovery; shares reveal only approved public data.
2. Acceptance: inquiry, viewing-first request and offer each start/link a case without a separate manual Inquire step; buyer–Terra and seller–Terra threads remain separate. Structured offers/counters/accept/decline work pre/post showing. Introduction is logged at authorization, disclosure/delivery separately; it does not create a general direct buyer–seller room or expose private histories.
3. Acceptance: unavailable Terra-verified representative blocks FIRST-viewing confirmation; buyer/seller agreement and agreed translator availability are recorded. Resource loss removes confirmed readiness and requires re-coordination/rescheduling; changed appointments need renewed agreement. Actual representative attendance, cancellation/no-show and optional additional-property evidence persist. No unaccompanied first-viewing exception or blanket subsequent-viewing mandate.
4. Acceptance: counters preserve prior exact terms; accepted never auto-marks sold. Ending an individual attempt does not reset inventory or override another active accepted/reserved transaction. Ending the controlling deal restores availability only as approved inventory policy permits. Actual closing and commission collection reconcile against evidence; required compliance gates block the relevant stage.
5. Internal readout: reviewed/published listings → branch-aware inquiry/viewing/offer entry → introductions/negotiation → accepted → completed/failed transactions. Qualification remains invisible internal Terra admin, not a mandatory funnel stage or buyer-facing ladder. Define cohorts/windows, counts and denominators before measurement; no viewing prerequisite.
6. Operating readout: response times, verification/coordination backlog, operator hours, travel, cancellations, completed/failed transactions and reasons, actual collected commission, attributed external closings and operating cost. Distinguish missing evidence from zero activity.
7. Closeout: decide continue, change or pause from transaction completion/failure, attrition, fee collection and operational cost. Set evaluation targets with the operator before beta; no fabricated numeric success thresholds or claimed traction.
8. Acceptance: optional buyer/seller meetup location sharing requires explicit opt-in and shows its private audience; decline preserves static coordination, revoke ends sharing, expiry stops it automatically, unauthorized reads fail. Exact audience/duration/retention await decisions; tests use explicit synthetic policies, not invented live defaults.
9. Acceptance: same seller and introduced buyer pursuing another LISTED OR UNLISTED property is represented in intended commission protection without a recorded additional-showing prerequisite; factual evidence is retained, legal eligibility remains counsel-assessed.
10. Acceptance: Like, Save, Follow/unfollow, public-only Share, PRIVATE Comment/Question, Inquire and TRENDING exist at thin depth. Private questions reuse Terra inquiry without direct chat/public Q&A; rankings treat Projects ordinarily; counts, notifications and share previews cannot expose buyer identities, private engagement or qualification. Ranking rule remains open.
11. Acceptance: owner-financing controls and financing-specific offer fields are absent from beta; structured offers/counters/acceptance/decline and exact term history remain available. No general direct buyer–seller room is inferred. Internal qualification creates no buyer-facing progression or mandatory entry gate.
12. Acceptance: beta scope consistently identifies Playa Venao / Cañas, roughly 100 listings and a four-person operating target; readiness evidence separately verifies available reviewed inventory and staffing. Do not treat other prototype geographies as beta scope.

PROPOSAL · NOT AN ACCEPTED DECISION · MUST-DECIDE-BEFORE-AFFECTED-IMPLEMENTATION

Implementation readiness · Must decide before affected implementation

The original readiness audits are retained as source history; the current entries below are reconciled with this owner correction. Open implementation choices remain PROPOSALS, not accepted decisions. They cannot weaken settled first-viewing attendance, optional temporary geolocation, private Terra coordination or thin social scope. Safe foundations proceed while affected policy details await decisions.

PROPOSAL · NOT AN ACCEPTED DECISION · NORMAL-BUILD-DESIGN-NOW

Implementation readiness · Normal build · design now

Engineering can resolve these with explicit design and tests during the build. Proposed mechanics remain PROPOSALS, not tested behavior; settled owner direction is not reopened. P5 appears in both groups because transition design and actual launch capacity are distinct gates.

PROPOSAL · NOT AN ACCEPTED DECISION · LAUNCH-ONLY

Implementation readiness · Launch-only counsel and operator gates

Professional, commercial and operational approvals gate only the relevant live capability, not the build. Implement explicit review/gate records and manual outcomes now. Keep affected live transitions unavailable until responsible operator/counsel confirms their rules. Mandatory first-viewing attendance has no unaccompanied exception; operational planning cannot waive it. No legal terms or implementation results are invented.

SETTLED BETA SCOPE · OPEN DETAILS IDENTIFIED

Scope decisions and remaining implementation details

SOURCE & AUTHORITY

Sources for this page

Current user feedback supplied through the delegated task corrects the current MVI and affected routes. Prior proposal assumptions, prototype evidence and source history remain retained. No fabricated message identifier, law research, implementation or operational verification is claimed.

CURRENT REVISION

v0.6 · Feedback closure

Owner financing is explicitly deferred beyond beta while structured negotiation stays core. The agreed first-beta target is consistently Playa Venao / Cañas, roughly 100 listings and a four-person operation; actual inventory/staffing readiness remains separate.

1. Retained optional temporary meetup geolocation, mandatory verified first-viewing attendance, separate Terra coordination, listed/unlisted cross-property protection intent, private Comment/Question and Trending, and invisible internal qualification.
2. Preserved original prototype, historical evidence and sold-market content. Exact privacy/ranking mechanics and counsel-owned terms remain appropriately open; no app implementation or legal approval claimed.

Prior revision · Preserved

Current correction · Terra MVI boundaries

Current user feedback corrects normative scope across MVI, Product shape, Journeys, Domain model, Listing Matrix and Build boundary. Source: current user feedback supplied in the delegated task; no source message identifier was provided. Prior evidence, prototype and changelog records remain retained.

1. A Terra-verified representative must attend the FIRST viewing; there is no unaccompanied exception. Confirmation requires buyer and seller agreement plus actual assigned representative availability (and agreed translator availability when needed). Missing availability blocks confirmation; later resource loss returns the appointment to re-coordination/rescheduling, not a still-confirmed unaccompanied visit. Reconfirm changed arrangements and record actual attendance, cancellation and no-show outcomes. This rule does not mandate representative attendance at all subsequent viewings; a viewing never gates an offer.
2. Optional temporary buyer/seller meetup geolocation is included at thin beta depth. Each sharing participant must explicitly opt in; sharing has a visible private audience, can be revoked and automatically expires. Exact audience, duration and retention are OPEN decisions before affected use; no permanent or background tracking and no implied consent from booking. Static directions remain available when sharing is declined.
3. Inquire and a viewing-first request each open or reuse a listing-linked private buyer–Terra thread, without an extra manual inquiry prerequisite. Seller–Terra coordination is separate. Structured offers, counters and accept/decline work before or after a showing. A Terra-authorized introduction is an evidence event, not room creation: a general direct buyer–seller shared room is not approved beta scope and needs an explicit inclusion decision. Private histories and internal notes stay separate.
4. Intended commission protection follows the same seller and Terra-introduced buyer to another LISTED OR UNLISTED property. Recording an additional showing may supply evidence but is not a prerequisite for that intended protection. Record introduction authorization, actual disclosure/delivery and attendance separately; none alone establishes legal entitlement. Counsel must settle duration, prior relationships, exclusions, attribution, enforceability and disputes; no invented protection period or reporting deadline.
5. Thin beta includes Like, Save, Follow, Share, PRIVATE Comment/Question, Inquire and TRENDING. A private Comment/Question can reuse the listing-linked buyer–Terra inquiry path: no direct buyer–seller chat or public Q&A. Follow/unfollow supports individual sellers and Project accounts and public new-listing/price-change updates. TRENDING uses ordinary Project treatment with no paid/featured Project preference; its ranking rule is OPEN. Buyer identities, saved collections, follower rosters and private questions stay private across counts, notifications, APIs, exports and shares; public-only share payloads and approved anonymous aggregate counts do not grant access to operational cases. Count definitions, privacy safeguards and notification details remain open.
6. Owner financing is not approved as a required beta feature. Its inclusion is an explicit OPEN product decision, not permanent exclusion. No financing-specific listing fields or acceptance tests are mandatory until that decision; retain structured versioned offers/counters/accept/decline on agreed transaction terms. Historical prototype financing remains source evidence, not beta authorization; servicing, underwriting and payments are not implied.
7. Buyer qualification is invisible internal Terra administration for fit, intent, budget and timing, not a buyer-facing Browsing/Interested/Qualified/Ready ladder and not a mandatory gate for inquiry, viewing requests or offers. Internal criteria, access and measurement definitions need decisions; do not expose qualification labels, notes or scores in buyer/seller views, notifications, exports or public analytics. Professionally defined AML/KYC gates remain distinct.
8. Updated MVI acceptance and readiness P1/P5/P6/P8/OPS-03/OPS-08/LG-3 consistently. Fixed owner-paid 4.5%, submission acceptance, distinct Presale review, ordinary Project discovery, professional AML/KYC gates and external closing/deposits without custody remain intact.

Prior revision · Preserved

v0.4 · Implementation-readiness proposals

Independent product and operations readiness audits of the accepted v0.3.1 MVI are recorded on the MVI page as a new Implementation readiness section. All sixteen findings are labeled PROPOSAL — none is an accepted decision and the approved product direction is unchanged.

1. Must decide before affected implementation: product P1–P7 and operations OPS-01/02/03 cover authorization and Project membership, publication/re-review, offer version semantics, controlling transaction and inventory restoration, listing dictionary, location/contact disclosure, private-document custody and introduction evidence.
2. Normal build · design now: operations OPS-04/06/07/08 and product P5/P8 cover the commission ledger, delivery-failure follow-up, the audit event catalogue, executable acceptance cases, showing operations and thin social semantics.
3. Launch-only counsel/operator gates: licensed authority and AML/KYC matrix, fee base and Protected Introduction terms, acceptance legal effect, staffed capacity and closing evidence gate only the relevant live capability.
4. Accepted v0.3.1 MVI text is preserved byte-for-byte; v0.4 adds proposals only.

Prior revision · Preserved

v0.3.1 · Inventory-state clarification

Independent review corrected an overbroad inventory transition before original-index delivery. The tightened MVI scope is otherwise unchanged. Earlier labels below describe their historical revision states.

1. A failed individual offer cannot reset a listing or override another active accepted/reserved deal; return to market depends on the controlling transaction and approved inventory policy.
2. Clarified that the asking price must not be artificially increased to cover commission.

Prior revision · Preserved

v0.3 · Minimum viable implementation

Matt’s current conversation approved tightening the MVI and giving it a dedicated page. Product direction only; no features executed or legal terms approved.

1. Added the complete supply-to-closing and commission collection contract, must-build/manual/later split, launch gates and measurable beta closeout.
2. Added concise scope links across Product shape, Journeys, Model, Listing Matrix and Build boundary; retained the full product direction.
3. Preserved Sold Properties & Market Intelligence, Original interactive prototype, prior history, password gate and source bytes.

Prior revision · Preserved

v0.2 · Simple social, Projects and Presale

One marketplace, one map and one listing system gain a lightweight social layer, verified Project seller profiles and verified Presale listing options. Terra-controlled introductions remain intact.

1. Buyers can Like/Save, Follow, Share and Inquire. Sellers see aggregate likes/saves without buyer identities; sharing excludes private contact and transaction data.
2. Following sellers or Projects provides listing and price-change updates. Notification delivery details remain to be specified; no public comments or Q&A are added.
3. Project is a seller/account type with multiple ordinary listings or units, not another administrative role or marketplace. Projects receive no featured section or preferential exposure.
4. Any seller or Project can select Presale, subject to verification before publication as Presale. Buyers use the existing marketplace/map filters.
5. Seller and Project dashboards cover views, likes/saves, followers, inquiries, viewing requests and offers.
6. Matt confirmed that listing-specific inquiries go through Terra first; direct buyer–seller chat opens only after Terra authorizes the introduction.
7. Historical status-label correction: v0.1.1 and v0.1.2 are prior versions, not simultaneous current versions. Their recorded content and immutable artifacts are preserved.

Prior revision · Preserved

v0.1.2 · Mobile navigation refinement

Placed workbook history on its own full-width row below all seven product pages on mobile. Product content and the prior review record are unchanged.

Prior revision · Preserved

v0.1.1 · Review corrections

Corrected the displayed baseline revision reference and placed Changelog in secondary navigation. The v0.1 product corrections remain unchanged.

Prior content iteration · Preserved

v0.1 · First product-feedback round

Terra is now described around the complete owner-to-buyer transaction. The operating team and Messenger support that lifecycle rather than define its limits.

1. Structured offers, counters and negotiation are core; an offer may precede or follow a showing.
2. The owner-paid 4.5% commission, listing-submission agreement and no automatic price inflation are established business terms.
3. Owner and ownership verification, document review and Terra’s beta operating responsibility are explicit.
4. Prototype findings remain implementation evidence; only unresolved operational details remain open. Sold-property content, illustrative records, privacy boundaries and the original prototype are preserved.

Superseded · Preserved

v0.0 · Initial baseline

The pre-feedback workbook contained seven pages covering product shape, journeys, system model, Listing Matrix, sold-property intelligence, build decisions and the original v14 prototype. It incorporated earlier communication, listing, sold-market and source-audit updates. This baseline label groups those existing retained draft revisions; it does not rename or rewrite them.

1. The baseline emphasized organization-mediated introductions and distinguished observed, proposed and unresolved behavior.
2. The first feedback round supersedes its narrower product framing and the treatment of core negotiation and commission as undecided or deferred.