Skip to content

Shared contracts crate (FeatureKey, Entitlement, DTOs) #21

Description

@AojdevStudio

Parent

#1 (Platform Spine Epic)

Plain English

Define the common vocabulary the desktop, cloud, and UI all share: the list of paid feature keys, the shape of a user's access, and the data passed over the API. Foundational; no behavior change yet.

What to build

crates/shared with a FeatureKey enum, an Entitlement model (plan, status, trial, features map, limits, license expiry), and the request/response DTOs for the API surface. Pure types, zero heavy dependencies.

Acceptance criteria

  • FeatureKey enum with baseline keys (export_pdf, cloud_sync, advanced_reports, team_members, max_projects, api_access)
  • Entitlement and DTO types serialize/deserialize round-trip in tests
  • crates/shared has no database, payment, or secret-loading dependencies

Blocked by

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

    model:sonnet-4.6Route this task to Claude Sonnet 4.6ready-for-agentFully specified, AFK-ready for a coding agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions