4
New override fields documented
Before Claude runs
Enforcement point
Spectare now lets you decide exactly which content components are allowed to appear on your site, and you can narrow or widen that control by audience and stage. The admin card for each component now shows its eligibility state without requiring you to open it. A component with no audience rule and no stage rule carries an OPEN badge on its collapsed card, so you can scan the full list and confirm that an ungated component is a deliberate choice rather than a setting you forgot.
When a component has guidance text that contains an unenforced restriction, its card carries an amber badge. The badge clears the moment a matching rule is added to back the instruction. That distinction matters: guidance is a suggestion Claude may follow or not, while a rule is enforced on every assembly before Claude runs. The amber badge is the admin's way of showing you which of your instructions are guaranteed and which are still hopes.
The component override reference has also been extended. Alongside the existing enabled, guidance, and zone fields, four additional fields are now documented. The audiences field restricts a component to named segments and is enforced before Claude sees the registry. The stages field replaces any Spectare default stage window with one you have chosen. The maxCount field caps how many of the component a single assembly may contain. The size field forces the rendered width for a workspace.
One distinction worth understanding: Spectare ships its own default stage windows for some components, and during exploration it may test a component outside those defaults, because a default nobody explicitly set is a hypothesis the data is allowed to challenge. A rule you set is never crossed, exploring or not. That is the line between the two.
This is one atom from the Spectare content library. Spectare assembles the right atoms for each visitor in real time, based on who they are and how they arrived.