This is the build plan for this decision record, bite by bite, as it was grilled and built. It’s copied from our repository unedited, apart from customer, partner and bank names, which read [redacted]. It was written for the people and agents building the product, so expect internal shorthand, and the mistakes are left in.

ADR-838 — Implementation Plan

Findings for the ADR

Files touched

Bite 1 — the symbols for a Raise wire, the asset reading, the merchant parameters, the activation check, headline

Bite 2 — CreditCard on the retail template

Bite 3 — the interest-free rule

Bite 4 — the card

Bite 5 — the viewer, the sample data, the guide, the probe, the register

Prior art

Nothing changed since the grill, and two declared names left: positionDays and the schedule occurrence dates (F6). PositionType.Headline (F4) is the one supporting type the signatures needed; it carries F4’s decision, which is raised.

Interfaces

// src/LedgerTM.Accounts/Domain/Configuration/PositionType.cs — changed (F4)
public bool Headline { get; init; }   // yaml `headline: true`; the hero slot shows it whatever its category; exported and imported with the row

// src/LedgerTM.Accounts/Application/Operations/FacilitySymbolResolver.cs — changed (D2; ADR-837's type)
// Raise wire: FacilityLimit = min(Amount, max(0, Amount − Σ max(0, usage[other accounts]))); FacilityAvailable = max(0, FacilityLimit − Reserved);
// Excess = max(0, ledger(wired position) − FacilityLimit), computed from the wired position at every site ADR-837 computes it from Current (F19). BelowZero as ADR-837. No wire → None.

// src/LedgerTM.Accounts/Application/Queries/AccountAvailabilityReader.cs — changed (D3; ADR-836's type)
// Liability nature: as ADR-837. Asset nature: Ledger = 0, Claims = 0, Available = max(0, FacilityAvailable − wiredPosition + Σ max(0, −standard position) − ExternalReductions) (F7, F23): an overpaid credit is spendable.

// src/LedgerTM.Accounts/Application/Commands/ProcessExternalSourcePaymentHandlers.cs — changed (D4; ADR-836's handlers)
// The card dispatch adds parameters merchantCategory (the MCC's four digits), merchantName, merchantCountry (alpha-2 or null) beside amount.

// src/LedgerTM.Accounts/Application/Limits/RegulatoryLimitEnforcement.cs — changed (D8, F17, F18)
// The guard context it evaluates in carries the rate lookup; TryEvaluate also catches the evaluator's InvalidOperationException; an Interest-category
// scheduled row's rate('name', valueDate) references are each checked on their own against the regime's ceiling at agreement date, refusing activation as a bound property is refused;
// a rate unknown or unfixed on that date refuses too (REGULATORY_RATE_UNPRICEABLE). RegulatoryLimitGuard resolves the row's basis from the category, so an Interest row is compared (F28).

// Configuration (D1, D5, D6, D7) — src/LedgerTM.Seeding.Provisioning/tenant-templates/packages/retail-bank/AccountTypesSettings.yaml, CreditCard:
//   nature: Asset; accountRoles: holder; statementSchedule: Statement
//   positionTypes: PurchaseBalance, CashAdvanceBalance, Fees, UnallocatedPayment, Arrears (standard; Arrears in the arrears balance group, an overlay); PurchaseAccrued, CashAdvanceAccrued (accrual);
//     Outstanding (memorandum, its own balance group), StatementBalance (headline), AmountDue (headline), MinimumPaymentDue (headline), CyclePurchases, StatementPurchases,
//     DeferredCycleInterest, DeferredStatementInterest, GracePeriodStatus (memorandum)
//   externalIntegrations: cardPurchase → card-purchase, cardRefund → card-refund, bankDeposit → receive-payment, debitOrder → receive-payment
//   openingTransactions: GraceStatusUpdate 1 (F12)
//   transactionTypes (every one with costOfCreditCategory and btcCode, none with a guard; isPostable on all):
//     Purchase (Dr PurchaseBalance, Dr Outstanding, Dr CyclePurchases), CashAdvance (Dr CashAdvanceBalance, Dr Outstanding),
//     PurchaseRefund (Cr PurchaseBalance, Cr Outstanding, Cr CyclePurchases), StatementPurchaseRefund (Cr PurchaseBalance, Cr Outstanding, Cr StatementPurchases), CashAdvanceRefund (Cr CashAdvanceBalance, Cr Outstanding),
//     RefundCredit (Cr UnallocatedPayment), Payment (Cr UnallocatedPayment; isDefaultInboundAllocation),
//     FeePayment, CashAdvancePayment, PurchasePayment (each Dr UnallocatedPayment, Cr its balance, Cr Outstanding), ArrearsCleared (Cr Arrears only — the overlay, F8),
//     AmountDueReduced, MinimumPaymentReduced (Cr the memorandum),
//     PurchaseInterestAccrued, CashAdvanceInterestAccrued, DeferredCycleInterestAccrued, DeferredStatementInterestAccrued (Dr their position; maximumPrecision; Interest),
//     PurchaseInterestCatchUp (Dr PurchaseAccrued; maximumPrecision; Interest), PurchaseInterestCapitalised, CashAdvanceInterestCapitalised (Cr the accrual, Dr the balance, Dr Outstanding),
//     StatementClose, AmountDueSet, MinimumPaymentSet, StatementPurchasesSet, CyclePurchasesReset, DeferredStatementInterestSet, DeferredCycleInterestReset, DeferredStatementInterestReset (Set),
//     GraceStatusUpdate (Set), MinimumPaymentOverdue (Dr Arrears, Cr MinimumPaymentDue — one type, two legs, F8),
//     AnnualFeeCharged (Fee), LateFeeCharged (DefaultAdmin), CashAdvanceFeeCharged (Fee), OverLimitFeeCharged (gb cell only, Fee, F9) — each Dr Fees, Dr Outstanding
//   scheduleTypes: Accrual (daily), Statement (monthly, startDateExpression addMonths(StartDate, 1)), PaymentDue (monthly, startDateExpression addDays(addMonths(StartDate, 1), paymentGraceDays)), Annual (yearly, startDateExpression addMonths(StartDate, 12), F24); businessDayConvention None (F11)
//   A Set row posts even at zero (F26): the close rows always post, so the cycle trigger fires and a statement is issued.
//   scheduledTransactions, EndOfDay, by the generated type's sequenceNumber:
//     Accrual: PurchaseInterestAccrued  PurchaseBalance * rate('CreditCardPurchase', valueDate) / daysInYear(valueDate)  condition GracePeriodStatus == 0 && PurchaseBalance > 0
//              CashAdvanceInterestAccrued  CashAdvanceBalance * rate('CreditCardCashAdvance', valueDate) / daysInYear(valueDate)  condition CashAdvanceBalance > 0
//              DeferredCycleInterestAccrued  CyclePurchases * rate('CreditCardPurchase', valueDate) / daysInYear(valueDate)  condition GracePeriodStatus == 1 && CyclePurchases > 0
//              DeferredStatementInterestAccrued  StatementPurchases * rate('CreditCardPurchase', valueDate) / daysInYear(valueDate)  condition GracePeriodStatus == 1 && StatementPurchases > 0
//     Statement, in sequence: OverLimitFeeCharged price('card-over-limit-fee') condition Excess > 0 (gb cell); capitalise both accruals; StatementClose = max(0, Outstanding); AmountDueSet = StatementBalance;
//                MinimumPaymentSet = min(StatementBalance, max(StatementBalance * minimumPaymentPercent, minimumPaymentFloor) + Arrears) (F25); StatementPurchasesSet = CyclePurchases; DeferredStatementInterestSet = DeferredCycleInterest;
//                CyclePurchasesReset = 0; DeferredCycleInterestReset = 0
//     PaymentDue, in sequence after the Accrual rows (D6): PurchaseInterestCatchUp  DeferredStatementInterest + DeferredCycleInterest  condition AmountDue > 0 && GracePeriodStatus == 1;
//                DeferredCycleInterestReset = 0  condition AmountDue > 0 && GracePeriodStatus == 1;  DeferredStatementInterestReset = 0 (always);  GraceStatusUpdate  AmountDue <= 0 ? 1 : 0;
//                LateFeeCharged price('card-late-payment-fee') condition MinimumPaymentDue > 0;  MinimumPaymentOverdue  MinimumPaymentDue  condition MinimumPaymentDue > 0
//     Annual: AnnualFeeCharged price('card-annual-fee')
//   operations (workflows; each step reads the balances the previous step left, F13):
//     receive-payment: postTransaction Payment $amount; FeePayment min(abs(UnallocatedPayment), Fees); CashAdvancePayment min(abs(UnallocatedPayment), CashAdvanceBalance);
//       PurchasePayment min(abs(UnallocatedPayment), PurchaseBalance); ArrearsCleared min($amount, Arrears); AmountDueReduced min($amount, AmountDue); MinimumPaymentReduced min($amount, MinimumPaymentDue)
//       — every drain under whenCondition amount > 0; the order is the allocation rule a tenant edits
//     card-purchase (the cardPurchase workflow): whenCondition $merchantCategory == '6010' || $merchantCategory == '6011' → CashAdvance $amount; CashAdvanceFeeCharged price('card-cash-advance-fee', valueDate);
//       FeePayment min(abs(UnallocatedPayment), Fees); CashAdvancePayment min(abs(UnallocatedPayment), CashAdvanceBalance) (fees first, F23) — else Purchase $amount; PurchasePayment min(abs(UnallocatedPayment), PurchaseBalance)
//     card-refund: the same branch → CashAdvanceRefund min($amount, CashAdvanceBalance) — else PurchaseRefund min($amount, min(PurchaseBalance, CyclePurchases)),
//       StatementPurchaseRefund min($amount − the first, min(PurchaseBalance, StatementPurchases)); then RefundCredit for any remainder (F14)
//     close
//   limitIntegrations: facility { position: Outstanding, facilityType: CreditCard, direction: Raise, activationCheck: false }
//   properties: regulatoryRegime (required), servicingUnit, taxReportingRegime, paymentGraceDays (Integer, defaultExpression 25; 28 or more is a load diagnostic, F11),
//     minimumPaymentPercent (Decimal, defaultExpression 0.05), minimumPaymentFloor (Decimal, defaultExpression 200)
//   The sign convention follows the asset nature: a Debit raises a balance the customer owes; a test reads +12 000 on PurchaseBalance and −2 500 on UnallocatedPayment after a 2 500 payment lands.

// src/LedgerTM.Seeding.Provisioning/tenant-templates/packages/retail-bank/CardTypesSettings.yaml — credit: credentialKinds [Plastic, DeviceToken], fundingShape SingleAccount,
//   fundableAccountTypes [CreditCard], defaultControls atm allowed, deviceProvisioning StepUp, credentialLifeYears 3, maxActivePerOwner 2
// regimes/za-nca/retail-bank/RegulatoryLimitsSettings.yaml — { regimeCode: NCA, category: Interest, accountType: CreditCard, ceiling: rate('SARB Repo Rate', valueDate) * 2.2 + 0.10, basis: PerAnnumRate, citation: PLACEHOLDER — not sourced }
// src/LedgerTM.Accounts/Application/Queries/GetAccountDetail.cs — ADR-837's facility figure is returned for a Raise wire too, as `facilityHeadroom` (limit = the facility's amount, available = the oracle's available, excess, frozen) (F15, F29)

Bite 5 — no contracts of its own.

Bites

Bite Description Acceptance criterion Status
1 The facility symbols for a Raise wire with Excess from the wired position; the asset-nature reading of AccountAvailability; the merchant parameters on the card workflow; the activation check evaluating named rates against the regime ceiling; headline on a position type; the roll-up validator; facilityHeadroom a loan reads its own facility symbols; a purchase rate above the regime’s ceiling refuses activation; a roll-up wire with a missing leg is refused at load Pending
2 CreditCard on the retail template: positions, transaction types, the cycle, the due date, the payment workflow’s allocation, fees, arrears, GL, rates, prices, the Reg 42 row, the CreditCard facility type a statement closes with its balance, amount due and minimum; a payment allocates to the most expensive balance first; the minimum is the percentage, floored, and never more than the statement; a payment on the close day is in the statement; an overpayment waits as a credit and floors the due figures at zero Pending
3 The interest-free rule: deferred interest accrued daily, charged at the due date when a statement is not paid in full, forgiven when it is a statement not paid in full loses the interest-free period; a statement paid in full keeps it; a previous statement paid in full inside the window is not charged; a purchase between the close and the due date is caught up too; a payment on the due day counts; an unpaid minimum becomes arrears and a late fee Pending
4 The card: the credit card type, the oracle’s available for the asset type, the cash advance through the clearing post a tap is approved against the revolving limit; an ATM withdrawal posts as a cash advance; a waiting credit raises the available; a frozen or missing facility declines every tap; a cash category posts a cash advance, anything else a purchase; a waiting credit absorbs a cash advance, fees first Pending
5 The viewer’s headline figures; sample data and the probe; the guide article; the register rows an operator sees the cycle’s figures on the account; the detail and the oracle read one available; a card owing past its limit shows the excess Pending

Scenarios

Feature: a revolving credit card prices purchases on the days they were outstanding

# Bite 1
Scenario: a loan reads its own facility symbols
  Given a loan whose type wires a facility to its balance and whose customer holds a facility of 100 000 with 60 000 drawn
  When a scheduled row on the loan asks for the facility limit, the facility available and the excess
  Then they read 100 000, 100 000 and 0, and the headroom after the draw is 40 000
  And a loan drawn to 110 000 reads an excess of 10 000
  # Seen at: none

# Bite 1
Scenario: a roll-up wire with a missing leg is refused at load
  Given an account type whose facility is wired to a memorandum roll-up position
  When a transaction type on it moves a standard balance without moving the roll-up, or the roll-up sits in a summed balance group, or the grace days default to twenty-eight
  Then the template is refused at load, naming the row
  # Seen at: none

# Bite 1
Scenario: a purchase rate above the regime's ceiling refuses activation
  Given a regime whose ceiling for the credit card's interest is 30% and a tenant whose purchase rate type reads 32%
  When a clerk activates a credit card account under that regime
  Then the activation is refused, naming the rate and the ceiling
  And with the rate type at 20% the activation passes
  # Seen at: route:/accounts/{id}

# Bite 2
Scenario: a statement closes with its balance, amount due and minimum
  Given a credit card with purchases of 12 000 and a minimum of 5% floored at 200
  When the statement closes on 30 September
  Then the statement balance is 12 000, the amount due is 12 000 and the minimum payment is 600
  And a scheduled statement is issued for the cycle
  # Seen at: route:/accounts/{id}

# Bite 2
Scenario: a payment allocates to the most expensive balance first
  Given a credit card owing 150 in fees, 2 000 in cash advances and 12 000 in purchases, with 12 000 due
  When a payment of 2 500 arrives during the day
  Then fees fall to 0, cash advances to 0 and purchases to 11 650 at once
  And nothing remains unallocated, and the amount due reads 9 500
  # Seen at: route:/accounts/{id}

# Bite 2
Scenario Outline: the minimum is the percentage, floored, and never more than the statement
  Given a credit card with purchases of <purchases>
  When the statement closes on 30 September
  Then the minimum payment is <minimum>
  # Seen at: route:/accounts/{id}

  Examples:
    | purchases | minimum |
    | 12 000 | 600 |
    | 3 000 | 200 |
    | 150 | 150 |
    | 0 | 0 |

# Bite 2
Scenario: a payment on the close day is in the statement
  Given a credit card with purchases of 12 000
  When 2 000 is paid on 30 September and the statement closes that day
  Then the statement balance and amount due are 10 000 and the minimum 500
  # Seen at: route:/accounts/{id}

# Bite 2
Scenario: an overpayment waits as a credit and floors the due figures at zero
  Given a credit card owing 12 000 with 12 000 due and a minimum of 600
  When 13 000 arrives
  Then purchases read 0, 1 000 waits as a credit, the amount due and the minimum read 0, and nothing is outstanding
  # Seen at: route:/accounts/{id}

# Bite 3
Scenario: a statement not paid in full loses the interest-free period
  Given a statement of 12 000 closed on 30 September from a purchase on 10 September, due 25 October at 20%
  When 600 is paid on 20 October and the due date passes
  Then one catch-up interest posting of 302.46 is charged on 25 October, on the statement's purchases and the current period's, of which there are none
  And purchases accrue daily from 26 October on 11 400, and the due day itself is priced once
  # Seen at: route:/accounts/{id}

# Bite 3
Scenario: a statement paid in full keeps it
  Given a statement of 12 000 closed on 30 September, due 25 October
  When 12 000 is paid on 20 October and the due date passes
  Then no interest is charged on September's purchases
  And a purchase on 5 October accrues nothing through October
  # Seen at: route:/accounts/{id}

# Bite 3
Scenario: a previous statement paid in full inside the window is not charged
  Given an August statement of 5 000 paid in full on 20 September, and a September purchase of 12 000 on 10 September
  When 600 is paid on 20 October and the due date passes
  Then the catch-up on 25 October is 302.46, on the 12 000 alone
  # Seen at: route:/accounts/{id}

# Bite 3
Scenario: a purchase between the close and the due date is caught up too
  Given a statement of 12 000 closed on 30 September, due 25 October, and a purchase of 2 000 on 5 October
  When 600 is paid on 20 October and the due date passes
  Then the catch-up on 25 October is 325.48: forty-six rounded rows on the statement's purchases and twenty-one on the October purchase from its own date
  # Seen at: route:/accounts/{id}

# Bite 3
Scenario: a payment on the due day counts
  Given a statement of 12 000 closed on 30 September, due 25 October
  When 12 000 is paid on 25 October itself
  Then no catch-up posts and the interest-free period stays
  # Seen at: route:/accounts/{id}

# Bite 3
Scenario: an unpaid minimum becomes arrears and a late fee
  Given a statement with a minimum payment of 600 due 25 October and a late fee of 150
  When nothing is paid by the due date
  Then 600 is raised on arrears and the arrears raise moves no balance; the late fee of 150 is charged
  And the account reads one day past due on 26 October, and a close with the arrears still raised would ask for the 600 again
  And a payment of 700 on 27 October clears the arrears and reduces the balances by 700
  # Seen at: route:/accounts/{id}

# Bite 4
Scenario: a tap is approved against the revolving limit
  Given a credit card on a revolving account with a 20 000 facility owing 12 000 and a 500 hold
  When a merchant asks to authorise 7 000
  Then it is approved and the account's available reads 500, the headroom after what is owed and held
  And a further tap of 501 is declined for insufficient funds
  # Seen at: route:/cards/{id}

# Bite 4
Scenario: an ATM withdrawal posts as a cash advance
  Given a credit card on a revolving account with a cash-advance fee of 50
  When a clearing line of 1 000 from a cash merchant category posts at day-end
  Then the cash-advance balance is 1 000 and the fee of 50 is charged
  And interest accrues on the 1 000 from its transaction date at the cash-advance rate
  # Seen at: route:/accounts/{id}

# Bite 4
Scenario: a waiting credit raises the available
  Given a credit card on a revolving account with a 20 000 facility owing nothing and a 2 500 credit waiting
  When a merchant asks to authorise 22 000
  Then it is approved, and 22 501 would have been declined
  # Seen at: route:/cards/{id}

# Bite 4
Scenario: a frozen or missing facility declines every tap
  Given a credit card whose customer holds no credit card facility, or a frozen one
  When a merchant asks to authorise 100
  Then it is declined for insufficient funds and the available reads 0, never below
  # Seen at: route:/cards/{id}

# Bite 4
Scenario Outline: a cash category posts a cash advance, anything else a purchase
  Given a credit card on a revolving account
  When a clearing line of 1 000 at merchant category <mcc> posts at day-end
  Then it posts as <kind>, with the 50 fee only for a cash advance, and counts in the cycle's purchases only for a purchase
  # Seen at: route:/accounts/{id}

  Examples:
    | mcc | kind |
    | 6011 | cash advance |
    | 6010 | cash advance |
    | 6051 | purchase |
    | 5411 | purchase |

# Bite 4
Scenario: a waiting credit absorbs a cash advance, fees first
  Given a credit card with 1 200 waiting as a credit
  When a cash line of 1 000 posts
  Then the fee of 50 is paid from the credit first, the cash advance is paid in full, and 150 still waits
  # Seen at: route:/accounts/{id}

# Bite 5
Scenario: an operator sees the cycle's figures on the account
  Given a credit card whose statement closed with 12 000 due and 600 minimum
  When an operator opens the account
  Then the header shows the statement balance, the amount due, the minimum payment and the available limit
  # Seen at: route:/accounts/{id}

# Bite 5
Scenario: the detail and the oracle read one available
  Given a credit card on a revolving account with a 20 000 facility owing 12 000 and a 500 hold
  When the account's detail and the card's funding walk are each asked what is available
  Then both answer 7 500
  # Seen at: route:/accounts/{id}

# Bite 5
Scenario: a card owing past its limit shows the excess
  Given a credit card owing 21 500 on a 20 000 facility
  When an operator opens the account
  Then the limit reads 20 000, the available 0 and the excess 1 500
  # Seen at: route:/accounts/{id}

Scenario → test

Scenario Bite Project Class Method Probe
a loan reads its own facility symbols 1 LedgerTM.Tests.Component RaiseWireSymbolsTests a_loan_reads_its_own_facility_symbols —
a purchase rate above the regime’s ceiling refuses activation 1 LedgerTM.Tests.Component NamedRateCeilingTests a_named_rate_above_the_regimes_ceiling_refuses_activation — refusal
a roll-up wire with a missing leg is refused at load 1 LedgerTM.Tests.Component RollUpWireValidationTests a_roll_up_wire_with_a_missing_leg_is_refused_at_load — refusal
a statement closes with its balance, amount due and minimum 2 LedgerTM.Tests.Component CreditCardCycleTests a_statement_closes_with_its_balance_amount_due_and_minimum adr-838-server-probe.ts
a payment allocates to the most expensive balance first 2 LedgerTM.Tests.Component CreditCardCycleTests a_payment_allocates_to_the_most_expensive_balance_first adr-838-server-probe.ts
the minimum is the percentage, floored, and never more than the statement — 12 000 / 3 000 / 150 / 0 2 LedgerTM.Tests.Component CreditCardCycleTests the_minimum_is_the_percentage_floored_and_never_more_than_the_statement (a [Theory], one row per example) —
a payment on the close day is in the statement 2 LedgerTM.Tests.Component CreditCardCycleTests a_payment_on_the_close_day_is_in_the_statement —
an overpayment waits as a credit and floors the due figures at zero 2 LedgerTM.Tests.Component CreditCardCycleTests an_overpayment_waits_as_a_credit_and_floors_the_due_figures_at_zero —
a statement not paid in full loses the interest-free period 3 LedgerTM.Tests.Component CreditCardInterestFreeTests a_statement_not_paid_in_full_loses_the_interest_free_period adr-838-server-probe.ts
a statement paid in full keeps it 3 LedgerTM.Tests.Component CreditCardInterestFreeTests a_statement_paid_in_full_keeps_the_interest_free_period —
a previous statement paid in full inside the window is not charged 3 LedgerTM.Tests.Component CreditCardInterestFreeTests a_previous_statement_paid_in_full_inside_the_window_is_not_charged —
a purchase between the close and the due date is caught up too 3 LedgerTM.Tests.Component CreditCardInterestFreeTests a_purchase_between_the_close_and_the_due_date_is_caught_up_too —
a payment on the due day counts 3 LedgerTM.Tests.Component CreditCardInterestFreeTests a_payment_on_the_due_day_counts —
an unpaid minimum becomes arrears and a late fee 3 LedgerTM.Tests.Component CreditCardInterestFreeTests an_unpaid_minimum_becomes_arrears_and_a_late_fee adr-838-server-probe.ts
a tap is approved against the revolving limit 4 LedgerTM.Tests.Component CreditCardAuthorisationTests a_tap_is_approved_against_the_revolving_limit adr-838-server-probe.ts
an ATM withdrawal posts as a cash advance 4 LedgerTM.Tests.Component CreditCardAuthorisationTests an_atm_withdrawal_posts_as_a_cash_advance adr-838-server-probe.ts
a waiting credit raises the available 4 LedgerTM.Tests.Component CreditCardAuthorisationTests a_waiting_credit_raises_the_available —
a frozen or missing facility declines every tap 4 LedgerTM.Tests.Component CreditCardAuthorisationTests a_frozen_or_missing_facility_declines_every_tap — refusal
a cash category posts a cash advance, anything else a purchase — 6011 / 6010 / 6051 / 5411 4 LedgerTM.Tests.Component CreditCardAuthorisationTests a_cash_category_posts_a_cash_advance_anything_else_a_purchase (a [Theory], one row per example) —
a waiting credit absorbs a cash advance, fees first 4 LedgerTM.Tests.Component CreditCardAuthorisationTests a_waiting_credit_absorbs_a_cash_advance_fees_first —
an operator sees the cycle’s figures on the account 5 LedgerTM.Tests.Component CreditCardViewerTests the_account_detail_carries_the_headline_positions_and_the_facility_figure adr-838-server-probe.ts
the detail and the oracle read one available 5 LedgerTM.Tests.Component CreditCardViewerTests the_detail_and_the_oracle_read_one_available adr-838-server-probe.ts
a card owing past its limit shows the excess 5 LedgerTM.Tests.Component CreditCardViewerTests a_card_owing_past_its_limit_shows_the_excess_and_nothing_available —

UI-surface sweep

Swept src/ui-apps/bank/src for CreditCard, GracePeriodStatus, AmountDue, MinimumPayment, Memorandum, headline:

Footprint

Feature projects touched: 4 — LedgerTM.Accounts, LedgerTM.Seeding.Provisioning, LedgerTM.Seeding.ZaRetail.Samples, ui-apps

Contracts types: 4 named, 1 changed by this ADR

Files reading each changed type: 1 types

Domain events touched: 0 Aggregates touched: 0

Methods at CRAP 30+ in changed files: 7 (unit coverage, cached at main 1a4b6f460)

Warnings

At land: 61 files touched, 44 predicted, 32 unplanned. LedgerTM.Tests.Component/Accounts/AccountsComponentFixture.cs, LedgerTM.Tests.Component/Cards/CurrentAccountExcessTests.cs, LedgerTM.Tests.Component/Cards/LatePresentmentValueDatingTests.cs, LedgerTM.Tests.Component/Seeding/SampleCardsSeedTests.cs, LedgerTM.Tests.Unit/Accounts/AccountTypeIconAndFamilyTests.cs, LedgerTM.Tests.Unit/Accounts/RollUpWireValidatorTests.cs, LedgerTM.Tests.Unit/Seeding/preset-snapshots.txt, reachability-baseline.txt, src/LedgerTM.Accounts/Application/Limits/RegulatoryLimitGuard.cs, src/LedgerTM.Accounts/Application/Queries/AccountStatementCloseReader.cs, src/LedgerTM.Accounts/Application/Settings/ExternalIntegrationsValidator.cs, src/LedgerTM.Accounts/Application/Settings/PaymentGraceValidator.cs, src/LedgerTM.Accounts/Application/Settings/RollUpWireValidator.cs, src/LedgerTM.Accounts/Application/Workflows/WorkflowInterpreter.cs, src/LedgerTM.Accounts/Bootstrapper.cs, src/LedgerTM.Accounts/Domain/Valuation/FacilitySymbols.cs, src/LedgerTM.Cards/Application/DayEnd/PostCardClearingBatch.cs, src/LedgerTM.Contracts/Accounts/IAccountStatementCloseReader.cs, src/LedgerTM.Scripting/Parsing/ExpressionSymbolScan.cs, src/LedgerTM.Seeding.Provisioning/tenant-templates/countries/gb/retail-bank/PriceSettings.yaml, src/LedgerTM.Seeding.Provisioning/tenant-templates/countries/gb/retail-bank/RateSettings.yaml, src/LedgerTM.Seeding.Provisioning/tenant-templates/countries/za/retail-bank/PriceSettings.yaml, src/LedgerTM.Seeding.Provisioning/tenant-templates/packages/investment-house/LookupTypesSettings.yaml, src/LedgerTM.Seeding.Provisioning/tenant-templates/packages/microlender/LookupTypesSettings.yaml, src/LedgerTM.Seeding.Provisioning/tenant-templates/packages/personal-lender/LookupTypesSettings.yaml, src/LedgerTM.Seeding.Provisioning/tenant-templates/packages/retail-bank/BalanceGroupsSettings.yaml, src/ui-apps/bank/src/__tests__/features/accounts/generic/__snapshots__/account-panel-rails.characterization.test.ts.snap, src/ui-apps/bank/src/__tests__/features/accounts/generic/overdraft-tiles.test.tsx, src/ui-apps/bank/src/__tests__/features/accounts/tenant-template-icons.test.ts, src/ui-apps/bank/src/features/accounts/generic/overdraft-tiles.tsx, src/ui-apps/bank/src/lib/api.ts, src/ui-apps/bank/ui-review/adr-uat/flows/adr-837-server-probe.ts

Land batches

One land, the whole ADR; reseed: true. Every bite starts after ADR-836 and ADR-837 have landed (F1): the type’s YAML names their integrations, direction and symbols.

Notes

Changed during the plan grill

Phase A (27 questions) and the plan grill (14 press points) ran 2026-10-02; the operator’s standing instruction was to take the recommendations. F6–F20 record what moved. The two largest: allocation is the payment workflow’s steps, because a triggered row runs only inside the day-walk (grill 1); and the catch-up is deferred interest accrued daily into memorandum positions, because a history-replaying function could not be reproduced by a re-walk (grill 2), which also removed positionDays, daysBetween and the schedule-occurrence dates from the ADR. Also moved: the activation check binds the rate lookup and the regime ceiling binds on a named rate (grill 7, 8; ADR-837 meets both first); Excess is computed from the wired position at ADR-837’s three sites (grill 11); the arrears raise is one two-legged transaction (grill 10); fee categories are Fee (grill 9); Outstanding sits in its own balance group and every new row has a master row (grill 13); the due date leaves the header (grill 13); every bite waits for ADR-836 and ADR-837 (grill 12). Held: the Outstanding roll-up over a list of positions, the credit card type’s shape, the Reg 42 row’s placeholder citation.

Phase B (five authors, 2026-10-02): F21–F30 — 302.46 by rounding; the current period’s purchases in the catch-up, said plainly; a waiting credit is spendable and the cash branch drains fees first; the annual fee a year after opening; the due figures fall by the whole payment and a missed minimum joins the next; a close posts even at zero; the roll-up invariant validated at load; a named rate that cannot be priced refuses activation; headline on the type’s binding; the detail’s figure is the oracle’s under facilityHeadroom; days past due from the aged debtor; twelve scenarios the authors wrote as unhappy paths join bites 1 to 5.

Landing notes