> 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_14/session_03_homepage_narrative_sections.md).

# Session 03: Homepage Narrative Sections

**Session ID**: `phase14-session03-homepage-narrative-sections` **Package**: public-website **Status**: Not Started **Estimated Tasks**: \~18-24 **Estimated Duration**: 2-4 hours

***

## Objective

Complete the homepage sections that explain observability, gamification, local-first behavior, the hook-to-cockpit loop, publishing previews, and final conversion actions.

***

## Scope

### In Scope (MVP)

* Build the three-pillar value deck:
  * Observability.
  * Gamification.
  * Local-first.
* Add a "how the loop works" preview:
  * Hook events enter local server.
  * WebSocket stream updates cockpit.
  * Optional adapters notify external systems.
* Add a security boundary callout:
  * Local-first by default.
  * No hosted account required.
  * No prompt/file/path upload by default.
* Add latest blog and latest news/changelog preview from content collections.
* Add final tactical CTA panel with demo and docs links.
* Ensure every section uses shared layout primitives and page metadata.
* Keep copy concrete and product-specific.

### Out of Scope

* Full `/security` page.
* Full `/how-it-works` architecture page.
* Full blog/news editorial polish.
* Adding forms, analytics, or runtime data collection.

***

## Prerequisites

* [ ] Sessions 01 and 02 completed.
* [ ] Blog/news collections exist from Phase 13.
* [ ] Shared CTA and panel components exist.

***

## Deliverables

1. `ThreePillarDeck.astro`.
2. `SecurityBoundary.astro` or homepage-specific security callout.
3. Homepage latest-content preview.
4. Final homepage CTA section.
5. Completed `src/pages/index.astro`.

***

## Content Requirements

Observability should cover:

* Hook tracking.
* File diffs or file touch visibility.
* Prompt lifecycles.
* Tool/event streams.

Gamification should cover:

* Roster building.
* Mission completion.
* Dynamic XP/readout style.
* Battlefield/mission metaphor without implying unseriousness.

Local-first should cover:

* Local REST snapshots.
* Local browser cockpit.
* Zero hosted storage required.
* Privacy boundary around prompts, file paths, credentials, terminal output, replay data, and user-provided code.

Final CTA should route to:

* Demo at `https://demo.faction-os.com/`.
* Public docs at `https://faction-os.gitbook.io/faction-os-docs`.

***

## Task Expansion Guidance

When expanded with `plansession`, keep the checklist to 18-24 tasks covering:

* Pillar data/copy.
* Pillar component.
* Loop preview.
* Security boundary section.
* Latest blog query.
* Latest news query.
* Final CTA panel.
* Section spacing.
* Responsive behavior.
* Metadata.
* Link validation.
* Mobile text wrapping.

***

## Success Criteria

* [ ] Homepage includes all required narrative sections.
* [ ] Latest blog/news previews render from non-draft content.
* [ ] Security copy is precise and local-first.
* [ ] Demo/docs CTAs remain clear at the end of the page.
* [ ] Homepage does not duplicate exhaustive docs or the full synthetic demo experience.


---

# 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_14/session_03_homepage_narrative_sections.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.