ARKTELOS / PRODUCTS

Purpose-built products. Shared engineering principles.

Each ArkTelos product owns a concrete responsibility and carries its own architecture, documentation, lifecycle model, and release history.

Choose by responsibility

AVAILABLE NOW

Six systems, one consistent product model.

Every product has a defined responsibility, a public package surface, and a complete path from overview to architecture, tutorials, recipes, package references, and releases.

CHOOSE BY RESPONSIBILITY

Start with the boundary the system needs to own.

Choose the problem you need to isolate. The selector points to the product with the matching responsibility and states its boundary.

PRODUCT OVERVIEWS

Open the product model that matches your task.

Each overview explains the model, responsibility boundaries, adoption fit, and the shortest evaluation path.

EXECUTION / LIFECYCLE

UseCase Forge

Policy-driven command execution with explicit concurrency, cancellation, output, history, and diagnostics.

usecase_forge1.1.0

DATA / REPOSITORY

Ark Data Layer

Typed DataSource contracts, Repository mechanics, observable business data, and explicit lifecycle ownership.

ark_data_layer1.1.0

COMPOSITION / LIFECYCLE

Ark DI

Hierarchical dependency scopes, deterministic async initialization, explicit ownership, and ordered teardown.

ark_di1.1.0

PRESENTATION / ADAPTATION

Ark MVP

Explicit Model composition, presentation-ready ViewState, bounded Presenter lifecycle, and one-time ViewEffects.

ark_mvp1.1.0

FAILURE / CONTROL

Ark Error Manager

Application-owned error assessment, sanitized reporting, user presentation, recovery policy, and root runtime integration.

ark_error_manager1.1.0

NAVIGATION / ROUTING

Ark Navigation

Typed destinations, explicit stack operations, modular graphs, separate Redirects and Guards, and native Flutter Router integration.

ark_navigation1.1.0

DETAILED COMPARISONCompare responsibility, platform, and common fit.

Product responsibility comparison
Product	Owns	Platform and scope	Common fit	Documentation
UseCase Forge	Coordinates command admission, concurrent execution, cancellation, output, history, and diagnostics as one explicit lifecycle.	Dart + Flutter4 packages	Adopt independently; connect repositories, presenters, error policy, or navigation only where an application boundary requires them.	Documentation →
Ark Data Layer	Defines typed DataSource and Repository boundaries and publishes current business data through a domain-owned contract.	Pure Dart1 package	A Repository can be used directly or called from a UseCase Forge Command when the application needs an execution lifecycle.	Documentation →
Ark DI	Builds hierarchical dependency scopes with explicit registration, ownership, asynchronous initialization, and ordered teardown.	Dart + Flutter2 packages	Use it as the composition root for any selected ArkTelos packages without making those packages depend on the container.	Documentation →
Ark MVP	Adapts complete business-facing Model state into presentation-ready ViewState and separate one-time ViewEffects.	Dart + Flutter2 packages	A Model can combine state and actions already provided by UseCase Forge, repositories, or other application-owned objects.	Documentation →
Ark Error Manager	Assesses application-level failures and coordinates sanitized reporting, user presentation, and recovery through one owned policy path.	Dart + Flutter2 packages	Place it at application boundaries; submit failures from selected packages without coupling those packages to the manager.	Documentation →
Ark Navigation	Resolves typed destinations through declared graphs, Redirects, Guards, explicit stack operations, URI contracts, and Flutter Router.	Flutter1 package	Call navigation from the application or presentation boundary; Redirects and Guards remain separate declared policies.	Documentation →

UseCase Forge

Dart + Flutter · 4 packages

Owns: Coordinates command admission, concurrent execution, cancellation, output, history, and diagnostics as one explicit lifecycle.
Common fit: Adopt independently; connect repositories, presenters, error policy, or navigation only where an application boundary requires them.

Ark Data Layer

Pure Dart · 1 package

Owns: Defines typed DataSource and Repository boundaries and publishes current business data through a domain-owned contract.
Common fit: A Repository can be used directly or called from a UseCase Forge Command when the application needs an execution lifecycle.

Ark DI

Dart + Flutter · 2 packages

Owns: Builds hierarchical dependency scopes with explicit registration, ownership, asynchronous initialization, and ordered teardown.
Common fit: Use it as the composition root for any selected ArkTelos packages without making those packages depend on the container.

Ark MVP

Dart + Flutter · 2 packages

Owns: Adapts complete business-facing Model state into presentation-ready ViewState and separate one-time ViewEffects.
Common fit: A Model can combine state and actions already provided by UseCase Forge, repositories, or other application-owned objects.

Ark Error Manager

Dart + Flutter · 2 packages

Owns: Assesses application-level failures and coordinates sanitized reporting, user presentation, and recovery through one owned policy path.
Common fit: Place it at application boundaries; submit failures from selected packages without coupling those packages to the manager.

Ark Navigation

Flutter · 1 package

Owns: Resolves typed destinations through declared graphs, Redirects, Guards, explicit stack operations, URI contracts, and Flutter Router.
Common fit: Call navigation from the application or presentation boundary; Redirects and Guards remain separate declared policies.