What the documents look like
Chain-store closure settlement runs in the opposite direction from site selection and store opening. It handles exit and asset recovery. The main data sources are POS inventory, the fixed-asset system, lease contracts and financial ledgers. The documents handled day to day are closure approvals, inventory clearance forms, lease termination agreements and asset count sheets. Updates are irregular and handled per store.
For contract and transaction material comparison, these features mean that the same store's exit status has to be checked across sources, while the materials sit in different systems with different access scopes. A lease termination agreement may state a signing date and a deposit-refund condition. An asset count sheet may state a count completion date and carry a blank confirmation field. The comparison task reads these materials together, so the access boundary decides which reviewer can see which document at all.
Constraints at the access controls step
Knowledge base permission is the threshold. Collection permission cannot bypass knowledge base permission. File-level permission is off by default. In the off state, collection readability matches the knowledge base and the system does not query any collection permission records. After it is switched on, each file or folder generates a complete permission snapshot, and the list, the detail view and retrieval recall are each authorized against that snapshot item by item.
Retrieval recall filters by the files readable by the current member only when authorization runs by current member identity. A workflow that preselects a knowledge base without member-identity authorization does not apply file-level filtering and still recalls by knowledge base permission. A relevance score is not a category, entity or permission filter. Retrieval is not authorization.
Hypothetical drill sample: an operations staff member for the East China region of a chain brand submits a closure material comparison request. The material text reads: "The store A lease termination agreement states that both parties signed on 10 March 2025, and the deposit refund clause is conditional on the asset count sheet being confirmed by the landlord. The store A asset count sheet states that counting was completed on 5 March 2025, and the confirmation status field is blank." The draft sentence reads: "The deposit refund condition for store A is satisfied and a refund can be initiated." The request covers two materials, the lease termination agreement and the asset count sheet, and requires checking three facts: signing, count confirmation and the refund condition.
Configuration and implementation checks
| Configuration item | Hypothetical starting value for this trial | Reason for the choice and comparison method |
|---|---|---|
| Knowledge base file-level permission switch | Off | This sample covers two materials only; in the off state authorization follows knowledge base permission. Compare list filtering behaviour against the on state. |
| Manageable role on the knowledge base holding the materials | Operations supervisor | Knowledge base manageable permission is required to switch file-level permission on. Compare visibility of the configuration entry against an ordinary member account. |
| Collection-level collaborator for the closure materials | Operations staff read permission | The comparison request only needs to read the materials. Compare permitted modification actions against a write-permission account. |
| Retrieval recall authorization mode | By current member identity | A workflow that preselects a knowledge base does not apply file-level filtering. Compare recall scope against the preselected scenario. |
| Account initiating the comparison request | Operations staff account | Verify the union effect of knowledge base read permission and collection read permission. Compare visible content against an account without permission. |
| Retention of the material creator | Submitted list includes the current creator | Collaborator configuration uses full overwrite semantics, so omitting the creator is rejected. Compare the result against a submission that omits the creator. |
Three common errors
- Treating the draft sentence "the deposit refund condition is satisfied" as a verified conclusion. The asset count sheet confirmation status field is blank, and a count completion date is not landlord confirmation. The input is the two material texts and the draft sentence. The comparison is between "satisfied" in the draft sentence and the confirmation status field on the count sheet. The observable result is that the draft sentence lacks landlord confirmation evidence and remains unsupported.
- Using retrieval relevance in place of a permission decision. Retrieval recall filters by readable files, but a relevance score does not constitute authorization. The input is the operations staff account and an account without permission issuing retrieval requests for the same material. The comparison is between the visible file lists for the two accounts. The observable result is that the account without permission does not see the material, even where a retrieval score is high.
- Treating a pending-review state as approved. A closure approval sitting in pending review does not show that operational permission is absent, and it does not show that the refund condition is satisfied. The input is the closure approval status field and the draft sentence. The comparison is between the pending-review status field and the wording "a refund can be initiated". The observable result is that pending review and a satisfied refund condition are different facts, and the draft sentence is unsupported.
How to verify the setup
- The input is the two material texts above and the draft sentence. Compare "the deposit refund condition is satisfied" in the draft sentence against the blank confirmation status field on the asset count sheet. The condition is met when the draft sentence is marked as pending verification and the count completion date is not equated with landlord confirmation. The expected result keeps the evidence gap open, without any claim that testing was performed.
- The input is the operations staff account and an account without permission issuing retrieval requests for the same material. Compare the visible file lists for the two accounts. The condition is met when the material does not appear in the retrieval results of the account without permission and does appear for the operations staff account. A retrieval relevance score does not participate in the permission decision.
- The input is the closure approval status field and the draft sentence "a refund can be initiated". Compare the two facts: the approval status is pending review, and the refund condition is satisfied. The condition is met when the draft sentence is not treated as approved and the refund condition is not treated as satisfied. A pending-review state does not show that operational permission is absent, and it does not show that the condition is satisfied.