# Made Sick Integration Recommendation

## Decision
**Status:** Implemented 2026-09-12. Section live in `ibloud/made-sick` README and index.html.

Add PIXIE to made-sick.org, but as a focused **Technology & Creative Access** program—not as a therapist dashboard or a general claim that Made Sick can determine mental state.

Made Sick should explain the human problem, invite creative-industry participation, and link to the PIXIE repository and campaign post. The research protocol, technical specification, case ledger, and provider submissions remain in the standalone repository.

## Why it belongs

Made Sick already presents PIXIE as a consent-first care interaction. Device stewardship extends the same principle: assistance should respect capacity, reduce shame, preserve agency, and let the person stop without penalty.

## Why it needs a boundary

The main Made Sick site also covers creator directories, storytelling, wellness practices, Duet, Germ, and Streamplace. Hosting the complete research project there would blur PIXIE's evidence status and could make an accessibility campaign appear to be a medical service.

## Ready-to-insert homepage section

### PIXIE: the system should remember

Creative tools ask people to remember filenames, folders, versions, and recovery steps while they are trying to make something. PIXIE is a consent-first research project asking technology to carry more of that administrative burden.

We are beginning with musicians, filmmakers, designers, and game developers. The goal is not to monitor people or diagnose how they feel. It is to help devices understand human intent, preserve provenance, suggest reversible organization, and make interrupted work easier to resume.

**Explore the research. Share a workflow barrier. Help us ask operating-system providers to change.**

## Navigation

Add one top-level or program link labeled **Technology & Creative Access**. On small screens, do not add a second PIXIE item if a PIXIE panel is already visible; link that panel to the campaign landing section.

## Participation boundary

Do not collect health histories, diagnoses, therapy information, raw files, or private screenshots through the public site. The initial contribution form should request only a description of the task, device/application, observable barrier, and permission level for follow-up or publication.