The checks
before the balance.
We fill this in on day five of the trial and sign it before the build starts. Your named reviewer accepts the work on your sandbox.
Write the scope first.
Name the buyer's signer and engineer, the builder, the sandbox and the clients covered. Set the start and end dates, including holidays and agreed pauses. Added tools or clients need a written change with hours and price. Dates move only in writing.
Inspect during the trial
Use isolated fixtures in your repo to inspect a blocked write, a denied or expired approval, a duplicate request without duplicate effects, and a failing API case with its replay. API access remains read-only.
Tools and permissions
List every tool, its title, API endpoints and rate limits. Mark reads, writes, destructive actions and idempotency. A script must fail if a title or permission annotation is missing.
The approval hold
Each write creates a held record in your queue. Nothing reaches your API before approval. Approve one: one execution and an audit record naming the approver. Reject one: no execution. Let one expire: an automatic rejection. We agree the expiry time before the build.
80 exact-match cases
Agree the expected tool, arguments and refusal for each case. You set the passing threshold. Invalid outputs allowed: zero. Name the case author and reviewer. Run in your CI on every push and nightly. The day-five trial score is the floor the build must beat.
Failure and replay
Retry failed reads with backoff, up to the limit we agree. Failed writes never retry on their own. Replay by audit id reproduces the request without a duplicate write. With your API down, return a safe error with no partial data and keep writes held. Test each tool’s off switch without a code change.
Audit and security review
Export the audit as JSON lines by date range. You set retention and redaction. Your named engineer reviews credentials, logging, input validation, idempotency and hold expiry with me. Findings are fixed before acceptance.
Clients and submission
Attach each client named in the scope against your sandbox. Check OAuth end to end using the written instructions. File the directory submission from your account with the required annotations, auth metadata, privacy policy and reviewer account. Filing is the deliverable; listing is the directory’s decision.
Handoff
Hold the recorded 90-minute session with your engineers. Put the runbook in your repo. Revoke my sandbox credentials.
Pass, sign, invoice.
The named signer accepts when all checks pass. The invoice follows that day; the balance is due in 15 days. The CAD 750 trial is credited in full.
The build is CAD 5,000 for the first three companies with a named reference and short case page, or CAD 6,500 without one or afterwards. State that choice in the agreement.
If acceptance fails, allow one fix week. After a second failure, you keep the build code and owe no balance.