ARKTELOS / PRODUCTS / USECASE FORGE

Command execution with a lifecycle you can reason about.

UseCase Forge gives Dart and Flutter applications one explicit place to coordinate ingress, policy, concurrent work, cancellation, output, failures, history, and diagnostics.

Read the documentationpub.dev ↗Source ↗
A Command passes Admission and Policy, resolves through an execution cell, and produces Output, History, and Diagnostics.COMMANDADMISSIONPOLICYEXECUTEOUTPUTDIAGNOSTICS
A Command passes Admission and Policy, resolves through an execution cell, and produces Output, History, and Diagnostics.

FIT / EVALUATION

Confirm the boundary before adopting the package.

Platform
Dart + Flutter
Primary package
usecase_forge
Current release
1.1.0
Responsibility
Coordinates command admission, concurrent execution, cancellation, output, history, and diagnostics as one explicit lifecycle.
Use when
Use it when application work needs visible overlap policy, cancellation, terminal outcomes, and operational evidence.
Does not own
It does not define domain decisions, persistence, presentation, dependency composition, or navigation.

Shortest evaluation path

  1. 01

    Confirm the responsibility and deliberate boundary above.

  2. 02Open tutorials →
  3. 03

    Inspect package ↗Inspect source ↗

01 / MODEL

A Command follows one explicit lifecycle.

An Input Port accepts a Command and applies admission policy. Accepted work receives an execution identity, passes through concurrency policy, cancellation, and failure handling, then publishes Output and snapshots in order while the terminal outcome, history, and diagnostics remain observable.

A Command passes admission and policy, executes with cancellation and failure context, then publishes Output and operational evidence.EXPLICIT LIFECYCLECOMMANDADMISSIONEXECUTIONOUTPUTHISTORY · RESULT · DIAGNOSTICS
  1. Command
  2. Admission
  3. Execution
  4. Output + evidence
A Command passes admission and policy, executes with cancellation and failure context, then publishes Output and operational evidence.

02 / BOUNDARIES

Ingress, execution, and observation remain separate boundaries.

01

Input Port

Accepts a Command, applies admission rules, and reports a typed rejection result before work begins.

02

Execution

Coordinates concurrency policy, execution identity, cancellation, and completion for accepted work.

03

Output and evidence

Publishes Output and snapshots while preserving the terminal outcome, history, and diagnostics for observation.

03 / DOCUMENTATION

Start with the lifecycle, then run the first scenario.

Learn the architecture and primary flow, then open tutorials for execution policies, packages, and DevTools.

Learn→Tutorials→Recipes→Packages→DevTools→Proof→Releases→