> 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_13_collaboration_and_handoff.md).

# Session 13: Collaboration And Handoff

**Session ID**: `phase19-session13-collaboration-and-handoff` **Packages**: apps/server, apps/web, apps/warroom **Status**: Complete **Completed**: 2026-06-26 **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Connect War Room posture, Notice Board decisions, remote access state, handoff, and resume workflows to Orchestration.

***

## Scope

### In Scope (MVP)

* Local-only, room-visible, relay unavailable, catch-up pending, imported, external, remote-originated, and external-transfer-disabled labels
* Notice links for tasks, approvals, conflicts, completions, handoffs, and room state
* Actions to post bounded review requests, blockers, and completions from selected queue or decision contexts
* Handoff readiness, scaffold creation, secret scan result, validation, staleness, branch/file-state checks, resume queue source, and lineage links
* Remote access/tunnel summary state without sensitive tunnel control

### Out of Scope

* Changing Worker privacy contracts
* Owning remote tunnel creation inside Orchestration

***

## Prerequisites

* [x] Sessions 04, 05, 08, and 09 complete
* [x] Current War Room, Notice Board, and handoff APIs inspected

***

## Deliverables

1. Federation and notice panel integrations
2. Handoff manager routes and resume source flow
3. Room, notice, handoff, and store updates
4. Tests for visibility labels, notice linkbacks, handoff validation, and privacy-safe payloads

***

## Source Coverage And Evidence

Source coverage:

* Session Split Plan Session 13: Collaboration And Handoff
* Implementation Targets 16, 17, and 18 for War Room/remote posture, Notice Board links, handoff, and resume workflows
* Balls-To-The-Wall Track B `handoffManager` routes
* Execution Family Order item 8 for War Room posture, Notice Board integration, and remote access summary

Key EXAMPLES links:

* [War Room guide](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/1st-pass-artifacts/skills/factionos-guide/SKILL.md#L279-L293)
* [External services War Room posture](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/external-services.md#L12-L24)
* [Remote access guide](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/1st-pass-artifacts/skills/factionos-guide/SKILL.md#L268-L278)
* [Remote and War Room routes](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/findings/api-routes.txt#L129-L207)
* [Notice Board skill](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/1st-pass-artifacts/skills/notice-board/SKILL.md#L1-L53)
* [Handoff skill](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/1st-pass-artifacts/skills/factionos-handoff/SKILL.md#L1-L207)
* [Handoff template](https://github.com/AI-with-Apex-VIP/factionos/tree/main/.spec_system/EXAMPLES/1st-pass-artifacts/skills/factionos-handoff/references/handoff-template.md#L1-L142)

***

## Success Criteria

* [x] Orchestration rows show whether they are local, room-visible, imported, or remote-originated
* [x] Operators can post bounded review/blocker/completion notices from context
* [x] Handoff and resume flows produce validated linked records
* [x] Worker payload contracts stay explicit, redacted, and versioned


---

# 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_13_collaboration_and_handoff.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.