Passed Is Not In Force

Colorado passed a law about automated decisions. Its own page on the legislature’s website gives it an effective date in May 2026.

Read further down that page. The duties begin on 1 January 2027. That second date is the one deciding what you can ask for.

Both are true. They answer different questions. Nothing on the page marks which is which.

That gap is the subject here. Not what your rights are. Which of them have started.

Artificial Intelligence (AI) is why the gap matters now. Legislatures are writing fast. Start dates drift a year out. Miss that and you demand something nobody owes you yet.

What rights do you actually have when software is involved in your care?#

Three, in rough order of how solid they are.

Notice. A few legislatures now require that a person know when a machine is involved in their care. Texas is the clearest case and its duty is live today.

Your own data. This one is older and it comes from health privacy law. It is the strongest of the three, because it does not depend on anything passed recently.

An explanation, after a decision goes against you. This is the newest of the three and the weakest. It is also the one most likely to appear in the press as though it already exists everywhere.

Notice what is missing. No general right to refuse the machine. No general right to a human reviewer. Those live in proposals, and in coverage of proposals.

What is absent is always harder to see than what is there. That is true of a rulebook, and it is true of the assumption never said aloud.

The data right deserves a longer look, because it is the one people underuse. It is older than any of this and it does not turn on whether software was involved at all. A record held by a doctor, a hospital or an insurer carries that right whether a machine touched it or not.

What it does not reach is the harder half. A wellness app you downloaded yourself is usually outside it, and so is much of what a watch on your wrist collects all day. The right follows the holder of the record rather than the sensitivity of the information, which is not how most people assume privacy works.

That mismatch is worth carrying into every conversation about health data. The question is never how personal the information feels. The question is who is holding it and under what arrangement they took it.

So one of the three is solid. One is real in some places. One is mostly on its way.

That ranking is the useful part. It decides which conversation is worth having this week. It decides which is worth a diary note for next year.

Treat all three as equally real and you will push hardest on the weakest one. You will get nowhere. That is a hard way to learn a distinction nobody printed for you.

Who grants each right, and why are they different lawmakers?#

Different governments, working at different speeds, on different problems.

Health privacy is federal and old. It was built for medical records held by doctors, hospitals and insurers, long before an app on a wrist existed. That age is a strength and a limit at once, because settled law was drawn around a world with different edges.

Disclosure is a state matter and it is new. A handful of legislatures decided a person should know when they are talking to a machine, and each one wrote its own version of that.

The right to an explanation is mostly state, mostly recent, and mostly not started. Three lawmakers. Three clocks.

Three lawmakers, three clocks. That is why no single answer covers your position, and why a national article about AI rights is nearly always describing somebody else’s state.

Like three roadworks on one street, each crew holds its own permit and its own finish date. The street is passable or not depending on which stretch you need today.

The three clocks matter more than the three rights, because a right you cannot use yet is a plan. A reader who knows only the rights will argue confidently about something that does not start until January 2027.

A reader who knows the clocks will ask for the one thing available today and get it. That is a smaller ambition. It is also the one that moves a case forward.

The gap between those two readers is not knowledge of the law at all. It is a habit. Check when a thing starts, then decide what it means.

So stop asking what the law says. Ask which law, whose, and from when.

Why is almost none of this federal?#

Because Washington has not passed a general rule, and the states did not wait.

The gap is not an accident of drafting. It is what happens when a technology arrives faster than a national legislature moves and slower than fifty state legislatures can each try something.

So the map is patchy by construction. One state requires disclosure while its neighbour requires nothing, and a third has passed a detailed act whose duties start next year.

That patchiness has a specific cost for an older reader, and it is not the obvious one. The cost is not that the protections are weak, but that they are invisible from where the person is standing.

Picture a woman reading a coverage decision on a screen. The tool behind it may sit under a disclosure rule. It may sit under nothing. It may sit under a rule that has not started.

The screen looks identical in all three cases. That is the blind spot when behaviour outruns the public account.

There is a second effect, and it lands on the people least able to absorb it. A reader with a lawyer in the family finds out. A reader without one does not.

Nothing in the design intends that. It falls out of a patchwork anyway. Rights that require research are rights distributed by who has time to research, and that is not how anyone would write it down if they were writing it down honestly.

So the practical skill is not knowing the rules. It is knowing how to find out which ones reached you.

What is the difference between a rule that exists and one that is in force?#

A rule that exists has passed. A rule in force is one somebody must obey today.

Legislatures separate those two on purpose. A body needs time to write rules, an industry needs time to build, and a start date a year out is the ordinary way to give it. Nothing sinister happens in that gap. It is simply a gap, and almost nothing written for the public marks it.

Colorado shows it plainly. Its bill page for that act records the governor signing on 14 May 2026. The session law carries that same day as its effective date.

Read the legislature’s own summary of that same act. The developer duties begin on 1 January 2027. The attorney general must write clarifying rules by that same date.

So one page carries a 2026 date and a 2027 duty. Neither is an error. The page is answering a question about the legislature, not a question about you.

The earlier Colorado act tells the other half of the story. It was enacted in 2024 and replaced before its requirements ever applied to anyone. A law can be passed, reported on for two years, and never bind a soul.

Texas is the contrast worth holding. House Bill 149, the Texas Responsible Artificial Intelligence Governance Act, took effect on 1 January 2026, and if you are in Texas its health care disclosure duty is live now.

Its wording repays a slow reading, and the first thing in it is a limit. The general duty to speak before or at the moment of interaction falls on a governmental agency. Not on every business running a chatbot.

For health care the act names a different party and a different clock. The provider of the service or treatment must give the disclosure to the person, or to that person’s representative, no later than the day the treatment is first provided. In an emergency the duty does not disappear. It moves, to as soon as reasonably possible.

Then comes the line that closes the usual escape route. The disclosure is required whether or not it would be obvious to a reasonable person that a machine is involved. Somebody clearly anticipated the argument that an obvious robot needs no introduction, and shut it.

That is what a live duty reads like when you meet one. It names who must speak, when they must speak, and what excuse will not work.

One state gives you a duty you can point to today, and its neighbour gives you a duty with a date on it. The difference is a calendar.

What can you ask for today, and what is still only proposed?#

Sort every claim into three boxes.

• In force now.
• Passed, starts later.
• Proposed only.

The confusion I keep seeing in this subject is two of those boxes poured into one. In the coverage I read, it happens constantly, and rarely on purpose. A bill is news the day it passes, and its start date is not.

Box one, you can ask now. A refusal is a matter you can take somewhere.

Box two, you can prepare. Knowing a duty starts in January is worth a diary note. It is also worth asking a provider what they plan to do about it.

Box three, you can have an opinion. Nothing more. Acting on a proposal as though it binds someone is how a reasonable person loses an argument they should have avoided.

Like a shop with a sign saying opening soon, the sign is real, the shop is real, and you still cannot buy anything.

Write the sorting down. A short list beats a strong memory. It survives an argument.

Where do you check whether a law that covers you has started?#

At the legislature’s own page for the bill, reading two dates rather than one.

The first date is the status line, where the bill is signed by the governor, chaptered, and given an effective date. That date records the act becoming law, and it is the one everybody quotes.

The second date sits inside the summary or the text, in a phrase like starting on, applies to, or on and after. That is the date deciding whether anyone owes you anything. Look for it.

When the two differ, the later one governs your position. Write both down, with the day you looked, because a page accurate this month can describe a duty starting next year and it will not flag the gap.

Then check who the duty falls on. Many of these acts bind a developer or a deployer rather than the clinic in front of you. A right that binds a company you have never heard of is exercised differently from one that binds your provider. Ask which, before you ask anyone for anything.

Naming the responsible party is the whole exercise, the same way it is when a business decides who answers for an agent. Somebody owns it. Find out who.

Keep a note of what you find. Bill number. Both dates. The day you looked.

That note is worth more than it looks. Pages get rewritten. Summaries get shortened. A duty that starts next January will be described very differently in December, and your note is the only fixed point you will have.

One more habit, and it costs nothing. When a law does start, check it again. Start dates move. Legislatures amend their own acts, courts pause them, and agencies miss the deadline for writing the rules that make a duty workable.

Colorado is the proof of that too. Its earlier act was enacted, reported on for two years, and replaced before it ever bound anyone. Anybody who filed that away in 2024 as settled was carrying a wrong answer for two years and had no reason to suspect it.

So treat every date as provisional. Not because the system is dishonest. Because it is slow, and slow things change shape while you are not watching.

None of this asks a reader to become a lawyer or to follow a legislature. It asks for one date, written down, with the day you found it beside it. That is a smaller discipline than most people expect from a subject this loud.

Find the date. Write it down. Check it again later.

A caregiver with a bill number and a phone can do all of this in twenty minutes. It is not legal work. It is reading two dates on one page and believing the later one.