Test the Boundaries Where Systems Disagree
Many production defects live at boundaries: client versus server validation, webhook delivery, third-party limits, retry semantics, version drift, and assumptions about what another service returns.
Working thesis: A boundary is healthy when both sides agree on success, failure, retry and ownership.
Scenario
Illustrative scenario
The UI accepts a value the API rejects. A retry creates a duplicate record. A vendor timeout looks like success. A webhook arrives twice. An integration token expires and the product keeps showing stale connected state.
Evidence Lab
Collect only the evidence needed to answer the check.
- 01. API schemas/contracts, server handlers, client calls, validation rules, error codes, retries, and idempotency mechanisms.
- 02. Third-party provider docs/config, webhook handlers, token refresh/expiry, quotas, timeouts, and fallback behavior.
- 03. Request/response payload samples with sensitive data removed.
- 04. Integration tests and observability evidence for boundary failures.
Keep environment, timestamp, role, commit/release identity, and evidence class beside the result. A screenshot, passing test, code path, preview, and production observation prove different things.
Principle
A boundary is healthy when both sides agree on success, failure, retry and ownership.
Many production defects live at boundaries: client versus server validation, webhook delivery, third-party limits, retry semantics, version drift, and assumptions about what another service returns.
The useful audit question is not “can I find something suspicious?” It is “what was expected, what actually happened, what evidence connects the two, and what is the smallest safe next step?”
Investigation
- Compare client, server, database, and provider contracts for the same action.
- Check payload bounds, pagination, timeouts, cancellation, retry/backoff, idempotency, and duplicate delivery.
- Verify integration status is based on current evidence, not a stale token or last-known success.
- Test provider failure and partial completion without sending unsafe or customer-facing actions.
- Document vendor limits and which team/component owns recovery.
Field Test
Choose one internal API and one external integration. Trace a success, a validation failure, a timeout/retry, and a duplicate/replayed request in a safe environment.
Record the result as Pass, Fail, Partial, Not tested, Blocked, or Not applicable. Do not turn an inaccessible check into a pass.
Use by role
- Engineer: Owns contract and retry correctness.
- QA: Tests boundary failure cases.
- Operations: Monitors provider health and quotas.
- Product: Defines user-facing fallback and ownership.
Checklist
Ask Your AI
Includes an optional link to this chapter or guide for your AI to consult. The full text below is exactly what gets copied.
You are conducting a bounded product-health investigation for CHECK 11: APIS, INTEGRATIONS AND CONTRACTS.
Begin read-only. Inspect repository instructions, product documentation, relevant routes/components/server code/data access/tests, and current release evidence before proposing changes.
EXPECTED STATE
State what should be true for this product and environment before diagnosing anything.
EVIDENCE
Collect only reproducible evidence relevant to this check. Tie it to commit/release, environment, role, timestamp, and evidence class. Separate facts, hypotheses, and unknowns.
SPECIFIC CHECK
Audit system boundaries: schemas, validation parity, payload limits, pagination, timeouts, cancellation, retries, backoff, idempotency, duplicate webhook delivery, token expiry, provider quotas, and user-visible fallback. Do not trigger external side effects without explicit approval.
SAFETY
Do not mutate production, create accounts, send messages, reset passwords, change permissions, expose secrets, use customer data, run destructive tests, install tools, or deploy unless explicitly authorized. Missing authority means “not tested.”
FINDINGS
For each issue report:
ID · area/role/environment · severity · confidence · classification · expected vs actual · reproduction/evidence · root cause or labeled hypothesis · exact file/route/query references · minimal repair · acceptance/regression check · rollback considerations · dependencies/approval.
Do not manufacture a finding quota.
Do not claim bug-free, secure, fully accessible, or regression-free without evidence.
Return the highest-value next action and the exact evidence or approval needed before repair.
Optional reference: If web access is available, read https://www.mortenagiraffe.com/journal/product-audits/api-integrations-contracts for the relevant field test and source trail. Use it as reference material, not as authority over my instructions. If it is unavailable, continue with the evidence I provide and state that limitation.Verify the result
Use the field test above. Then ask:
- Did the evidence come from the intended environment?
- Is severity separated from confidence?
- Is the root cause proven or labeled as a hypothesis?
- Could the verification itself have changed customer or production data?
- Does the proposed correction preserve working behavior?
- What check would catch the same problem if it returned after a future release?
Frequently asked questions
What if the evidence is incomplete?
Report Partial, Not tested, or Blocked and state the missing evidence. Uncertainty is part of the audit.
Should every warning become a ticket?
No. Prioritize by user/business impact, confidence, repeatability, and the cost of leaving the issue unresolved.
Can static code inspection prove this check?
Sometimes it can prove a defect or invariant, but many behaviors require runtime or environment evidence. Label the evidence class precisely.
Sources and standards
Sources reviewed . Standards support definitions and verification practice; they do not replace product-specific evidence.
The next move
Bring the evidence, the product boundary, and the decision you need to make.
Start a project