S2 Property

Property portfolio manager — units, tenancies, income/expenses and document storage for the S2 property portfolio.

BuildingWatchProperty / FinanceGPT4 openUpdated 1w ago

Open Workspace

Tick what you need, then launch this project's tools together.

Links open in your current Chrome profile — RobOS can't switch profiles for you. Use Chrome · Personal (rob@rob-os.com). If your browser blocks the bulk open, click any link's arrow individually.

Current status & focus

Statusbuilding

Healthamber

Current focusUnits + tenancies model and finance summary.

Last update6 Jun 2026

Next action

Build the per-unit financial summary (rent in, costs out, yield).

Architecture

Next.js App Router + TypeScript + Tailwind. Supabase for units/tenancies/finances. Vercel hosting.

Design standard

Financial clarity. Clean numbers, clear tables, confident summaries. RobOS design language.

Known issues & blockers

Need a clean list of current units and tenancy dates to seed real data.

Decisions

All decisions

No decisions logged for this project yet.

Reusable prompts

Prompt library

Strategy / planning (any project)
Strategy · best with gpt
AI handover builder (any project)
Handover · best with gpt

AI handover

S2 Property tracks a property portfolio's units, tenancies and finances (Next.js + Supabase). Financial data — keep it private. Need real unit/tenancy data before seeding. GPT for modelling the finance summary. Personal profile.

Quick launch

Live app GitHub repo Vercel project Supabase project Domain / DNS

cd command

cd "C:\dev\s2-property"

Account & profile

Account identityrob@rob-os.com · GitHub · Vercel via GitHub

Browser profileChrome · Personal (rob@rob-os.com)

Local repo pathC:\dev\s2-property

Domains2property.example

Environment map

NEXT_PUBLIC_SUPABASE_URL

Used by app runtime + Vercel · value in Vercel project env

public

NEXT_PUBLIC_SUPABASE_ANON_KEY

Used by app runtime + Vercel · value in Vercel project env

public anon key

SUPABASE_SERVICE_ROLE_KEY

Used by server only · value in Vercel project env (server)

financial data

Credentials map

All credentials

GitHub login

GitHub · Login

CriticalAI: never share

Account: rob@rob-os.com
Secret location: Password manager › RobOS vault › GitHub
MFA: Enabled
Recovery: Password manager › RobOS vault › GitHub › recovery
Last reviewed: 2026-06-13

Used by:HumanVercel

Shared in a chat transcript on 2026-06-13 — ROTATE soon and enable a passkey. Vercel & Supabase log in via this GitHub account.

AI-safe handover: GitHub is the identity hub — Vercel and Supabase authenticate via 'Continue with GitHub'. Never request or print the GitHub password. Use a fine-grained Personal Access Token in CI via the GITHUB_TOKEN env var instead.

Vercel (via GitHub SSO)

Vercel · Oauth App

Medium riskAI: never share

Account: rob@rob-os.com (GitHub SSO)
Secret location: No separate password — logs in via GitHub
MFA: Enabled
Last reviewed: 2026-06-13

Used by:HumanApp Runtime

No standalone secret; secured by the GitHub account. Use VERCEL_TOKEN for API automation later.

AI-safe handover: Vercel logs in with GitHub SSO — there is no separate Vercel password. For future API automation use a VERCEL_TOKEN env var; do not request it inline.

Supabase database password

Supabase · Login

CriticalAI: never share

Account: postgres (per project)
Secret location: Password manager › RobOS vault › Supabase DB; also in Supabase project settings
MFA: Off
Last reviewed: 2026-06-13

Used by:HumanApp Runtime

Shared in a chat transcript on 2026-06-13 — ROTATE in Supabase project settings. Dashboard login itself is via GitHub SSO.

AI-safe handover: The Supabase Postgres password is a secret. Never request, print or hardcode it. Connect using the pooled connection string from process.env (e.g. DATABASE_URL / SUPABASE_DB_URL) which I configure manually.

Stripe (future billing)

Stripe · Api Key

High riskAI: env var only

Secret location: Stripe dashboard › API keys; Vercel env when used
Env var: STRIPE_SECRET_KEY
MFA: Enabled

Used by:App RuntimeVercel

Use restricted keys per project. Webhook secret separate.

AI-safe handover: Use process.env.STRIPE_SECRET_KEY on the server and STRIPE_WEBHOOK_SECRET for webhooks. Never log or expose secret keys; prefer restricted keys.

For Codex

Generate a repo-ready task brief with acceptance criteria in the Prompt Builder.

Repo: rob-os/s2-property