artifacts

Storefront Application (Next.js App Router)

Next.js App Router storefront with Tailwind UI and Redux state for browsing and purchase flows.

Checkout and Fulfillment Pipeline

Stripe Checkout and webhook-driven order/download generation pipeline for post-purchase delivery.

Secure Download Delivery (GCS Signed URLs)

Token-gated download endpoint that signs private Google Cloud Storage URLs and enforces download limits.

Transactions Store (Prisma + PostgreSQL)

Prisma-backed transactional data model for orders, downloads, licenses, and customer records.

SEO and Merchant Feed Pipeline

Search/discovery system including structured SEO metadata and Google Merchant Center feed endpoints.

CI/CD and Drift Detection Workflows

GitHub Actions workflows for CI checks, schema drift detection, sync jobs, and Vercel deployment orchestration.

Digital Product Pipeline Subproject

Adjacent generation pipeline using n8n/ImageMagick/Puppeteer for wall-art assets, PDFs, and CMS registration flows.

Authentication Layer (Clerk Middleware)

Clerk middleware and auth routes are present in code; source docs still include legacy NextAuth references.

Aerial — authorized evidence and human follow-through

I connect authorized source evidence to a human review decision, while keeping identity uncertainty and follow-up visible.

Build one connected product demo across three roles

The September 5–8 Aerial demo followed the same fictional family, donor and institution through working product states. A synthetic roster supplied realistic scale while role-specific sharing and visible-versus-recorded counts kept the story truthful. Production evolved through versioned films, narration, transcripts, contact sheets and playback checks. Project 0086 identifies V12 as the latest technically delivered draft and explicitly pauses further video work pending user direction and editorial acceptance.

Aerial + 1

Aerial — Cryobank family capacity and reservation reconciliation

I track recorded families, reservations, children, and institution-specific policy separately. HBR-2041 currently has 23 recorded families and two reservations against a 25-family limit, so its capacity is fully committed.

Aerial — Cryobank donor and recipient record review

I keep donor and recipient oversight connected to the exact person, file, claim, and accepted relationship behind each record. The Brooks family view links directly to HBR-2041, two children, visible files, and clinic coordination.

Aerial — design review and connected demo release

I use Codex to implement and capture a connected product story, then review the visual result and narrative before release.

Aerial — Donor profile fields and separate identity access

I separate a donor’s general profile audience, individual field exceptions, and identity access. Evan’s saved medical-history exception is clinic-only while four other fields use the Personal Networks audience.

Aerial — Donor health history and sharing

I keep donor health updates dated and distinguish the shared record from private preparation notes. The current demo shows four shared updates, one private update, and a future reminder.

Aerial — Family–donor conversation to a shared health record

I connect an accepted family–donor conversation to the dated health history it prompts. Maya’s question and Evan’s reply remain in the thread, and his later shared update gives that context a durable home.

Aerial — Family health updates and independent audiences

I give families a way to record their own health context and follow donor updates without combining their audiences. The current Brooks account shows one family-authored update and four shared donor updates.

Aerial — Institution partnership and scoped case access

I treat institutional agreement and case permission as separate decisions. Harbor’s accepted Northstar partnership and pending Lakeview request show why an institutional relationship alone cannot open a patient roster or donor evidence.

Aerial — Cryobank notice review, family receipt, and follow-up

I keep a medical notice’s reviewed content, eligible audience, availability, acknowledgment, and staff follow-up distinct. The synthetic notice has 23 eligible families, 20 acknowledgments, two pending receipts, and one clinic follow-up.

Recover approved positioning before revising a product site

Aerial’s September 8–13 work exposed a continuity gap: approved product and institutional positioning was present in demo materials but absent from the documents guiding marketing. The recovery combined conversation decisions, canonical docs, product evidence and the actual live baseline, then preserved audience-specific messaging and the Connected Atlas direction through HTML, Figma and browser review. The September 8 marketing draft remained a preview; later source checkpoints report PRs 183 and 184 merged. These are dated source claims, not a fresh production audit.

Aerial + 1

Aerial — Family request to institutional correction review

I preserve a family’s correction request alongside the disputed source value, deadline, and responsible reviewer. This demo request is overdue and has no final response; its draft has not corrected the record.

Ambient work-history context before and after Chronicle

A branched operating model that compares legacy Chronicle's screenshot/OCR pipeline with Computer History's structured event and Accessibility pipeline, then rejoins them at reviewed memory, private retention, report-input, and public-derivative gates.

Chronicle Visualizer

Xyppy App LP and Support Hub + 1

Xyppy app landing-page and support loop

How the Xyppy App LP and Support Hub guides a Shopify merchant from the public education surface for the Xyppy Bulk Product Editor app into a safer bulk-edit workflow: review app scope, filter products or variants, choose one action, preview count and changed values, run the job, verify job history, use CSV/support docs for edge cases, and route launch-readiness gaps through human review before public claims are treated as final.

Chat intake and publication

How an AI conversation becomes a durable Hyphenomenon chat record while its complete transcript stays private by default and only reviewed, public-safe context reaches the live site.

Chronicle Visualizer private archive and publication loop

The operating loop that preserves Chronicle frames and written context privately, verifies encrypted storage, reviews candidate derivatives, and only publishes redacted public timeline assets after human approval.

Chronicle Visualizer + 1

Clinic / Cryobank Operational Oversight

How professional operators enter the clinic-facing surface, onboard an organization context, and use the dashboard for member management and donor-program oversight.

Family Shapes

Codex Skills sync and catalog governance

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.

Codex Skills Library

Context Layer — carry project decisions between sessions

Use repository records, evidence and human review to preserve continuity as work moves between coding sessions.

Context Layer + 1

Daily intake queue summary

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.

Maggie Todo

Donor Control and Health Update Workflow

How donors use Family Shapes to manage profile completeness, privacy choices, health history, and communication settings through a dedicated donor experience.

Family Shapes

Family Discovery and Connection Journey

How recipient families move from discovery and onboarding into privacy-aware family-tree exploration, connection review, and relationship follow-up.

Family Shapes

Human-in-the-loop archive workflow

How raw work traces become reviewed public evidence across Hyphenomenon's projects, notes, workflows, chats, screenshots, and map.

Image evidence intake

How a screenshot, photo, mockup, diagram, or scan becomes a first-class evidence object with source provenance, verified media, and explicit project or chat relationships.

Local review and promotion loop

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.

Maintain validation and surface-capture loop

How Maintain turns native iOS and backend work into reviewable evidence: regenerate the Xcode project, run simulator surface capture, verify docs/backend/iOS gates, check staging when credentials are available, and keep TestFlight/App Store blockers explicit before release decisions.

Maintain iOS

MLNNA portfolio sync and review loop

The workflow that turns scattered repository activity and manual context into a reviewable portfolio dashboard: sync GitHub activity into Notion, attach conversation/task context, run AI synthesis, export snapshots, review rendered dashboard evidence, and let the human operator correct the source-of-truth records before the next run.

MLNNA + 1

Durable scheduled monitor report

How independent mailbox coverage becomes one exact scheduled report without losing items to heartbeat drift, incomplete pagination, partial mailbox failure, process restart, or an unacknowledged user-visible delivery.

Multi Mailbox Ops

Guarded named-mailbox operation

How one operator request becomes a mailbox-specific, exact, reviewable, reversible action while identity ambiguity, untrusted message content, stale authority, protected mail, and state drift fail closed.

Multi Mailbox Ops

Review a Native Capability Before Retaining a Workaround

A decision workflow extracted from the September 11 Gmail reassessment: measure actual native overlap, compare the safeguards that matter, and retain only gaps worth maintaining. A capability inventory is evidence for a decision, not proof that an account migration or custom-system retirement has occurred.

Multi Mailbox Ops

Note hydration intake

How a curated source document or hydration payload becomes a public note without requiring a full project re-import or turning unreviewed source material into public copy.

Personal measured art-layout review

The workflow behind my Personal AI fail. I gave Codex measurements, art, and references; it produced multiple schemes and an editable Figma file, but the visual design still fell short. I’m retaining the process and the critique it needed, not recommending it as a proven design method.

Living Room Art Layouts

Portfolio — give each study an owner and a next decision

I preserve exploratory work while making its relationship to the real portfolio explicit. The initial migration is verified; future reduction in rework remains to be observed.

Maggie Lerman Portfolio

Reconcile upstream code and local project documentation without losing evidence

The September 8 Reconcile main and docs task joined 26 upstream commits with 20 locally changed files in Shopify Headless. Its final source checkpoint reports six documentation conflicts resolved, the V45 pilot renumbered to 1188, indexes refreshed, and a clean synchronized checkpoint at 57f30e43. The reusable Context Layer method is to inventory and preserve work before integration, settle conflicting project ownership, then verify both source evidence and the documents future agents will use.

Codex Skills Library + 1

Prompt-to-project intake workflow

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.

Review public work with evidence, reversible decisions and readback

Audit GitHub for YC readiness began with a cross-repository inventory and an interactive review surface. It distinguished signed-in metadata, signed-out public visibility, private implementation and public proof, then tracked the operator’s decisions and verified authorized visibility changes. The reusable method evaluates what a stranger can actually inspect, recommends a small number of useful public examples, and never turns a candidate label into deletion, publication or a settings change.

Codex Skills Library

Watch Platform Updates for Changes That Matter to Existing Work

A recurring review pattern from the September 11 automation-creation conversation. Scheduled checks compare installed builds and official shipped changes, maintain a baseline, and produce an evidence-backed alert only when the change affects permissions, controls, integrations or the need for custom work. The source established configuration, not later execution proof.

Recover scattered Etsy research into a dated evidence workbook

A September 4 recovery task consolidated May 8–26 research into a 17-tab workbook. The useful result is traceable evidence: 1,011 reviewed listings, separate winner and benchmark cohorts, architecture metrics, planned concepts, and source/rights caveats. A historical review-count proxy can guide a test; it does not establish current sales, listing availability, artwork rights or launch readiness.

Report artifact intake

How a generated or curated report becomes a public artifact through an exact source window, aggregate-only content, deterministic validation, guarded database sync, and live verification.