What the documents look like
Franchisee training and opening coaching transfer operating capability. This work differs from franchise filing and disclosure, which is a legal filing activity. The material for this page comes from a training system, a supervisor app, store photographs and a headquarters SOP library. Day-to-day documents include training sign-in sheets, opening checklists, SOP manuals and assessment scores. These materials update per store, per month, and they form the evidence chain through which a regional supervisor hands operating capability to a franchisee owner.
The conversation logs and audit step handles dialogue records, run details and feedback data produced during training and coaching. Whether such data can support a handover depends on whether identity fields, session ownership and run details can be checked against each other. The existence of a log does not by itself settle that question.
Constraints at the conversation logs step
Session ownership is distinguished by chatId. Under one application, different chatId values represent different sessions. A dialogue record is located through dataId. Run details require detail=true on the chat interface, after which they are read from responseData. With detail=false, only the final answer returns and intermediate module state does not appear. With detail=true and stream=false, responseData holds moduleName, moduleType, runningTime and tokens for each module. With stream=true, the same content travels through event=flowResponses.
authProxy proxies a team member identity. The team owner must enable it when creating or editing the key, and the proxied identity still needs permission for the target application and session. A retrieval similarity score reflects textual similarity only. It does not perform business entity isolation or permission filtering. Log retention does not equal completed compliance audit. Reconciliation and compliance requirements are carried out separately by a full business plan.
Hypothetical drill sample: a chain brand training department creates an opening coaching dialogue application for a new franchise store in East China, "Sample Store A". On 10 March 2025, a regional supervisor submits a handover request with the draft sentence "Cashier training at Sample Store A is complete and opening can be handed over." The source material provided for checking reads as follows. The training sign-in sheet records that on 8 March 2025, four people attended cashier training, and the sign-in column holds three signatures. The assessment score sheet shows three people passed for that role and one was absent. The opening checklist cashier module status column reads "pending review". The authorization boundary for this request is: the regional supervisor may submit a handover application; handover confirmation requires joint signature by the training department and the operations department; this request has not yet obtained signature.
Configuration and implementation checks
| Check item | Value or action relevant to this page | Basis for judgement |
|---|---|---|
| Session identifier | Record appId and chatId, verify the target dialogue belongs to the intended session | Under one chatId, dataId is unique |
| Run details | Set detail=true on the chat interface, read module fields from responseData | detail=false returns no intermediate state |
| Identity proxy | Verify whether authProxy was enabled by the team owner | A proxied identity still needs target application and session permission |
| Feedback data | Read userGoodFeedback or userBadFeedback by dataId | Omit the corresponding parameter to cancel |
| Retrieval score | Record the similarity number as a textual similarity reference only | The score performs no permission or entity filtering |
| Hypothetical starting value | Set the similarity reference value to 0.80 for this paper comparison | Chosen to separate high-similarity from low-similarity entries, and compared against actual returned scores such as 0.61 in the sample |
Three common errors
- Treating a detail=false response as a complete run record. That mode returns only the final answer; module state and tokens do not appear. The check is to confirm the actual value of detail in the request parameters, then inspect whether responseData is present in the returned structure.
- Using the similarity score to decide whether a session may be accessed. The score reflects textual similarity only; permission is decided by authProxy and target application session permission. The check is to inspect the identity configuration and the score value separately, without merging the two into one judgement.
- Reading an opening checklist with pending-review status as complete. In the sample, the cashier module status is "pending review" while the draft sentence states training is complete and handover can proceed. The check is to compare the checklist status column against the wording of the draft sentence field by field. Until the status changes to passed, the handover request lacks support.
How to verify the setup
- Input the draft sentence from the sample, "Cashier training at Sample Store A is complete and opening can be handed over." Compare it against the training sign-in sheet with three signatures out of four attendees, the assessment score sheet with one absence, and the opening checklist status "pending review". The draft sentence gains support only when sign-in, assessment and checklist all show completion. At present two of the three are not closed, so the draft sentence is not supported.
- Input a chat interface request with detail set to true and stream set to false. Compare whether the returned structure contains a responseData array and whether its elements carry moduleName, moduleType and runningTime. When responseData is present and holds the expected modules, run details can be read. If detail is false, responseData does not appear and run details remain unknown.
- Input the regional supervisor's handover request from the sample. Compare the signature requirement stated in the authorization boundary against the current signature record. Handover confirmation holds when both the training department and the operations department signatures are present. At present only the submission action exists, the signature record is missing, and handover confirmation does not hold; the item remains pending verification.