artifacts

    Proof, evidence, and context, organized by project and artifact type.

    38 of 433 artifacts

    Active
    Data modelWork date: Date unknown

    Aerial — connected records and permission boundaries

    I keep the relationship graph, institutional source records, and permission grants distinct so a visible aggregate never implies access to every identity or document.

    Aerial
    Data modelWork date: Date unknown

    Ambient work-history context lineage

    A before-and-after entity model for legacy Chronicle frames/OCR/mosaics and current Computer History interaction events/Accessibility context, including summaries, archives, coverage gaps, redaction decisions, and public derivatives.

    Data modelWork date: Date unknown

    Acquisition-to-value experiment lifecycle

    The experiment joined discovery, qualification, reviewed outreach, attribution, product telemetry, activation, and review prompting into one stateful loop so growth actions could be inspected against real downstream value.

    App Growth Agent
    Data modelWork date: Date unknown

    Agent trace and action boundary

    A campaign tick records every model-assisted step and preserves an explicit decision boundary between generated work and external action.

    App Growth Agent
    Data modelWork date: Date unknown

    BPE merchant support flow

    Merchant guidance moves from feature promise into support docs, then into a safe first-edit loop that uses preview and verification before trusting a bulk catalog change.

    Xyppy App LP and Support Hub
    Data modelWork date: Date unknown

    Chronicle Daily Report Analyzer v2

    The Chronicle analyzer that turns persisted ten-minute summaries into coverage, citation, app-mention, and overlapping work-lane evidence.

    Hyphenomenon
    Data modelWork date: Date unknown

    Local viewer evidence relationship model

    The local viewer binds a selected frame to its time, source path, nearby frames, noisy OCR, inferred project labels, and closest Chronicle summary, while keeping those relationships private until reviewed.

    Chronicle Visualizer
    Data modelWork date: Date unknown

    Private archive and public derivative boundary

    Chronicle Visualizer separates raw capture ingestion, private encrypted archive storage, redaction candidate processing, human approval, and public derivative publication so useful visual evidence does not leak private screen context.

    Chronicle Visualizer
    Data modelWork date: Date unknown

    Plugin Backup Model

    Custom local plugin bundles stay in `plugins/` with plugin metadata and registry records so larger workflow surfaces are preserved without pretending they are ordinary standalone skills.

    Codex Skills Library
    Data modelWork date: Date unknown

    Skill Suite Catalog Model

    The source suite maps portable skill folders through an allowlist and lifecycle metadata into generated Markdown, JSON, and TypeScript catalog surfaces.

    Codex Skills Library
    Data modelWork date: Date unknown

    Codex Usage Report Analyzer v5

    The report analyzer that de-duplicates sessions, separates observed tool evidence from availability, and verifies delivery through terminal outcomes.

    Hyphenomenon
    Data modelWork date: Date unknown

    Community Content And Media Model

    The linked schema confirms that Family Shapes includes a real content and community system. Forums branch into threads and posts, blog posts branch into comments, resources stand on their own, and media albums link to media files through join rows.

    Family Shapes
    Data modelWork date: Date unknown

    Donor Boundary and Health Model

    The donor surface is backed by a distinct donor profile model that connects privacy settings, health updates, and donor-recipient relationship state instead of treating donor controls as simple account preferences.

    Family Shapes
    Data modelWork date: Date unknown

    Donor Profile And Connection Model

    The donor layer is real in the schema, not just the UI. `donor_profiles` stores donor-specific identity, privacy, and health fields, while `donor_recipient_connections` tracks the relationship state between donor profiles, organizations, and recipient-side users.

    Family Shapes
    Data modelWork date: Date unknown

    Organization and Oversight Model

    The clinic and cryobank layer depends on organizations as the tenant and oversight anchor, tying professional users to shared operational views, people records, and family relationship context.

    Family Shapes
    Data modelWork date: Date unknown

    Organization Membership And Oversight Model

    The remote schema makes the institutional layer much clearer: organizations connect to memberships, invitations, user profiles, groups, family trees, persons, and donor-recipient operations. That is a stronger SaaS and coordination story than the earlier editorial model captured.

    Family Shapes
    Data modelWork date: Date unknown

    Relationship Graph And Access Model

    The linked Supabase schema shows Family Shapes as a graph product with explicit access control. Family trees can belong to groups or organizations, persons join trees through membership rows, connections link people, and collaborator plus invitation tables govern who can work inside a sensitive tree.

    Family Shapes
    Data modelWork date: Date unknown

    Relationship Graph Core

    Family Shapes centers the product on family trees, people, and connections, then layers collaboration and invitations on top so sensitive relationship graphs can be explored and maintained safely.

    Family Shapes
    Data modelWork date: Date unknown

    One-prompt intake artifact flow

    The hardened process shows how a simple prompt with local paths becomes a dossier, packets, dry-run reports, local database records, and public review surfaces.

    Hyphenomenon
    Data modelWork date: Date unknown

    Maintain app and backend loop

    The native app captures maintenance context locally, syncs authenticated changes through Worker routes, and uses staging/TestFlight gates before broader release decisions.

    Maintain iOS
    Data modelWork date: Date unknown

    MLNNA sync, synthesis, snapshot, and review loop

    The system moves from repository activity and manual context through Notion, AI synthesis, snapshot export, dashboard rendering, and human review. Human correction remains part of the loop because AI fields are inferential.

    MLNNA
    Data modelWork date: Date unknown

    Mailbox identity, plan, and receipt boundary

    A human alias resolves to one immutable account and live provider identity; all reversible mutation evidence remains bound to that identity from preview through rollback.

    Multi Mailbox Ops
    Data modelWork date: Date unknown

    Coverage ledger and scheduled delivery state

    Hourly mailbox coverage and scheduled report delivery use independent checkpoints so classification can progress without losing an unreported or unacknowledged delivery.

    Multi Mailbox Ops
    Data modelWork date: Date unknown

    Project Intake + Dossier Analyzer v1

    The baseline project-intake contract: a manually reviewed source packet became one project record and a small set of linked evidence.

    Hyphenomenon
    Data modelWork date: Date unknown

    Project Intake + Dossier Analyzer v2

    The dossier-era analyzer that expanded intake into structured project context, related evidence, and repeatable validation.

    Hyphenomenon
    Data modelWork date: Date unknown

    Project Intake + Dossier Analyzer v3

    The P3 intake analyzer: discovery-first packets, dry-run comparison, additive evidence, and safeguards against accidental project-page overwrites.

    Hyphenomenon
    Data modelWork date: Date unknown

    Catalog Generation Model

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

    RPS Digital P3 Intake Archive
    Data modelWork date: Date unknown

    Secure Fulfillment Model

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

    RPS Digital P3 Intake Archive
    Data modelWork date: Date unknown

    Automation and permission boundary

    A product can enter the pipeline through a webhook, schedule, or manual run, but criteria, billing, risk mode, and explicit review determine whether generation becomes action.

    Shopify AI Product Optimizer
    Data modelWork date: Date unknown

    Product evidence and suggestion lifecycle

    The experiment preserved a source product snapshot, deterministic analysis evidence, generated alternatives, and a reversible action record instead of treating model output as the catalog's new truth.

    Shopify AI Product Optimizer
    Data modelWork date: Date unknown

    Bulk edit job and rollback lifecycle

    A merchant configures a task, the app queues and executes Shopify mutations in controlled batches, stores before-values and logs, and exposes rollback or manual recovery paths from Job History.

    Xyppy Shopify Merchant App
    Data modelWork date: Date unknown

    Agentic API Gate Model

    External agent access is intentionally constrained by feature flags, catalog mode, checkout mode, allowed origins, path validation, Shopify token selection, and structured error contracts.

    Shopify Headless Storefront
    Data modelWork date: Date unknown

    Cutover And Catalog Evidence Model

    The proof system separates source docs, generated run manifests, summaries, compare CSVs, review-board manifests, media upload reports, product-media ledger outputs, and human approval checkpoints.

    Shopify Headless Storefront
    Data modelWork date: Date unknown

    Storefront Commerce Model

    The public app maps Shopify products, variants, collections, menus, blogs, articles, cart lines, checkout URLs, reviews, feeds, and customer-account state into customer-facing routes and machine-readable endpoints.

    Shopify Headless Storefront
    Data modelWork date: Date unknown

    Solo Mom editorial governance model

    Restricted source material is normalized into redacted corpus records, retrieval annotations, ideas, calendar entries, briefs, drafts, and review decisions before public blog publication.

    The Solo Mom Project
    Data modelWork date: Date unknown

    Solo Mom resource and taxonomy model

    Public resources are persisted as products, linked to taxonomy terms and contribution/moderation records, then surfaced through directory, taxonomy, search, and admin workflows.

    The Solo Mom Project
    Data modelWork date: Date unknown

    Xyppy checkout handoff boundary

    A stable quote preserves print selections and production prerequisites while separating preview metadata from future merchant checkout and fulfillment.

    Xyppy Print This
    Data modelWork date: Date unknown

    Xyppy Print This plugin contract

    The connected ChatGPT surface, MCP tools, widget resource, optional host image, and print configuration form one read-only plugin boundary.

    Xyppy Print This

    1-38 of 38 results