A growing little world · Select a building · The empty lot becomes whatever we imagine next ✨
BIG DREAMS · SMALL STEPS · EVERYBODY BELONGS
Your practical lakeside retreat meets a town that changes with the calendar. Amounts are blank until you enter verified figures. The Groundskeeper is a seasonal planner, not an autonomous agent.
The schedule is a reminder inside this page, not a bank transaction or background notification. No payments are made.
The garden and town decorations follow the current month automatically when you open this page. Choose a manual override for a special occasion.
Plant suggestions are seasonal inspiration, not a local planting guarantee. Confirm frost dates, planting windows, soil, and USDA hardiness zone before planting. No automatic weather checks or push alerts are active.
Give every business its own mailbox. Add a message below, and your rules will route it to a building automatically—or flag it for you to sort. This demo does not read Gmail or Outlook.
Rules match sender email, sender domain, or subject keywords. First matching rule wins; drag-and-drop and more advanced conditions can come later.
Unrecognized messages go to the Post Office for sorting, never to an arbitrary business. You can always move a letter manually.
Choose a Neighborhood mail snapshot JSON file to bring actual message summaries into the building mailboxes. Duplicates are skipped. This does not connect your inbox or change messages in Outlook.
One communication headquarters for every business. Review its mailbox, register social and email channels, plan campaigns, and prepare requests for presidential approval.
Showing messages already stored in your town, not fetching new mail.
Keep account names and URLs together. Never store passwords or access tokens here.
Plan content by business; drafts remain in the town until reviewed.
Queue proposed replies, posts, outreach, or campaigns. Approving records a decision only—nothing is published.
Select a building to see its communications desk.
One backup for all four departments: the town and Agent Academy, the Post Office, Communications, and the President’s decisions. Existing town data remains in place, and this vault packages it together without silently replacing your records.
Backups contain your entered notes and imported mail summaries. Keep backup files private. Local browser storage is device- and origin-dependent: older downloaded HTML files may not share data with this version. To migrate, open the old version, export its backup, then restore it into that department before making a complete V12 backup. The City Vault does not connect to an online database.
A town square for sharing project discoveries, proposing ideas and gathering questions for the President. These are recorded planning notes, not messages exchanged by live AI agents. Future connectors can add authenticated, attributable agent reports here.
Brainstorming, creative ideas, friendly critique and questions.
Open questions and contributions across departments. Nothing is a validated finding until reviewed.
Collect a concise recommendation or question for presidential review.
A town-wide record of reported decisions, accomplishments and follow-ups. Every entry has a source and an honest status. Adding a record never performs the action it describes.
Privacy: records are stored in this browser and now included in City Vault backups. Do not paste passwords, private customer details or medical records. The ledger does not automatically validate claims or monitor outside systems.
This town is not approved for medical-record storage. Do not add medical documents, diagnoses, test results, treatment details, or other sensitive health data to tasks, notes, the City Ledger, mail, cloud uploads, or backups. Use secure patient portals for records. The hospital is a general planning space only until a separately secured health-record system is developed and reviewed.
Take the Neighborhood beyond downloaded files. This edition supports an optional private, authenticated cloud vault using your own Supabase project. Once you configure hosting and the database, the same town can open on your phone and computer.
Log into your own town account. Cloud storage stays off until you configure it. No business services or AI agents are connected.
Nothing syncs without your command. Keep a local backup before changing devices.
Restore will replace your local town records. Export a City Vault backup first. This never edits Gmail, Outlook, Shopify, or any external service.
Security: The database policies separate accounts; logins use Supabase Authentication. Do not paste any Supabase service-role key here. The public client key is safe for browsers only when row-level security is configured. Cloud backups can contain mail summaries and business notes—protect your account with a strong password and consider MFA through your authentication provider.