> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Engineering: Build and Ship with Spine Context

> SpineWorkspace for Product Engineering unifies tickets, code, and incidents into one contextual workbench for planning, building, and operating software.

The Product Engineering domain inside SpineWorkspace is the one contextual workbench for product development and engineering delivery. It unifies issues, epics, pull requests, incidents, and release activity from systems like Linear, GitHub, PagerDuty, and Datadog so product managers, engineers, and designers share a single view of what to build, what is shipping, and what needs fixing.

**Domain Purpose:** Deliver software faster with fewer handoff gaps by keeping every work artifact in context.

<CardGroup cols={2}>
  <Card title="Human Workbench" icon="user" href="/internal-docs/domains/product-engineering/human-workbench">
    How PMs and engineers plan, review, and ship in Spine.
  </Card>

  <Card title="AI Workbench" icon="bot" href="/internal-docs/domains/product-engineering/ai-workbench">
    How Twin assembles context and drafts proposals for engineering work.
  </Card>

  <Card title="System Flow" icon="server" href="/internal-docs/domains/product-engineering/system-flow">
    How Spine Fabric ingests and normalizes engineering data.
  </Card>

  <Card title="Execution Flow" icon="play" href="/internal-docs/domains/product-engineering/execution-flow">
    How governed actions write back to source systems.
  </Card>
</CardGroup>

### Core Entities

* Issue, Epic, Sprint, Release
* PullRequest, Incident, Feature, Roadmap

### Key Views

* Sprint Board, Roadmap, Release Pipeline
* Incident Queue, Backlog Health

### Primary Workflows

* Ticket Triage, Sprint Planning, Release
* Incident Response, Code Review

<CardGroup cols={2}>
  <Card title="Domain Model" icon="map" href="/internal-docs/domains/product-engineering/domain">
    Business needs and operating model for engineering teams.
  </Card>

  <Card title="Domain Views" icon="table" href="/internal-docs/domains/product-engineering/domain-views">
    Table of projections and sources.
  </Card>

  <Card title="Business Context" icon="briefcase" href="/internal-docs/domains/product-engineering/business-context">
    Entities, relationships, and evidence.
  </Card>

  <Card title="Integrations" icon="plug" href="/internal-docs/domains/product-engineering/integrations">
    Connected source systems.
  </Card>
</CardGroup>

### Related

* [Domain Views](/internal-docs/domains/product-engineering/domain-views)
* [Integrations](/internal-docs/domains/product-engineering/integrations)
* [Human Workbench](/internal-docs/domains/product-engineering/human-workbench)
* [How It Works: Continuity](/how-it-works/continuity)
* [Domains Overview](/internal-docs/domains/overview)