Roadmap

Planned user stories and test scenarios for SG/Send QA. This page is the living backlog — each story will become a test, a set of screenshots, and a documentation page on this site.

Current Coverage

flowchart LR
    subgraph done["Done ✓"]
        A[Landing Page\nLoads]
        B[Access Gate\nPresent]
        C[Invalid Token\nRejected]
    end
    subgraph next["Next Up"]
        D[Valid Token\nAccepted]
        E[File Upload\nFlow]
        F[File Download\nFlow]
    end
    subgraph later["Later"]
        G[Token Expiry]
        H[Admin Panel]
        I[Multi-file\nSharing]
    end
    A --> B --> C --> D --> E --> F
    D --> G
    H -.-> I

Next Up: Authentication Completion

These stories complete the token authentication flow — the foundation everything else builds on.

US-04: Valid Token Accepted

Field Value
Priority P0 — blocks all downstream stories
Test file tests/integration/user/test_valid_token.py (new)
Precondition TEST_ACCESS_TOKEN secret configured in CI

As a user with a valid Beta Access token, I want to enter my token and be granted access, so that I can use the file sharing features.

Acceptance criteria:

sequenceDiagram
    participant U as User
    participant B as Browser
    participant S as SG/Send

    U->>B: Enter valid token
    U->>B: Click Go
    B->>S: POST token
    S-->>B: 200 OK — session created
    B->>B: Render file sharing UI
    Note over B: Screenshot: authenticated state

Implementation notes:

US-05: Session Persistence After Token Entry

Field Value
Priority P1
Test file tests/integration/user/test_session.py (new)
Precondition US-04 (valid token)

As an authenticated user, I want my session to persist across page navigation, so that I don’t have to re-enter my token on every action.

Acceptance criteria:

File Sharing Flow

The core functionality of SG/Send — uploading and downloading encrypted files.

US-06: File Upload Flow

Field Value
Priority P0 — core feature
Test file tests/integration/user/test_file_upload.py (new)
Precondition US-04 (valid token)

As an authenticated user, I want to upload a file through the SG/Send interface, so that I can share it securely with others.

Acceptance criteria:

flowchart TD
    A[Authenticated user] --> B[Select file]
    B --> C[Upload initiated]
    C --> D{Upload success?}
    D -->|Yes| E[Share link generated]
    D -->|No| F[Error displayed]
    E --> G[Screenshot: share link]
    F --> H[Screenshot: error state]

Implementation notes:

US-07: File Download Flow

Field Value
Priority P0 — core feature
Test file tests/integration/user/test_file_download.py (new)
Precondition US-06 (file uploaded, share link available)

As a recipient, I want to download a shared file using the link I received, so that I can access the files shared with me.

Acceptance criteria:

Implementation notes:

US-08: Share Link Details Page

Field Value
Priority P1
Test file tests/integration/user/test_share_link.py (new)
Precondition US-06 (share link exists)

As a user who uploaded a file, I want to see details about my shared file (name, size, expiry), so that I can manage my shares.

Acceptance criteria:

Error Handling & Edge Cases

US-09: Token Expiry Handling

Field Value
Priority P2
Test file tests/integration/user/test_token_expiry.py (new)
Precondition An expired token available for testing

As a user with an expired token, I want to see a clear expiry message, so that I know to request a new token.

Acceptance criteria:

US-10: Empty Token Submission

Field Value
Priority P2
Test file tests/integration/user/test_landing_page.py (extend)
Precondition None

As a user who clicks Go without entering a token, I want to see a validation message, so that I know a token is required.

Acceptance criteria:

US-11: Large File Upload Behaviour

Field Value
Priority P3
Test file tests/integration/user/test_file_upload_large.py (new)
Precondition US-04 (valid token)

As a user, I want to understand the upload size limits, so that I know what files I can share.

Acceptance criteria:

Admin Panel

US-12: Admin Login

Field Value
Priority P1
Test file tests/integration/admin/test_admin_login.py (new)
Target URL https://send.sgraph.ai/admin/
Precondition ADMIN_API_KEY secret configured

As an admin, I want to log into the admin panel, so that I can manage tokens, view usage, and configure the platform.

Acceptance criteria:

sequenceDiagram
    participant A as Admin
    participant B as Browser
    participant S as SG/Send Admin

    A->>B: Navigate to /admin/
    B->>S: GET /admin/
    S-->>B: Admin login page
    A->>B: Enter API key
    B->>S: POST authentication
    S-->>B: Admin dashboard
    Note over B: Screenshot: dashboard

US-13: Admin Token Management

Field Value
Priority P2
Test file tests/integration/admin/test_token_management.py (new)
Precondition US-12 (admin authenticated)

As an admin, I want to create, view, and revoke access tokens, so that I can control who has access to the platform.

Acceptance criteria:

QA Infrastructure

US-14: Visual Regression Baseline

Field Value
Priority P1
Test file tests/unit/ci/test_diff_screenshots.py (new)

As a QA engineer, I want the visual diff system to reliably detect real UI changes and ignore rendering noise, so that screenshot commits are meaningful.

Acceptance criteria:

US-15: Documentation Auto-Update

Field Value
Priority P2
Test file tests/unit/cli/test_generate_docs.py (new)

As a QA engineer, I want the doc generator to scaffold new use-case pages automatically, so that new tests get documentation without manual work.

Acceptance criteria:

Priority Summary

gantt
    title Implementation Priority
    dateFormat YYYY-MM-DD
    axisFormat %b

    section Authentication
    Valid Token Accepted (US-04)     :crit, us04, 2026-02-24, 3d
    Session Persistence (US-05)      :us05, after us04, 2d

    section File Sharing
    File Upload Flow (US-06)         :crit, us06, after us04, 5d
    File Download Flow (US-07)       :crit, us07, after us06, 4d
    Share Link Details (US-08)       :us08, after us07, 2d

    section Error Handling
    Empty Token Submit (US-10)       :us10, 2026-02-24, 1d
    Token Expiry (US-09)             :us09, after us04, 2d
    Large File Upload (US-11)        :us11, after us06, 2d

    section Admin
    Admin Login (US-12)              :us12, after us05, 3d
    Token Management (US-13)         :us13, after us12, 4d

    section Infrastructure
    Visual Regression Tests (US-14)  :us14, 2026-02-24, 2d
    Doc Auto-Update Tests (US-15)    :us15, 2026-02-24, 2d
Priority Stories What It Unlocks
P0 US-04, US-06, US-07 Core flow: authenticate → upload → download
P1 US-05, US-08, US-12, US-14 Session handling, share details, admin access, visual regression
P2 US-09, US-10, US-13, US-15 Edge cases, admin management, doc tooling
P3 US-11 Size limits and constraints

How Stories Become Documentation

Each user story above will follow this lifecycle:

flowchart LR
    A[User Story\non Roadmap] --> B[Test Written\nin pytest]
    B --> C[Screenshots\nCaptured]
    C --> D[Doc Page\nGenerated]
    D --> E[Published to\nThis Site]
    E --> F[Story Moved to\nUse Cases Index]

When a story is implemented:

  1. A new test file is created under tests/integration/
  2. The test captures screenshots during execution
  3. generate_docs.py scaffolds a documentation page
  4. The page is enriched with context, diagrams, and annotations
  5. The story moves from this Roadmap to the Use Cases index