orchestrator: Add the ReportSink seam for the Report effects - #447
Open
chrysh wants to merge 1 commit into
Open
Conversation
The four Effect::Report* variants have no consumer seam. Add a non_exhaustive Report enum and a single ReportSink::report instead of a method or a trait per variant, so a new report is one variant rather than a trait break and a sink routes only what it recognises. report returns nothing: a report names something that already happened, so an undeliverable one costs information, not containment, and reporting stays off the driver's fail-closed path. A sink that needs to know it dropped one records that on its own side. Every payload stays Copy and lifetime-free, like the effects these mirror; a report names its component and nothing more. The unit impl drops them, for a board with no management side to tell. Trait only, composing a sink into the board follows. Assisted-by: Claude:claude-opus-5
chrysh
force-pushed
the
add-report-sink
branch
from
August 27, 2026 20:44
e957f93 to
fafe830
Compare
chrysh
marked this pull request as ready for review
August 27, 2026 20:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft: the management path behind the sink is not designed yet, so this adds the seam only.
The four
Effect::Report*variants have no consumer seam. This adds a#[non_exhaustive]Reportenum and a singleReportSink::reportinstead of a method or a trait per variant, so a new report is one variant rather than a trait break and a sink routes only what it recognises.reportreturns nothing: a report names something that already happened, so an undeliverable one costs information, not containment, and reporting stays off the driver's fail-closed path. Payloads stayCopyand lifetime-free, like the effects they mirror.The seam lives in
driver/src/board.rsrather thanorchestrator-capabilities, becauseReportcarries aComponentIdand that crate is a dependency-free leaf. Same split the driver already makes forVerifier.Composing a sink into the board follows in the next PR.
References 9elements#3.