Skip to content

Phases¶

Who this is for: developers wiring a new bank, debugging a phase failure, or auditing the typed contract between phases.

Every phase implements BasePhase and owns four sub-step hooks: pre, action, post, final. The PipelineExecutor drives them in order and threads an immutable IPipelineContext snapshot between phases.

Slot	Phase	Always-on?	One-line role
1	INIT	✅	Launch Camoufox, build context, navigate to bank URL
2	HOME	✅	Landing-page discovery, signal login readiness
3	PRE-LOGIN	⚙️	"Show login" toggle (Amex, Isracard, Max, VisaCal)
4	LOGIN	✅	7-strategy `SelectorResolver` + declarative `LoginConfig`
5	OTP-TRIGGER	⚙️	Ask bank to dispatch SMS
6	OTP-FILL	⚙️	Fill the code from `otpCodeRetriever`
7	AUTH-DISCOVERY	✅	Capture post-login auth token + API origin
8	`BIND-API-MEDIATOR`	✅	Bind an authenticated `ApiMediator` to the live page; prime bearer / session token
9	API-DIRECT-SCRAPE	✅	Walk the bank's hard-model shape (accounts + balances + transactions) — no nav; `.final` emits `ctx.balanceResolution`
10	TERMINATE	✅	Close browser, finalise result
—	dormant: ACCOUNT-RESOLVE · DASHBOARD · SCRAPE · BALANCE-RESOLVE	—	Retired generic navigation + DOM-scrape chain; still in the tree (ESLint-canary-guarded) but unused by any pipeline bank

API-direct banks — 2 phases¶

Phase	Replaces (browser side)	One-line role
API-DIRECT-CALL	INIT → HOME → … → OTP-FILL	Login + OTP via JSON API
API-DIRECT-SCRAPE	shared — the same scrape phase browser banks run	Shape-driven walk; `.final` emits `ctx.balanceResolution`

Sub-step contract template¶

sequenceDiagram
    participant Exec as PipelineExecutor
    participant Phase as 
    Exec->>Phase: .pre(prevCtx, currCtx)
    Phase-->>Exec: Procedure
    Exec->>Phase: .action(sealedCtx)
    Phase-->>Exec: Procedure
    Exec->>Phase: .post(prevCtx, currCtx)
    Phase-->>Exec: Procedure
    Exec->>Phase: .final(prevCtx, currCtx)
    Phase-->>Exec: Procedure

Hook	Owns	Cannot
`.pre`	Read shared slots, plan the action	Modify slots outside the phase's declared scope
`.action`	Execute the work; sealed action-context — no mediator, no network discovery	Reach outside `IActionContext`; mutate prior slots
`.post`	Validate, partition, hard-fail on universal failure	Re-run the action
`.final`	Commit one new slot to `IPipelineContext`	Touch other phases' slots

Failure at any sub-step returns Procedure fail — the executor records errorType + errorMessage and the run terminates cleanly through the rest of the chain's .final hooks (no half-finished state).