Skip to content

Adopt the shared C design system for the first document workflow #14

Description

@PeterGuy326
schemaVersion: requirement-record.v1
revision: R2
status: ready
priority: P2
productOwner: "@PeterGuy326"
technicalOwner: "unassigned"
userOutcome: "A user can sign in locally, create the first document, edit and refresh it, and see the C design consistently across the entire path."
requirements:
  - REQ-001
  - REQ-002
  - REQ-003
  - REQ-004
acceptanceCriteria:
  - AC-001
  - AC-002
  - AC-003
  - AC-004
parent: null
dependencies:
  - "https://github.com/fullstack-ai-infra/design-system/issues/1"
supersedes:
  - "R1 unnumbered scope/acceptance draft"
lastDecisionAt: "2026-08-23T06:11:44Z"

Context

Migrate the first complete document workflow to @fullstack-ai-infra/ui using the organization-approved C direction: warm paper canvas, stone navigation, sage primary accent, and lavender reserved for AI.

R1 scope

  • Consume the shared token and Tailwind contracts.
  • Replace local primitives through compatibility re-exports instead of a large import rewrite.
  • Migrate sign-in, application shell, document tree, editor chrome, AI panel, dialogs, empty/error/loading states, and theme behavior.
  • Remove fixed colors from the migrated surfaces.
  • Preserve Tiptap/Yjs behavior, routing, i18n, and permission semantics.
  • Add visual regression and keyboard/accessibility coverage.

R1 acceptance checklist

  • A user can sign in locally, create the first document, edit and refresh it, and see the C design consistently across the entire path.
  • Light and dark themes use shared semantic tokens.
  • The migrated path contains no new raw brand colors or direct primitive duplication.
  • Existing collaboration, revocation, restore, API, and build checks remain green.

Dependencies named in R1

Depends on fullstack-ai-infra/design-system#1 (recorded above as the full canonical URL) and the zero-credential local loop issue.

Requirements

REQ-001 — Consume shared design contracts

Consume the shared token and Tailwind contracts.

REQ-002 — Compatibility re-export migration

Replace local primitives through compatibility re-exports instead of a large import rewrite.

REQ-003 — Migrate the first-workflow surfaces

Migrate sign-in, application shell, document tree, editor chrome, AI panel, dialogs, empty/error/loading states, and theme behavior. Remove fixed colors from the migrated surfaces.

REQ-004 — Preserve behavior and add coverage

Preserve Tiptap/Yjs behavior, routing, i18n, and permission semantics. Add visual regression and keyboard/accessibility coverage.

Acceptance Criteria

AC-001 — Consistent first document path

A user can sign in locally, create the first document, edit and refresh it, and see the C design consistently across the entire path.

AC-002 — Shared semantic theming

Light and dark themes use shared semantic tokens.

AC-003 — No raw colors or duplicated primitives

The migrated path contains no new raw brand colors or direct primitive duplication.

AC-004 — Existing checks remain green

Existing collaboration, revocation, restore, API, and build checks remain green.

Non-goals

None stated in R1.

Decisions

  • DEC-DOC-14-001 (2026-08-23T06:11:44Z): requirement record formalized to requirement-record.v1 with numbered REQ/AC, owners, and ledger; R1 scope and acceptance content unchanged.

Status and evidence

  • Status: ready; Priority: P2
  • Baseline: organization-approved C direction (warm paper canvas, stone navigation, sage primary accent, lavender reserved for AI); shared token and Tailwind contracts supplied through fullstack-ai-infra/design-system#1; local primitives otherwise not yet migrated.
  • Latest accepted implementation ledger: none

Change history

Revision Effective time Decision Superseding comment
R1 2026-08-02T08:07:15Z Initial unnumbered scope and acceptance Initial body
R2 2026-08-23T06:11:44Z Formalize requirement-record.v1 with numbered REQ/AC, owners, and ledger This edit

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:p2Useful backlog work outside the immediate critical pathstatus:readyScope and acceptance criteria are ready for implementationtype:featureA focused user-facing capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions