rustic-hi is a personal AI agent built for one person. The product intent, taken directly from the authoritative requirement thread, is to give a single user — Nandu — a personal agent that consolidates their day-to-day assistance needs all in one place, rather than spread across separate tools. The agent is personal: it is tailored to the individual user's way of thinking and working, and the user interacts with it conversationally, in a chat-style interface.
The audience is exactly one human actor: the Personal Agent Owner. There is no team, no shared workspace, and no multi-user behavior. The product is a hand-built, dependable instrument for one desk — a place where the owner talks to their agent, keeps the resulting conversations, and shapes how the agent thinks and works.
This document defines the current delivery: an anonymous public entry, self-service enrollment, returning verification, the conversational workspace, the preserved conversation history, and the personalization workspace that tailors the agent to its owner.
rustic-hi is a first-party web application with an application-owned identity boundary and custom UI. It delivers:
Actors. The only active human actor is the Personal Agent Owner. The AI agent itself is a system-side responder, not a persona: it produces responses inside the owner's conversational workspace and holds no independent goals, destinations, or account.
Ownership. All six surfaces are application-owned custom pages. Identity is application-owned: the owner privately owns and resumes durable, actor-specific state (their conversations and their personalization), so enrollment and returning verification are first-party interactions. The Landing page is anonymously reachable; Chat, Conversations, and Personalization require the owner to be verified.
Narrow exclusions. The agent is personal to a single user; no multi-user or shared-account behavior is in scope. The agent's day-to-day capabilities — managing tasks, answering questions from notes, drafting messages — were raised only as examples and are not confirmed scope; they are not built as features, modules, or destinations. No adjacent account-management capabilities (password reset flows, profile administration, billing, team management) are added.
rustic-hi is delivered as a first-party web application the owner signs into and uses directly. The public entry is anonymous and explains what the agent is and what "all in one place" means before any identity exists. Because the owner's conversations and personalization must survive across sessions and remain bound to the correct person, the application owns identity: the owner establishes it once through self-service enrollment, and verifies it on return. The protected working surfaces — Chat, Conversations, and Personalization — are unavailable until that verification succeeds; the anonymous entry never owns the interaction that establishes access to itself.
Everything the owner does with the agent happens inside the application: conversation, history, and personalization are first-party surfaces, not provider-owned or external destinations. The agent's responses are produced by the application's backend on the owner's behalf and rendered inside the owner's conversational workspace.
Current horizon. The six surfaces above, the enrollment and verification boundary, the conversational workspace, the preserved history, and the personalization workspace are all current.
Future horizon. Any expansion of the agent's day-to-day capabilities beyond conversation, history, and personalization — including the example capabilities named in the source (task management, answering questions from notes, drafting messages) — remains unconfirmed and out of current scope. Nothing in this document commits to them.
Not applicable. No reference directive in this project declares a content_source, so no source content inventory is produced.
FR-1 — Personal agent for the owner As a Personal Agent Owner, I should have a personal AI agent of my own, so that my day-to-day assistance is handled by one agent dedicated to me.
FR-2 — Tailored to how the owner thinks and works As a Personal Agent Owner, I should be able to tailor the agent to my way of thinking and working, so that its assistance fits me rather than a generic user.
FR-3 — All in one place As a Personal Agent Owner, I should have my assistance needs consolidated in one place, so that I do not switch between separate tools.
FR-4 — Conversational interaction As a Personal Agent Owner, I should interact with my agent conversationally, so that I can ask, say, and refine things in plain language.
FR-5 — Start a new conversation As a Personal Agent Owner, I should be able to start a new conversation, so that a fresh topic does not have to continue an old thread.
FR-6 — Preserved conversation history As a Personal Agent Owner, I should have my conversations preserved, so that what I have already worked through is still there when I come back.
FR-7 — Browse and continue prior conversations As a Personal Agent Owner, I should be able to browse my preserved exchanges and continue a prior conversation, so that I can pick a thread back up instead of restarting it.
FR-8 — Self-service enrollment As a Personal Agent Owner, I should be able to enroll myself before first use, so that I can begin using my agent without waiting on anyone else.
FR-9 — Returning verification As a Personal Agent Owner, I should be able to verify myself on return, so that I get back to my preserved conversations and personalization.
FR-10 — Protected workspace As a Personal Agent Owner, I should have my conversations and personalization kept private to me, so that my personal agent stays personal.
Product context. The Personal Agent Owner is the single user of rustic-hi — Nandu. They want a personal AI agent that consolidates their day-to-day assistance into one place. They converse with the agent through a chat interface and rely on it to handle their personal tasks, questions, and drafting needs, with the agent tailored to how they think and work. Success means one unified place where their personal assistance needs are handled without switching between separate tools.
Primary goal. To have one dependable, personal agent that handles their day-to-day assistance in a single place, shaped to the way they actually think and work.
Distinct accepted responsibilities.
Relevant inputs and decisions. What to say to the agent and when to start a new thread rather than continue one; which preserved conversation to reopen; what to record about their name and voice, how they think, and what the agent should handle; whether to save or revise personalization values.
Interactions with other accepted participants. The only other participant in the owner's work is the agent itself, which responds inside the owner's conversational workspace. The agent is a system-side responder, not a persona: it holds no independent goals, no account, and no destination of its own. There is no second human participant, no team, and no shared state — the owner's conversations and personalization are theirs alone.
Observable success. The owner returns after time away, verifies, and finds their conversations and personalization exactly as they left them; they send a message and get a response that reflects how they have tailored the agent; they move between conversation, history, and personalization without leaving the application.
Source-backed constraints. The agent is personal to a single user; no multi-user or shared-account behavior applies. The agent's day-to-day capabilities beyond conversation, history, and personalization — managing tasks, answering questions from notes, drafting messages — were raised only as examples and are not confirmed scope.
Failure and recovery: if the email is already enrolled, or the email or password is rejected, an inline all-caps error appears on a ruled bar above the form and the entered values other than the password are preserved. The owner corrects the flagged field and resubmits, or follows the link row to Login if they already have an identity.
Failure and recovery: if the credentials are not recognized, an inline all-caps error appears on a ruled bar above the form, the email is preserved, and the password field is cleared. The owner corrects the credentials and resubmits, or follows the link row to Sign Up.
Failure and recovery: if the history cannot be loaded, an all-caps error appears on a ruled bar with a retry control, and the owner retries. If a single conversation cannot be opened, its card shows an inline all-caps failure label while the rest of the grid stays usable.
Empty state: if no conversations are preserved yet, the badge-stamp motif appears with an all-caps message and a control to start the first conversation.
Failure and recovery: if the save fails, an all-caps error appears on a ruled bar and the owner's unsaved edits remain in place. The owner retries the save without losing the edits.
Failure and recovery: if the conversation cannot be created, an inline all-caps notice appears with a retry control, and the owner retries or continues in the conversation already open.
The creative direction is authoritative for this section.


rustic-hi is a personal AI agent built for one person — you.
It is shaped around your way of thinking and working, not a team's, so the agent stays yours alone.
Talk to it in one place, keep every conversation, and shape how it works as it goes.
rustic-hi is a personal AI agent dedicated to a single owner — Nandu. It is not a generic assistant shared between teams or accounts. Everything it holds belongs to one person, and it is shaped around how that one person thinks and works.
You talk to it the way you would talk to anything else on the desk: in plain language, in your own words. No commands to memorise, no forms to fill in. You say what you need, the agent answers in the conversation, and the exchange stays with you.
You talk to your agent the way you talk to a person — in plain sentences, in one place, in a single thread of exchange.
What you have already said stays where you said it. Conversations are preserved rather than discarded when a session ends.
How the agent thinks and works is shaped around you, and it stays shaped as your conversations continue.
This agent is not a shared workspace and it is not a team tool. It is personal: made for a single owner, tuned to one person’s way of thinking and working, and used from one desk.
All in one place means the owner keeps everything the agent holds about them here — the conversations they have had and the personalization that shapes how it works. Nothing belongs to anyone else, because there is no anyone else.
The agent is personal to one person. It is built around how a single owner thinks and works, and it stays bound to that owner.
Every conversation kept here and every personalization setting belongs to that owner — it is theirs alone, not shared out to anyone else.
Leave and come back and it is still there: the same conversations and the same personalization, waiting where they were left.
Come back later and the agent is still there, still personal, still holding the same conversations and the same personalization.
No comments yet. Be the first!