A compliance-review agent has a short, stable set of non-negotiable rules (about one page) that must apply to every response, plus a 300-page library of jurisdiction-specific guidance of which any given review uses a small part. A proposal moves both into on-demand Skills to minimize context. What is the best assessment?

Answer: C — Partly correct: the guidance belongs on demand, but the mandatory rules belong in a cached, always-loaded prefix

The guidance is large and mostly irrelevant to any one review, so progressive loading fits. The rules are small, stable and mandatory, so they belong in the always-loaded core, where caching makes them cheap and their application doesn't depend on the model choosing to load them. (a) makes hard rules optional. (b) brings back the 300-page monolith. (d) is an expensive, slow-to-update change that removes auditability of the guidance in use.