Projects
One memory for the people on a piece of work. Save a decision to the project once, and everyone on it can recall it from their own assistant. Your personal memory stays private.
What a project is
A project is a shared memory for one piece of work, with its own six buckets: decisions, plans, people, references, learnings and state. Sharing is per project, not per team or company.
Every assistant you use loads your personal memory and your projects. Only what goes into a project is shared.
Create
Create a project in the web app (Projects → New) or from any assistant you use: “nura, create a shared project called Harbor.”
A target date is optional. Your assistant learns it from a sentence like “we ship on the 15th.”
Invite
Invite people by email, from the web app or your assistant: “nura, invite priya@… to Harbor.” The invitation is tied to that address: your teammate accepts it the next time they sign in with that address. A teammate without an account gets one on accepting, with an empty, private personal memory.
Invitations don't expire: a pending one stands until it's accepted or revoked, and can be re-sent. There's no limit on members or projects during the launch phase.
Roles
There are four roles. An Owner can do everything, including transferring ownership and deleting the project.
An Admin invites people and manages invitations, adds and removes Members and Viewers, sets their roles up to Admin, renames the project, and sets its target date and intake policy. An Admin can't remove or demote an Owner, transfer ownership, or delete or restore the project.
A Member reads and writes the project's memory. A Viewer is read-only: they can read it and see who's on the project. Only someone who outranks you can change your role.
Any assistant
See what your team did since you were last there. Open a project on any AI you use and it starts with what your teammates saved. Teammates use their own models, and the project's decisions, plans and people come back the same on every one.
Name the project and Nura routes there:
“nura, save to Harbor: we chose Postgres.”
“what's open in Harbor?”
“nura, move these to Harbor.”
Privacy
A save lands in a project only when you name it or ask for it; nothing is copied in from your personal memory. Every project record says who saved it.
Your personal life stays out even when you name a project: a health note, a family matter, money that's your own. Nura keeps it personal and says so.
Disagreements
When two teammates record conflicting decisions, both stay, along with who decided what. Anyone who asks gets both, and you settle it on the record.
Intake policy
Owners and Admins can make fields required or suggested, per project. For example, every decision needs a rationale, or every plan needs an owner and a date.
A save that misses a required field still lands, flagged, and your assistant asks you for the missing piece.
Admin
Depending on your role, you can rename a project, set its target date, change roles, remove people, transfer ownership, leave, export, delete and restore. All of it works in the web app, and most of it from your assistant too.
Remove someone and they lose access right away; what they saved stays in the project, attributed to them. After a transfer, the previous Owner becomes an Admin. A sole Owner must transfer or delete the project before leaving.
A deleted project is hidden from everyone on it, and the Owner can restore it within 30 days. After that, it's purged for good.
Slack · Microsoft Teams
A Slack or Microsoft Teams channel can be connected to a project with opt-in capture. Decisions made in the channel land in the project, with a visible notice in the channel. Nothing is read without opt-in. Recall them from any assistant you use.
Price
Nura is free during the launch phase, including projects.