Dossier

    Project Intake - Xyppy Print This

    Xyppy Print ThisUpdated Aug 16, 2026
    Markdown file

    Imported markdown

    Project Intake - Xyppy Print This

    1) Executive Summary

    The project and the plugin are two proof surfaces of the same product. The private repository is the current implementation source; the connected personal ChatGPT plugin is the host integration. Repository verification passed on 2026-08-16 with 17 tests, typecheck, build, manifest generation, and docs links. Historical evidence proves that the custom widget rendered in ChatGPT Developer Mode on 2026-08-14. A fresh invocation of the user-linked plugin on 2026-08-16 failed because its temporary MCP endpoint was unavailable, so this intake does not claim that the plugin is currently operational.

    No cart, checkout session, order, payment, production file, or fulfillment task was created during the source project or this intake.

    2) Project Type and Domain

    • Project Type: private software project, MCP app server, React custom UI, and personal ChatGPT plugin.
    • Status: active. The three-day prototype is complete; launch-readiness work remains active.
    • Domain: ecommerce, custom printing, wall art, conversational commerce, image tooling, and human-reviewed fulfillment.
    • Trail: eCommerce.
    • Primary user: someone who has an image in ChatGPT or on their device and wants to understand how it can become a physical print.
    • Product boundary: configuration and preview are implemented; live commerce and production are explicitly disabled.

    3) Repository and Live URLs

    • Repository: Private Xyppy ChatGPT repository.
    • Durable public app URL: Unknown. The project has not been deployed to an approved long-running host.
    • Plugin surface: installed as a personal ChatGPT app, with no public directory page.
    • Historical endpoint: a temporary Cloudflare development tunnel was used for Developer Mode proof; it is not durable hosting and was unavailable during this intake.

    4) Product/User Journey Summary

    1. The user invokes Xyppy Print This around an image they want to print.
    2. The app accepts a host-supplied image when available, offers ChatGPT file selection, and preserves local upload as a fallback.
    3. Image dimensions are inspected to estimate DPI, crop loss, and suitable print sizes.
    4. The user configures size, archival or fine-art paper, frame, mat, layout, and quantity while seeing a representative preview and deterministic prototype price.
    5. Continue opens a demo summary that repeats the selected configuration and states that no real order exists.
    6. The optional checkout preview prepares a stable quote ID, provider-specific handoff fields, estimated shipping, and next backend action without creating a cart or checkout session.
    7. A future approved backend would translate the reviewed quote into merchant-hosted checkout, followed by separate image, order, production, and fulfillment review.

    5) Architecture and Stack Summary

    • Runtime: Node.js, TypeScript, Express, and the Model Context Protocol SDK.
    • ChatGPT app layer: @modelcontextprotocol/ext-apps tool and widget registration with a single-file React UI resource.
    • Frontend: React 19, Vite, TypeScript, and self-contained CSS/assets suitable for an embedded iframe.
    • Tool contract: source main registers read-only, idempotent configure_print and preview_checkout tools; both explicitly deny transactional side effects.
    • Image handling: ChatGPT file helpers are feature-detected; browser upload and object URLs provide fallback behavior.
    • Product logic: shared deterministic catalog, pricing, size recommendation, image assessment, quote, and checkout-handoff modules.
    • Commerce boundary: runtime readiness reports whether required provider configuration exists, but canCreateLiveCheckout remains false.
    • Verification: Vitest, Testing Library, TypeScript, Vite production build, MCP contract checks, launch checks, docs manifest/link checks, and repository-owned visual evidence.

    6) Key Workflows and Operational Flows

    In-chat print configuration

    invoke plugin -> resolve or choose image -> inspect dimensions -> recommend sizes -> configure materials and layout -> calculate prototype estimate -> review demo summary

    Safe checkout preview

    review configuration -> generate deterministic quote -> map Shopify-first handoff fields -> show shipping and next action -> keep live checkout disabled

    Promotion to a durable plugin

    verify source -> choose durable host -> deploy MCP and widget -> refresh ChatGPT metadata -> invoke the installed app -> review current tool/widget behavior -> decide separately on live commerce

    The fresh plugin invocation attempted during this intake stopped at the endpoint connection boundary. No fallback was represented as current plugin proof.

    7) AI Context: Prompts, Chats, Agent Workflows

    • The original ChatGPT idea conversation narrowed a broad wall-art plugin concept to the custom-print utility wedge and is published as xyppy-plugin-library-idea-6a7b2581.
    • The linked Codex implementation session planned, built, validated, and connected the prototype and is published as xyppy-print-this-build-019ff1ea.
    • The app's server instructions prohibit claims that checkout, payment, production, or fulfillment occurred.
    • ChatGPT-specific file APIs are treated as optional host capabilities rather than assumed behavior.
    • Human review remains required before durable hosting, checkout backend selection, asset retention, live cart/session creation, production, or fulfillment.

    8) Supporting Docs and External Resources

    Hydration Source Artifacts

    Artifact (relative repo path)Canonical URLTypeHydration value
    README.mdGitHub sourcemarkdownConcise product contract, runtime commands, Developer Mode path, and commerce boundary.
    DOCS/PROJECTS/active/1001_xyppy_chatgpt_app.mdGitHub sourcemarkdownParent vision, initial wedge, milestones, and platform risks.
    DOCS/PROJECTS/completed/1002_xyppy_print_this_prototype.mdGitHub sourcemarkdownComplete prototype scope, visual gate, Developer Mode proof, and explicit exclusions.
    DOCS/PROJECTS/active/1003_xyppy_launch_readiness.mdGitHub sourcemarkdownCurrent launch decisions, checkout-preview contract, hosting options, and unresolved gates.
    server/index.tsGitHub sourcetextAuthoritative MCP tool metadata, resource registration, health endpoint, and side-effect boundary.
    DOCS/evidence/active/1002/platform/chatgpt-widget-rendered.jpgGitHub sourceimageHistorical visual proof that ChatGPT rendered the connected custom widget in Developer Mode.

    No .pdf or .docx source artifact exists in the source repository.

    9) Screenshot Gallery (with relative links + captions)

    1. Configurator desktop - Standalone desktop surface showing the first-load image placeholder, full print controls, prototype pricing, and explicit no-order notice.
    2. Configured image workflow - Primary workflow with an image, DPI warning, recommended sizes, material choices, representative framing, and a two-print estimate.
    3. Demo summary - Key completion state showing the configured print and the explicit statement that no order, payment, or production file exists.
    4. Checkout preview - Operational handoff equivalent showing stable quote metadata, Shopify-first backend mapping, shipping preview, and the disabled live-checkout control.
    5. Plugin rendered in ChatGPT - Historical platform evidence from the successful Developer Mode connection, distinct from the current failed endpoint probe.

    10) Candidate Import Nodes and Relationships

    Minimum durable shape

    • One active project: Xyppy Print This (xyppy-print-this, eCommerce).
    • One first-class plugin contract data model: host invocation, MCP tools, widget resource, image transfer, configuration state, and side-effect boundary.
    • One checkout-handoff data model: deterministic quote, provider mapping, asset requirement, and manual-review status.
    • Two workflows: in-chat image-to-print configuration and evidence-gated promotion to a durable connected app.
    • Six hydrated notes and five project-owned screenshots.
    • Two related chat records: the original product-idea conversation and the Codex implementation session.

    Relationships

    • Xyppy Print This project -> demonstrates -> in-chat plugin workflow.
    • Xyppy Print This project -> documented by -> plugin contract, checkout-handoff model, and screenshot gallery.
    • Plugin workflow -> originated in -> xyppy-plugin-library-idea-6a7b2581.
    • Plugin workflow -> implemented through -> xyppy-print-this-build-019ff1ea.
    • configure_print -> opens -> the Xyppy configurator widget.
    • Configurator state -> produces -> a demo summary and optional checkout preview.
    • Checkout preview -> cannot create -> carts, sessions, orders, payments, production files, or fulfillment tasks.

    11) Risks, Gaps, and Unknowns

    • The current installed plugin could not connect during this intake because its temporary MCP endpoint was unavailable. Current host rendering and tool discovery are therefore unverified.
    • Source main registers two tools, while the currently cached connector description exposed only configure_print; the endpoint failure prevented a live metadata refresh or exact capability comparison.
    • There is no durable public host or Plugin Directory page.
    • Direct transfer of the immediately preceding generated image remains host-dependent; file selection and upload are required fallbacks.
    • Prototype prices, shipping estimates, frame previews, and crop treatments are not authoritative manufacturing or commerce data.
    • Live Shopify or Stripe checkout, image storage/retention, production-file generation, and fulfillment remain unimplemented and require explicit decisions.
    • The GitHub repository is private; public readers may not be able to open source links.
    • The source repository contains no .pdf or .docx hydration candidates.

    12) Handoff Checklist for Hyphenomenon Import

    • Read source AGENTS.md, CHANGELOG.md, ROADMAP.md, README, canonical project docs, and evidence.
    • Confirmed clean source main matching origin/main at 538c591bbdae182ca2bbc79b67426f32b967ea8a before verification.
    • Ran source typecheck, 17 tests, production build, docs manifest generation, and docs link validation successfully.
    • Reverted the generated manifest timestamp so the source repository remained clean.
    • Invoked the user-linked installed plugin and recorded its current endpoint connection failure without claiming current runtime success.
    • Reused five reviewed repository-owned product/plugin screenshots; no synthetic product screenshots were generated.
    • Created the Hyphenomenon-owned dossier, hydration payload, project-page packet, workflow packet, runtime probe, rollback plan, and dry-run evidence.
    • Applied the absent project as project-intake-apply-2026-08-16T11:07:08.285Z, then the two workflows as workflow-packet-apply-2026-08-16T11:07:20.713Z.
    • Reapplied both chat records after project creation so each received one verified created_from_conversation backlink while the Codex-to-ChatGPT relation remained intact.
    • Production drift passed at 258 nodes / 242 edges.
    • Verified the project, two workflow, two data-model, five screenshot/image-evidence, two source-chat, Explore, Artifact Index, and sitemap surfaces in production.

    Dataset Preview

    • Raw CSV row/table content is available in the source artifact.