Behind the Scenes: A Day at Inky

The Content Safety Stack

Safety isn't a feature we added at the end. It's the foundation the whole system is built on. Every story request passes through multiple layers before any content reaches a child.

The first layer is input filtering: we check what you've entered for anything that shouldn't become part of a prompt sent to the AI. The second layer is the AI's own built-in guardrails — the model we use is configured specifically for children's content and will decline to generate anything outside those parameters. The third layer is output filtering: before the story reaches your screen, an automated system scans it against our content policy.

Fail any layer and the request doesn't go through. We'd rather tell a parent 'we couldn't generate that one' than ship something we're not proud of.

How Prompts Are Built

The inputs you see in the Inky interface — character name, age, theme, art style — are the visible surface of a much more detailed set of instructions assembled behind the scenes. Your inputs get combined with age-calibration parameters, narrative structure guidelines, vocabulary constraints, and tone instructions before anything reaches the AI.

A prompt for a 3-year-old looks very different from a prompt for an 8-year-old, even if both parents typed in the same theme. The age calibration is one of the most important variables we tune — it's what makes the language feel right for where your child actually is developmentally, not just generically 'kid-friendly.'

Where Art Comes From

Text and illustrations are generated by separate systems that work in parallel once the story text is approved. The illustration system reads key narrative moments from the story — not a generic description — and generates images that are specific to your story rather than generic stock art.

Art style consistency within a single story is something we work hard to maintain. If you pick watercolor, every illustration in that story uses the same visual treatment, the same character designs, the same color palette. Continuity matters because kids notice when the character looks different from page to page, and inconsistency breaks the reading experience.

What We Obsess Over

A short list of things that get disproportionate attention from the Inky team:

• Reading level accuracy — a story rated for a 6-year-old should feel right to a 6-year-old reader, not a 4-year-old or an 8-year-old.

• Story endings — how a story concludes has outsized impact on how it lands emotionally. We tune specifically for satisfying, age-appropriate resolutions.

• Name rendering — nothing breaks the magic like your child's name being misspelled or mispronounced in the audio. We handle name normalization carefully.

• Load time — a child waiting more than 15 seconds for a story is a child who's moved on. Speed is a design requirement, not a nice-to-have.

What We're Still Building

Inky is a product in active development, which means there are things we know we haven't gotten right yet. Story length calibration for different attention spans. Better handling of unusual names. More art styles. Deeper series continuity so a character truly feels like the same character across multiple stories rather than a slightly different version of them.

Every parent who sends feedback — the good and the frustrating — is directly shaping where we put our attention next. If something doesn't feel right about a story, the report button is the fastest path to fixing it. We read every one.

The Part That Still Surprises Us

We built Inky to make personalized storytelling easy. The part we didn't fully anticipate is how often families turn the story-creation process itself into a ritual — the conversation about what the story should be, who the characters are, what adventure they'll go on. The app is just the delivery mechanism. The real thing happening is a parent and child building something together. That keeps us motivated on the hard days.