Effective dating
Which version of the rule applied at that moment?
Rules, prices and facts change, and regulated industries have to answer for the past. Effective dating is how a system knows which version applied on a given day, so you can recalculate, explain or defend an old decision.
What it is
Every rule, rate and fact carries the dates it was valid, and every calculation uses the version that was true when the event happened, not when you run it. Corrections that reach back in time ("retro" changes) are routine, not edge cases.
If your system only knows the current value, it can't answer the questions auditors, customers and courts actually ask.
Where you'll see it
| Industry | Where the date matters |
|---|---|
| Payroll | Retro pay after a backdated raise; a tax rate that changed mid-year |
| Telco | Fee changes; was this sender approved when the message went out? |
| Insurance | Policy amendments that apply from a past date |
| Payments | Fee schedule changes; network rules with announced effective dates |
| Healthcare | Coverage that started or ended in the middle of treatment |
Questions to ask in week one
- Which values change over time, and do we keep the history?
- When something is corrected after the fact, do we recalculate the past?
- Do we record both when something happened and when we learned about it?
- Which upcoming rule changes already have an effective date?
- Can we reproduce a calculation exactly as it ran on a past date?
The trap
Overwriting values in place because "we only care about now". The first backdated correction, audit or dispute proves otherwise. Two dates beat one: when it was true, and when we recorded it.
In the Field Guides
AI agents: orchestration platforms
One of the two extra ideas: the retirement clock is a hidden operating cost. Published policies back it; the cost itself isn't public. Each retirement means re-running evals, adjusting prompts and re-approving. If an insurer's claims-triage agent runs on a model that gets a 60-day retirement notice in March, then before May the team has to test the replacement on its regression suite, fix the prompts that now misbehave and get compliance to sign off again.
| Lab or cloud | Published notice (Oct 2026) | Dated example |
|---|---|---|
| OpenAI | GA models 6 months or more; previews about 2 weeks | GPT-5 and o3 snapshots: deprecated 2026-06-11, off 2026-12-11 |
| Anthropic | At least 60 days; "not sooner than" dates about 12 months out | Claude Sonnet 4.5: deprecated 2026-09-30, off 2026-11-30 |
| Previews 2 weeks or more; -latest aliases swap each release | An embedding model deprecated 2026-01-14 | |
| Mistral | No formal period; 24 days to about 4 months observed | Small 2.0: 2025-11-06 to 2025-11-30 |
| Meta, xAI | Not researched as first-party APIs; Meta's are mostly open-weight | On Azure: grok-3 retired 2026-05-01, some Llama 3.x deployments 2026-06-13 |
| Microsoft Foundry | 18 months for most GA models, 12 for Anthropic's and Mistral's | Standard deployments auto-upgrade; no extensions |
| AWS Bedrock | From 2026-09-07: Legacy for 6 months or 45 days | Inactive accounts may lose access after 15 days |
The same model can retire on different dates at the lab and at each cloud, so a platform inherits the shortest notice in its catalogue. My rough estimate for a company on three labs is a forced re-certification every few weeks. Prices and token counts move too: Google's Gemini 3.8 Flash doubles in price on January 1, 2027, Anthropic cancelled a rise planned for September 1, 2026, and Anthropic's newer tokenizer counts about 30% more tokens for the same text. Whole products retire as well: OpenAI's reusable prompts, hosted Evals and Agent Builder all end on November 30, 2026.
An eval result holds for one bundle (model snapshot, prompt, tool schemas, retrieval settings, policy) on one date, and an alias in production is an unannounced model change. Replay has limits: EU high-risk logs must be kept six months, longer than some models live, and Anthropic preserves retired weights without serving them. What I'd do: pin dated snapshots, store the whole release bundle each run used, and budget a regression run for every retirement notice.
AI coding agents: writing, reviewing and shipping code
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| npm revokes all classic publishing tokens | December 9, 2025 | In force |
| Codex moves to token-based credits | April 2, 2026 (all Enterprise from April 23) | In force |
| Copilot individual plans train on interaction data by default | April 24, 2026 | In force, opt-out |
| Amazon Q Developer closes to new signups | May 15, 2026 | In force |
| Copilot AI Credits replace premium requests | June 1, 2026 | In force; annual plans keep the old model until renewal |
| EU Cyber Resilience Act vulnerability and incident reporting | September 11, 2026 | In force |
| Ninth Circuit rejects the DMCA output claim in Doe v. GitHub | September 16, 2026 | Licence claims still pending |
| GPT-5.5 retires from Codex | October 14, 2026 | Upcoming |
| OpenAI's models leave Cursor (as reported) | November 12, 2026 | Upcoming |
| EU Product Liability Directive covers software | December 9, 2026 | Upcoming |
| Amazon Q Developer IDE plugins lose support | April 30, 2027 | Upcoming |
| EU Cyber Resilience Act main obligations | December 11, 2027 | Upcoming |
Configuration is dated too: Cursor's cloud agents get their secrets at start, and an MCP tool definition can change after you approved it. And promotions end on dates that users read as price rises: GitHub's extra credits stopped on September 1, 2026.
AI evals and observability: how teams measure AI quality
An eval result holds for one bundle, one judge and one dataset version on one date. An alias in production is an unannounced model change, and a judge called by alias is an unannounced change to your ruler. Datasets age too: a test set built before a policy change passes the agent confidently on the old policy.
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Anthropic's Claude Sonnet 4.5 retires (deprecated September 30) | November 30, 2026 | Upcoming |
| OpenAI's hosted Evals goes read-only, then shuts down | October 31 and November 30, 2026 | Upcoming |
| OpenAI's GPT-5 and o3 snapshots shut down (deprecated June 11) | December 11, 2026 | Upcoming |
| Gemini 3.8 Flash list price doubles, so a judge on it doubles in cost | January 1, 2027 | Upcoming |
| LangSmith changed how base traces are counted and billed, per a third-party tracker | July 21, 2026 | Live |
| EU AI Act high-risk duties, including testing against preset metrics | December 2, 2027 | Upcoming; moved from August 2, 2026 |
Notice periods set the rhythm: at least 60 days at Anthropic, at least six months for OpenAI's generally available models, as little as two weeks for some Google previews, and Microsoft's Foundry upgrades standard deployments automatically when a model retires. A team on several providers inherits the shortest clock in its stack. Changes can break the call itself: Anthropic's models from Claude 4.7 onward return an error if temperature or top_p is set to a non-default value. Benchmarks age as well; SWE-bench Verified lasted about 18 months from launch in August 2024 to OpenAI dropping it.
AI governance and model risk
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| EU AI Act prohibited practices | February 2, 2025 | In force; no fines found |
| California rules on automated hiring decisions | October 1, 2025 | In force |
| SR 26-2 replaces SR 11-7 for US bank model risk | April 17, 2026 | In force; not enforceable; excludes generative and agentic AI |
| Colorado insurance AI rules, auto and health compliance | July 1, 2026 | In force |
| Disparate impact removed from Reg B | July 21, 2026 | In force |
| EU Article 50 transparency duties | August 2, 2026 | In force |
| Connecticut: relying on AI is no defense to discrimination | October 1, 2026 | In force |
| EU marking grace ends; new prohibition on generated intimate images | December 2, 2026 | Upcoming |
| Colorado's replacement AI law; California automated-decision compliance | January 1, 2027 | Upcoming; Colorado may slip |
| OSFI E-23 for Canadian banks and insurers | May 1, 2027 | Upcoming |
| Connecticut pre-decision notices in employment | October 1, 2027 | Upcoming |
| EU high-risk duties for Annex III uses (credit, hiring, insurance pricing) | December 2, 2027 | Upcoming; moved from August 2, 2026 |
| EU high-risk duties for regulated products | August 2, 2028 | Upcoming; moved from August 2, 2027 |
Dates here slip often: Colorado's moved twice, the EU's high-risk date by 16 months, and the Commission's guidelines on classifying high-risk systems, due by February 2, 2026, came out as a draft in May. Vendors' retirement dates are often "not sooner than" dates.
Agent identity and delegated access: how AI agents act for people
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Agent identity products generally available | AWS AgentCore October 2025; Auth0 November 2025; Google April 2026; Microsoft Entra around May 2026; Okta for AI Agents April or May 2026, Agent SSO August 2026 | Live |
| Cloudflare folds signed agents into verified bots | July 1, 2026 | Live |
| Microsoft requires Agent 365 or E7 for agent Conditional Access | July to August 2026 | Live |
| MCP specification deprecates dynamic client registration | July 28, 2026 | Live |
| EU AI Act transparency duties (Article 50) | August 2, 2026 | Live |
| Web Bot Auth's working-group draft | September 1, 2026 | Draft |
| NIST IR 8587 on protecting tokens | September 2026 | Final |
| ID-JAG draft expires unless renewed | November 22, 2026 | Upcoming |
| EU Product Liability Directive transposed | December 9, 2026 | Upcoming |
| EU AI Act high-risk duties | December 2, 2027 | Moved from 2026 |
| PSD3 and the Payment Services Regulation apply | Around 2028 | Provisional |
When a vendor says "MCP support", ask which version: June 2025, November 2025 and July 2026 differ on how clients register, and dynamic registration can't be removed before July 2027 under the project's 12-month rule, by my reading.
B2B payments: cross-border payouts
Quotes expire within seconds or hours, pay dates follow the destination's calendar, and the rules themselves keep moving. India's export realisation period (the time an exporter has to bring the money home) went from 9 to 15 months in November 2025 and back to 9 in June 2026. An Indian software contractor who invoiced a US client in March 2026, when the period was 15 months, and planned around it had to check which rule covered that invoice once it went back to 9.
New rules under FEMA, India's foreign exchange law, notified in January with 15 months, were amended on September 22 to 9 (12 for rupee invoices), days before taking effect on October 1, 2026.
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| US orders barring three Mexican institutions | October 20, 2025 | Live; one eased for its liquidation |
| Swift: MT and ISO 20022 coexistence ends | November 22, 2025 | Live |
| India: FEMA export and import rules, 9 months | October 1, 2026 | In force |
| Brazil: eFX rules (Resolution BCB 561) | October 1, 2026 | In force |
| India: rupee drawing arrangement direction update | October 1, 2026 | Wording only |
| UK: Confirmation of Payee direction expiry | November 1, 2026 | PSR proposes removing it |
| Swift: fully unstructured addresses rejected | November 14, 2026 | Upcoming; rejections possible |
| FedGlobal ACH to Mexico: last forward items | November 20, 2026 | Upcoming |
| GENIUS Act (US stablecoins) | By January 18, 2027 | Upcoming; no final rules |
| EU instant payments and VoP: non-euro banks; payment and e-money institutions | January 9 to July 9, 2027 | Upcoming |
| FATF R.16 in national law | By the end of 2030 | Upcoming |
I'd store the rate, the rule version and the calendar each payout used, since a quote can last seconds and, as India showed, a regulation can change twice before it starts.
B2B payments: order to cash
A sale's cost and rights depend on the day each thing happened. Prices change between PO and shipment, promotions carry date ranges that deductions cite months later, limits change mid-order, and Visa US interchange changes each April and October.
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Canada: criminal interest rate 35% APR; business advances over $10,000 capped at 48% up to $500,000 | January 1, 2025 | Live |
| US bankruptcy amounts reset ($8,575 minimum to sue a business over a preference) | April 1, 2025 | Live |
| ASU 2025-05 credit-loss expedient | Years beginning after December 15, 2025 | Live for calendar-2026 year-ends |
| Visa interchange: enhanced-data "Product 3" rates; Level II gone except fuel | April 18, 2026 | Live |
| CFPB Section 1071 rule revised; still excludes trade credit and factoring | Effective June 30, 2026; compliance January 1, 2028 | Live |
| Federal Prompt Payment interest 4.75% | July 1 to December 31, 2026 | Live; resets every six months |
| ACH credits (not same-day) available by 9 a.m. | September 18, 2026 | Live |
| Canada: paper remittances no longer exchanged between banks for bill payments | December 1, 2026 | Upcoming |
| Canada: Real-Time Rail, first participants | Q4 2026 | Upcoming |
| Same Day ACH limit $1M → $10M | September 17, 2027 | Upcoming |
| Canada: paper PADs no longer exchangeable | December 1, 2028 | Upcoming |
| Visa and Mastercard merchant settlement | Preliminary approval June 2026 | Final approval pending |
Store the price, promotion, terms, fee schedule and card product that applied to each order, invoice and payment at the time, rather than a pointer to today's version, because deduction fights turn on which version applied. If a snack maker ran a 10% promotion in March and a retailer deducts it from a June payment, checking the deduction means pulling the promotion terms as they stood in March.
B2B payments: procure to pay
A payment's cost, tax treatment and rights depend on the day it moved. Terms can start their clock at the invoice date, invoice arrival, goods arrival or month end, depending on the contract. Bank details have effective dates too, since many buyers hold payments to newly changed details. And 1099 thresholds follow the payment date rather than the invoice date. A freelance designer paid $1,500 over 2026 is under the new $2,000 threshold, so no 1099-NEC, though the same total paid in 2025 needed one.
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Fedwire moves to ISO 20022 | July 14, 2025 | Live |
| Rebate schedule amended in one state cooperative card contract | October 1, 2025 | Live; rebates change by contract amendment |
| FedNow network limit $1M → $10M | November 2025 | Live |
| Lynx fully on ISO 20022 | November 22, 2025 | Live |
| 1099-NEC and most 1099-MISC thresholds $600 → $2,000 | Payments after December 31, 2025 | Live; indexed to inflation from 2027 |
| 1099-K back to more than $20,000 and 200 transactions | Proposed regulations January 8, 2026 | Law live; regulations proposed |
| Nacha fraud monitoring, phases 1 and 2 | March 20 and June 22, 2026 | Live |
| Visa US interchange table | April 18, 2026 | Live; Visa updates in April and October |
| First-Class stamp price rises | July 12, 2026 | Filed by USPS |
| Prompt Payment interest 4.75% | July 1 to December 31, 2026 | Live; resets every six months |
| Non-same-day ACH credits available by 9 a.m. | September 18, 2026 | Live |
| Canada: Real-Time Rail, first participants | Q4 2026 | Upcoming |
| Same Day ACH limit $1M → $10M | September 17, 2027 | Upcoming |
| Nacha R90 return code for sanctions | March 17, 2028 | Upcoming |
| Visa and Mastercard merchant settlement | Preliminary approval June 9, 2026 | Final approval pending |
So I'd store the terms, tolerance, tax threshold and bank details as they stood when each invoice was approved and each payment released, rather than a pointer to today's version.
B2B payments: real-time payments and open banking
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| RTP limit raised to $10 million | February 9, 2025 | Live |
| EU banks must send instant payments and run Verification of Payee | October 9, 2025 | Live |
| FedNow limit raised to $10 million | November 2025 | Live |
| RTP fraud reporting covers induced payments | March 31, 2026 | Live |
| UPI merchant fee above ₹2,000 | October 15, 2026 | Reported in the press |
| UK Confirmation of Payee direction expires | November 1, 2026 | Removal proposed |
| Canada's Real-Time Rail, first participants | Q4 2026 | Targeted |
| EU Payment Services Regulation, Parliament vote | December 14, 2026 | Indicative |
| RTP fraud reports due within two business days | March 1, 2027 | Upcoming |
| EU payment and e-money institutions must send instant payments | April 9, 2027 | Upcoming |
| Same Day ACH limit raised to $10 million | September 17, 2027 | Upcoming |
| EU Payment Services Regulation applies | Around 2028 | Provisional |
The US open banking rule has no date at all: the rewrite by the CFPB, the US consumer finance regulator, has sat with the White House's regulatory review office since August 6, 2026, and every original compliance date is stayed. A UK reimbursement claim is judged by the rules in force on the payment date, so I'd store the rule version each payment ran under.
B2B payments: spend management
Every rate in an expense has an effective date, and the IRS mileage rate has two. It rose from 72.5¢ to 76¢ a mile on July 1, 2026, the first mid-year change since 2022, but only for miles driven and paid on or after that date: a June trip reimbursed in July stays at 72.5¢. The IRS per diem year starts October 1; through December, an employer on the high-low method uses old or new rates, consistently for everyone.
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Canada: small-merchant interchange cuts, consumer credit only | October 19, 2024, for five years | Live; commercial cards not covered |
| Visa validates Level 3 data | October 17, 2025 | Live |
| No deduction for employer-convenience meals | Amounts after December 31, 2025 | Live |
| CRA kilometre allowance $0.73 / $0.67 | January 1, 2026 | Live; 2027 rates due in January |
| Nacha: wage credits must say "PAYROLL" | March 20, 2026 | Live |
| Visa US interchange table | April 18, 2026 | Live; updates in April and October |
| IRS business mileage 72.5¢ → 76¢ | July 1, 2026 | Live; 2027 rate due mid-December |
| IRS high-low per diem $319 / $225 → $329 / $230 | October 1, 2026 | Live |
| GSA standard per diem $181 ($113 lodging, $68 meals and incidentals) | October 1, 2026 | Live |
| NJC travel meals $123.20 plus $25 incidentals a day | October 1, 2026 | Live |
| Visa and Mastercard merchant settlement | Preliminary approval June 9, 2026 | Final approval pending |
| CFPB Section 1071 small-business data | Compliance January 1, 2028 | Revised rule live; card coverage to confirm |
I'd key every rate to the expense date and the jurisdiction, and US mileage to the payment date too, and store the rate actually applied rather than a pointer to today's table.
B2B payments: stablecoins and blockchain payments
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Brazil: stablecoin payments abroad treated as FX operations | February 2, 2026 | In force |
| Canada's Stablecoin Act | March 26, 2026 | Law; regulations expected in 2027 |
| MiCA's transition period for crypto firms ends | July 1, 2026 | Live |
| Brazil: no stablecoin settlement for eFX providers | October 1, 2026 | In force |
| OCC's final GENIUS rule | November 2026, the OCC's stated target | Upcoming |
| GENIUS Act takes effect | January 18, 2027 at the latest | Upcoming |
| UK stablecoin regime in force | October 25, 2027 | Upcoming |
| US exchanges may offer only permitted or qualifying foreign coins | July 18, 2028 | Upcoming |
Prices move as well: Tron cut its energy price on August 29, 2025, changing what a USDT transfer costs, and Circle's docs say to check its cross-chain fees weekly. I'd store the coin, chain, fees, route and rule version each payment used.
Card issuing: launching a card program
Most of the money in a card program depends on dates someone else sets. These are the ones I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| Visa US interchange table | April 18, 2026 | Live; Visa usually updates in April and October, and no October 2026 table was out by October 6 |
| Visa rules edition | April 18, 2026 | Live; next edition October 24, 2026 |
| Visa: prepaid cards may expire after up to 10 years | Cards issued from July 25, 2026 | Live |
| UK safeguarding rules for e-money firms | May 7, 2026 | Live |
| Canada's retail payments law (RPAA) | September 8, 2025 | Live |
| Durbin threshold | Assets at December 31; cap from July 1 of the next year | Every year |
| Replacement for the 2023 third-party risk guidance | Comments due November 10, 2026 | Proposed |
| Fed's proposal to lower the Durbin cap | Proposed November 2023 | Not final |
| FDIC custodial-account recordkeeping | Proposed September 2024 | No date |
Contract dates matter as much: notice windows (180 or 365 days), minimum-fee step-ups, exclusivity periods and the right to terminate if the bank loses its Durbin exemption, which The Bancorp's filing says some of its agreements allow.
A neobank whose bank sits at $9.6 billion in assets in September should be modelling two scenarios for the following July. If the bank ends the year above $10 billion, debit interchange drops to the cap within about six months, and the contract decides whether the program can move first.
Cloud security (CNAPP): posture, workloads and permissions
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| PCI DSS 4.0's future-dated requirements (51 of the 64 new ones) | March 31, 2025 | Live |
| NYDFS Part 500 final phase: MFA for any individual, asset inventory | November 1, 2025 | Live |
| DORA designates 19 critical providers, including AWS, Google Cloud, Microsoft and Oracle | November 18, 2025 | Live |
| AWS's new Security Hub, with exposure findings and attack paths | December 2, 2025 | Live |
| FedRAMP Consolidated Rules for 2026 published | June 25, 2026 | Mandatory January 1, 2027 |
| UK designates AWS, Google Cloud, Microsoft and Oracle as critical | July 13, 2026 | Live |
| Snowflake's MFA phase 3: people can no longer sign in with a password alone | August-October 2026 | Rolling out |
| Sentencing in the Snowflake attack case | October 27, 2026 | Upcoming |
| FedRAMP's vulnerability detection and response rules required | December 7, 2026 | Upcoming; grace period to March 7, 2027 |
Some changes have no date yet: SEC Item 1.05 is under pressure to be rescinded, the EU proposed NIS2 amendments on January 20, 2026, and the UK's Cyber Security and Resilience Bill is still in Parliament. And since December 2025, "CSPM" also names an AWS product, the old Security Hub.
Identity and trust: KYB, KYC and ongoing monitoring
Ownership changes over time, lists change daily, and the rules changed a lot in 2025 and 2026.
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| US banks may collect only the last four SSN digits and get the rest from a third party | June 27, 2025 | Live, optional |
| FinCEN's guidance easing suspicious activity reporting | October 9, 2025 | Live |
| Canada: report ownership mismatches on high-risk federal companies | October 1, 2025 | Live |
| UK: identity checks for new directors and owners | November 18, 2025 | Live; transition ends November 17, 2026 |
| US: banks re-verify a company's owners only at the first account, or when in doubt | February 13, 2026 | Live |
| Canada: maximum FINTRAC penalties 40 times higher | March 26, 2026 | Live |
| FinCEN's new AML program rule | Proposed April 2026 | No final rule yet |
| US ownership reporting ends for US companies (final rule) | August 14, 2026 | Live |
| Digital credentials accepted as ID for account opening (US) | September 8, 2026 | Live |
| EU digital identity wallets due in every member state | December 24, 2026 | Upcoming; many will be late |
| EU AMLR and its ownership and refresh rules | July 10, 2027 | Upcoming |
| EU banks must accept the wallet on request | Around December 2027 | Upcoming |
| EU Company Certificate | July 31, 2028 | Upcoming |
Inside your data, store dates on ownership, list versions and clocks. Canada's register records when someone became and stopped being a significant owner, and your graph needs valid-from and valid-to dates too. A sanctions screen is only as good as the list version it ran against. A US suspicious activity report is due 30 days from initial detection of the activity, and examiners argue about that detection date.
Picture the landscaper selling 30% of itself to a new investor in May. If your graph only holds the current owners, you can't answer the question an examiner will ask in December: who owned it when you paid out in June? Examiners keep coming back to what you knew and when, so date every ownership link, list version and review.
Login and access for apps: authentication and authorization
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| PCI DSS 4.0.1: MFA for all access to cardholder data | March 31, 2025 | Live |
| NIST SP 800-63-4 final | July 31, 2025 | Live |
| New York's financial regulator: MFA for anyone accessing any system | November 1, 2025 | Live |
| WebAuthn Level 3 becomes a W3C Recommendation | August 25, 2026 | Live |
| Snowflake: password sign-ins need MFA, final phase | August-October 2026 | Rolling out |
| ID-JAG draft (basis of MCP's enterprise extension) expires unless renewed | November 22, 2026 | Upcoming |
| OAuth 2.1 targeted for submission to the IETF's steering group | December 2026 | Upcoming; still a draft |
| EU digital identity wallets due in every member state | December 24, 2026 | Upcoming |
| Clerk bills SCIM separately from SSO | January 1, 2027 | Upcoming |
| HIPAA rule making MFA required for health data | July 2027, reportedly | Proposed |
Inside the product, dates sit on SAML certificates, token lifetimes, invitations, recovery codes and the gap between someone's last day and the moment the app learns of it. A questionnaire written in 2026 may still ask for 8-character passwords with complexity rules NIST dropped in 2025, so ask which version a requirement comes from.
Models and inference: what AI runs on
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| EU AI Act duties for general-purpose model providers | August 2, 2025 | In force |
| California SB 53 for frontier developers | January 1, 2026 | In force |
| H200-class chips to China move to case-by-case review | January 13, 2026 | In force; China limits imports |
| EU AI Office enforcement powers, including fines | August 2, 2026 | In force; first requests September 1 |
| Claude Sonnet 4.5 retires | November 30, 2026 | Upcoming |
| EU Product Liability Directive covers software | December 9, 2026 | Upcoming |
| OpenAI GPT-5 and o3 snapshots retire | December 11, 2026 | Upcoming |
| Gemini 3.6-3.8 Flash prices double | January 1, 2027 | Upcoming |
| New York RAISE Act | January 1, 2027 (some sources say July 1) | Upcoming |
| Older general-purpose models must comply with the AI Act | August 2, 2027 | Upcoming |
Some dates float. Retirement dates are "not sooner than" (Anthropic, AWS) or "earliest possible" (Google), and introductory prices can end or be made permanent: Anthropic kept Sonnet 5's and cancelled a rise planned for September 1, 2026. DeepSeek even prices by time of day.
Observability: metrics, logs and traces
Everything in observability is measured over a window. Alerts evaluate over minutes, SLOs over a rolling 28 or 30 days, burn rates over 5 minutes to 3 days, and billing over hours, months and contract years. Retention clocks usually start when data arrives, so late mobile or batch data can land in the wrong window.
The meaning of a field has a date. OpenTelemetry's semantic conventions are versioned, and renames break things quietly: database spans renamed db.system to db.system.name in version 1.33.0 in 2025, and dashboards keyed on the old name stopped matching.
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| PCI DSS 4.0's future-dated requirements, including automated log review | March 31, 2025 | Live |
| Atlassian Opsgenie end of sale | June 4, 2025 | Done; support ends April 5, 2027 |
| California's cybersecurity audit rules, covering audit-log management | January 1, 2026 | Live; first certifications from April 1, 2028 for the largest businesses |
| OpenTelemetry graduates in the CNCF | May 21, 2026 | Done |
| OMB M-26-14 replaces M-21-31 for US federal logging | May 22, 2026 | Live |
| Datadog's AI SRE moves to AI credits | Around June 2026 | Live |
| FedRAMP 20x rules launched | June 25, 2026 | Mandatory January 1, 2027 |
| OpenTelemetry Governance Committee election results | October 30, 2026 | Upcoming |
| EU Data Act bans switching and egress fees | January 12, 2027 | Upcoming |
| HIPAA Security Rule update | Proposed January 2025 | Final rule targeted around July 2027; uncertain |
Take the dispatch company's commitment renewing in March. Overage from a cardinality spike in January sits in the usage history the vendor brings to the renewal, so a mistake fixed in a week can still raise next year's commitment.
Phone numbers, messaging and voice
The price of a message depends on the day it was sent, and sometimes on which carrier memo you read.
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| T-Mobile 10DLC SMS fee up by about half, to just under half a cent | January 2026 (sources cite the 15th, 19th and 29th) | Live |
| AT&T SMS fee up to about a third of a cent, both directions; MMS (picture message) to about a cent | April 1, 2026 | Live |
| Verizon SMS fee of just under half a cent, sent messages only | May 1, 2026 | Live |
| Verizon 10DLC and toll-free SMS fee raised again, to about half a cent | October 1, 2026 | Reported by one aggregator; Twilio's October 2026 list shows it |
| WhatsApp charges for service replies and in-window utility templates | October 1, 2026 | Live |
| FCC "revoke-all" opt-out rule | Waived to January 31, 2027 | Rewrite scheduled for an FCC vote on Sept 30, 2026; outcome unconfirmed |
| Auth+ for all brands except sole proprietors | January 21, 2027 | Reported by providers |
Meta runs a cleaner calendar: WhatsApp prices change only on January 1, April 1, July 1 or October 1, with at least a month's notice for a rate change and six for a change of pricing model. A template is charged at whatever category it holds when sent.
The FCC splits dates in two. A rule can be "effective" while compliance waits for OMB (the White House office that approves paperwork burdens) and a Federal Register notice, as the SIM-swap and NG911 rules did. The date to track is the compliance notice.
Picture a logistics company sending 50,000 delivery texts a month, mostly to T-Mobile users. The January 2026 change added a fraction of a cent to each, which is roughly $75 a month on a contract nobody reopened. Multiply that across every customer and every carrier, and you need to know which fee applied to which message.
I'd store two dates on every approval and every fee: when it took effect and when you learned about it. Finance and carriers will both ask what applied when a given message went out.
Voice AI: real-time voice agents
Dates I'd keep on a calendar as of October 2026:
| Change | Effective | Status (Oct 2026) |
|---|---|---|
| FCC: AI voices are "artificial" under the TCPA | February 8, 2024 | In force, and applied to calls made before it in pending suits |
| California: prerecorded calls must say if the voice is artificial | January 1, 2025 | In force |
| Maine: AI chatbots, spoken ones included, need a clear notice | September 2025 | In force |
| Carriers must sign caller ID with their own token | September 18, 2025 | In force |
| Carriers blocking on analytics must return a specific SIP code (603+) | March 25, 2026 | In force |
| EU AI Act: tell people they're talking to AI; mark synthetic audio | August 2, 2026 | In force |
| FCC comment deadline on letting political AI calls reach mobiles without consent | October 19, 2026 | Upcoming |
| EU: marking deadline for audio systems already on the market | December 2, 2026 | Upcoming |
| Google's Gemini Flash and Flash speech models double in price | January 1, 2027 | Upcoming |
Some dates float. Deepgram's streaming prices are "limited-time promotional rates" with no end date, so I'd budget at the regular rate. Google's Live API is a preview with no deprecation guarantees, and some OpenAI model names point at a default snapshot that can change, so I'd pin dated snapshots where offered. The FCC's 2024 proposal to require AI disclosure at the start of calls hasn't been adopted, and Canada's regulator opened its own review in June 2026.
Field Guides are learning notes, not legal or compliance advice. Rules and fees change; check the cited primary sources before you act on anything here.