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.

Ark Error Manager incident gateFailures from root runtime boundaries pass through ordered assessment and policy; only a sanitized report crosses the external boundary.ZONEFLUTTERISOLATEASSESSCONTEXTPOLICYSANITIZEPRESENTRECOVERREPORTAPPLICATION BOUNDARY

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.

Ark Error Manager modelAn ErrorOccurrence passes through assessment, context, and policy in order; a sanitized ErrorReport reaches reporters while the local ErrorIncident remains available to presentation and recovery.OCCURRENCEINTAKEASSESSCLASSIFYCONTEXTPOLICYSANITIZEPRESENTRECOVERREPORTRAW INCIDENT / APPLICATION-LOCAL

02 / BOUNDARIES

Raw incident data stays inside the application boundary.

01

Assessment

ErrorCategory, ErrorSeverity, and ErrorCaptureSource describe independent properties and never substitute for one another.

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.

ARKTELOS

Purpose-built engineering systems for software that has to hold.