01
Assessment
ErrorCategory, ErrorSeverity, and ErrorCaptureSource describe independent properties and never substitute for one another.
ARKTELOS / PRODUCTS / ARK ERROR MANAGER
One application boundary for failures that need a decision.
Ark Error Manager classifies impact, sanitizes diagnostics, and chooses reporting, user presentation, and recovery without injecting a manager into every feature.
FIT / EVALUATION
Confirm the boundary before adopting the package.
- Platform
- Dart + Flutter
- Primary package
- ark_error_manager
- Current release
- 1.1.0
- Responsibility
- Assesses application-level failures and coordinates sanitized reporting, user presentation, and recovery through one owned policy path.
- Use when
- Use it when root runtime boundaries need consistent failure decisions and external reports must cross an explicit trust boundary.
- Does not own
- It does not replace local validation, feature-specific recovery logic, logging infrastructure, or the source of an error.
Shortest evaluation path
- 01
Confirm the responsibility and deliberate boundary above.
- 02Open tutorials →
- 03
01 / MODEL
One ordered process turns a failure into an action plan.
Root Dart and Flutter boundaries submit an ErrorOccurrence to one manager. It assesses the failure, gathers bounded context, applies policy, sanitizes the external report, and coordinates independent actions in a stable order.
- ErrorOccurrence
- Assessment
- Policy
- ErrorReport
02 / BOUNDARIES
Raw incident data stays inside the application boundary.
02
Action plan
Reporting, user presentation, and recovery are selected independently in one typed ErrorActionPlan.
03
Trust boundary
ErrorReporters receive only a sanitized ErrorReport; the raw ErrorIncident remains local to ErrorPresenter and ErrorRecoveryController.
03 / DOCUMENTATION
Follow the path from capture to a safe decision.
Begin with ownership and assessment, build a root Dart or Flutter integration, and review ErrorReporter security as a separate trust boundary.