> 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_15/session_04_company_and_contact_pages.md).

# Session 04: Company And Contact Pages

**Session ID**: `phase15-session04-company-and-contact-pages` **Package**: public-website **Status**: Not Started **Estimated Tasks**: \~16-22 **Estimated Duration**: 2-4 hours

***

## Objective

Build investor, about, contact, and press pages without introducing hosted forms, private financial claims, or unverifiable product claims.

***

## Scope

### In Scope (MVP)

* Create or complete `src/pages/investors.astro`.
* Create or complete `src/pages/about.astro`.
* Create or complete `src/pages/contact.astro`.
* Create or complete `src/pages/press.astro`.
* Build `PressAssetGrid.astro` if needed.
* Add mailto or owner-approved external contact links.
* Segment contact intents:
  * Product/demo.
  * Security.
  * Press.
  * Investors.
  * Partnerships.
* Add press boilerplate, product summary, brand assets, showcase assets, press contact, and recent announcement links.
* Add investor category thesis, product wedge, market problem, differentiation, and contact CTA.

### Out of Scope

* Hosted form submission.
* CRM integration.
* Private financial data.
* Unverified market, revenue, adoption, or traction metrics.
* Final legal/privacy pages.

***

## Prerequisites

* [ ] Phase 13 asset pipeline available for press assets.
* [ ] Phase 15 security claim boundaries reviewed.

***

## Deliverables

1. `/investors` route.
2. `/about` route.
3. `/contact` route.
4. `/press` route.
5. Press asset preview/download handling.
6. Contact routing through `mailto:` or approved external links.

***

## Page Content Requirements

Investors:

* Category thesis.
* Product wedge.
* Market problem.
* Differentiation:
  * Local-first observability.
  * Provider-neutral protocol.
  * Developer cockpit.
  * Optional collaboration path.
* Contact CTA.
* No unverifiable metrics.

About:

* Mission.
* Product principles.
* Local-first stance.
* Who FactionOS is for.
* Links to docs, demo, and contact.

Contact:

* Product/demo contact.
* Security contact.
* Press contact.
* Investor contact.
* Partnership contact.
* No server-side form handling.

Press:

* Boilerplate.
* Product summary.
* Brand assets.
* Screenshots/showcase assets.
* Press contact.
* Recent announcements.
* Processed image previews.
* Downloadable files from `public/press/` when needed.

***

## Task Expansion Guidance

When expanded with `plansession`, keep the checklist to 16-22 tasks covering:

* Investors route.
* About route.
* Contact route.
* Press route.
* Press asset grid.
* Contact link data.
* Metadata per page.
* Navigation/footer links.
* No-form verification.
* Copy guardrail review.
* Build/typecheck.

***

## Success Criteria

* [ ] Investor, about, contact, and press pages render.
* [ ] Contact does not require server-side handling.
* [ ] Investor page avoids unverifiable metrics.
* [ ] Press assets use approved files and do not promote blocked media.
* [ ] All four routes include metadata and accessible CTAs.


---

# 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_15/session_04_company_and_contact_pages.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.