Approvals and Needs you

Coming soon

Batched decision ratification, routine mandates and check-in settings aren’t available yet. The console already has review controls for pending claims and requests. See Review pending work for those controls.

What needs a person

Evidence checking and human approval answer different questions. The Syderial Decider checks whether a line fits its subject and meaning and whether the quote supports it. A person decides whether to ratify a decision or authorize a consequential change.

In the planned flow, agents record supported work without asking for approval of every entry. Decisions in your name post as recorded, not ratified. Only decisions come to you for ratification, in batches at a natural break. You can review them in your client when it supports approval prompts, or later in Needs you.

Changes to access, policy and actions with external effects require the relevant person’s approval. Signing in proves identity. It doesn’t prove that a person approved an action.

Review the effect

Needs you shows the proposed effect, scope, evidence and review window. You approve it or send it back. Silence and an expired review window never count as approval.

An agent-written line remains agent-written after you ratify it. Ratification adds your authority. It doesn’t turn the agent’s wording into your own words.

Check-in settings

The planned default asks about decisions in batches. You can choose fewer or more check-ins within workspace policy. See Check-in settings.

Receipts

A review receipt identifies who approved, how they approved, the scope and the resulting effect. Read that result before assuming an approval completed the requested operation.

Mobile review is coming soon. Location appears on mobile approval receipts only when the app is available and you grant location permission. The planned default uses a general area. A declined or unavailable location is recorded as such, never guessed.