> 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/prd/phase_25/session_06_emissary_notices_decrees_and_banners_unite.md).

# Session 06: Emissary, Notices, Decrees, And Banners Unite

**Session ID**: `phase25-session06-emissary-notices-decrees-and-banners-unite` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Make inbound collaboration, notices, local decrees, and channel-intake moments read as ceremonial messages while preserving redaction, local-only boundaries, provider-health copy, and optional Worker limitations.

***

## Scope

### In Scope (MVP)

* Update `NoticeBoard.tsx` rows to resolve notice ceremony specs
* Add Warchief's Decree treatment for critical or high-priority local notices and existing manual override surfaces where present
* Preserve Notice Board detail modal behavior, selected hero and mission filters, canonical payload normalization, caps, and deduplication
* Preserve War Room notice convergence redaction posture and do not turn notice counts into enemy spawns or score
* Update `ChannelCommandPanel.tsx` to use `receive_emissary` for inbound command rows
* Allow local approval, queue conversion, attention conversion, or guarded conversion to show a wax stamp/missive movement only after the existing action succeeds
* Preserve provider health, replay metadata, scope labels, state labels, validation status, blocked-category copy, and detail opening
* Update `WarRoomPanel.tsx` to use Banners Unite treatment for successful room join, participant approval, and connected collaboration summary
* Preserve local-only, unavailable, create, join, pending, approved, rejected, connected, reconnecting, caught-up, disconnected, and left states
* Preserve participant limit, six-character join codes, in-flight decisions, redacted federation, and room notice handling
* Extend Notice Board, Channel Command Panel, and War Room Panel tests

### Out of Scope

* Raw header, cookie, auth payload, webhook secret, raw body, signature, prompt, file content, diff, log, terminal output, or broad path exposure
* Remote trust, provider correctness, automatic execution, hosted identity, shared score, or trusted collaboration claims
* New War Room federation or Notice Board protocol behavior

***

## Prerequisites

* [ ] Session 01 registry is available
* [ ] Shared ceremony presentation components are available

***

## Deliverables

1. Notice, decree, emissary, and Banners Unite presentation
2. Preserved channel and War Room safety copy
3. Tests covering ceremony attributes and unchanged redaction/boundary behavior
4. `commandCenterUi` or privacy tests where view-helper/copy paths change

***

## Success Criteria

* [ ] Inbound commands feel like received emissary messages without exposing raw payload detail
* [ ] Collaboration ceremony does not imply remote execution, hosted identity, shared scoring, or trusted collaboration guarantees
* [ ] Notice Board detail and filter behavior remain intact
* [ ] War Room in-flight decisions and optional Worker boundary copy remain intact
* [ ] `WarRoomBattlefieldOverlay` remains unchanged or is covered if remote markers gain shared-banner presentation


---

# 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/prd/phase_25/session_06_emissary_notices_decrees_and_banners_unite.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.