# Operational Workflow # Operational Workflow | Field | Value | | --- | --- | | Distribution | WCT English — OpenC5ISR | | Product | OpenC5ISR | | Release | 0.15.1 | | Deployment | `openc5isr-en.wallacecorptech.com` | | Source | `/srv/wct/releases/OpenC5ISR-v0.15.0` | | Evidence | Static release scan | | Source fingerprint | `63d2b1097707e25d666401cdc6362e395968600a40a08690210cd8c0b75fbf50` | | Status | Generated baseline — human review required | > **Verification boundary:** This page combines platform design guidance with static evidence from the release. It does not prove that every detected interface is enabled, reachable, secure, or operational in the deployed environment. ## Reference workflow | Step | Action | Outcome | | --- | --- | --- | | 1 | Collect | Acquire observations, messages, tracks, files, imagery, video, spectrum and telemetry. | | 2 | Exploit | Extract useful features, metadata and operational signals at the source or edge. | | 3 | Associate | Relate observations to entities, locations, missions, cases, tasks and prior evidence. | | 4 | Share | Publish governed information through OpenBus, APIs, files and collaboration services. | | 5 | Collaborate | Build shared understanding through COP, chat, annotations, knowledge and reviews. | | 6 | Task | Convert understanding into assigned, acknowledged, executing and completed work. | | 7 | Preserve | Retain evidence, provenance, decisions and replayable operational history. | ## Why this matters The workflow is deliberately cross-application. A sensor product should not terminate at a viewer; it should be associable with a track, shareable with a release group, usable as evidence, able to trigger analytics, and convertible into a task. The platform is strongest when these transitions are explicit and auditable. --- ## Maintainer Notes Add human-reviewed deployment notes, corrections, decisions, screenshots, and links here. Content outside the generated block is preserved on future runs.