Your agent, not ours
PINKTURKEY assembles and sends the context; the coding agent you already use does the work. Nothing here asks you to change how you write code.

When PINKTURKEY assembles the context for a run, it sends the objectives, requirements, decisions and constraints that are currently effective for that scope. Superseded records do not enter the context. That is the guarantee, and it is the reason the rest of the system exists.
The two usually pull against each other. Here they do not, because the records that are dropped are the ones that stopped applying.
PINKTURKEY assembles and sends the context; the coding agent you already use does the work. Nothing here asks you to change how you write code.
The agent receives what binds for the scope it is working in, not the whole corpus. Fewer tokens, fewer wrong turns, and a shorter path to the part that matters.
A superseded decision is not sent. Neither is a proposal nobody accepted. What was withheld is recorded next to what was sent, so a result can be explained later.
What the agent received, what it returned and what it contradicted are kept together. A surprising output has a traceable cause rather than a lost one.
The system reports what currently binds and where records contradict each other. Which one should win is a judgement, and it stays yours.
An unexamined record cannot constrain an agent. A record has to be reviewed before it is allowed to shape a run — a rule that costs something up front and pays for itself the first time it prevents a bad input.
Withholding a record is a decision the system made on your behalf, so it is recorded as one and is there for you to check.
That is the whole claim. Everything else in the product exists so that this one holds.