1. Your exact project agreement
The identified proposal and final offer set out the participants, purpose, deliverables, exclusions, professional fee, buyer total, currency, timing, stages, responsibilities, required inputs and correction allowance. Read these details together. Specific project terms govern those details; the Terms of Use govern Borage’s coordination services. Mandatory rights take priority over any provision that cannot lawfully apply.
The professional confirms their proposal and availability. This is conditional on selection and the buyer’s agreement. The buyer then explicitly confirms the final offer. When payments are enabled, required first-stage funding must be confirmed before the project starts. The workspace shows whether the stage is ready for work.
Do not begin work because you received an invitation, were recommended by AI or saw an administrator select a proposal. Wait for the agreed project and funded stage to become active. A clearly labelled fictional sandbox test creates no commercial delivery or real-money obligation. The payment-off POC follows its disclosed pilot arrangements.
A browser confirmation is connected to the exact proposal and the terms version shown with it. If the scope changes while you are deciding, review the current version before confirming. Earlier messages and files remain part of the history; they do not silently replace the agreed proposal.
2. What each person is responsible for
The professional must deliver the agreed work with reasonable care and skill, follow the stated requirements and explain a material obstacle promptly. They control how they carry out the work, subject to the agreed result and responsibilities. Registration alone creates no employment relationship; any mandatory worker or employment protections that actually apply are preserved.
The buyer must supply the agreed inputs, make funding and review decisions, and give clear consolidated feedback. If you represent an organisation, obtain its approvals before committing its materials, budget or instructions. Each participant is responsible for the accuracy and permission of what they supply.
The desk coordinates the recorded workflow, questions and exceptions. It can help identify the next action or prepare a proposed resolution. Coordination does not transfer the professional’s delivery promises to the desk or let the desk approve work on the buyer’s behalf.
Report delays or missing inputs as soon as you can. Explain what is blocked and propose the next practical step. A late input or payment does not automatically extend an agreed deadline. Changes to dates or obligations need the affected parties’ explicit agreement.
3. AI assistance and human review
AI may prepare a structured draft, compare a professional’s evidence with a brief, help interpret a reply or produce delivery review notes. Automated matching, routing and selection can operate within configured rules. These outputs can contain errors, so review the actual scope, files and reasons rather than relying only on a score or summary.
The buyer remains responsible for approving the brief, final agreement and delivered work. The professional remains responsible for agreeing their own proposal and submitting their work. Administrators handle exceptions, uncertainty and supported holds or recovery actions. Routine automation is not described as having been individually approved by an administrator.
An automated preflight can return an observable missing requirement for a bounded correction before the delivery reaches the buyer. Subjective judgments go to the buyer. AI review does not itself accept a delivery, authorise a new project price or decide a legal dispute.
If a review note seems wrong, identify the requirement, relevant file and your explanation through the available review or issue action. A human can then assess the concern using the project record. Keep feedback about the agreed scope separate from a request for additional work.
4. Inputs, files and timing
The agreement identifies which buyer inputs are needed and who supplies each one. Use the workspace to provide the required files or answers so the professional and desk can relate them to the correct project. Tell the desk if an input is missing, unusable, restricted or superseded.
Dates and review windows must be read as stated in the agreement. Some timing is measured from the project or stage becoming active. Funding, inputs and an explicit hold can affect when an action becomes available, but do not quietly rewrite the agreed schedule.
Only supply materials you are authorised to share. Do not include passwords, payment credentials or unrelated sensitive information in a brief or delivery file. Tell the desk before sharing material subject to a special confidentiality, regulatory or geographic restriction.
Uploaded files have type and size limits and are accessed through the relevant authorised project flow. Those checks do not guarantee that a file is safe to open. Participants remain responsible for sensible file handling and for reporting an unexpected or suspicious file.
5. Delivery, acceptance and corrections
Submit a complete stage delivery through the workspace with the files and evidence needed to assess the frozen acceptance criteria. Identify any agreed restriction on use or licensing. A partial upload or informal message does not establish that all delivery obligations have been fulfilled.
The buyer reads the available files and review notes and records acceptance, a permitted consolidated correction or an unresolved issue through the review action. AI notes are assistance, not the buyer’s decision. Silence does not automatically accept a delivery in this POC.
The saved agreement specifies the correction allowance and whether it is allocated across the contract or particular stages. Give one clear consolidated request within that allowance. A new direction, additional deliverable or request outside the agreed scope needs a separate agreement to its price, timing and responsibilities.
When the correction allowance is exhausted or the parties disagree about scope, use the issue or project-desk route. The workflow can pause for review rather than run an unlimited correction loop. Acceptance is recorded against the exact submission and files; a later upload does not replace an already accepted file version.
6. Funding, release and payment concerns
When payments are enabled, the buyer funds each stage before work on that stage begins. The next stage remains closed until its required payment is confirmed. Payment-off pilot arrangements must be understood separately; do not assume they are evidence of a real charge.
The professional’s accepted stage payment is normally scheduled 48 hours after buyer acceptance, subject to the saved payment terms, recipient readiness, currency and provider checks. A recorded hold may pause the affected transfer. Completion of delivery, transfer eligibility, a Stripe transfer and bank arrival are different events.
Borage verifies payment-provider confirmations and relates them to the expected order. It also checks transaction details and records holds and release attempts. These controls reduce the risk of starting unfunded work or releasing an affected payment while an issue is open, but they do not guarantee every transaction or prevent all fraud.
If Checkout was interrupted or payment status is unclear, check the workspace and contact the desk before paying again. Keep the relevant order or project reference. A refund, dispute or reversal needs a recorded review of the affected work and payment; an issue button does not automatically move money.
The desk must explain any agreed cancellation or payment resolution, including its financial consequences. Provider and bank processing times remain outside the project workflow. These draft terms do not promise a particular refund outcome or describe the POC as a licensed escrow service.
7. Materials, confidentiality and licences
Each party must have permission to supply and use its materials. Keep non-public project information confidential, use it only for the authorised project purpose and share it only with people or providers who need it. Disclosure required by law is permitted; notify the affected party where doing so is lawful.
For work the professional creates specifically for the project, after buyer acceptance and full payment of the agreed price, the professional grants the buyer a worldwide, perpetual, non-exclusive licence to use and adapt the accepted work for its intended project purpose. A transfer of ownership or exclusive rights needs an explicit written project term.
Existing tools, fonts, stock assets, templates and other third-party materials retain their applicable licences. Disclose material restrictions before agreement, including costs or limits that affect the buyer’s intended use. No trademark clearance, exclusive rights or font licence is implied by a general acceptance.
If the project needs ownership transfer, exclusivity, permission for portfolio display or a particular confidentiality arrangement, put that requirement into the written project terms before confirmation. An example image or AI suggestion does not prove that the material may be used. Mandatory intellectual-property and privacy rights remain applicable.
8. Changes, safety concerns and unresolved issues
Use the project desk to record a proposed scope change, replacement professional or dispute. State the affected requirement, the evidence and the result you want. A replacement or additional piece of work requires the affected parties’ agreement to its scope, price and dates.
Original accepted work, payment records and decisions remain in the project history. A hold can stop affected activity while a person investigates; it does not undo an acceptance, waive a legal right or silently change the commercial terms. An administrator must use the available recorded actions.
Report suspected impersonation, unauthorised access, malicious files or misuse of confidential information promptly. Keep private links and credentials out of your report. The desk can assess the affected access or workflow and explain the supported next step. No immediate response time or security outcome is guaranteed by these draft terms.
The desk coordinates resolution and is not a court or binding arbitration service. The Terms of Use explain governing law and preserve mandatory local rights, including applicable US federal and state rights. Operator details, consumer arrangements, licence wording and live payment operations need review before commercial launch.