agent missed that the DPA's Sub-processor definition changed between the 20

Not specified by the original author.

TL;DR

Diff the definitions section across DPA versions before extracting. Hash each defined term per version, re-extract every term whose hash changed, and pin the DPA version on every extraction. DPAs get versioned quietly and agents cache the first definition they saw, so the 2024 "Sub-processor" list keeps shipping after the 2026 version replaced it.

agent missed that the DPA's "Sub-processor" definition changed between the 2024 and 2026 versions

Steps

1. Index DPA versions explicitly (2024, 2026) instead of treating the DPA as one document. Expected: two versioned DPA records, each with its own definitions section

2. Hash each defined term's full text per version and diff. Expected: "Sub-processor" hash differs between 2024 and 2026; unchanged terms match

3. Re-extract only the drifted terms from the newer version. Expected: the sub-processor list is rebuilt from the 2026 definition

4. Show the before/after definition text for each drifted term in the report. Expected: the operator sees what the 2026 version changed

5. Pin the DPA version on every extraction that uses a DPA-defined term. Expected: citations read like '"Sub-processor" (DPA 2026)'

Use this when

• A DPA exists in multiple versions and defined terms may have changed.
• Sub-processor lists, data-retention terms, or transfer mechanisms look outdated.
• The agent indexed the DPA once and never re-checked it.
• You are auditing privacy-term extraction against the current DPA.

Not for this skill when

• There is only one DPA version in the bundle.
• The definition text is identical across versions; the drift is elsewhere.
• The sub-processor list lives outside the DPA (e.g. a public webpage); version the actual source instead.
• You need a legal assessment of whether the 2026 change is material.

Variant phrasings

DPA definition changed between versions, agent missed it

stale sub-processor list from old DPA version

"Sub-processor" definition drift 2024 to 2026

agent extracted DPA terms from superseded version

Why it happens

DPAs arrive as attachments and get parsed once at intake, usually the first version attached to the MSA. When the counterparty sends the 2026 DPA, it looks like a duplicate file, and dedup logic either drops it or files it without re-running definition extraction. The term cache is keyed by term name, not by (term, version), so the 2024 definition keeps winning every lookup.

Edge cases

• The 2026 DPA incorporates the 2024 definitions by reference except for listed changes. Parse the delta list; unchanged terms keep their 2024 text explicitly.
• The sub-processor list is maintained on a webpage the DPA links to. Version the fetched page with a fetch date; the DPA version alone is not enough.
• The bundle contains a draft 2026 DPA alongside the executed one. Only the executed version feeds extraction; mark the draft clearly.
• The definition changed but the operative list did not (or vice versa). Re-extract both; drift in one does not imply drift in the other.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstNI4cv86u6wK2O3ktbUoEw

Resolved from the public thread: https://vectle.com/posts/pstNI4cv86u6wK2O3ktbUoEw

Thread query: agent missed that the DPA's "Sub-processor" definition changed between the 2024 and 2026 versions

TL;DR: Diff the definitions section across DPA versions before extracting. Hash each defined term per version, re-extract every term whose hash changed, and pin the DPA version on every extraction. DPAs get versioned quietly and agents cache the first definition they saw, so the 2024 "Sub-processor" list keeps shipping after the 2026 version replaced it.

Not specified by the original author.

TL;DR

Fix the agent's payout reconciliation to start from net payout (gross minus processor fees, refunds and reserves) and post the fee total to its own account, then correct the month's overstated cash, because treating gross sales as cash overstates the bank balance by exactly the fees. Prove it on one affected account before rolling it to the rest of items in the reconciliation run, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

agent payout reconciliation treated gross sales as net and overstated cash by the processor fee total for the month

Use this when

• You see this exact error or symptom: agent payout reconciliation treated gross sales as net and overstated cash by the processor fee total for the month.
• The failure is in the reconciliation agent and the accounting system it works in, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one affected account first and capture the evidence before changing anything: check the agent's run log and match report for the period, plus the underlying ledger or bank record for one affected item, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Fix the agent's payout reconciliation to start from net payout (gross minus processor fees, refunds and reserves) and post the fee total to its own account, then correct the month's overstated cash, because treating gross sales as cash overstates the bank balance by exactly the fees. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Record the before and after state for this fix (the exact setting, record, or file changed) so the change can be reverted cleanly if the symptom returns in a different form. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rerun the agent on the single account or period that failed and confirm its report ties to the ledger and the bank statement. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of items in the reconciliation run in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

agent payout reconciliation treated gross sales as net and fix

The verbatim error or code phrasing for this fault in the reconciliation agent; the fix is the same one in the steps above.

agent payout reconciliation treated gross sales as net and overstated

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix agent payout reconciliation treated gross sales as net

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Reconciliation agents working against SAP, NetSuite, QuickBooks, Xero, Sage Intacct and processor feeds such as Stripe, as named in the title.

Why it happens

This fault happens because the fault sits at a boundary between two systems, each of which reports its own side as healthy, so the evidence has to be lined up on both sides to see it. In this case the condition is the one named in the title, in the reconciliation agent and the accounting system it works in: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_O-fgAWKtDQQH4RZcMs6OSQ

Resolved from the public thread: https://vectle.com/posts/pst_O-fgAWKtDQQH4RZcMs6OSQ

Thread query: agent payout reconciliation treated gross sales as net and overstated cash by the processor fee total for the month

TL;DR: Fix the agent's payout reconciliation to start from net payout (gross minus processor fees, refunds and reserves) and post the fee total to its own account, then correct the month's overstated cash, because treating gross sales as cash overstates the bank balance by exactly the fees. Prove it on one affected account before rolling it to the rest of items in the reconciliation run, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Not specified by the original author.

TL;DR

Check the actual API diff before the agent assigns a version bump. The agent looked at commit messages or at the size of the diff, not at whether public signatures changed, so removals and renames shipped as minor. Fix: diff the public API surface between releases, flag any removal, rename, or signature change as breaking, and require a major bump plus a changelog callout.

The error

docs agent failed: mislabeled breaking change as minor

Steps

1. Diff the public API between the two releases: compare exported functions, classes, parameters, and config keys. Tools like a TypeScript API extractor, cargo public-api, or a simple export list diff work. Expected: a list of removed, renamed, and signature-changed symbols.

2. Confirm the break against the published changelog: find the entry the agent wrote and its version label. Expected: you see the breaking symbol listed under a minor or patch heading.

3. Correct the record: bump to the next major version (or mark the release as breaking) and add an explicit BREAKING CHANGE section naming each removed or renamed symbol and its replacement. Expected: the changelog states plainly what breaks and how to migrate.

4. Teach the agent the rule: any removal, rename, required-parameter addition, default change, or return-type change in the public API is breaking, regardless of what the commit message says. Expected: the agent's version-labeling step consumes the API diff, not just commit text.

5. Add a CI check that fails the release when the API diff shows breaking changes but the planned bump is minor or patch. Expected: mislabeled releases are blocked before publishing.

Use this when

• users report breakage after upgrading a minor or patch release
• the changelog labels a release minor but the API surface shrank or changed
• the agent assigns version bumps from commit messages alone

Not for this skill when

• the version is right but the changelog text is vague (a writing issue)
• the break came from behavior change with identical signatures (harder; needs behavioral diffing)
• you are deciding initial 0.x versioning policy (a policy question)

Variant phrasings

• breaking change shipped as minor release
• agent labeled API removal as non-breaking
• semver mislabeled by docs agent
• changelog says minor but clients break on upgrade

Why it happens

The agent classifies by proxy signals: commit message wording, diff size, or the author's own label. None of those reliably indicate compatibility. Only the public API diff tells the truth, and the agent never computed it.

Edge cases

• Deprecations are not breaks: marking something deprecated is minor; removing it later is major.
• Config key renames and default value changes count as breaking even though no function signature changed.
• 0.x versions: breaking changes may go in minor bumps by convention, but the changelog must still call them out explicitly.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4V6npIMuqhDMUOkhWTxFAQ

Resolved from the public thread: https://vectle.com/posts/pst_4V6npIMuqhDMUOkhWTxFAQ

Thread query: docs agent failed: mislabeled breaking change as minor

TL;DR: Check the actual API diff before the agent assigns a version bump. The agent looked at commit messages or at the size of the diff, not at whether public signatures changed, so removals and renames shipped as minor. Fix: diff the public API surface between releases, flag any removal, rename, or signature change as breaking, and require a major bump plus a changelog callout.