When a settled pair is unwound after an outsider has acted on it

A matched pair (600) settles between two parties and involves no third-party intermediary, the settlement record (604) being produced from the two parties' own signed observations. That record comprises the two signed observations, a cryptographic binding over both, and an attestation of the window within which the pair was recognized, and it is verifiable by a downstream consumer from the record alone. Settlement writes a settlement-lineage entry (606) into the append-only lineage field (104) of each party, and that entry is neither removed nor modified, a subsequent reversal or amendment being itself appended.

Reversal is provided for. Section 6.16 subjects a settled pair to challenge through a credentialed dispute procedure, initiated by either settled party under its authority credential, evaluated for admissibility against declared time limits, an authority scope enclosing the action class, and standing, and routed to a dispute-resolution procedure declared in the governing policy object. The resolution rendered may include a settlement reversal, a settlement amendment, a compensation directive, or a no-change outcome, and no step of that procedure increments any refusal meter of either party.

The party at issue here is neither of the two. It verified the settled pair for itself and then produced a determination of its own that consumed the settlement. Two paragraphs of the filing operate together on that situation: one registers the reliance with the settled parties, and one conditions a reversal upon the completeness of the reverting party's own enumeration.

The enumeration a reverting party completes against its own register

Registration comes first. A relying party that independently verifies a settled matched pair (600), against the counterparty identity records (114) it holds for both settled parties, and that then produces a determination consuming that settlement, appends to its append-only lineage field (104) a reliance record. That record carries the settlement identifier, a consuming-determination reference identifying the exact determination with its action class and scope partition, the relying party's identity primitive, and its attested epoch. It is bound to exactly one settlement and one determination.

The relying party emits the reliance record to both settled parties as a governed observation, complete upon emission and soliciting no acceptance. Each settled party, on verifying the record and resolving the settlement identifier to a settlement-lineage entry (606) of its own, enters it in a reliance register indexed by settlement identifier and appends a reliance acknowledgment.

A settled party reversing or amending a settlement appends a reversal record carrying a reliance enumeration field. Section 6.16 recites the same act at the settlement layer: a reversal is given effect by the settled party appending a reversal record enumerating each reliance entered under the settlement identifier and emitting a reversal notice to each relying party so enumerated.

Evaluation is local. The reverting party evaluates a reliance-completeness predicate by an evaluator in its own memory field (102), and the predicate is satisfied only where, for every reliance record entered in that party's own reliance register under the settlement identifier, the enumeration carries a matching entry by relying-party identity and consuming-determination reference.

Where the predicate is satisfied, the reversal is given effect and a reversal notice is emitted to each enumerated relying party. Where it is not satisfied, the reversal record is appended as an attempted-reversal entry and the settlement is not reversed, continuing to obtain for a downstream consumer verifying it from the record alone.

The filing states the condition negatively as well as positively. It rests upon the reverting party's own enumeration alone: no other party is polled, votes, or responds, and the non-response of a relying party neither prevents nor conditions the reversal.

What a notified relying party then does is recited separately. On receiving a reversal notice, verified against the counterparty identity record (114) of the emitting settled party, it appends to its append-only lineage field (104) a reversal mark carrying the settlement identifier, the resolution class, the emitting identity and epoch, and a reference to its reliance record. The settlement the mark names is not deleted. Thereafter that party tests each settlement identifier presented as a determination input against its reversal marks, and one bearing a reversal-class mark is not admitted.

Two resolution classes diverge from there. Where the class is a reversal, the relying party re-resolves the referenced determination with the barred input unavailable, emitting an outcome of its recorded abstention class (126). Where the class is an amendment, it re-resolves against the amended terms and, if those terms supply every consumed input, produces a fresh determination and a fresh reliance record. The outcome propagates to consuming determinations under the conversion bar (502) and is adverse to no settled party.

Section 5.4 supplies that bar. The conversion bar (502) forecloses a consuming determination from converting an abstention outcome into a scalar value, into a default value, into an operand of a threshold comparison (510), or into a consequence adverse to any party, the foreclosure being affirmative rather than an absence of defined behavior.

Which quantities the filing declares and which it leaves open

No count, quorum, fraction, or tolerance appears in the predicate. It is stated as a match holding for every entry of one register, with no minimum enumerated count and no numeric threshold.

Two elements carry the match: relying-party identity and consuming-determination reference. The reliance record also carries the relying party's attested epoch and the action class and scope partition of the consuming determination, and the filing recites the match by the two elements named. Cardinality is fixed rather than declared: a reliance record is bound to exactly one settlement and one determination, and the reliance register is indexed by settlement identifier. Placement is fixed for the evaluator, which sits in the reverting party's own memory field (102).

The emission carries no interval. A reliance record is emitted as a governed observation, complete upon emission and soliciting no acceptance, a governed observation being defined as emitted, in an embodiment, without acknowledgment, handshake, delivery confirmation, or registration with a central authority.

Adjacent bounds are policy-declared with no value stated. The credentialed dispute procedure evaluates a dispute record against declared time limits, and the filing states no duration. Propagation of a reversal within a party's own lineage is bounded by a re-resolution cascade bound declared in that party's signed policy object (112), the traversal terminating in a recorded abstention state rather than unbounded recursion, and again no value is given. The temporal proximity window (602) governing recognition of the underlying pair is defined by form rather than by value, its forms including an absolute duration measured from the first governed observation (608), a declared relative event, an adaptive window, a count of epochs of the dynamic agent hash chain, and any temporal-window form declared in the governing policy object.

Where the predicate sits among the reliance paragraphs

Section 10.5 of the filing, titled "Tool provenance, reliance, and contested pairing," carries the predicate paragraph within a sequence of five. The paragraph before it supplies the reliance record and the register. The three after it supply the relying party's response, transitive reliance, and propagation.

Transitive reliance carries the same structure one step out. A party consuming not a settlement but another party's reliance-bearing determination appends a reliance record carrying, in place of the settlement identifier, an upstream-reliance reference naming that other party, the entry of its lineage at which its reliance record was appended, and the settlement identifier ultimately relied upon. Such a record is a transitive reliance record, and a sequence of them each referencing the next and terminating in one carrying a settlement identifier constitutes a reliance chain. The further party emits its transitive record to the referenced party alone and not to any settled party, and that party enters it in its own reliance register after confirming the upstream reference resolves to its own reliance record. Each party thus holds a register of the parties immediately downstream of it and no enumeration of the whole chain.

The predicate is then evaluated again at each hop. A party of a reliance chain that admits a reversal notice and appends its reversal mark and re-resolution evaluates the reliance-completeness predicate over its own reliance register indexed by the reliance record the notice named, and emits to each downstream party so enumerated a transitive reversal notice carrying its own reliance record identifier, the settlement ultimately reversed or amended, the resolution class, any amended terms, and a hop count. Each downstream party treats it as a reversal notice, appends its own mark, re-resolves, and discharges the same duty onward, so the reversal reaches a chain of arbitrary length with no party holding the whole enumeration.

Composition with Section 6 runs through the settlement layer: the pair and the settlement record (604) from Section 6.2, the settlement-lineage entry (606) and its append-only handling of a later reversal from Section 6.6, and the credentialed dispute procedure from Section 6.16. Composition with the wider architecture runs through recomputation. The semantic agent (100) recomputes a dispatch-authority predicate responsive to each request to dispatch an action, from state then carried in the memory field (102), and not from a previously issued authorization token, a cached predicate result, or a session grant, so that an append to the append-only lineage field (104) takes effect at the next dispatch request without revocation infrastructure. The reliance record and the reversal mark are appends to that field.

Distinguishing quorum commit, revocation publishing, and compensating transactions

Several established lines of work address neighboring problems. The comparisons below are structural and assert nothing about any product, party, or practice.

Two-phase commit, quorum protocols, and consensus rounds condition an outcome on responses gathered from participants, and a silent participant blocks or forces a timeout path. The filed condition is structured the other way: no other party is polled, votes, or responds, and the non-response of a relying party neither prevents nor conditions the reversal. At the settlement layer the filing separately recites that no quorum, no distributed ledger commit, and no consensus round is a condition of settlement.

Certificate revocation lists, OCSP responders, and revocation registries publish a status that clients poll. Here the reversal notice is emitted to each enumerated relying party by the reverting party itself, drawn from that party's own register, and a settlement absent a reversal is verifiable by a downstream consumer from the record alone.

Publish and subscribe invalidation, webhooks, and cache invalidation callbacks route through a broker holding the dependency list. The dependency here is held per party: each settled party enters a verified reliance record in its own register, and along a chain each party holds only the parties immediately downstream of it.

Sagas and compensating transactions unwind by writing compensating state. The filed handling appends instead. A settlement-lineage entry (606) is neither removed nor modified, a subsequent reversal or amendment being itself appended; a reversal that fails the predicate is appended as an attempted-reversal entry; and the relying party's reversal mark leaves the settlement it names undeleted.

Arbitration, chargeback, and escrow reversal procedures vest the unwinding in an adjudicator or an intermediary that executes it. Under the filed procedure, the credentialed dispute procedure renders a resolution, and giving that resolution effect is a further act by the settled party itself, conditioned on that party's own enumeration.

Multi-party approval and consent workflows hand affected parties an approval step, so an unreachable party stalls the change. Registration here supplies no such step, the relying party's recourse on notice being re-resolution and, where an input is unavailable, an outcome of its recorded abstention class (126).

Each of these addresses a real need and can sit alongside what the filing describes. The filed paragraph is directed at something different: a completeness test over the reverting party's own register, failing which an attempted-reversal entry is appended and the settlement stands, and satisfied without input from the parties the enumeration names.

Disclosure Scope

This article describes subject matter disclosed in U.S. Provisional Application No. 64/117,812, at Section 10.5, paragraph [0409], titled "Reliance-completeness predicate conditioning a reversal." Immediately supporting it are [0408] on the reliance record registered with the settled parties, [0410] on the relying party's reversal mark and re-resolution, [0411] on the transitive reliance record and the reliance chain, and [0412] on one-hop propagation and the re-resolution cascade bound. Supporting architecture appears at Section 1.5 for the dispatch-authority predicate, Section 5.4 for the conversion bar (502), Section 6.2 for the matched pair (600), the settlement record (604), and the temporal proximity window (602), Section 6.6 for the settlement-lineage entry (606), Section 6.16 for credentialed dispute resolution, and Section 11 for the definition of a governed observation.

Everything asserted above is drawn from that filed disclosure. Descriptions are of embodiments, and the scope of any exclusive right is determined by the claims of any application claiming benefit of that provisional, not by this article. Publication establishes public, timestamped prior art on this mechanism. It is not a license, an offer, or legal advice.