Traceability
Requirement registry
Every product requirement is represented in this prototype or explicitly labeled as a future or simulated enterprise capability.
460
Requirement records
23
Capability areas
Mapped
Prototype traceability
| ID | Requirement | Release | Coverage |
|---|---|---|---|
| ACC-01 | Users sign in with J&J single sign-on. There is no separate password. | Launch | Represented |
| ACC-02 | Only approved users or groups can open the app. Anyone else sees how to request access. | Launch | Represented |
| ACC-03 | Three roles exist: Member, Group owner and Admin. A person can be a member of one group and an owner of another. | Launch | Represented |
| ACC-04 | Admins create user groups, for example by therapeutic area, brand, function or leadership team. A user can be in several groups. | Launch | Represented |
| ACC-05 | Group members can be added and removed by hand. | Launch | Represented |
| ACC-06 | Every document, prompt, playlist and output has an owner and a visibility: private, named people, one or more groups, or everyone. | Launch | Represented |
| ACC-07 | Access rules apply everywhere: library, search, assistant suggestions, recommendations, questions, Voice AI and shared audio. A user never gets an answer drawn from a document they cannot open. | Launch | Represented |
| ACC-08 | Access changes take effect right away, including for content already shared. | Launch | Represented |
| ACC-09 | Users can see which groups they are in and what each one gives them. | Launch | Represented |
| ACC-10 | Group membership can sync from existing J&J directory groups. | Next | Represented |
| ACC-11 | Users can ask to join a group. The group owner approves or declines. | Next | Represented |
| ACC-12 | A reviewer role can approve content before it is published to a large audience. | Next | Represented |
| ACC-13 | A leader can name a delegate, for example a chief of staff, who prepares content on their behalf. | Later | Represented |
| ADM-01 | See all users with their roles, groups and last activity. Activate and deactivate users. | Launch | Represented |
| ADM-02 | Create, rename and archive groups. Set owners. Add and remove members. | Launch | Represented |
| ADM-03 | Assign roles. | Launch | Represented |
| ADM-04 | Transfer ownership of documents and sessions when someone leaves or changes role. | Next | Represented |
| ADM-05 | Manage the company library and any group library: bulk upload, organize, tag, and assign to users or groups with a note. | Launch | Represented |
| ADM-06 | Publish ready-made audio to groups. | Launch | Represented |
| ADM-07 | Withdraw any document or output from circulation right away, with a notice to the people who had it. | Launch | Represented |
| ADM-08 | Set document status and expiry dates. | Next | Represented |
| ADM-09 | Set storage and retention rules by content type and group. | Next | Represented |
| ADM-10 | Manage featured content and announcements on the landing page. | Next | Represented |
| ADM-11 | Manage the lexicon. | Launch | Represented |
| ADM-12 | Manage the voice list: which voices are available, their names, and the defaults per format. | Launch | Represented |
| ADM-13 | Create and publish common prompts. | Launch | Represented |
| ADM-14 | Manage the shared option lists: tones, lengths, depth levels and session types. | Next | Represented |
| ADM-15 | Manage personas and scenarios for Voice AI. | Next | Represented |
| ADM-16 | Review prompt proposals and lexicon suggestions from users. | Next | Represented |
| ADM-17 | Set the rules that apply to every output and that users cannot edit. | Launch | Represented |
| ADM-18 | Define protected content: passages or content types that are never summarized, shortened or dropped. | Launch | Represented |
| ADM-19 | Define restricted topics and content types, and what happens when one is triggered. | Launch | Represented |
| ADM-20 | Set policy switches: whether voice audio is stored, whether audio can be downloaded, whether shared audio needs source access, and when a review step is needed before publishing. | Launch | Represented |
| ADM-21 | Turn a feature on for selected groups first, for pilots. | Next | Represented |
| ADM-22 | Usage report: active users, sessions by format, minutes generated and listened, and most used documents and prompts, by group and over time. | Launch | Represented |
| ADM-23 | Audit log of uploads, shares, generations, updates, deletions, access changes and admin actions, with who and when. It can be searched and exported. | Launch | Represented |
| ADM-24 | Quality report: ratings, reported problems by type, failed checks, pronunciation flags and failed generations. | Next | Represented |
| ADM-25 | A review queue for reported problems, with the flagged moment, the source and a way to resolve it. | Next | Represented |
| ADM-26 | Cost and consumption by group, with limits and alerts. | Next | Represented |
| ADM-27 | Service status for generation, voice and document processing, with a banner to users during an incident. | Next | Represented |
| ADM-28 | A support view to look up a user's failed generation and its error, without showing content the support person is not allowed to see. | Next | Represented |
| ADM-29 | Reports for governance reviews: model and voice versions in use, guardrail outcomes and sample outputs. | Next | Represented |
| ART-01 | Two narration modes: Read as written, and Summarized. The mode is shown on the output. | Launch | Represented |
| ART-02 | Read as written keeps all the content and adds nothing, while sounding natural. Bullets, tables and headings are spoken the way a person would read them aloud. | Launch | Represented |
| ART-03 | Summarized uses the shared depth levels to decide how much to keep. | Launch | Represented |
| ART-04 | The narrator is chosen from the approved voices, and tone comes from the shared list. | Launch | Represented |
| ART-05 | The readthrough follows the document's order and is chaptered by its sections, slides or pages. | Launch | Represented |
| ART-06 | Slide and section titles are announced so the listener knows where they are. | Launch | Represented |
| ART-07 | Page numbers, headers, footers and repeated boilerplate are left out by default. | Launch | Represented |
| ART-08 | Charts, tables and images are described briefly with their main numbers by default. | Launch | Represented |
| ART-09 | Several documents can be read one after another, in the order the user sets, as chapters of one readthrough. | Launch | Represented |
| ART-10 | Protected passages are always read in full, in both modes. See Trust, compliance and data. | Launch | Represented |
| ART-11 | The words being read are highlighted in the transcript and on the source page. | Launch | Represented |
| ART-12 | Estimated listening time is shown before generating. | Launch | Represented |
| ART-13 | The output includes audio, a synced transcript, chapters and page or slide references. | Launch | Represented |
| ART-14 | Users choose which sections, pages or slides are read, and whether speaker notes, footnotes, references and appendices are included. | Next | Represented |
| ART-15 | Users choose how visuals are handled: described, summarized or skipped. | Next | Represented |
| ART-16 | Long documents can be split into parts. | Next | Represented |
| ART-17 | The narrator voice can be changed after generation without redoing the script. | Next | Represented |
| AST-01 | Users can speak or type, and switch between the two in the same conversation. The prototype is voice only. | Launch | Represented |
| AST-02 | The assistant shows what it heard as text. The user can correct it before the assistant acts. | Launch | Represented |
| AST-03 | The assistant replies in text and can also reply by voice. Spoken replies can be turned off. | Launch | Represented |
| AST-04 | It can do everything the manual route can: find and select documents, suggest documents, choose a format, ask goal questions, propose settings, write the brief, start generation and open the result. | Launch | Represented |
| AST-05 | It finds documents from a description, such as "my financial documents" or "the deck shared with me last week". When several match, it shows them and asks. | Launch | Represented |
| AST-06 | It asks only for what is missing. If the request already gives length and tone, it does not ask again. | Launch | Represented |
| AST-07 | It takes answers in the user's own words and follows them exactly. "Under 25 minutes" means a 25-minute limit, not the nearest preset. | Launch | Represented |
| AST-08 | Before generating, it shows the plan: documents, format, length, tone, voices and focus. The user can change any part by voice, typing or tapping. | Launch | Represented |
| AST-09 | It asks for a clear yes before generating, updating, sharing or deleting. | Launch | Represented |
| AST-10 | It offers example things to say at each step. | Launch | Represented |
| AST-11 | It can start any Voice AI session directly, for example "quiz me on the Q3 deck". | Launch | Represented |
| AST-12 | It can explain the product: what each format is for and what it can and cannot do. | Launch | Represented |
| AST-13 | It never suggests or uses a document the user cannot open. | Launch | Represented |
| AST-14 | When it cannot do something, it says so and offers the closest thing it can do. | Launch | Represented |
| AST-15 | It answers quick questions straight from the documents, with source references, without creating audio. | Next | Represented |
| AST-16 | It can open and manage things: "open my last podcast", "share this with the Immunology leadership group", "make it shorter". | Next | Represented |
| AST-17 | It can be reached from anywhere in the app, not only the landing page. | Next | Represented |
| AST-18 | It remembers the user's usual choices for length, tone and voices and applies them unless told otherwise. | Next | Represented |
| AST-19 | Conversations with the assistant are saved and can be picked up again. | Next | Represented |
| AST-20 | The user can interrupt it while it is speaking. | Next | Represented |
| AST-21 | Hands-free use on a phone, with large controls and voice only. | Later | Represented |
| GEN-01 | Progress shows real stages and a time estimate based on document size and the length requested. | Launch | Represented |
| GEN-02 | Generation runs in the background. The user can leave the screen, start something else or close the app. | Launch | Represented |
| GEN-03 | The user is told when the output is ready. | Launch | Represented |
| GEN-04 | A generation in progress can be canceled. | Launch | Represented |
| GEN-05 | If generation fails, the user gets a plain reason and can retry with all settings kept. | Launch | Represented |
| GEN-06 | Before release, every output is checked: each statement traces to a source passage; numbers, names, dates and units match; nothing comes from outside the documents; the lexicon is applied; guardrails pass; protected passages are intact; length is on target. | Launch | Represented |
| GEN-07 | If a check fails, the system corrects and checks again. If it still fails, the user is told what could not be verified. | Launch | Represented |
| GEN-08 | Each output shows that it is AI-generated, its sources, its date and the brief used. | Launch | Represented |
| GEN-09 | If the documents do not hold enough for the length or topic requested, the system says so and suggests a shorter output or more documents. | Launch | Represented |
| GEN-10 | Audio quality is consistent: even loudness, natural pacing, no cut-offs, clean joins between segments. | Launch | Represented |
| GEN-11 | Several generations can be queued, and the user can see the queue. | Next | Represented |
| GEN-12 | When documents disagree, for example two figures for the same measure, the user is told and decides. | Next | Represented |
| GEN-13 | A request that matches an existing output (same documents, same brief) offers that output instead of generating again. | Next | Represented |
| GEN-14 | Admins set generation limits per user and group. Users see their limit before they reach it. | Next | Represented |
| GEN-15 | Listening can start while later chapters are still being made. | Later | Represented |
| HOME-01 | New users get a short tour of the three formats, how documents are used, and the assistant and manual routes. It can be skipped and replayed later. | Launch | Represented |
| HOME-02 | The tour only promises what the product does. File types, timings and names match the live product. | Launch | Represented |
| HOME-03 | A first-use notice explains what is processed and stored. | Launch | Represented |
| HOME-04 | A new user with an empty library gets a sample document and a sample podcast to try. | Next | Represented |
| HOME-05 | One place at the top to say or type what you need. The request goes to the assistant. | Launch | Represented |
| HOME-06 | One-step starts for Podcast, Audio Readthrough and Voice AI, each with a plain line on what it is best for. | Launch | Represented |
| HOME-07 | Both routes, assistant and manual, are always available. The user does not have to pick a mode before starting. | Launch | Represented |
| HOME-08 | Continue where you left off: unfinished listening, drafts not yet generated, and conversations that can be resumed. | Launch | Represented |
| HOME-09 | Anything still generating is shown with its progress. | Launch | Represented |
| HOME-10 | Recent sessions and recently added documents. | Launch | Represented |
| HOME-11 | New for you: documents and audio shared with the user or published to their groups since the last visit. | Launch | Represented |
| HOME-12 | A short guide for newcomers: example requests, what each format is good for, and links to help. | Launch | Represented |
| HOME-13 | The greeting uses the signed-in user's name and the local time of day. | Launch | Represented |
| HOME-14 | AI suggestions based on what is new, for example: "You added the Q3 deck yesterday. Want a 10-minute podcast?" One action accepts. | Next | Represented |
| HOME-15 | Featured content and announcements set by admins or group owners. | Next | Represented |
| HOME-16 | Popular and recommended prompts for the user's role. | Next | Represented |
| HOME-17 | Search across documents, sessions and prompts from one box. | Next | Represented |
| HOME-18 | Short notes on what is new when features ship. | Next | Represented |
| HOME-19 | Users can switch between assistant and manual at any point and keep everything they have selected or answered. | Launch | Represented |
| HOME-20 | Users can set which route opens by default. | Next | Represented |
| IDEA-01 | What changed. Give two versions of a document and get a short audio covering only the differences. Useful for label updates, policy changes and deck revisions. | Next | Represented |
| IDEA-02 | Meeting prep pack. From one deck, a single request produces a short podcast, the questions most likely to be asked, and a rehearsal session. | Next | Represented |
| IDEA-03 | Audience versions. The same documents become several versions in one go, for example 5 minutes for leadership and 15 minutes for the field. | Next | Represented |
| IDEA-04 | Written companions. Every session can also produce a summary, FAQ, glossary and flash cards. | Next | Represented |
| IDEA-05 | Ask my library. A question answered across everything the user can access, with sources, without creating audio. | Next | Represented |
| IDEA-06 | Scheduled briefs. A recurring podcast from a folder or group library, such as ten minutes every Monday on what is new. | Later | Represented |
| IDEA-07 | Narrated deck. Export a PowerPoint with the readthrough as narration, or as a video, for places where audio alone does not work. | Later | Represented |
| IDEA-08 | Other languages. Generate the same content in other languages, or translate an existing podcast, with pharma terms kept right. | Later | Represented |
| IDEA-09 | Teams and Outlook. Play and share inside Teams. Get a brief of the documents attached to a meeting invite. | Later | Represented |
| IDEA-10 | Learning paths. Ordered sets of audio and quizzes for onboarding to a brand or therapeutic area, with progress. | Later | Represented |
| IDEA-11 | Service for other apps. Other J&J applications can request audio from documents through an API. | Later | Represented |
| IDEA-12 | Morning brief. A personal playlist each morning of what is new for the user. | Later | Represented |
| IDEA-13 | Panel practice. Role-play with two or three personas at once, such as a leadership panel. | Later | Represented |
| IDEA-14 | Meetings as sources. Use a Teams meeting transcript as a source, for example a five-minute recap of a leadership meeting. | Later | Represented |
| IDEA-15 | Data briefs. Connect a report or dashboard and get a spoken summary of what changed since last time. | Later | Represented |
| LEX-01 | A central lexicon holds terms and their correct pronunciation: brand and generic drug names, molecules, mechanisms, disease areas, trial names, and J&J organization names and acronyms. | Launch | Represented |
| LEX-02 | The lexicon applies to all spoken output: podcasts, readthroughs, Voice AI, spoken answers and the assistant. | Launch | Represented |
| LEX-03 | The same terms are understood when users say them. | Launch | Represented |
| LEX-04 | Terms that look like something else are read correctly. IL-23 is never read as "Illinois 23". | Launch | Represented |
| LEX-05 | Each acronym has a rule: spelled out letter by letter, said as a word, or expanded on first mention. | Launch | Represented |
| LEX-06 | Numbers, units, doses, dates, percentages, ranges and statistical terms are read correctly and the same way every time. | Launch | Represented |
| LEX-07 | When a document contains a term the lexicon does not know, the system makes its best attempt, flags it and queues it for review. | Launch | Represented |
| LEX-08 | Existing J&J lexicons and ontologies from other voice products are the starting point. | Launch | Represented |
| LEX-09 | Admins can add, edit and test entries by listening, and import or export them in bulk. | Launch | Represented |
| LEX-10 | Lexicons by therapeutic area and brand sit on top of a shared core. | Next | Represented |
| LEX-11 | The same abbreviation can be read differently depending on therapeutic area or document. | Next | Represented |
| LEX-12 | Users can add their own terms and pronunciations, applied to their audio right away. | Next | Represented |
| LEX-13 | Users can propose a correction to the shared lexicon while listening. Admins approve, edit or reject. | Next | Represented |
| LEX-14 | A corrected term can be applied to existing audio through Update without redoing the rest. | Next | Represented |
| LEX-15 | The system knows meaning as well as sound: synonyms and brand-to-generic links, so a question about a product finds content under either name. | Next | Represented |
| LEX-16 | A regular report shows the most flagged and most corrected terms. | Next | Represented |
| LIB-01 | Upload one or many files by drag and drop or file picker, from a laptop or a phone. | Launch | Represented |
| LIB-02 | Supported at launch: PowerPoint, PDF, Word, plain text and Markdown. | Launch | Represented |
| LIB-03 | Limits are shown before upload: file size (50 MB in the prototype), pages or slides per file, and files per session. | Launch | Represented |
| LIB-04 | Files that cannot be used get a clear reason: wrong type, password protected, damaged, too large, empty, or no readable content. | Launch | Represented |
| LIB-05 | Each file shows its upload progress. Uploads continue if the user moves elsewhere in the app. | Launch | Represented |
| LIB-06 | Every upload is scanned for malware. | Launch | Represented |
| LIB-07 | Uploads are checked for patient-identifiable and other restricted data, with a warning or a block as policy decides. | Launch | Represented |
| LIB-08 | Excel and CSV files, read as data with sheet names and column headers kept. | Next | Represented |
| LIB-09 | Image files (PNG, JPG) and scanned pages. | Next | Represented |
| LIB-10 | The system warns when the same file already exists and offers to replace it, keep both or cancel. | Next | Represented |
| LIB-11 | Import straight from SharePoint, OneDrive and Teams. | Next | Represented |
| LIB-12 | Import from approved-content systems, so materials arrive with their approval status and expiry date. | Later | Represented |
| LIB-13 | Send a document to Converse AI from email or Teams. | Later | Represented |
| LIB-14 | Scan a paper document with a phone camera. | Later | Represented |
| LIB-15 | Each document is read in full: text, headings, tables, charts, images, speaker notes and footnotes. | Launch | Represented |
| LIB-16 | Image-heavy slides are read with AI OCR. | Launch | Represented |
| LIB-17 | Charts, tables and diagrams are turned into accurate spoken descriptions, with the numbers kept exact. | Launch | Represented |
| LIB-18 | Document structure is kept (sections, slides, pages) so audio can be chaptered and synced to the source. | Launch | Represented |
| LIB-19 | Each document shows its status: uploading, processing, ready or failed. A failed one can be retried. | Launch | Represented |
| LIB-20 | The system writes a title, short description, topics and estimated listening time for each document. Users can edit them. | Launch | Represented |
| LIB-21 | Acronyms and unusual terms found in a document are offered to the user to confirm. Confirmed terms feed the brief and the lexicon. | Next | Represented |
| LIB-22 | Users choose whether speaker notes, hidden slides, appendices and references count as content. Admins set the default. | Next | Represented |
| LIB-23 | Documents are tagged by therapeutic area, brand and function. Tags are suggested by AI and editable. | Next | Represented |
| LIB-24 | Non-English documents are detected and flagged until other languages are supported. | Next | Represented |
| LIB-25 | Views: My documents, Shared with me, each group library, and the company library. | Launch | Represented |
| LIB-26 | Search by name. Filter by type, date and owner. Sort by name, date, size and last used. | Launch | Represented |
| LIB-27 | Select one, several or all documents to use in a session. | Launch | Represented |
| LIB-28 | Preview a document inside the app. | Launch | Represented |
| LIB-29 | Search inside document content. | Next | Represented |
| LIB-30 | Folders, tags and favorites. | Next | Represented |
| LIB-31 | Saved document sets: a named set of documents with its primary document and relationships, for example "Q3 QBR pack", that can be reused. | Next | Represented |
| LIB-32 | A document's detail view shows its description, main terms, versions, who it is shared with and the sessions made from it. | Next | Represented |
| LIB-33 | Rename, edit the description, move and delete. | Launch | Represented |
| LIB-34 | Deleting a document warns about sessions built from it and says what will happen to them. | Launch | Represented |
| LIB-35 | Deleted documents sit in a recycle bin for a set period before they are removed for good. | Next | Represented |
| LIB-36 | Upload a new version of a document. Sessions built on the older version are flagged, with an offer to update them. | Next | Represented |
| LIB-37 | Documents can carry a status (draft, approved, expired) and an expiry date. Expired documents cannot be used for new sessions. | Next | Represented |
| LIB-38 | Download the original file, where policy allows. | Next | Represented |
| LIB-39 | Storage limits per user and per group, with a warning before the limit. | Next | Represented |
| LIB-40 | Documents are private until the owner shares them. | Launch | Represented |
| LIB-41 | Owners can share a document with named people or with groups they belong to. | Launch | Represented |
| LIB-42 | Group owners add documents to their group library. Admins add to any group library and to the company library. | Launch | Represented |
| LIB-43 | Admins and group owners can assign documents to specific users or groups, with a note on what the document is and why it matters. | Launch | Represented |
| LIB-44 | Sensitivity labels on a file are respected. Restricted files can be blocked or limited in how they are shared. | Next | Represented |
| NFR-01 | Devices — Works in current Edge, Chrome and Safari on a laptop, and in mobile browsers on iOS and Android. All launch features work on both. | Launch | Represented |
| NFR-02 | Scale — Supports 50 or more users and 100 or more uploaded files at launch, with a clear path to grow. | Launch | Represented |
| NFR-03 | Voice response — The agent and the assistant start replying fast enough to feel like a conversation. Target to confirm: about one second. | Launch | Represented |
| NFR-04 | Generation time — Targets are set per format and length from pilot measurements and shown to users as estimates. | Launch | Represented |
| NFR-05 | Processing time — A typical deck or report is ready to use within a few minutes of upload. Target to confirm. | Launch | Represented |
| NFR-06 | Concurrency — Several users can generate and hold live conversations at the same time without slowing each other down. Target to confirm. | Launch | Represented |
| NFR-07 | No lost work — Uploads, drafts, briefs and generations survive a refresh, a sign-out and a dropped connection. | Launch | Represented |
| NFR-08 | States — Every empty, loading and error state says what is happening and what to do next. | Launch | Represented |
| NFR-09 | Microphone — Microphone permission is requested clearly, and the product explains what to do when it is blocked. | Launch | Represented |
| NFR-10 | Accessibility — Meets WCAG 2.1 AA: keyboard use, screen readers, captions and contrast. | Launch | Represented |
| NFR-11 | Security — Single sign-on, role-based access, encryption, and a security test before launch. | Launch | Represented |
| NFR-12 | Availability — The availability target and maintenance windows are agreed with IT. Planned downtime is announced in the app. | Launch | Represented |
| NFR-13 | Monitoring — Every generation and conversation can be traced end to end. Errors are logged with enough detail to fix them. | Launch | Represented |
| NFR-14 | Cost tracking — Usage and cost are tracked per user and per group. | Launch | Represented |
| NFR-15 | Backup — Documents and sessions are backed up, with recovery targets agreed with IT. | Launch | Represented |
| NFR-16 | Languages — English at launch. The design allows more languages later. | Launch | Represented |
| NOT-01 | A generation finished or failed. | Launch | Represented |
| NOT-02 | A document finished processing or failed. | Launch | Represented |
| NOT-03 | Something was shared with the user or published to one of their groups. | Launch | Represented |
| NOT-04 | Notifications are collected in one place in the app, with read and unread states. | Launch | Represented |
| NOT-05 | Email and Teams notifications, by user choice. | Next | Represented |
| NOT-06 | A source document behind the user's output has a new version or has expired. | Next | Represented |
| NOT-07 | A shared output the user listens to was updated. | Next | Represented |
| NOT-08 | A group request, prompt proposal or lexicon suggestion was answered. | Next | Represented |
| NOT-09 | A storage or generation limit is close, or content is about to expire. | Next | Represented |
| NOT-10 | An optional weekly digest of what is new in the user's groups. | Later | Represented |
| PLY-01 | Play, pause, scrub, skip back and forward 15 seconds, and change speed and volume. | Launch | Represented |
| PLY-02 | See chapters and jump between them. | Launch | Represented |
| PLY-03 | Resume where the user left off, on any device. | Launch | Represented |
| PLY-04 | On a phone, audio keeps playing in the background and with the screen locked, with lock-screen and headset controls. | Launch | Represented |
| PLY-05 | Line up several sessions to play one after another. | Next | Represented |
| PLY-06 | Mark a session as finished. Listening progress shows in history. | Next | Represented |
| PLY-07 | Download for offline listening on a phone, where policy allows. | Later | Represented |
| PLY-08 | A synced transcript shows speaker names and highlights the current line. Selecting a line jumps the audio there. | Launch | Represented |
| PLY-09 | Search inside the transcript. | Next | Represented |
| PLY-10 | Text size and contrast options. | Next | Represented |
| PLY-11 | The source can be shown or hidden next to the transcript. | Launch | Represented |
| PLY-12 | The source follows the audio: the right slide or page is shown and the passage being spoken is highlighted. | Launch | Represented |
| PLY-13 | The user can browse the source freely while audio continues, then return to the current point. | Launch | Represented |
| PLY-14 | From any slide or page, the user can jump to where it is discussed in the audio. | Launch | Represented |
| PLY-15 | With several documents, the view shows which document the current segment comes from. | Launch | Represented |
| PLY-16 | The source shown is always the real document the session was built from. | Launch | Represented |
| PLY-17 | The full document can be opened from the source view. | Next | Represented |
| PLY-18 | The user can ask a question at any moment by voice or typing. Playback pauses and resumes afterward. | Launch | Represented |
| PLY-19 | Answers come from the session's documents, in text and speech, and point to the slide or page. | Launch | Represented |
| PLY-20 | Follow-up questions keep their context. | Launch | Represented |
| PLY-21 | If the answer is not in the documents, the product says so. | Launch | Represented |
| PLY-22 | Questions and answers are saved with the session. | Launch | Represented |
| PLY-23 | The user can widen a question to other documents they have access to. | Next | Represented |
| PLY-24 | Suggested questions appear based on the current point in the audio. | Next | Represented |
| PLY-25 | Shortcuts work by voice or typing: explain that again more simply, give an example, skip to the part about pricing. | Next | Represented |
| PLY-26 | A question can turn into a full Voice AI conversation with the context carried over. | Next | Represented |
| PLY-27 | Rate a session with a thumbs up or down. | Launch | Represented |
| PLY-28 | Report a problem at a specific moment: wrong fact, mispronounced term, missing content, tone or audio glitch. | Launch | Represented |
| PLY-29 | Bookmark a moment and add a note. See all bookmarks and notes for a session. | Next | Represented |
| PLY-30 | Fix a pronunciation on the spot: flag the word, say or type how it should sound, and hear a preview. | Next | Represented |
| PLY-31 | Each podcast and readthrough comes with written takeaways. | Next | Represented |
| PLY-32 | A short knowledge check of three to five questions is offered after listening. | Next | Represented |
| PLY-33 | Export the audio, transcript and takeaways, where policy allows. | Next | Represented |
| PLY-34 | Share a clip or a moment with a colleague who has access. | Later | Represented |
| POD-01 | One, two or three hosts, chosen from the approved voices. | Launch | Represented |
| POD-02 | Tone comes from the shared list. The three styles already sampled with stakeholders (direct, balanced, conversational) must all be available. | Launch | Represented |
| POD-03 | The user sets a length target in minutes, and the podcast lands close to it. | Launch | Represented |
| POD-04 | With several documents, the podcast connects them as the brief describes and makes clear which document each point comes from. | Launch | Represented |
| POD-05 | Numbers, names, dates and quotes are stated exactly as in the source. | Launch | Represented |
| POD-06 | Hosts do not add opinions or claims that are not in the documents. | Launch | Represented |
| POD-07 | Every segment is linked to the slide or page it came from. | Launch | Represented |
| POD-08 | AI writes the title, a short description and chapter titles. All are editable. | Launch | Represented |
| POD-09 | The output includes audio, a synced transcript with speaker names, chapters and source references. | Launch | Represented |
| POD-10 | Host names in the transcript match the voices the user chose. | Launch | Represented |
| POD-11 | Each host can have a role: lead host, co-host, expert or challenger. | Next | Represented |
| POD-12 | Discussion formats beyond the default: interview, debate and teaching. In a debate, both sides come from the documents. | Next | Represented |
| POD-13 | Structure options the user can turn on or off: opening summary, chapters by topic, recap of takeaways, closing. | Next | Represented |
| POD-14 | The user can review and edit the outline or script before the audio is made. | Next | Represented |
| POD-15 | A 30-second sample with the chosen voices and tone can be played before the full run. | Next | Represented |
| POD-16 | A podcast can belong to a series with the same hosts and intro each time. | Later | Represented |
| POD-17 | Hosts can take a listener's question and answer it as part of the show. | Later | Represented |
| PRM-01 | Two shelves at launch: My prompts, and Common prompts curated by admins. | Launch | Represented |
| PRM-02 | A prompt is a saved brief with a name, description, format, default settings, suggested document types and tags. It can contain blanks to fill in, such as audience, brand or meeting name. | Launch | Represented |
| PRM-03 | Users can browse, search and filter prompts by format and use case. | Launch | Represented |
| PRM-04 | To use a prompt, the user picks it, picks documents, fills the blanks, reviews the brief and generates. | Launch | Represented |
| PRM-05 | Any brief can be saved as a prompt. Users can edit, duplicate, rename and delete their own prompts. | Launch | Represented |
| PRM-06 | A starter set of common prompts is ready at launch. | Launch | Represented |
| PRM-07 | A third shelf for group prompts. Users can share a prompt with people or groups, and group owners can pin prompts for their group. | Next | Represented |
| PRM-08 | Users can propose a prompt for the common shelf. Admins review and publish. | Next | Represented |
| PRM-09 | Each common prompt has a short audio sample of what it produces. | Next | Represented |
| PRM-10 | Prompts show how often they are used and how users rate them. | Next | Represented |
| PRM-11 | Admins can lock parts of a common prompt, such as compliance wording. | Next | Represented |
| PRM-12 | Prompts are versioned, and each output records the version it used. | Next | Represented |
| PRM-13 | Prompts are suggested based on the documents selected. | Next | Represented |
| PRM-14 | The library also holds quiz templates, role-play scenarios, personas and question sets. | Next | Represented |
| PRM-15 | Admins can retire prompts, limit a prompt to certain groups and see usage. | Next | Represented |
| SES-01 | Podcasts, readthroughs and Voice AI conversations are saved without the user doing anything. | Launch | Represented |
| SES-02 | History can be filtered by format, with a count for each. | Launch | Represented |
| SES-03 | Each entry shows an AI-written title and description (both editable), the format, date, length and source documents. | Launch | Represented |
| SES-04 | Titles, descriptions and listed sources always match the real content. | Launch | Represented |
| SES-05 | Any session can be reopened to play it, read the transcript, and see its sources, questions asked, recap, quiz results, brief and versions. | Launch | Represented |
| SES-06 | Sessions can be renamed and deleted. | Launch | Represented |
| SES-07 | A new session can be started from an old one's documents and brief. | Launch | Represented |
| SES-08 | Generations that are in progress or failed appear in history with their status. | Launch | Represented |
| SES-09 | Search by title. | Launch | Represented |
| SES-10 | Search inside transcripts. Filter by date, document, tag, owner and whether it was shared. | Next | Represented |
| SES-11 | Entries show listening progress and the current version. | Next | Represented |
| SES-12 | Tags, favorites, folders and playlists for organizing sessions. | Next | Represented |
| SES-13 | Drafts and saved assistant conversations appear in history. | Next | Represented |
| SES-14 | Deleted sessions sit in a recycle bin for a set period. | Next | Represented |
| SES-15 | Sessions are kept for the period policy sets. Users see when something is due to expire. | Next | Represented |
| SET-01 | A short set of questions captures what the user is trying to achieve. Questions adapt to the format and skip anything already known. | Launch | Represented |
| SET-02 | Questions cover purpose, audience and what they already know, depth, the primary document and how the others relate, what to focus on, what to leave out, and acronyms or prior context. | Launch | Represented |
| SET-03 | Each question can be answered by picking an option, typing or speaking. | Launch | Represented |
| SET-04 | One document can be marked as primary with the rest as support, or all can be treated equally. | Launch | Represented |
| SET-05 | Users can skip the questions and go straight to a recommended brief. | Launch | Represented |
| SET-06 | Answers are kept if the user goes back or switches route. | Launch | Represented |
| SET-07 | AI fills in answers it can work out from the documents and the user's profile, marked as suggestions. | Next | Represented |
| SET-08 | Users can exclude sections, pages or slides of a document. | Next | Represented |
| SET-09 | A setup can be saved as a draft and finished later. | Next | Represented |
| SET-10 | One action asks AI to recommend the whole setup from the selected documents: format, primary document, depth, length, tone, voices and focus areas. | Launch | Represented |
| SET-11 | Each recommendation comes with a one-line reason. | Launch | Represented |
| SET-12 | Users can accept all of it, change any part, or ask for a different recommendation. | Launch | Represented |
| SET-13 | With nothing selected, it recommends what to create from the user's library: which documents go together and why. | Next | Represented |
| SET-14 | Recommendations take the user's role, groups and past choices into account. | Next | Represented |
| SET-15 | It can point to a matching prompt in the prompt library. | Next | Represented |
| SET-16 | From the answers or the recommendation, AI writes a brief in plain language. Every brief uses the same sections, so outputs are consistent from one user to the next. | Launch | Represented |
| SET-17 | Users can edit any editable section by typing, or by telling the assistant what to change. | Launch | Represented |
| SET-18 | Quick controls (tone, length, depth, voices) and the brief text stay in step. Changing one updates the other. | Launch | Represented |
| SET-19 | The system checks an edited brief for conflicts, such as "5 minutes" with "cover every section in depth", and for requests it will not follow. It tells the user before generating. | Launch | Represented |
| SET-20 | The brief shows the expected length of the output and how long generation will take. | Launch | Represented |
| SET-21 | Rules for grounding and compliance always apply. Users can read them but cannot edit or remove them. | Launch | Represented |
| SET-22 | A brief can be saved to the prompt library, and a setup can start from a saved or common prompt instead of the questions. | Launch | Represented |
| SET-23 | The brief used for an output is stored with it and can be viewed and reused. | Launch | Represented |
| SET-24 | Users can reset to the AI-written version and see what they changed. | Next | Represented |
| SET-25 | One tone list is used everywhere: in setup, in Update and by the assistant. | Launch | Represented |
| SET-26 | Length is offered as presets with the minutes shown, plus a custom target. | Launch | Represented |
| SET-27 | Depth uses the same three levels in every format: Quick overview, In-depth, Expert. | Launch | Represented |
| SET-28 | Voices are picked from an approved list, each with a short audio preview. | Launch | Represented |
| SET-29 | The user's saved defaults are applied to every new setup. | Next | Represented |
| SET-30 | Output language can be chosen. English only at launch. | Later | Represented |
| SHR-01 | A podcast or readthrough can be shared with named people or with groups. | Launch | Represented |
| SHR-02 | Group owners and admins can publish audio to a group. It appears on members' landing pages and in the group library. | Launch | Represented |
| SHR-03 | A link to a session can be shared in Teams or email. It opens only for people with access. | Launch | Represented |
| SHR-04 | Shared items show who shared them, when, and which documents they came from. | Launch | Represented |
| SHR-05 | The owner can stop sharing at any time, and access ends right away. | Launch | Represented |
| SHR-06 | Voice AI conversations are private to the user. They are never shared automatically. | Launch | Represented |
| SHR-07 | Nothing can be shared outside J&J, and there are no public links. | Launch | Represented |
| SHR-08 | Permission levels: listen only, listen and update, or listen and share onward. | Next | Represented |
| SHR-09 | Playlists and series: ordered sets of sessions, such as onboarding to a brand in five episodes. | Next | Represented |
| SHR-10 | Users can follow a playlist or group and are told when something new is added. | Next | Represented |
| SHR-11 | A setup can be shared without its output: a brief, a quiz or a role-play scenario that colleagues run themselves. | Next | Represented |
| SHR-12 | Owners of published audio see listens, completion, where people stop and the questions asked most often. | Next | Represented |
| SHR-13 | A user can choose to share the recap of a Voice AI conversation. | Next | Represented |
| SHR-14 | A group owner can mark a session as recommended or required for a group and see who has listened. | Later | Represented |
| SHR-15 | Comments and reactions on shared sessions. | Later | Represented |
| TRU-01 | Every statement in an output or answer traces to a passage in the source documents. There is no open internet and no added general knowledge. | Launch | Represented |
| TRU-02 | Each output stores its sources and their versions, the brief, the model and voice versions, the check results, and who created and updated it. | Launch | Represented |
| TRU-03 | When something is not covered by the documents, the product says so plainly. | Launch | Represented |
| TRU-04 | Every output and conversation is labeled as AI-generated. Shared audio also carries an internal-use notice. | Launch | Represented |
| TRU-05 | J&J Gen AI guardrails apply to what goes in and what comes out: uploads, briefs, questions, live conversation and generated audio. | Launch | Represented |
| TRU-06 | Protected content, such as safety information and required disclaimers, is never summarized, shortened or dropped in any format. | Launch | Represented |
| TRU-07 | Uploads and conversations are checked for patient-identifiable and other restricted data. | Launch | Represented |
| TRU-08 | Documents, transcripts, audio, prompts and logs stay in the J&J Azure tenant. Models run through Azure services in the tenant, and nothing is used to train models. | Launch | Represented |
| TRU-09 | Data is encrypted in transit and at rest. | Launch | Represented |
| TRU-10 | Access rules are enforced on every request, not only in the interface. | Launch | Represented |
| TRU-11 | A user's voice audio is not kept after it is transcribed, unless policy says otherwise and the user is told before the session. | Launch | Represented |
| TRU-12 | The intended use is stated in the product, with the uses that are out of scope named. | Launch | Represented |
| TRU-13 | Voices are approved synthetic voices. No real person's voice is imitated. | Launch | Represented |
| TRU-14 | Retention periods are set per content type. Deleting a document or session also removes its transcripts, audio and search entries. | Launch | Represented |
| TRU-15 | Guardrail triggers, failed checks and reported problems are logged and reviewed on a regular schedule. | Launch | Represented |
| TRU-16 | Before any model, voice or lexicon change is released, it is tested against a fixed set of reference documents for grounding, pronunciation and quality. | Launch | Represented |
| TRU-17 | Content published to groups above a set size needs a named reviewer. | Next | Represented |
| UPD-01 | When a session ends, the user is offered next steps that fit the format: update, start over, switch format, share or finish. | Launch | Represented |
| UPD-02 | Update accepts corrections and additions to an existing podcast or readthrough: missed content, wrong emphasis, wrong facts, things to remove, tone, length, voices and pronunciation. | Launch | Represented |
| UPD-03 | The user gives the changes by typing or speaking, in their own words. | Launch | Represented |
| UPD-04 | The user can add or remove source documents as part of an update and change which one is primary. | Launch | Represented |
| UPD-05 | The existing script is the starting point. Parts the user did not ask to change stay word for word. | Launch | Represented |
| UPD-06 | Before anything is redone, the system lists the changes it will make, what stays the same and the new expected length, then asks for a go-ahead. | Launch | Represented |
| UPD-07 | Update offers the same tones, lengths and voices as the original setup, with the current choices already selected. | Launch | Represented |
| UPD-08 | Every update creates a new version. Earlier versions stay available to play and restore. | Launch | Represented |
| UPD-09 | Version history shows who changed what, when, and the request behind it. | Launch | Represented |
| UPD-10 | Start over creates a fresh version from the same documents with a different angle, and is labeled as such. | Launch | Represented |
| UPD-11 | Switch format: create a podcast, readthrough or Voice AI session from the same documents, with the brief and context carried over. | Launch | Represented |
| UPD-12 | For Voice AI, the equivalent is restarting the conversation with a different tone, persona or scenario. | Launch | Represented |
| UPD-13 | The user can point at a transcript line, chapter or timestamp so a change applies to that exact place. | Next | Represented |
| UPD-14 | Only the changed segments are recorded again. The rest of the audio is untouched. | Next | Represented |
| UPD-15 | Problems reported while listening are carried into the update automatically. | Next | Represented |
| UPD-16 | The user can edit the script of a segment directly, or delete and reorder segments, and have only those recorded again. | Next | Represented |
| UPD-17 | Two versions can be compared side by side. | Next | Represented |
| UPD-18 | Make a variant: copy an output and change it, for example a 5-minute version for leadership, without touching the original. | Next | Represented |
| UPD-19 | When a source document gets a new version, the owner of any output built from it is told and can update in one action. | Next | Represented |
| UPD-20 | When a shared output is updated, the people it was shared with get the new version and are told it changed. | Next | Represented |
| USR-01 | Profile: name, role, function and therapeutic area, taken from the directory where possible. | Launch | Represented |
| USR-02 | Groups: the groups the user is in, who owns each, and what each gives access to. | Launch | Represented |
| USR-03 | Assistant and audio: spoken replies on or off, and microphone and speaker choice. | Launch | Represented |
| USR-04 | Privacy: what is stored about the user, the retention periods, and a way to delete their own data. | Launch | Represented |
| USR-05 | Help: replay the tour, short guides, contact support and send product feedback. | Launch | Represented |
| USR-06 | Defaults: opening route, format, length, tone, depth, voices and playback speed. They apply to every new setup and can be changed each time. | Next | Represented |
| USR-07 | My context: standing notes applied to every brief, such as "I already know the brand basics" or "always end with three takeaways". | Next | Represented |
| USR-08 | My terms: personal acronyms and pronunciations. | Next | Represented |
| USR-09 | Notifications: what to be told about and where. | Next | Represented |
| USR-10 | Display: light or dark, text size, reduced motion, and captions always on. | Next | Represented |
| USR-11 | Requests to join or leave a group. | Next | Represented |
| USR-12 | Language of the interface and the audio. | Later | Represented |
| VAI-01 | Discuss: an open back-and-forth about the documents. | Launch | Represented |
| VAI-02 | Quiz me: the agent tests the user on the documents. | Launch | Represented |
| VAI-03 | Role-play: the agent plays a named persona in a scenario, such as a skeptical investor. | Launch | Represented |
| VAI-04 | Read and ask: the agent reads sections aloud on request and answers questions about them. | Launch | Represented |
| VAI-05 | Setup uses the same goal questions and brief as the other formats, with Voice AI options: session type, primary document, tone, agent voice and persona, the user's role, difficulty and an optional time limit. | Launch | Represented |
| VAI-06 | For a scenario, the user gives a line or two by typing or speaking. AI writes the full scenario: who the agent is, what they care about, how tough they are, and what a good outcome looks like. The user can edit it before starting. | Launch | Represented |
| VAI-07 | There is no fixed length. The user can set a time limit and gets a warning before it ends. | Launch | Represented |
| VAI-08 | Rehearse: the user presents, and the agent listens, asks questions like a real audience and gives feedback. | Next | Represented |
| VAI-09 | Reusable personas and scenarios, managed by admins, with users able to save their own. | Next | Represented |
| VAI-10 | Before starting: microphone permission, choice of microphone and speaker, and a quick sound check. | Launch | Represented |
| VAI-11 | Clear states: connecting, live, reconnecting and ended, with a timer. | Launch | Represented |
| VAI-12 | Turn-taking feels natural, with a short delay, and the user can interrupt the agent mid-sentence. | Launch | Represented |
| VAI-13 | Mute and end are always available. | Launch | Represented |
| VAI-14 | The agent opens by saying which documents it has and offering places to start. | Launch | Represented |
| VAI-15 | A live transcript shows both sides. Names match the scenario, not a fixed label such as "Customer". | Launch | Represented |
| VAI-16 | The agent has one name and one voice, the same on screen, in the transcript and in the audio. | Launch | Represented |
| VAI-17 | Answers come only from the selected documents. The agent says so when something is not covered and steers off-topic requests back. | Launch | Represented |
| VAI-18 | The agent understands pharma terms when the user says them. | Launch | Represented |
| VAI-19 | If the connection drops, the conversation reconnects and continues with its context. | Launch | Represented |
| VAI-20 | If the user goes quiet, the agent checks in, then ends and saves the conversation. | Launch | Represented |
| VAI-21 | There is one clear way to finish, and it leads to the recap. | Launch | Represented |
| VAI-22 | The user can pause and resume, use push-to-talk in noisy places, or type instead of speaking. | Next | Represented |
| VAI-23 | While the agent speaks, the slide or page it is drawing on is shown and can be opened. | Next | Represented |
| VAI-24 | Spoken commands work during a session: repeat, slow down, explain more simply, go deeper, read a section, switch to a quiz. | Next | Represented |
| VAI-25 | The agent can offer to bring in another document the user has access to. | Next | Represented |
| VAI-26 | The user sets up a quiz with: documents and sections to cover, topics to focus on, number of questions or time available, difficulty, question style and whether hints are allowed. | Launch | Represented |
| VAI-27 | AI writes the quiz plan from those inputs and the documents. The user can read and edit it before starting. | Launch | Represented |
| VAI-28 | The user can ask for a revision first: the agent walks through the main points before asking questions. | Launch | Represented |
| VAI-29 | The agent asks one question at a time aloud, and the user answers aloud. | Launch | Represented |
| VAI-30 | The agent checks each answer against the documents, says what was right and what was missing, gives the correct answer and points to the slide or page. | Launch | Represented |
| VAI-31 | The user can ask for a hint or a repeat, skip a question, or come back to it. | Launch | Represented |
| VAI-32 | The user can ask their own questions during the quiz and after it. The agent answers from the documents, then returns to the quiz. | Launch | Represented |
| VAI-33 | Results show the score, strengths, gaps, and each question with the user's answer, the correct answer and the source. | Launch | Represented |
| VAI-34 | Results recommend what to do next: sections to revisit or audio to listen to again. | Launch | Represented |
| VAI-35 | Difficulty adapts to how the user is doing. | Next | Represented |
| VAI-36 | The user can retake only the questions they missed. | Next | Represented |
| VAI-37 | Progress across quizzes on the same documents is tracked over time. | Next | Represented |
| VAI-38 | Group owners can assign a quiz and see completion and scores. | Later | Represented |
| VAI-39 | A tap-to-answer quiz as an alternative to voice. | Later | Represented |
| VAI-40 | In a role-play the agent stays in character and pushes back as hard as the scenario says, while taking every fact from the documents. | Launch | Represented |
| VAI-41 | After a role-play or rehearsal the user gets feedback: what landed, what was missed against the documents, where they struggled, and suggestions. | Next | Represented |
| VAI-42 | Rehearsal feedback also covers accuracy, clarity, pace and time used. | Next | Represented |
| VAI-43 | A recap covers what was discussed, the main points, open questions and actions. | Launch | Represented |
| VAI-44 | The recap lists context to add next time: documents or information that would have made the answers sharper. | Launch | Represented |
| VAI-45 | The full transcript is saved with the session. | Launch | Represented |
| VAI-46 | The user can restart with a different tone, persona or scenario. | Launch | Represented |
| VAI-47 | The user can create a podcast or readthrough from the same documents. | Launch | Represented |
| VAI-48 | The user can pick a conversation back up later with its history. | Next | Represented |
| VAI-49 | The recap can be exported as a written note. | Next | Represented |
| SRC-01 | A user can add documents directly during Podcast, Audio Readthrough, or Voice AI setup without first visiting the document library. | Launch | Represented |
| SRC-02 | A user can explain how each selected document should contribute as a lead, supporting, reference, or equally weighted source. | Launch | Represented |
| SRC-03 | A user can preview available pages or slides, mark them essential, useful, or excluded, and add page-specific guidance. | Launch | Represented |
| SRC-04 | Source direction offers both a quick high-level instruction and a detailed per-document workflow without removing later setup questions. | Launch | Represented |
| PLY-25 | The listening workspace provides a persistent microphone action that pauses audio, answers from the current session, and can continue into Voice AI with the same context. | Launch | Represented |
| EXP-01 | The application uses a restrained J&J red visual system with neutral surfaces and Johnson Display and Johnson Text typography when licensed font files are available. | Launch | Represented |
| EXP-02 | The leadership home presents Podcast, Audio Readthrough, and Voice AI with equal prominence and does not repeat a separate Voice AI promotion. | Launch | Represented |
| EXP-03 | Sessions, playlists, and saved prompts are consolidated under My work while remaining directly accessible as separate views. | Launch | Represented |
| EXP-04 | Podcast, Audio Readthrough, Voice AI, Assistant, playback, and update workflows share one coherent executive interaction and selection language. | Launch | Represented |
| EXP-05 | The leadership home uses a connected source-to-format infographic to explain how one trusted source becomes Podcast, Audio Readthrough, or Voice AI without displacing the primary Ask or Speak action. | Launch | Represented |
| EXP-06 | Every screen uses the same Johnson typography hierarchy, restrained J&J red semantic palette, neutral panels, icon treatment, and control language. | Launch | Represented |
| EXP-07 | The leadership home and primary creation, listening, and Voice AI workflows remain legible and usable across desktop and mobile layouts. | Launch | Represented |
| EXP-08 | The complete leadership landing workspace fits within a standard desktop viewport while preserving a comfortable, scrollable mobile presentation. | Launch | Represented |
| EXP-09 | Podcast, Audio Readthrough, and Voice AI use one responsive three-stage guided workspace with Sources, Configure, and Preview without a repetitive live summary. | Launch | Represented |
| EXP-10 | Creation settings are captured once and reused across the editable intent, format controls, review, and cross-format continuation without duplicate confirmation. | Launch | Represented |
| EXP-11 | The application uses a dark-purple navigation shell with J&J red actions, paper surfaces, restrained tinted panels, DM Serif Display headings, and Fira Sans interface text. | Launch | Represented |
| EXP-12 | The landing continuation area remains visible and stable at normal zoom without experience cards stretching into or clipping the section. | Launch | Represented |
| EXP-13 | The supplied Johnson & Johnson logos identify expanded, collapsed, and mobile navigation while ConverseAI appears in the global page header with Converse in J&J red and AI in bold black. | Launch | Represented |
| EXP-14 | Creation captures each intent and format decision once while retaining every advanced Podcast, Audio Readthrough, and Voice AI control. | Launch | Represented |
| EXP-15 | High-value actions and scannable information use consistent semantic icons across every application page. | Launch | Represented |
Showing 460 records. Duplicate IDs preserve repeated requirements from the source appendix.