# Pillowfort – Creative Team in a Box (v1)

**Canonical summary:**  
Pillowfort turns ideas into momentum with an always-on, self-organizing, self-configuring creative team that is understandable, extendable, and practical for real projects.

## North Star

Pillowfort turns ideas into momentum with an always-on, self-organizing creative team that you can understand and extend.

## Product Summary

Pillowfort is a **Creative Team in a Box** for makers who need steady creative execution without enterprise complexity.

It is designed for long-form reasoning and stateful workflows so context is retained, tasks stay coherent, and work can continue beyond a single chat session.

Core behavior: if enabled and connected, it runs continuously on your project context and helps organize planning, collaboration, and execution.

## What Pillowfort is and is not

Use the sections below as hard constraints for capability statements.

### Human Control

- Pillowfort assists and proposes work, but human intent and approval remain the final control point for sensitive actions where configured.
- People remain the project owner; the system executes within those explicit guardrails and can always be interrupted, reprioritized, or stopped.

### Allowed Claims

- Self-configuring onboarding and workflow adaptation.
- Self-organizing orchestration among internal collaborators.
- Long-form planning, context retention, and stateful follow-through.
- Cross-environment operation on mixed hardware from low-spec laptops to larger systems (when compatible).
- Open-source positioning and transparent collaboration.
- Continuous operation when configured and connected.

### Inter-System Coordination

- Cross-system agent coordination is only active when explicitly configured in system policy and connector setup.
- All cross-repository or cross-agent interactions are constrained by security policy, identity, and permissions.
- No remote orchestration is assumed by default; external access must be enabled and auditable.
- Coordinators may communicate across systems only through documented interfaces and approved credentials.

### Avoid Claims

- “Fully autonomous execution on your accounts.”
- “Guaranteed results.”
- “Completely offline.”
- “No hallucinations.”
- “Enterprise-grade reliability out of the box.”
- Any claim of data guarantees not explicitly documented.

## Brand Voice

Use these rules for all generated copy and responses.

- Do:
  - Warm, capable, practical, and quietly confident.
  - Playful with structure (clear priorities, no fluff).
  - Concrete language and specific outcomes.
  - Respectful, inclusive, and creator-first.
- Don’t:
  - Use corporate jargon or vague buzzwords.
  - Use hypey AGI framing.
  - Use fear-based messaging.
  - Use exclusivity or elitist positioning.

## Core Differentiators

- **Self-Configuring**  
  Onboarding shapes the team setup to your goals, tools, and habits.
- **Self-Organizing**  
  Agents coordinate behavior and prioritize work across context boundaries.
- **24/7 Momentum**  
  The team keeps moving when you pause, switch context, or sleep (if enabled).
- **All it takes is an idea**  
  You provide intent; the team creates plans and drives actionable work.

## Page Structure and Content Expectations (for copy drafting)

Use this structure when generating or editing page content so agents stay aligned:

- `hero`
  - 1 headline
  - 1 short subhead
  - 1 CTA label (action-oriented)
- `about`
  - 2–3 paragraphs max
  - Explain differentiators in plain language
  - Include one short “in plain English” paragraph for accessibility
- `features`
  - 6–9 tiles
  - Each tile: verb-led title + one-line output-oriented example
- `notify`
  - 1 short trust line
  - Form labels: first name, last name, email, social handle
- `footer`
  - Keep trust, licensing, and open-source signals concise

### Feature Tile Format Examples

- `Plan → Draft`  
  **Verb-led title:** `Plan → Draft`  
  **Example output:** `Agent translates your idea into a production-ready brief and first pass plan.`  

- `Research → Summarize`  
  **Verb-led title:** `Research → Summarize`  
  **Example output:** `Agent collects relevant references and returns a ranked short-list with why-and-so-what notes.`

## Current Landing Message Themes

1. **Coming Soon Creative Stack**  
   Pillowfort is preparing beta access for makers wanting a steady creative partner.

2. **Functional Team Model**  
   Positioned as an execution-oriented team, not a passive assistant.

3. **Run Anywhere**  
   Designed for mixed hardware and deployment styles.

4. **Open-Source and GPL-3.0**  
   Community-minded implementation with transparent collaboration.

## Primary Audience

- Makers and creators with constrained budgets
- Students and teams exploring AI-first creative workflows
- Small studios transitioning from idea-heavy execution to continuous delivery
- Founders who want momentum without building internal complexity

## Core Use Cases

- Long-form ideation sessions
- Creative planning and editorial direction
- Coordinated execution across multiple tracks
- Early marketing, notes, and outreach workflows
- Stateful, persistent collaboration for iterative projects

## Content Guardrails for Future Editing

- Prefer simple language over technical spectacle.
- Keep claims scoped to documented capabilities.
- Tie outcomes to user-visible effects, not promises of inevitability.
- Keep the tone warm and grounded.
- Preserve `Pillowfort` capitalization consistently (single token: “Pillowfort”).
- Treat the Allowed Claims and Avoid Claims as hard constraints for generated content.
- Mention constraints explicitly when copy discusses risk, timing, or capability boundaries.

## Operational Assumptions

- Pillowfort runs in configured environments with supported dependencies and connectors.
- The user must provide clear intent and context; quality follows intent clarity.
- Automation quality depends on available context, connector health, and policy configuration.
- Stateful behavior and collaboration breadth depend on platform integrations, not only model capability.