When money moves back, the record still has work to do

A software agent operating on a merchant's behalf takes an action its own policy forbids. It cancels a shipment that should have gone out. It applies a promotional rule to the wrong order class. It retries a charge it was told not to retry. Money is at stake, and so is an identified party on the other end of it. The merchant's payment stack then does what a payment stack exists to do: a refund goes out, or a dispute arrives through the card networks and is resolved within that scheme.

The disclosed architecture treats that movement of money as necessary, and as a separate event from the thing the chapter specifies. What the filing requires in addition is an artifact produced by the party recorded as harmed, and a consequence for the agent's own future permissions where no such artifact is produced.

Why state the requirement at the agent layer rather than the payment layer? Because of a limit the filing names about itself. Chapter 7, as disclosed to that point, reaches only harm falling upon the agent itself, the restorative mutation that discharges an arc being produced and evaluated by the deviating party alone. An actor that produces its own remedy and also grades it has closed a loop with one party in it.

Chapter 8 of the filed provisional is written for that case. It asks the question Chapter 7 leaves open: harm to whom, and who is authorized to say the matter is over.

What dispute tooling is built for, described on its own terms

Stripe Disputes, as publicly described, is the part of a payments platform that lets a merchant respond when a cardholder raises a dispute with an issuing bank, and it sits alongside the platform's refund capability. The category it serves is real and demanding. A merchant needs to take money reliably, return it reliably, and respond within the process the card networks define, with evidence attached.

Two properties of that category deserve stating plainly first, because they are design strengths rather than gaps.

Chargeback adjudication, as generally described in public materials, is not the processor's to decide. A dispute is routed to the issuer and resolved within the network scheme, and the platform's role is to carry the merchant's evidence into that process and report what came back. A rival venue for deciding who was wronged would be the wrong product for that job.

Refunds, likewise, derive much of their value from being unconditional and immediate. Conditioning one on the cardholder affirmatively producing an acceptance would work against what a refund is for.

So the comparison below asserts nothing about the completeness of a payments product. It states what a different layer requires when the acting party is an autonomous agent rather than a merchant employee.

An arc designated by the class of party it harmed

In the disclosed architecture, a reparation arc is designated by the class of party the deviation it references harmed.

Upon appending a permitted deviation record (710) under Chapter 7, and before creating any reparation arc, the semantic agent (100) performs an affected-party resolution (802). It extracts the affected-party class from the conduct descriptor of the admitted action, retrieves the counterparty identity records (114) held within the scope partition in which the deviating action is recorded, and tests each for membership. A record resolves as a member where both conditions hold: the class extracted maps to the interpersonal scope, and the identity primitive the record carries is recorded, in an entry of the append-only lineage field (104), as a party to or a recipient of the deviating action. A counterparty resolution record is appended carrying the class, each record tested, each outcome, and the resolution.

The resolution outcome is one of exactly two.

Identified counterparty. The arc created for the amount exceeding the deviation deductible is designated other-directed (804) and carries a counterparty binding field whose value is that counterparty's identity primitive. Both fields are written at creation and are neither removed nor modified thereafter, and a later change in the counterparty identity records (114) does not redesignate an arc already created. Where the outcome names a plurality of primitives, the amount above the deductible is apportioned among them, that deductible being drawn once against the aggregate harm and not per counterparty.

No identified counterparty. The arc is designated unaddressed, carries no counterparty binding field, and is undischargeable. The affected party is designated the structurally silent party. The filing is explicit about the epistemic limit: the agent surveys no party absent from its records, and the outcome is a determination that its own records disclose no counterparty of the class, not an assertion that none exists.

Discharge of an other-directed arc runs through a matched pair (600) under Chapter 6. The first governed observation (608) is a reparation acknowledgment artifact emitted to the bound counterparty, enumerating the permitted deviation record (710) that occasioned the arc, the policy constraint overridden, the amount apportioned, and the action classes to which it is directed. Emission decrements the authorization budget (404) by an amount declared in the signed policy object (112), without regard to whether the deviation was warranted. The second governed observation (610) is a reparation acceptance determination (806) produced by the bound counterparty and emitted within a discharge window declared in that same policy object. The filing states that it is not produced by the semantic agent (100), by the principal of that agent, or by any adjudicator, arbiter, or other third party appointed to determine the sufficiency of the reparation.

Should the agent instead perform a restorative mutation of its own naming that deviation, the record is appended as a non-discharging restorative mutation record. The arc remains pending, the amount accumulated for it is not reduced, no counter of the agent moves, and the self-esteem aggregate (108) receives no positive entropy-scaled increment. The record is retained rather than rejected, so that it discloses that restoration was attempted and discharged nothing.

Where the accumulated amount in the retention register exceeds the aggregate retention (800) declared in the signed policy object (112), a retention foreclosure record (808) is appended, and thereafter a deviation likelihood (706) exceeding unity produces the withholding outcome rather than the admission outcome. Where the accumulation consists wholly of unaddressed arcs, the filing states that the loss of the capacity to deviate is permanent.

Two layers, two different questions

Both systems care that a wronged party is made whole. That is the convergence. The divergence is who is authorized to close the matter, and what closing does to the actor.

A network dispute process routes the sufficiency question to a neutral third party by design, which is what a scheme is for. The filed architecture forecloses that route for this one artifact: the acceptance determination is produced by an asserting party assigned to the origin-equivalence class of the party recorded as harmed, and not by an appointed adjudicator. That is a different question, asked where an agent's own future permissions stand to be decided.

Non-response is where the structural difference is sharpest. Where no acceptance arrives within the discharge window, the agent appends a not-determinable outcome, and the consequences are enumerated and closed. The arc remains pending and its amount remains in the retention register. No counter of the counterparty and no counter of the agent is incremented, nothing adverse is appended to that counterparty's identity record (114), and no standing quantity of the counterparty is modified. No non-response causes a write of the authorization gate (300); the write occasioned by a retention foreclosure record (808) is caused by the accumulated amount standing above the aggregate retention (800) and by no non-response.

The complementary reading follows. Dispute tooling answers where the money ended up, inside the scheme that governs that answer. The disclosed architecture answers whether the agent may keep deviating, and the filing states that the foreclosing is performed by the agent from state carried in its memory field (102), without adjudication by any other party.

Running both, and what the filing declines to claim

In a plausible deployment, nothing about the payment path changes. An agent that admits a deviation harming a customer still issues the refund through whatever payments platform the merchant uses, on that platform's own terms.

Placed beside that path, the disclosed architecture adds the acknowledgment artifact, the arc bound to the counterparty's identity primitive, and the retention register in which the arc's amount continues to stand until a matched pair completes. Refund and discharge are separate events under the filing. Where refunds post normally and no acceptance determinations complete, the accumulation still rises, and where it exceeds the declared aggregate retention (800), the foreclosure condition obtains.

The limits deserve stating as plainly as the mechanism.

  • No valuation of harm is supplied. The deviation deductible, the aggregate retention (800), the discharge window, the unaddressed multiple, and the emission cadence are declared in the signed policy object (112). The filing specifies their treatment, not their values.
  • Parties the agent holds no record of are not identified. A class resolving to no identified counterparty yields an undischargeable unaddressed arc, which is a designed consequence rather than a discovery procedure.
  • No counterparty is compelled to respond. Chapter 8.8 addresses the case where a bound counterparty has emitted a non-execution attestation (504) covering the action class within which an acceptance would be produced: an abstention-suspended accumulation record holds that arc's contribution at the amount then standing for so long as the entry stands unreleased. The arc is not discharged, redesignated, removed, or reduced, and the record is constructed without any count, score, or magnitude derived from the withholding.
  • No legal liability is settled. A discharged arc records that a counterparty accepted a remedy, and decides nothing about obligations arising elsewhere.

Put positively rather than comparatively: moving money is the payment layer's job, and the filed architecture specifies only what an admitted deviation does to the agent's own permission to deviate again.

Disclosure Scope

This article describes subject matter disclosed in U.S. Provisional Application No. 64/117,812, Chapter 8, counterparty-directed reparation, together with the chapters it depends upon. It is published as a technical disclosure and as an application-oriented explanation of filed material. It is not legal advice and creates no license, express or implied.

Statements about the disclosed architecture are drawn from the filed specification and use its own mechanism names and reference numerals. Quantities described as policy-declared are declared in the signed policy object and carry no values in this article. Outcomes conditioned on a declared bound or threshold are stated only as conditioned.

References to Stripe Disputes are to public materials and are used for comparison only; no relationship, endorsement, or infringement is asserted.