# Long-horizon feature work

Implementation, acceptance cases and delivery records are tracked in [WO-01](../work-orders/long-horizon-feature-delivery/WO-01-native-research-feature-workflow.md).

Use a feature workflow when one objective needs sustained research, a reviewed specification, several dependent changes, integration and explicit acceptance checks. Give Omnius the objective, constraints and observable acceptance criteria. For example:

> Use the native feature workflow to add resumable imports. Research the current import and storage paths, write a specification, have a separate read-only worker review it, implement the parser and persistence changes, integrate them, and test interruption and duplicate-record recovery. Preserve accepted work across restarts. Report unresolved questions and failed checks before claiming completion.

The runner exposes `feature_workflow` to create or revise the plan, inspect readiness, reopen scoped repair work after a recorded failure, and select an exact prior program to resume. Work still runs through the ordinary file, terminal and child-agent tools. A workflow does not grant permission to publish, deploy or contact other people.

## What carries the work forward

| Phase | Required result |
| --- | --- |
| Research | Bounded findings and durable source/artifact references; missing streams remain visible. |
| Specification | An exact specification artifact and a separate review of that version, including findings and unresolved questions. |
| Implementation | Changes owned by individual tasks, with their prerequisite evidence and output artifacts. |
| Integration | The combined source state and an integration artifact identifying it. |
| Acceptance | Declared commands executed against that combined state, with actual command receipts. |
| Handoff | The result, remaining limitations and evidence needed to continue or publish. |

A worker completing its run is not sufficient to approve its own specification. An approval is tied to the reviewed artifact version. A later edit makes an older review stale. Similarly, a passing check on an individual change does not verify a different integrated source state.

When acceptance fails, the workflow retains accepted research and other unaffected work. Remaining tasks and stale checks stay open. A later source mutation invalidates checks on the preceding integrated state.

Omnius rebuilds the current plan identity, ready tasks, required artifact references and unresolved obligations from durable records for each request. That compact state survives context reduction; older artifact bodies can be reopened by their exact references. Insufficient capacity for required current state leaves inference admission blocked with a reason.

## Continuing after interruption

Keep the objective ID, accepted plan reference and owning run identity shown by the workflow. Resume selects that exact durable program. It does not reconstruct authority from a conversational summary or the latest unrelated handoff.

The recovered program must validate its artifact references, operation receipts and ownership before allowing dependent work. Work whose external effects are uncertain needs reconciliation before it can be repeated. A normal continuation may enter a new runner epoch; its adoption record preserves the original evidence identities.

Replacing the objective retires the old program. Delayed child results cannot reopen it. Adding a constraint to the same objective should preserve accepted work that remains valid and expose any newly required work.

## Reading the result

Telegram can display a report derived from the committed task evidence when a run has no separately authored final reply. It includes recorded changes, command outcomes, evidence gaps and next actions. The Evidence view retains additional detail when the visible result must be shortened.

The report distinguishes successful verification from an observation command that merely exited successfully. Failed, timed-out or stale checks remain visible. A missing final report is reported as a delivery problem with a reconstruction step, so a retry does not silently repeat completed changes.

The design was adapted from [AIWG's research and delivery mechanisms](../research/aiwg-long-horizon-feature-workflow.md). It uses Omnius's existing workboard, completion authority, immutable artifact storage and interruption lifecycle.
