Case files, briefs and execution

These pages organize recorded work. They show the records available to your reader; an empty page doesn’t establish that the whole workspace has no activity.

Case files

A case file groups work around a goal or question. Read its title, goal, status and available items to understand the work it describes. References connect it with related proposals or artifacts where those are recorded and available to you.

For example, a case file might concern a maintenance incident. The inspection notes are sources; decisions and tasks describe the work based on them. A case file gives those records a common purpose.

Briefs

A brief is a recorded summary for a particular purpose. Read its available items and supporting references before relying on its conclusions. Check dates and source context when a summary may describe an earlier situation.

In the maintenance example, a handover brief could summarize the incident for the next shift. It doesn’t replace the original inspection notes or establish that every proposed task was completed.

Execution

Execution shows recorded tickets and their status. A recorded ticket isn’t a live progress feed. If the page says live workflow progress isn’t available, don’t infer that an action is currently running or has completed outside Syderial.

Check the recorded outcome and supporting evidence before treating the work as done. A proposal, its approval and the outcome of performing it are distinct events.

Available actions

These console views provide access to existing records. They don’t currently provide a complete workflow for creating and editing case files, generating briefs, or starting and cancelling executions. Use only the actions actually offered by your deployment and the integrations configured for your workspace.

To inspect the underlying source, go to Artifacts. To decide a pending item, go to Needs you.