Port View Residency is a small independent residential property — rooms and suites for rent — that needs a public website. The product intent is twofold and comes directly from the residency owner's request: give Port View Residency a warm, human, trustworthy public web presence, and carry practical location details obtained from Google Maps so that people can actually find and reach the place.
The audience is people looking for a place to stay or live — travellers, students, families, and workers relocating — who arrive to learn what the residency is and where it is located, plus the residency owner/manager who maintains the published information about the residency.
The website is delivered as a first-party web application with a public, account-free visitor experience and a protected management workspace for the residency owner/manager.
garnet-hi is a website for Port View Residency. It presents the residency to the public and gives the owner/manager a way to keep the residency's published information and location details correct.
Current delivery consists of five first-party pages:
Actors:
Accepted behavior in scope: a public website for the residency; Google Maps-sourced location details displayed publicly; self-service enrollment and returning verification for the owner/manager; and a protected workspace for maintaining the residency's published information and location details.
Narrow exclusions: no booking, reservation, payment, tenancy application, messaging, or listing-marketplace capability is accepted by the source. No account is required for visitors to read the residency's public information or its location details.
The public side of the site is open and account-free. A visitor can read about Port View Residency and see its location details without signing up for anything. The location details are not authored by the site itself — they are obtained from Google Maps, which is the authoritative source for that content, and the site presents them.
The management side is first-party and protected. Because the residency's published information is durable and must remain bound to the correct owner, the Residency Owner / Manager establishes access once through self-service enrollment on Sign Up, and thereafter verifies identity on Login before resuming protected management on Residency Info. Sign Up and Login are anonymously reachable entry surfaces; Residency Info is not, and its protected state remains unavailable until identity is established.
Everything described above is current. No future-horizon capability has been accepted by the source; nothing beyond the current scope is planned or promised here.
The reference directive for Google Maps declares uses: ["domain_context", "content_source"] with authority: authoritative, instructing that Google Maps be used to obtain the residency's location details for display on the website.
Verified factual entities available from that directive:
No further verified factual entities, collection items, field values, descriptions, dates, contacts, links, or media references were supplied by the directive. Location detail values (street address, coordinates, landmarks, transport, contact numbers) are resolved at runtime from Google Maps and are not invented here.
FR-1 — Public residency website (explicit) As a Residency Owner / Manager, I should have a public website for Port View Residency so that the residency has an accurate public web presence.
FR-2 — Google Maps location details presented publicly (explicit) As a Prospective Resident / Visitor, I should see Port View Residency's location details obtained from Google Maps so that I can find and reach the residency.
FR-3 — Google Maps as the location-details provider (required_inference) As the system, I should obtain the residency's location details from Google Maps so that the public Location destination presents authoritative location content.
FR-4 — Self-service enrollment (required_inference) As a Residency Owner / Manager, I should complete self-service enrollment on Sign Up so that I can establish access for maintaining the residency's durable published information.
FR-5 — Returning verification (required_inference) As a Residency Owner / Manager, I should complete returning verification on Login so that I can resume protected management of the residency's durable published information.
FR-6 — Maintain the residency's published information (required_inference) As a Residency Owner / Manager, I should edit and save the residency's published information on Residency Info so that the public pages stay correct as the residency's details change.
FR-7 — Maintain the residency's location details (required_inference) As a Residency Owner / Manager, I should edit and save the residency's location details on Residency Info so that the publicly displayed location information stays accurate.
FR-8 — Anonymous public reading of the residency's information (required_inference) As a Prospective Resident / Visitor, I should read about Port View Residency and its location without creating an account so that I can decide whether to reach out or visit.

Port View Residency
A small independent residency of rooms and suites, run by the people who live here.
Port View Residency’s published information is kept and maintained by the owner / manager.

Port View Residency
A small independent residency of rooms and suites, run by the people who live here.
Port View Residency’s published information is kept and maintained by the owner / manager.
No comments yet. Be the first!