Publication Scope — FlowRail

Controlled staging recording.

The API failed.

The audience changed.

That shouldn't be a fallback.

FlowRail checks the code your agent proposes against

your design requirements,

before that code is saved.

Here,

the rule is simple.

Publish this report to one document,

for its owner,

without notifications.

If that fails,

save it locally.

Our controlled candidate tries a shared board instead.

Same service.

Different people.

And that board queues notifications.

FlowRail flags the fallback before Claude's file write

completes.

The file is still absent.

The unsafe candidate never lands.

Claude corrects the code.

After verification,

the file is saved.

We run that exact version: failed publication keeps

the report local,

without a board post.

Every check stays connected to the design.

This write is allowed,

but three requirements still need evidence from the service.

Failure doesn't expand permission.

Keep your requirements connected to the code your

agent writes.

FlowRail.