# noticed terminology

Use the smallest clear term. Do not invent synonyms to make the product sound more sophisticated.

| Term | Meaning and use |
| --- | --- |
| `noticed` | The company and product name. Always lowercase. |
| professional relationship | A person someone knows, plus the history and context of that connection. Prefer this to `contact` when the relationship is what matters. |
| network | The professional relationships a person or team already has. |
| relationship context | Who someone is, how you know them, what has happened, and why the relationship may matter now. |
| social memory | noticed's living memory of people, professional relationships, and their context. Use `professional social memory` on first mention when `social` could be mistaken for social media or personal life. Use `shared social memory` when it combines a team's relationships. Do not use `relationship memory` as a synonym. |
| source | An account or dataset someone explicitly connects to noticed. Use `source`, not `relationship source` or `data source`, unless a technical distinction is necessary. |
| noticed agent | The noticed product acting as an AI coworker that understands and helps with professional relationships. |
| noticed Chrome extension | The Chrome extension used to sync supported professional accounts and import relationships into noticed. Use the full name on first mention and `Chrome extension` afterward. |
| builder | A founder, operator, or other person building a company or a product. |
| goal | The concrete outcome the person or team wants help with. |
| Team | The product workspace shared by a group. Use lowercase `team` when referring to the people generally. |
| early access | The limited noticed experience available before full access. Do not call it a sandbox, beta, private beta, or waitlist. |
| full access | Access to noticed beyond the early-access experience. |