One index for the public artifacts behind the work: notes, workflows, chats, images, data models, and datasets.
136 shown
A stale but relevant local AI infrastructure workflow showing how the self-hosted n8n/Ollama/Qdrant/Postgres starter kit was adapted for day-to-day AI Ops use with local setup, startup, backup, restore, and recovery notes. It belongs as runtime evidence because it explains the infrastructure substrate behind agent and automation experiments.
A stale but story-bearing LangGraph prototype that models an LLM supervisor routing marketing work between SEO and email specialists, then returning each specialist result to the CMO node until the graph finishes. It is useful runtime evidence for early agent orchestration thinking in the AI Ops trail.
A killed but useful AI Ops dashboard planning workflow that describes Notion as the editable project/activity source of truth, snapshot exports as the interchange layer, and a private Observable notebook as the review UI. It belongs in runtime as lineage for the dashboard automation experiments rather than as a separate public project page.
Report-only heartbeat automation that reviews the Hyphenomenon intake queue each morning, summarizes active queue IDs and next actions for the operator, and preserves the human review boundary by refusing artifact creation, file edits, sync/apply commands, production mutation, or raw transcript preservation.
Codex thread that separated intake candidates from completed intake logs, added stable queue IDs, chose a daily report-only automation, and extended chat evidence so created automations can link to workflow evidence.
How local skill or plugin changes become durable repository artifacts: inspect the repo instructions, compare local skill homes to the allowlisted suite, decide whether new local work belongs in the curated catalog, regenerate source-backed indexes, review docs-site output, and record drift or blockers before publishing or handoff.
Gemini AI Mode thread researching cryobank workflows, donor-profile verification gaps, cross-bank registry blind spots, and technical requirements for a Family Shapes transparency and privacy platform.
Codex thread that defined Maggie Todo as a top-level Codex orchestration layer, hardened its Markdown-first project/checkpoint contract, moved the initial setup docs to completed, and scanned local repos for actionable Maggie-owned todo blockers.
Screenshot preserved from the Maggie Todo setup and Hyphenomenon intake queue thread, showing the feedback context that produced the image-evidence dependency.
How the Shopify Headless project moves from issue, content audit, catalog review, or cutover need into live storefront change: inspect source and production state, create reviewable evidence artifacts, get human/operator approval for live Shopify or deploy mutations, apply bounded changes, and verify public routes plus repo evidence afterward.
Codex thread that created the Maggie Todo aggregate repo, recorded the Hyphenomenon intake queue, preserved the screenshot evidence, and defined the connected intake batch.
Codex thread that audited Shopify-backed RPS blog articles, checked link/media quality, and carried the approved Anna Atkins hero/mockup remediation through production verification.
Codex session that turned RPS Shopify catalog work into a more durable operating system: local branch cleanup, catalog-health prioritization, source-image alt text, artist attribution, collection strategy, custom-product route planning, and a lightweight PDP-native product-studio direction.
Codex thread that consolidated scattered Faire lead and customer exports, separated existing customers from a 50-contact outreach queue, and created a private lead-ops repo with Context Layer docs and campaign tracking.
How a generated Hyphenomenon project stays editable and accountable after the first intake run: local pages expose the draft record, the operator reviews narrative, artifacts, workflows, and graph links, then decides whether to revise the packet, keep the record local, or later request a separate production apply.
How a new Hyphenomenon project starts with one operator prompt that names the intake skill, local repo path, project title, and route context, then becomes a reviewable project page, workflow record, notes, screenshots, and graph membership through scaffold, hydration, dry-run, and human approval.
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.
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.
How raw work traces become reviewed public evidence across Hyphenomenon's projects, notes, workflows, chats, screenshots, and map.
How professional operators enter the clinic-facing surface, onboard an organization context, and use the dashboard for member management and donor-program oversight.
How donors use Family Shapes to manage profile completeness, privacy choices, health history, and communication settings through a dedicated donor experience.
How recipient families move from discovery and onboarding into privacy-aware family-tree exploration, connection review, and relationship follow-up.
Clerk middleware and auth routes are present in code; source docs still include legacy NextAuth references.
Adjacent generation pipeline using n8n/ImageMagick/Puppeteer for wall-art assets, PDFs, and CMS registration flows.
GitHub Actions workflows for CI checks, schema drift detection, sync jobs, and Vercel deployment orchestration.
Search/discovery system including structured SEO metadata and Google Merchant Center feed endpoints.
Prisma-backed transactional data model for orders, downloads, licenses, and customer records.
Token-gated download endpoint that signs private Google Cloud Storage URLs and enforces download limits.
Stripe Checkout and webhook-driven order/download generation pipeline for post-purchase delivery.
Next.js App Router storefront with Tailwind UI and Redux state for browsing and purchase flows.
Catalog of 73 n8n workflow artifacts spanning ecommerce operations, Shopify automation, AI-assisted content, and agentic workflow experiments.
Conversation mapping the multi-agent orchestration landscape, shortlisting likely platforms, and refining a solo product studio plan with a focus on experimentation speed and distribution pipelines.
Conversation focused on finding credible paths into complexity-systems work and frontier R&D roles, with emphasis on signaling through public experimentation and network proximity.
Conversation defining the right one-page product document patterns for micro-SaaS and converting that guidance into a reusable Codex docs retrofitting skill contract.
Decision to capture ChatGPT conversations and key decisions inside Hyphenomenon as constellation nodes.
Source Summary Agent Instructions These instructions apply to all AI assistants working in this repository. Core Rules - Always review CHANGELOG. Imported Co...
Paused agent-growth experiment for compliant early-user acquisition and Shopify app growth workflows.
Source Summary Changelog All notable changes to this project will be documented in this file. The format is based on , and this project aims to follow . [Unr...
Source Summary title: Docs index description: "TODO: Add description" status: draft lastUpdated: 2026-02-17 owner: Documentation --- Docs index If you only o...
Source Summary title: Development Roadmap description: Future development plans and milestones status: evolving lastUpdated: "2026-02-17 11:42 ET (America/Ne...
What the lightweight Notion-first and dashboard-heavy phases taught us before we narrowed into Project Compass.
The durable decision model behind Project Compass and the solution loop that turns scattered repo evidence into a trustworthy portfolio view.
Marketing landing page for the BPE commerce product, linked to the Render-wired Shopify bulk editor app rather than treated as the app itself.
Source Summary { "name": "cult-landing-page", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "format": "prett...
Source Summary Get started Install dependencies and run Next. js bash pnpm i pnpm run dev or npm i npm run dev or yarn yarn dev open http://localhost:3000/ i...
Source Summary © MasgieLeman by Googe Soper CODEX SKILLS LIBRARY PUBLIC CODEX SKILLS LIBRARY CURRENT Focus r WwW Nn Co . Maggie Lerman y Buildingin public I]...
Source Summary Repository Guidance This repository stores portable custom Codex skills, backups of custom local plugins, and the docs/scripts that maintain b...
Codex Skills Library is the durable source repository for Maggie Lerman's custom Codex skills, custom local plugin backups, generated skill catalogs, and the public docs site that explains the workflows. The repo turns local agent behavior into portable, inspectable artifacts: each skill folder carries trigger metadata, instructions, references, scripts, examples, assets, and validation expectations, while the catalog tooling keeps the public docs aligned with the suite allowlist.
Source Summary { "name": "context-layer", "version": "0. 1. Imported Context { "name": "context-layer", "version": "0.1.0", "description": "Skill package for...
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.
Source Summary Maggie Lerman Codex Skills Site This is the public marketing and documentation site for Maggie Lerman's Codex skills library. It is intentiona...
The source suite maps portable skill folders through an allowlist and lifecycle metadata into generated Markdown, JSON, and TypeScript catalog surfaces.
Source Summary Agent Instructions These instructions apply to all AI assistants working in this repository. Core Rules - Always review CHANGELOG. Imported Co...
Source Summary title: Changelog description: Chronological list of notable changes status: stable lastUpdated: "2026-02-11 14:19 ET (America/NewYork)" owner:...
Retired Replit-era dashboard automation experiment with Neon and auth/runtime lessons, linked to the other killed dashboard attempts.
Source Summary title: Documentation Index description: Canonical documentation map for the project status: stable lastUpdated: "2026-02-13 07:22 ET (America/...
Source Summary title: Development Roadmap description: Future development plans and milestones status: evolving lastUpdated: "2026-02-11 14:19 ET (America/Ne...
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.
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.
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.
A linked breakdown of the family, donor, clinic or cryobank, and community surfaces that make Family Shapes a multi-surface platform.
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.
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.
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 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.
One-page product summary covering users, problem, MVP scope, and success metrics
Plan and implement a multi-tenant SaaS portal for cryobanks and clinics with RBAC, billing, analytics, and professional workflows, separate from the Family and Donor apps
Comprehensive documentation of the Donor Portal feature
Product vision, scope, and system map for Family Shapes
Inventory and rationalization across frontend and backend
Source Summary title: Database Operations and Maintenance description: Operational procedures for Neon persistence, migrations, verification, and rollback st...
Source Summary title: Projects description: Public list/detail pages for project supernodes that function as Hyphenomenon's primary project and proof surface...
Source Summary title: Workflows description: Public list/detail pages for workflow entries with Mermaid diagrams sourced from the merged content catalog stat...
Source Summary title: Solution Implementation description: How Hyphenomenon implements its editorial public-experience and living-map strategy via data model...
How This Site Works is an onboarding project for Hyphenomenon itself: it explains how a new project can start with one operator prompt that names the Hyphenomenon intake skill, the local repo path, source paths, a project title, and route context.
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.
Source Summary id: "0002" title: Hyphenomenon Intake Queue status: active track: hyphenomenon owner: Maggie updated: 2026-05-23 --- Hyphenomenon Intake Queue...
Source Summary QO @® OO <« rps-blogs v 0 B88 0 A 4g owes: Google Drive = visual/binary source of truth Q Search Repo manifest = durable machine-readable cata...
Maggie Todo is a Markdown-first aggregate todo and context-layer repository for Maggie-owned work, personal follow-ups, cross-project manual tasks, evidence, and generated local dashboard views. It is intentionally not a live app or website; its primary runtime surface is a local static dashboard generated from markdown todo sources.
Source Summary DOCS Canonical context layer root for the Maggie Todo aggregate. This repo tracks: - personal todos - Maggie-owned manual follow-ups - cross-p...
Source Summary Agent Instructions These instructions apply to all AI assistants working in this repository. Core Rules - Always review CHANGELOG. Imported Co...
Source Summary title: Changelog description: Chronological list of notable changes status: stable lastUpdated: "2026-05-04 07:03 ET (America/NewYork)" owner:...
Native iOS maintenance and habit-support app with backend coordination, treated as active but needing source-state refresh because the local branch is ahead and behind origin.
Source Summary title: Documentation Index description: Canonical documentation map for the project status: stable lastUpdated: "2026-04-05 16:41 ET (America/...
Source Summary title: Development Roadmap description: Future development plans and milestones status: evolving lastUpdated: "2026-05-04 07:03 ET (America/Ne...
Year-by-year operating model covering occupancy and ADR assumptions, expenses, NOI, debt service, cashflow, and DSCR trajectory.
Borrower context assumptions for age, employment, credit profile, income, and investable assets used in financing scenarios.
Exit sensitivity scenarios showing modeled net proceeds and gain or loss under cost-basis and downside sale outcomes.
Top-line scenario sheet with purchase and financing assumptions, year-one cashflow, ten-year IRR, and modeled net-sale proceeds.
Financing matrix across down-payment tiers and 15/30-year terms with monthly payment and total-interest comparisons.
Downside and upside operating scenarios with resulting NOI, cashflow, and DSCR impacts under changing demand assumptions.
Retired GitHub-to-Notion-to-Observable dashboard automation experiment, preserved as AI Ops process evidence rather than a live dashboard.
Source Summary { "name": "notion-project-dashboard-automation-root", "private": true, "dependencies": { "better-auth": "^1. 5. Imported Context { "name": "no...
Source Summary title: Documentation Index description: Canonical documentation map for the project status: stable lastUpdated: 2026-02-10 owner: Documentatio...
Source Summary Agent Instructions These instructions apply to all AI assistants working in this repository. Core Rules - Always review CHANGELOG. Imported Co...
Source Summary title: Changelog description: Chronological list of notable changes status: stable lastUpdated: "2026-03-22 12:07 ET (America/NewYork)" owner:...
Retired operator dashboard and repository-intelligence experiment, useful as evidence for why current context layers emphasize source-backed checkpoints.
Source Summary title: Documentation Index description: How to navigate the docs for Portfolio Command, the private AI-assisted portfolio command center. stat...
Source Summary title: Development Roadmap description: Future development plans and milestones status: evolving lastUpdated: "2026-03-22 13:07 ET (America/Ne...
Source Summary import { json, type ActionFunctionArgs } from '@remix-run/node'; import { randomUUID } from 'node:crypto'; import path from 'node:path'; impor...
Source Summary import { json, type LoaderFunctionArgs } from '@remix-run/node'; import { useLoaderData } from '@remix-run/react'; import { getEntitlementByTo...
Prompt input, defaults, generated assets, products, releases, and background jobs form the repeatable generation loop for RPS Digital.
Source Summary Downloads Customers receive their files after purchase through secure links. Customer experience - After checkout, customers see a download pa...
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 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 Summary CREATE TABLE IF NOT EXISTS shops ( id TEXT PRIMARY KEY, shopifydomain TEXT NOT NULL UNIQUE, accesstoken TEXT NOT NULL, createdat TEXT NOT NULL...
Orders, entitlements, releases, and signed download URLs create a traceable chain from purchase to delivery.
Source Summary Settings Use settings to control how products are generated and how downloads appear to customers. Default generation options - Choose your de...
Source Summary Changelog All notable changes to this project will be documented in this file. The format is based on Keep a Changelog, and this project adher...
Source Summary { "name": "shopify-ai-product-optimizer", "version": "1. 0. Imported Context { "name": "shopify-ai-product-optimizer", "version": "1.0.0", "pr...
Source Summary Documentation index This folder is the source of truth for project docs, day-to-day handoff notes, and decisions. Quick links - Handoff (start...
Source Summary services: - type: web name: shopify-ai-product-optimizer-web runtime: node plan: free region: oregon branch: main buildCommand: npm ci --inclu...
Paused Shopify AI product SEO optimizer prototype with Render web/worker evidence, treated as an AI Ops and commerce automation experiment.
Source Summary Agent Instructions These instructions apply to all AI assistants working in this repository. Core Rules - Always review CHANGELOG. Imported Co...
Source Summary @shopify/shopify-app-template-remix 2026. 03. Imported Context @shopify/shopify-app-template-remix 2026.03.10 [1001] Refreshed lifecycle email...
Source Summary title: Documentation Index description: Canonical documentation map for the project status: stable lastUpdated: "2026-03-09 14:52 ET (America/...
Source Summary title: Development Roadmap description: Near- and mid-term priorities for release readiness and platform maintenance status: evolving lastUpda...
Render-wired Shopify bulk product editor app for xyppy.com/BPE, preserved as the application half of the BPE commerce pair.
Source Summary title: 1110 - Blog Content Audit and Remediation description: Audit and remediate current Shopify blog article quality, article media, article...
External agent access is intentionally constrained by feature flags, catalog mode, checkout mode, allowed origins, path validation, Shopify token selection, and structured error contracts.
Source Summary title: Agentic Commerce API Endpoints description: Feature-flagged catalog and checkout-prep API contracts for external agents. status: evolvi...
Source Summary title: Catalog Review Workflow description: Standard operating pattern for numbered review boards, collaborative catalog cleanup, and audit-ba...
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 Summary title: Cutover Evidence System description: Repo-canonical workflow for preflight reruns, normalized compare output, master-pack generation, a...
Source Summary title: PRD: Shopify Headless Storefront (MVP) description: MVP requirements and constraints for the Shopify headless storefront implementation...
Source Summary Brand image artifact for the Rock Paper Scissors production storefront identity. Imported Context This image source is the public RPS primary...
Source Summary title: Product brief: Shopify Headless Storefront description: One-page summary of user problem, MVP scope, and success metrics for the headle...
Source Summary Rock Paper Scissors Headless Storefront Headless Shopify storefront built with Next. js App Router. Imported Context Rock Paper Scissors Headl...
Shopify Headless Storefront is the Rock Paper Scissors production storefront and operating system for Shopify-backed catalog, collection, product, cart, checkout-handoff, review, blog/article, feed, agentic-discovery, catalog-governance, and cutover-proof work. This reintroduction replaces the thin local fallback with source-backed project evidence and keeps the project attached to Codex chat 019e45cf-299f-7ae0-aff9-fef3a18f5d44, the blog audit and Anna Atkins remediation thread.
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.
Source Summary Agent Instructions These instructions apply to all AI assistants working in this repository. Core Rules - Always review CHANGELOG. Imported Co...
Source Summary title: Changelog description: Chronological list of notable changes status: stable lastUpdated: "2026-03-25 12:39 ET (America/NewYork)" owner:...
Source Summary title: Documentation Index description: Canonical documentation map for the project status: stable lastUpdated: "2026-03-21 06:17 ET (America/...
Source Summary title: Development Roadmap description: Future development plans and milestones status: evolving lastUpdated: "2026-03-25 12:39 ET (America/Ne...
Active Solo Mom Project resource directory, editorial surface, admin tooling, and taxonomy workflow, classified under the DAR trail with public tags for community, SMC, and content creation.
Database operations policy for keeping production canonical while local remains a review mirror.