Authority
What actually governs this task? A model can cite a fact and still use the wrong authority.
Architecture
Models don’t naturally know which source controls, which remembered fact is still current, whether something was discussed or implemented, whether missing evidence means “no,” or whether an apparently completed action actually happened.
Those things have to exist somewhere around the model.What actually governs this task? A model can cite a fact and still use the wrong authority.
What belongs here now? Availability is not the same thing as relevance or permission.
What should survive the session without turning every remembered thing into permanent truth?
What has actually happened? Discussion, approval, implementation, verification and release remain separate.
What did the system really do, in which environment, against which source state?
What can be claimed now, and what is still only plausible, proposed or inferred?
Context governance
Continuity has a reason to bring prior context forward. Separation has a reason to keep neighboring context out. Too much inherited context contaminates the work; too little destroys useful continuity.
The architecture has to preserve both motives without pretending they are the same problem.
Context Governance record →The site shows the concerns and visible operating consequences. Private routing, inheritance, activation, relationship grammar and full runtime topology are not published.