Skip to content

feat(topup-agent): Pix with a passkey (Iniciador JSR) as a second rail, over the agentic MCP (sandbox) - #111

Closed
rapguit wants to merge 6 commits into
feat/runtime-consent-stepfrom
feat/topup-agent-jsr
Closed

rapguit wants to merge 6 commits into
feat/runtime-consent-stepfrom
feat/topup-agent-jsr

Conversation

@rapguit

@rapguit rapguit commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Closed for rework. This draft will come back in a different shape.

@rapguit
rapguit force-pushed the feat/runtime-consent-step branch from e854e77 to 8f42309 Compare November 3, 2026 21:33
…l, over the agentic MCP (sandbox)

`--rail api` with INICIADOR_RAIL=jsr: the person registers a passkey once on
Iniciador's hosted page and signs each pull there with the phone's
biometrics. The rail hands both pages as consent steps of one attempt
(enroll, then sign), creates the payment at most once (marker before the
request, a lost answer is uncertain and never retried), and settles on the
Pix end-to-end id read from the one REST call the MCP does not answer.
INICIADOR_RAIL=jsr without --rail api runs it on an in-memory fixture.
The creditor goes inline and enters the mandate as a digest, so the
account number never sits in a snapshot or an event. The core's rail-name
union gains "iniciador-jsr". No tool added; no receipt is sealed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@rapguit
rapguit force-pushed the feat/topup-agent-jsr branch from b354bff to 2491337 Compare November 3, 2026 21:57
rapguit and others added 5 commits November 4, 2026 15:42
…read times out, the MCP is down

An enrollment that ends before COMPLETED is charge_expired and never reaches
create_payment; a sign page left open stays the sign step until the bank ends
it TIMEOUT_CONSENTIMENTO. A status_payment or status_authorization read that
times out is uncertain, not final and not a human's, and the next look goes
on. The MCP down before the enrollment leaves nothing on record; at
create_payment (no answer, or a 503 echoing the credentials) it is
pull_dispatch_uncertain, asked once, with no credential in the outcome or in
state.db. No change to the rail.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… and the open questions

README: what the rail is, its two pages, the variables by name, --rail api
with INICIADOR_RAIL=jsr, the offline fixture and INICIADOR_JSR_ENROLL=always.
SYSTEM_PROMPT: the two links (Cadastrar biometria, Confirmar biometria), both
from the code, and an expired link is either. OPEN_QUESTIONS §68: the payment
bound to the newest passkey, a passkey deleted on the phone not revoked at the
server, the enrollment's lifetime, no end-to-end id in the MCP.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… two pages point to #110's consent_step

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…yment, pays only with the newest, and keeps no hosted link in state.db

An expired (INACTIVE) or revoked enrollment on record is a new enroll page,
not a charge_issuer_error. The payment goes out only when the enrollment
checked is the newest COMPLETED one (jsr_enrollment_not_newest otherwise);
one the MCP bound to another anyway is enrollment_mismatch, uncertain with
needs_human, its signing page never shown. The enroll link lives in memory
only; the signing page is read again from status_payment while it waits.
Mirrors codespar-enterprise#2428.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t off disk, in the README

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@rapguit

rapguit commented Nov 11, 2026

Copy link
Copy Markdown
Contributor Author

Closing this draft for rework.

@rapguit rapguit closed this Nov 11, 2026
@rapguit
rapguit deleted the feat/topup-agent-jsr branch November 11, 2026 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant