ZED Coordination Engine v1.4, Release Notes

Released: July 28, 2026 | Type: Feature release | Breaking changes: None | Minimum upgrade time: 0 minutes (non-breaking)

This release focuses on three operational improvements that operators have requested since the v1.3 launch: a restructured mission briefing format that reduces the time required to process daily approvals, more granular approval threshold configuration, and improved handling of cross-agent sequencing dependencies.

What Changed in v1.4

New Mission Briefing Format

The most visible change in this release is the restructured daily intelligence briefing. Operator feedback from early deployments consistently identified one pain point: the previous briefing format presented approvals, status updates, and informational items in a single continuous list. Operators with five or more active agents were spending more time parsing the briefing than reviewing the actual decisions within it.

The v1.4 briefing introduces a three-tier structure:

Tier 1. Immediate Decisions. Actions that agents are holding for operator approval before execution. These are presented first, with the full context needed to approve or redirect without leaving the briefing view. The expectation is that these are reviewed and actioned before the operator's first major commitment of the day.

Tier 2. Same-Day Review Items. Actions that agents will execute unless redirected by end of business. These include outreach sequences, content publication schedules, and operational monitoring escalations that do not require immediate approval but benefit from a daily review window.

Tier 3, FYI Items. Completed actions, in-progress monitoring, and low-priority status updates. These do not require operator action but keep the operator informed of what the workforce is doing.

At the top of the briefing, a one-line status panel now shows each active agent's current operational state: running, waiting for approval, paused, or escalated. Operators can identify at a glance which agents need attention before reading the detail.

The new format reduces average briefing review time in tested deployments by approximately thirty-five percent, primarily because operators can process the decision queue in sequence rather than scanning a mixed list for items requiring action.

Improved Approval Threshold Configuration

Approval thresholds have historically been configurable at the agent level: you set a threshold for SAL, and all SAL actions above that threshold require approval. This works for simple deployments but becomes imprecise as operators develop confidence in specific agent behaviors while maintaining tighter oversight in others.

v1.4 introduces action-type granularity: thresholds can now be set per agent per action category. For SAL, operators can configure:

  • Initial outreach to new prospects: require approval (recommended for new deployments)
  • Follow-up sequences to accounts that have already responded: execute automatically
  • Proposal preparation: require approval
  • Meeting coordination with approved accounts: execute automatically
  • Account research and pipeline updates: execute automatically

This allows an operator who has reviewed sixty days of SAL outreach and is confident in the quality to set initial outreach to automatic while keeping proposal preparation at a higher scrutiny level. The approval queue shrinks to the actions that actually warrant human review rather than everything above a single dollar or action threshold.

Similar action-type breakdowns are available for MAX (content types), BEN (financial alert types), KAI (operational escalation types), and JOY (customer communication types). The configuration interface is available in each agent's settings panel under Approval Thresholds.

Cross-Agent Dependency Resolution

ZED's dependency management has been improved to handle explicitly configured cross-agent sequencing. Previously, dependencies between agents were inferred from operating brief context, ZED would attempt to identify when one agent's output was a prerequisite for another's action. This worked for common patterns but produced incorrect sequencing in complex multi-agent deployments.

v1.4 introduces explicit dependency declaration in mission briefs. Operators can now specify rules such as: SAL prospect research must complete before MAX account-based content is produced, and MAX account-based content must be ready before SAL account-based outreach executes.

ZED enforces these dependencies as hard constraints. If an upstream agent's output is not yet complete, the downstream agent's action is held, and the reason is surfaced in the briefing (Tier 1 if time-sensitive, Tier 2 otherwise).

For operators running SAL and MAX in coordinated account-based programs, this is a significant improvement. The previous behavior occasionally produced outreach before the corresponding content assets were ready. v1.4 eliminates this by making the sequencing explicit and enforced.

Performance Improvements

Briefing compilation has been optimized for full-workforce deployments (five or more active agents). The compilation process ran serially in previous versions, each agent's status was compiled in sequence before the briefing was assembled. v1.4 compiles agent statuses in parallel, reducing briefing generation time by approximately forty percent for full-workforce configurations.

Operators running smaller deployments (one to three agents) will see modest improvement. The performance gain is most pronounced for operators with five or more agents and high daily activity volume.

Deployment Notes

This is a non-breaking update. No configuration changes are required for existing deployments. The new briefing format activates automatically on the next briefing cycle after update. Existing approval threshold configurations are preserved and remain fully functional, action-type granularity is additive and optional.

Recommended configuration review: If you have been using agent-level approval thresholds for six or more weeks and have established confidence in specific agent behaviors, this is a good time to review your threshold configuration against the new action-type granularity options. The goal is reducing approval overhead on agent behaviors you trust while maintaining scrutiny on higher-stakes actions.

For deployments using SAL + MAX in coordinated programs: The explicit dependency configuration is available in ZED's coordination settings under Mission Dependencies. Review your current brief for implicit sequencing assumptions and codify them as explicit dependencies to improve reliability.

Known Issues

One edge case has been identified in the dependency resolution update: explicit dependencies that reference an agent currently set to Paused state are not resolved gracefully in this release. ZED holds the downstream action correctly but surfaces an ambiguous status message. A clarifying patch will be included in v1.4.1.

Workaround: If a dependency references a paused agent, reactivate the agent before the dependency is triggered, or temporarily remove the explicit dependency from the mission brief and manage the sequencing manually until the patch is applied.

What's Coming in v1.5

v1.5 development is in progress. Planned for the next release:

  • Mission Replay filtering improvements: Filter replay by agent, action type, date range, and approval status. The current Mission Replay interface shows all activity in chronological sequence; v1.5 will make specific activity retrievable.
  • Agent performance trend reporting: ZED's weekly briefing will include trend metrics per agent, output volume, approval rate, escalation frequency, giving operators a longitudinal view of how each agent's performance is calibrating over time.
  • Brief update workflow improvements: Updating an operating brief currently requires replacing the document in full. v1.5 will introduce section-level brief updates, allowing operators to revise specific sections without recreating the full brief.

FAQ

Does the new briefing format change how approvals are submitted? No. The approval interface is unchanged, actions are approved or redirected in the same way as before. The new format changes how items are organized and presented, not how they are actioned.

I have existing action-type threshold configurations I set manually in agent settings. Will they be migrated? Agent-level thresholds set in previous versions are preserved and displayed in the new action-type configuration interface as the default threshold applied to all action types for that agent. You can leave them as-is (behavior is identical) or refine them with action-type granularity.

Are explicit dependencies required, or is inferred sequencing still active? Both. Inferred sequencing continues to operate as a fallback. Explicit dependencies take precedence where defined. If you define an explicit dependency between SAL and MAX, that explicit dependency governs their sequencing. Everything else continues to be inferred from brief context.

Key Changes Summary

  • Briefing reorganized into Immediate / Same-Day / FYI tiers with one-line agent status panel
  • Approval thresholds now configurable per agent per action type
  • Cross-agent dependencies now declarable explicitly in mission briefs
  • Briefing compilation ~40% faster for full-workforce deployments

[View the command center →](/command-center) | [Read about ZED's coordination model →](/intelligence/why-zed-changes-multi-agent-coordination) | [Previous release: v1.3 →](/intelligence/platform-update-v1-3) | [Back to Intelligence →](/intelligence)