Distinguishes "confirming the service scope" from "confirming a collaboration record": the former confirms content before cooperation, the latter records the fact of cooperation after it is reached or completed, for public credit.
Explains that "confirming the service scope" and "confirming a collaboration record" are two independent actions, each with its own purpose, timing, and effect, to avoid confusion.
Confirming the service scope (before cooperation) - Timing: after the cooperation is accepted and before contact exchange is enabled. - Purpose: both parties agree on service content, budget, deliverables, revision counts, and safety boundaries. - Effect: contact exchange can only be enabled after both confirm. Confirming a collaboration record / marking as collaborated (after cooperation is reached or completed) - Timing: after cooperation is reached or completed. - Purpose: records the fact of cooperation; once both confirm, it counts toward public credit and honors. - Effect: creates a collaboration confirmation record used as a credit basis. The two are independent: confirming the service scope is not the same as confirming the collaboration record, and confirming the collaboration record cannot replace the service scope confirmation.
1. After a cooperation intent is accepted, the requester can click "Mark as collaborated" in the cooperation area to create a confirmation record. 2. The provider confirms it under "My collaboration confirmations" in the account center. 3. Once both confirm, the record becomes "Both confirmed" and counts toward public credit. A collaboration confirmation only records the fact of cooperation. It does not involve funds, guarantees, or platform arbitration.
- Collaboration confirmation records are used for public credit and honors; mark them truthfully. False records can be reported, and the platform will handle them and revoke certifications. - A collaboration confirmation does not replace an offline contract or payment records. Payment, acceptance, and performance are confirmed by both parties. - In case of disputes, the parties resolve them themselves; LynHub does not act as an arbitrator.