projectInitiativeActive

    RPS Digital P3 Intake Archive

    RPS Digital is a digital-product commerce system centered on a public storefront plus an operational Shopify app and worker that generate product assets, manage releases, and deliver purchased files through secure expiring links.

    BuilderEntrepreneur

    Metadata

    Type
    Initiative
    Status
    Active
    Connected nodes
    11
    Curated visuals
    6 screenshots
    Product surfaces
    4
    Workflows
    2
    Supporting artifacts
    7

    Links

    View live surface →Open the map →Open repo →

    Narrative

    What the system does

    RPS Digital turns a digital-art catalog workflow into a Shopify-backed download business. The work connects a public storefront, a merchant app, generated product metadata, release records, secure download links, and supporting documentation so products can move from prompt or catalog input into purchasable files.

    How the work moves

    The core process starts with an operator prompt or bulk catalog input, turns that input into product metadata and image assets, stages the release for review, and then connects purchased orders to entitlement checks and expiring download URLs. The constraint that matters is control: AI can accelerate product creation, but naming, quality review, release state, and delivery access still need explicit operator decisions.

    Product surfaces

    Public Storefront And Product Discovery

    Shoppers

    The customer-facing surface for browsing digital products, inspecting listings, and moving into purchase or download flows.

    Prompt-To-Product Merchant Workflow

    Merchant operator

    The operator surface where prompts, defaults, and generated metadata become product drafts and release candidates.

    Catalog Intake And Release Operations

    Merchant operator

    Batch-oriented documentation and worker logic support repeatable asset generation, naming, release management, and import discipline.

    Secure Download Fulfillment

    Customer support and shoppers

    Order and entitlement records connect purchase proof to expiring download URLs so fulfillment is auditable and not manual.

    System design

    Data model

    Catalog Generation Model

    Prompt input, defaults, generated assets, products, releases, and background jobs form the repeatable generation loop for RPS Digital.

    promptdefaultsassetsproductsreleasesjobs
    Data model

    Secure Fulfillment Model

    Orders, entitlements, releases, and signed download URLs create a traceable chain from purchase to delivery.

    ordersentitlementsreleasesdownload tokenssigned URLs

    Commerce Application

    • • Shopify
    • • Remix
    • • React
    • • Polaris

    Automation And Assets

    • • TypeScript worker
    • • AI image generation
    • • Prompt templates
    • • Release pipeline

    Data And Delivery

    • • SQLite schema
    • • Google Cloud Storage
    • • Signed URLs
    • • Entitlement checks

    Workflows

    workflow5 steps

    Prompt-To-Product Release Loop

    Operator prompt inputs and catalog defaults become product drafts, generated image assets, release records, and reviewable storefront output. This workflow is the proof layer for how AI-assisted product creation stays inspectable instead of becoming a black-box generation step.

    workflow5 steps

    Secure Download Fulfillment

    Purchase proof is converted into entitlement records and expiring download links, with documentation and source code showing where the access decision happens. This workflow preserves the operational evidence for a customer-facing delivery path that could otherwise look like a simple download page.

    Supporting evidence

    noteStandard

    prompt-to-product

    Source Summary Prompt-to-Product Describe the artwork you want and the app generates a product draft with metadata and assets. Create a product from a prompt...

    Source reference available
    noteStandard

    downloads

    Source Summary Downloads Customers receive their files after purchase through secure links. Customer experience - After checkout, customers see a download pa...

    Source reference available
    noteStandard

    settings

    Source Summary Settings Use settings to control how products are generated and how downloads appear to customers. Default generation options - Choose your de...

    Source reference available
    noteStandard

    api.prompts

    Source Summary import { json, type ActionFunctionArgs } from '@remix-run/node'; import { randomUUID } from 'node:crypto'; import path from 'node:path'; impor...

    Source reference available
    noteStandard

    apps.downloads.$token

    Source Summary import { json, type LoaderFunctionArgs } from '@remix-run/node'; import { useLoaderData } from '@remix-run/react'; import { getEntitlementByTo...

    Source reference available
    noteStandard

    schema

    Source Summary CREATE TABLE IF NOT EXISTS shops ( id TEXT PRIMARY KEY, shopifydomain TEXT NOT NULL UNIQUE, accesstoken TEXT NOT NULL, createdat TEXT NOT NULL...

    Source reference available
    noteStandard

    logo

    Source Summary <svg width="120" height="120" viewBox="0 0 120 120" fill="none" xmlns="http://www. w3. Imported Context <svg width="120" height="120" viewBox=...

    Source reference available

    Visual evidence

    Public storefront homepage showing new arrivals, category navigation, featured collections, and the instant-download positioning.
    Local docs page for the prompt-to-product merchant workflow, used as evidence for the authenticated generation surface that is not publicly accessible.
    Local docs page describing post-purchase download behavior, signed links, and customer verification steps.
    Local docs page summarizing generation defaults, delivery behavior, and storage/AI-provider configuration boundaries.
    Product catalog view with filter controls and pagination, representing the shopper discovery surface for a large digital-download inventory.
    Product detail page showing price, instant-download labeling, license/format context, and add-to-cart flow.

    Key dates

    2026-04
    Source intake created

    The source repo includes an intake dossier with screenshots, hydration candidates, and implementation artifacts.

    2026-05-10
    P3 side-by-side import prepared

    The archive import keeps the existing RPS Digital project untouched while testing the proof-record intake contract.