TT Linear workspace setup (Phase α of Model C migration)

Bootstrap state for the SOTA Claude + Linear multi-repo architecture (Model C — Initiative → Project → Issue hierarchy). Captured 2026-05-26 during the Wave-C.1-post-close brainstorm + design.

Workspace identity

PropertyValue
Linear workspace namemediahq2 (URL: linear.app/mediahq2)
TT team nameTestateTechnologies
TT team keyTT
TT team ID94c6bdcd-61fb-46c7-974e-2fe23a80716e
Rich account IDeb02773d-f1c5-4fa3-8116-0a2d11ae4331 (richard@mediahq2.com; admin)
Steven account ID18faabef-24f1-4a79-a710-e6ae7264986f (steven@mediahq2.com)
Workspace plan tierBusiness ($14/user/month) — confirmed 2026-05-26
Other teamRichSte (key: RIC, ID: 57e33538-3824-43e0-9d4f-610f4061ed68) — Rich + Steven test workspace

Linear features available on Business plan

  • ✅ Initiatives (Phase → Wave → Issue hierarchy = Model C)
  • ✅ Projects with labels + milestones + sub-issues
  • ✅ Triage Intelligence
  • ✅ Code Intelligence (beta — admin must enable in AI Settings + GitHub integration must include code access)
  • ✅ Linear Releases (CI/CD integration; up to 15 release pipelines)
  • ✅ Project Slack channels (auto-create p-)
  • ✅ Custom views + filters
  • ✅ Linear Agent + Agent automations + Agent skills
  • ✅ Mobile agent sessions
  • ❌ SSO (Enterprise)
  • ❌ GitHub Enterprise Cloud integration (Enterprise; not needed — TT uses regular GitHub)
  • ❌ Linear Asks web forms (Enterprise; not needed yet)

Labels created (Phase α step 1) — 14 workspace-scoped

LabelIDHex
repo:standard908e799f-5b34-42fd-be0d-24aea175e038ff6b6b
repo:sdke264d75c-17e0-4606-a10f-f9013fd530e84ecdc4
repo:app14dec2cc-b62a-4c8d-8785-6a327d70b1ca45b7d1
repo:websitef62d2256-0c5c-4233-858b-271235356bf0ffa07a
repo:test-suite0831390e-bf7a-419e-be3c-5daec899f16798d8c8
repo:docs-strategy568e1655-4c5b-4f42-890c-1d904754122d6c5ce7
repo:docs-admin8da3badd-f939-4ca9-a0b2-9122a582b3d2a8e6cf
repo:all9e050476-16e4-4687-b5ec-a01eb8a2bdde95a5a6
type:schemaa0970607-ad70-4111-9081-840ed8c8cfbbbb87fc
type:rule8ecd50c0-47ba-4e26-9b1c-dac3b81f3e78fcbf49
type:docfcbe63f1-eb75-4a93-8426-0b57c7a4e8094ea7fc
type:ci23313c9c-0b87-4720-bf13-d88c10b9e46006d6a0
type:tooling5fd2f786-0c63-4003-8bbc-70d8ec2a5b7cef476f
type:auditc468aeb7-f4c8-4459-a2b4-fc18bfb1f3b9118ab2

Initiatives queued for Rich-side creation (Phase α step 2)

Linear MCP doesn’t expose save_initiative — Initiative creation is via Linear Agent (⌘J then ask) or Linear UI.

  1. Phase-1 Build Standardisation — Waves A → D + C.1 (already closed Waves A/B/C/C.1)
  2. Phase-1.5+ Build-Process Maturation — Waves E → I
  3. Phase-2 Launch — v1.0 release arc

Existing projects (pre-Phase-α)

  • [SPIKE-S11] TT TaskList ↔ Linear sync prototype (CANCELED 2026-05-25; Spike S11 closure record)
  • testatetech (created by Steven 2026-05-24; placeholder; status: Backlog)

Both should be tagged as Archive / orphaned (not under any Initiative) — they predate Model C.

Pre-existing default labels (pre-Phase-α)

  • Bug (default Linear)
  • Improvement (default Linear)
  • Feature (default Linear)
  • spec-kit-smoke-test (Path E test artefact; can be archived)

These remain — additive only, not replaced by the 14 new labels.

Phase α — 100% complete 2026-05-26

  • α.1: ✅ Plan tier verified (Business)
  • α.2: ✅ 3 Initiatives created via Linear Agent (Phase-1 Build Standardisation ID c99c64ec-f450-446b-8668-ca343000f9c0; Phase-1.5+ Build-Process Maturation; Phase-2 Launch)
  • α.3: ✅ Memory captured
  • α.4: ✅ Code Intelligence enabled (2026-05-26; Linear Agent can now reason about TT codebase via GitHub integration)
  • α.5: ✅ 14 labels created (workspace-scoped)

Phase β — 1 of 5 steps remaining (Wave D LP v2.0 restructure)

  • β.1: ✅ Wave D Linear Project created (5627ed2c-aa55-4fc8-82d5-03cd8a385f7e; URL linear.app/mediahq2/project/wave-d-stage-10-mkdocs-cloudflare-pages-41be8be23f3e)
  • β.2: ✅ 4 Wave D Issues created (TT-13 mkdocs.yml / TT-14 CF Pages verify / TT-15 609-doc scale / TT-16 optional OPA migration)
  • β.3: ⏳ Wave D LP v1.8 → v2.0 restructure under Model C (deferred to next coordinator session)
  • β.4: ⏳ Update wave-execution-record template with linear_project_id field (next session)
  • β.5: ⏳ Pre-flight battery refresh including Model C readiness checks (next session)

Phase β — Wave D under Model C (after α.2 closes)

After Initiatives exist, coordinator creates via MCP:

  • 1 Project under “Phase-1 Build Standardisation” Initiative: Wave D — Stage 10 mkdocs + Cloudflare Pages
  • 3 mandatory Issues (TT-D1 / TT-D2 / TT-D3) + 1 optional (TT-D4 OPA migration)
  • All Issues labelled repo:docs-strategy + appropriate type:*

References