> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_19/session_10_mission_artifacts.md).

# Session 10: Mission Artifacts

**Session ID**: `phase19-session10-mission-artifacts` **Packages**: apps/server, apps/web **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Bring mission progress, workpad, evidence, verification, and review gates into Orchestration details.

***

## Scope

### In Scope (MVP)

* Mission progress chips for objectives, verification state, elapsed time, token/cost estimates, line-change estimates, last tool family, stalls, and escalations
* Durable workpad records, evidence artifact metadata, verification attempts, retry limits, visual check instructions, review decisions, merge action, and skip-verification action
* Links between artifacts, plans, tasks, queue entries, missions, and execution runs
* Attention item creation for budget, stall, verification, escalation, and review states
* Tests for metadata, verification retries, review transitions, mission chips, and event reducers

### Out of Scope

* Raw evidence file content display in broad Orchestration rows
* Full Mission Control replacement

***

## Prerequisites

* [ ] Sessions 04 through 06 complete
* [ ] Session 09 mission links available or compatibility path identified

***

## Deliverables

1. Workpad/evidence manager behavior and artifact/review routes
2. Workpad, evidence, verification, and review panel
3. Mission progress integrations for queue, graph, and attention rows
4. Server and web tests for artifact and review behavior

***

## Source Coverage And Evidence

Source coverage:

* Session Split Plan Session 10: Mission Artifacts
* Implementation Targets 7 and 9 for mission progress, workpad, evidence, verification, and review gates
* Balls-To-The-Wall Track B `workpadEvidenceManager` routes
* Execution Family Order item 5 for workpad/evidence/verification/review flow

Key EXAMPLES links:

* [Mission guide](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/1st-pass-artifacts/skills/factionos-guide/SKILL.md#L69-L78)
* [Mission and progress events](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/websocket-events.txt#L83-L146)
* [Task evidence routes](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/api-routes.txt#L29-L30)
* [Task queue workpad route](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/api-routes.txt#L179-L179)
* [Verify route](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/api-routes.txt#L198-L198)
* [Verification instructions schema](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/llm-prompts/plan-decomposer.md#L35-L41)

***

## Success Criteria

* [ ] Each plan/task can show workpad, evidence, verification history, and review state
* [ ] Budget, stall, verification, and escalation states can raise attention items
* [ ] Completed-but-unmerged work can enter the review queue
* [ ] Orchestration shows metadata and links, not raw artifact contents


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_19/session_10_mission_artifacts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.