A Work Session is not another installation
Work Sessions are task chats inside the same installed Project. They give a piece of work a clear scope; they are not separate products and do not require another installation or another installer paste just to start a session.
Use the Work Session instructions delivered with your product for exact procedures. Public Academy guidance does not reproduce proprietary session commands, workspace-state structures or recovery instructions.
Prepare the next piece of work
Confirm that you are in the correct installed Project and identify the task, relevant current sources and desired result. Keep unrelated communities, clients or operational scopes from being mixed. Supply only information you are authorized to use.
Before relying on earlier work, check the confirmed facts and relevant references available to this session. Being in the same Project is useful organization, not a guarantee that every previous detail will be used correctly.
- State the immediate task and what is outside it.
- Identify current source versions and approved decisions.
- Keep unresolved items visibly unresolved.
- Choose the required review point before sending or changing anything.
Work in steps and close with a review
For a large task, review extracted facts before moving to a draft or plan. Verify dates, ownership, commitments and missing information. Follow your product's closeout guidance and retain official records in the appropriate system of record.
A useful human-reviewed closeout distinguishes completed work, confirmed decisions, open questions and next actions. Do not allow a suggested action to become a completed action in the record simply because it appeared in a generated summary.
Try it thoughtfully
Using fictional notes, create a brief task list, review it, and make a closeout note. Check that suggested actions are not labeled completed and unstated owners stay unconfirmed.
If a session becomes unreliable
Stop if the assistant starts using an old source, losing important constraints or guessing workspace details. Save the relevant state and follow the product's recovery instructions. Do not solve it by loading another edition, reinstalling repeatedly or creating a duplicate workspace.
If a new task chat is appropriate, use a reviewed handoff and verify the important sources and facts. There is no guarantee of complete cross-chat recall. Archiving or deleting chats is not a reliable inference-speed fix.
Continue learning
- Getting started with your purchased Ginny product
- Context and memory: what continuity really requires
- Workflow habits that make AI assistance repeatable
Product-specific instructions take precedence over general education. Installation materials stay in your protected customer library.
Customer setup and product materials require sign-in.