Scheduled payments screen (auto-debit, installment plans, standing orders): a list of upcoming payment rows stamped with a date, the total debit amount, and — where relevant — a breakdown of principal / interest / fee components.

• Third parallel Table-family record with a new schema. After Table (type × no. of columns × icon) and Table - Transaction (type × no. of columns × icon, peso content), Scheduling introduces another axis shape: a single type enum that gates a fixed 0 / 2 / 4 detail count. Three records, three different schemas for the same underlying "rows of label/value pairs" idea. C1 · Layer Structure & Naming
• type values embed the detail count in a sentence. Values are "no display amount", "2 amounts display", "4 amounts display" — natural-language strings that bake the count into the property. Should be an integer detailCount: 0 | 2 | 4, or — better — replaced by a data-driven details: [Pair] array that accepts any length. C2 · Variant & Property Naming
• No native mobile primitive matches the layout. Payment schedules on iOS and Android render as list cells (List / LazyColumn) — a date header, an accessory amount, and optional secondary label/value rows. The 360px fixed grid is a desktop pattern; on phone width the two-cell detail row already crowds at the 12px type scale used here. C4 · Native Mappability
• No tap, pressed, or disabled states. A scheduled payment row is typically tappable — to view, edit, or cancel the scheduled entry — and can be visually disabled (past / cancelled / skipped). None of that coverage exists. C5 · Interaction State Coverage
• Peso sign is a raster image asset. Primary amount's currency prefix is an <img> pointing at a Figma-hosted bitmap, same remote URL as Table - Transaction. Detail amounts, meanwhile, use the literal string "PHP" — two different currency-prefix treatments in one component. C6 · Asset & Icon Quality
• Code Connect mappings not registered. Blocked until the family consolidation decision lands — Code Connect for Scheduling would just duplicate the Inline Text mapping. C7 · Code Connect Linkability

• Remove Table - Scheduling from core DS; publish as a recipe on Table's page composing Inline Text rows. Same guidance as Table - Transaction. Recipe reads: "For scheduled-payment lists (auto-debit, installments, standing orders), compose a date / primary-amount header row with EBInlineText, then stack additional EBInlineText rows for breakdown details inside a Generic Transaction Card or native List cell." Eliminates 3 variants, a raster peso asset, and the mixed ₱/PHP prefix inconsistency. Family
• Collapse the Table family (Table + Table - Transaction + Table - Scheduling) into one data-driven row primitive. If the family is retained for wider surfaces, publish a single EBTableRow with role: .header | .content and a columns: [Column] array where each column carries its own format: .text | .amount | .date. Scheduling's date-header + amount + detail-grid becomes: one row with two columns (date / amount), followed by N rows with detail pairs. Collapses 18 family variants into 2 role variants × data. Family
• Rename type values to integers, or drop the property. If Scheduling is kept, rename to detailCount: 0 | 2 | 4 (no sentence fragments in property values). If merged into Inline Text / Table's data-driven row, drop the property entirely — the count is inferred from the details array. Rename
• Unify the currency prefix treatment. Primary amount uses a raster peso glyph; detail amounts use the literal string "PHP". Pick one. Preferred: the Unicode ₱ glyph (U+20B1) everywhere, rendered in the row's type style — drop the raster asset and drop the "PHP" literal. Alternative: ship a vector peso icon (icon/currency/peso-sm) for the primary line and an optional "PHP" prefix for breakdown values, wired up as real tokens / slots. Asset
• Compose each detail cell from Inline Text. The component already matches Inline Text's label + value shape (main/table/color/label-preamble on top, main/table/color/label below). Instance-swap to Inline Text so the tokens consolidate under main/inline-text/* and state / a11y improvements flow through to every consumer. Composition
• Add row interaction states if Scheduling stays. A scheduled-payment row is tappable — add State=Pressed and State=Disabled variants (disabled = past / cancelled with muted labels and a strike or tag). Without these, every consumer re-invents the tap target. State
• Document scheduling semantics. If Scheduling is kept, add guidance on which amounts belong on the primary line (total debit) vs. breakdown cells (principal / interest / fee / tax). Prevents the component from being used as a generic 3-amount row on non-scheduling surfaces. Docs