> 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/sessions/phase20-session01-truthful-capability-baseline/tasks.md).

# Task Checklist

**Session ID**: `phase20-session01-truthful-capability-baseline` **Total Tasks**: 18 **Estimated Duration**: 3-4 hours **Created**: 2026-06-28

***

Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID.

***

## Progress Summary

| Metric              | Value   |
| ------------------- | ------- |
| Tasks Completed     | 18 / 18 |
| Estimated Remaining | 0 hours |
| Blockers            | 0       |

***

## Setup (2 tasks)

* [x] T001 \[S2001] Verify Phase 20 Session 01 source findings and current overclaim locations (`.spec_system/PRD/phase_20/session_01_truthful_capability_baseline.md`)
* [x] T002 \[S2001] Confirm command-center status vocabulary supports non-ready file and lifecycle states (`packages/protocol/src/orchestrationCommandCenter.ts`)

***

## Foundation (4 tasks)

* [x] T003 \[S2001] \[P] Update file executor readiness expectations before implementation (`apps/server/tests/executorRegistry.test.ts`)
* [x] T004 \[S2001] \[P] Update guarded file approval route expectations to require non-executing results (`apps/server/tests/guardedActions.test.ts`)
* [x] T005 \[S2001] \[P] Update command-center capability route expectations so file probes cannot become `executor_ready` (`apps/server/tests/commandCenterRoutes.test.ts`)
* [x] T006 \[S2001] \[P] Update web copy expectations for capability, queue, campaign, and observed hero lifecycle states (`apps/web/tests/commandCenterUi.test.ts`)

***

## Implementation (9 tasks)

* [x] T007 \[S2001] Downgrade default file executor entries until real file mutation exists with explicit non-executing guidance (`apps/server/src/managers/executorRegistry.ts`)
* [x] T008 \[S2001] Remove metadata-only file execution summaries from guarded approval results with schema-validated input and explicit error mapping (`apps/server/src/managers/executorRegistry.ts`)
* [x] T009 \[S2001] Update queue action labels and reasons to describe record-only tracking with duplicate-trigger prevention while in-flight (`apps/web/src/lib/commandCenterUi.ts`)
* [x] T010 \[S2001] Update campaign action labels, state descriptions, and graph copy to avoid execution verbs for tasks without executable payloads (`apps/web/src/lib/commandCenterUi.ts`)
* [x] T011 \[S2001] Update queue workbench buttons, feedback, and captions for metadata-only actions with platform-appropriate accessibility labels, focus management, and input support (`apps/web/src/components/orchestration/QueueWorkbench.tsx`)
* [x] T012 \[S2001] Update campaign workbench buttons, feedback, and task copy for planning-only work with duplicate-trigger prevention while in-flight (`apps/web/src/components/orchestration/CampaignWorkbench.tsx`)
* [x] T013 \[S2001] Update observed hero lifecycle labels to record intent instead of claiming process control (`apps/web/src/lib/commandCenterUi.ts`)
* [x] T014 \[S2001] Update Hero/Lineage buttons and accessible names for observed-only record intent with platform-appropriate accessibility labels, focus management, and input support (`apps/web/src/components/orchestration/HeroLineageWorkbench.tsx`)
* [x] T015 \[S2001] Update command-center API, event, web, and architecture docs to remove file executor-ready audit execution and metadata-only dispatch claims (`docs/api/README_api.md`, `docs/api/event-api-hook-contracts.md`, `apps/web/README_web.md`, `docs/ARCHITECTURE.md`)

***

## Testing (3 tasks)

* [x] T016 \[S2001] \[P] Update integrated web pane tests for record-only queue, campaign, and hero lifecycle controls (`apps/web/tests/CommandCenterPanes.test.tsx`, `apps/web/tests/HeroLineageWorkbench.test.tsx`)
* [x] T017 \[S2001] Run focused Vitest coverage for touched server and web behavior (`npx vitest run apps/server/tests/executorRegistry.test.ts apps/server/tests/guardedActions.test.ts apps/server/tests/commandCenterRoutes.test.ts apps/web/tests/commandCenterUi.test.ts apps/web/tests/CommandCenterPanes.test.tsx apps/web/tests/HeroLineageWorkbench.test.tsx`)
* [x] T018 \[S2001] Run typecheck, diff, ASCII, and LF verification for the session (`npm --workspace packages/protocol run typecheck`, `npm --workspace @factionos/server run typecheck`, `npm --workspace @factionos/web run typecheck`, `git diff --check`)

***

## Completion Checklist

* [x] All tasks marked `[x]`
* [x] All tests and checks passing
* [x] All files ASCII-encoded with LF line endings
* [x] implementation-notes.md updated
* [x] Ready for `creview` to continue the implement -> creview -> validate sequence

***

## Next Steps

Run the `creview` workflow step.


---

# 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/sessions/phase20-session01-truthful-capability-baseline/tasks.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.