Artifacts
The Hyphenomenon archive of proof, evidence, and context. Organized by project and artifact type to support clear review and traceable decisions.
1-27 of 27 shown from 187 total
Active
| Summary | Tags | |||||
|---|---|---|---|---|---|---|
| Data modelXyppy App LP and Support Hub | Xyppy App LP and Support Hub | 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. | landing_pagesupport_centerfirst_edit_doc+1 | ModelRecorded | Jul 15, 2026 |
| Data modelXyppy Shopify Merchant App | Xyppy Shopify Merchant App | 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. | MerchantFilter DSLActionConfig+1 | ModelRecorded | Jul 15, 2026 |
| Data modelApp Growth Agent | App Growth Agent | 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. | AgentRunAgentStepLlmCall+1 | ModelRecorded | Jul 13, 2026 |
| Data modelApp Growth Agent | App Growth Agent | 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. | CampaignLead evidenceQualification+1 | ModelRecorded | Jul 13, 2026 |
| Data modelShopify AI Product Optimizer | Shopify AI Product Optimizer | 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. | TriggerAutomationSettingsCatalog criteria+1 | ModelRecorded | Jul 13, 2026 |
| Data modelShopify AI Product Optimizer | Shopify AI Product Optimizer | 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. | ShopProductAnalysisRun+1 | ModelRecorded | Jul 13, 2026 |
| Data modelMLNNA | MLNNA | 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. | GitHub repositoriesManual conversation logsNotion databases+1 | ModelRecorded | Jun 13, 2026 |
| Data modelChronicle Visualizer | Chronicle Visualizer | 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. | FrameNearby frameOCR text+1 | ModelRecorded | Jun 4, 2026 |
| Data modelChronicle Visualizer | Chronicle Visualizer | 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. | Raw frameWritten contextEncrypted S3 archive+1 | ModelRecorded | Jun 4, 2026 |
| Data modelThe Solo Mom Project | The Solo Mom Project | 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. | raw_sourceredacted_source_itemeditorial_chunk+1 | ModelRecorded | Jun 3, 2026 |
| Data modelThe Solo Mom Project | The Solo Mom Project | 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. | userproducttaxonomy_term+1 | ModelRecorded | Jun 3, 2026 |
| Data modelMaintain iOS | Maintain iOS | 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. | userSwiftUI appSwiftData store+1 | ModelRecorded | Jun 2, 2026 |
| Data modelCodex Skills Library | Codex Skills Library | 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. | plugins/<slug>/.codex-plugin/plugin.jsonplugin assetsbundled plugin skills+1 | ModelRecorded | May 27, 2026 |
| Data modelCodex Skills Library | Codex Skills Library | 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. | skills/<slug>/SKILL.mdskills/SUITE_SKILLS.txtskills/SUITE_METADATA.json+1 | ModelRecorded | May 27, 2026 |
| Data modelShopify Headless Storefront | Shopify Headless Storefront | 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. | source docrun manifestsummary+1 | ModelRecorded | May 23, 2026 |
| Data modelShopify Headless Storefront | Shopify Headless Storefront | 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. | agent catalog endpointagent checkout endpointorigin allowlist+1 | ModelRecorded | May 23, 2026 |
| Data modelShopify Headless Storefront | Shopify Headless Storefront | 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. | productsvariantscollections+1 | ModelRecorded | May 23, 2026 |
| Data modelRPS Digital P3 Intake Archive | RPS Digital P3 Intake Archive | Catalog Generation Model | Prompt input, defaults, generated assets, products, releases, and background jobs form the repeatable generation loop for RPS Digital. | promptdefaultsassets+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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. | forumsforum_threadsforum_posts+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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. | donor_profilesdonor_recipient_connectionsprivacy_settings JSONB+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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. | donor_profilespersonsdonor_recipient_connections+1 | ModelRecorded | May 17, 2026 |
| Data modelHow This Site Works | How This Site Works | 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. | operator promptsource repointake dossier+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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. | organizationsuser_profiles.organization_idgroups+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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. | organizationsorganization_membershipsorganization_invitations+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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. | organizationsgroupsfamily_trees+1 | ModelRecorded | May 17, 2026 |
| Data modelFamily Shapes | Family Shapes | 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_treesfamily_tree_memberspersons+1 | ModelRecorded | May 17, 2026 |
| Data modelRPS Digital P3 Intake Archive | RPS Digital P3 Intake Archive | Secure Fulfillment Model | Orders, entitlements, releases, and signed download URLs create a traceable chain from purchase to delivery. | ordersentitlementsreleases+1 | ModelRecorded | May 17, 2026 |
1-27 of 27 results