prototype-ingestion

Turn raw prototypes into governed prototype artifacts.

prototype-ingestion governs the part of the Software Development Lifecycle where prototypes, mockups, screenshots, or flow artifacts carry meaningful project intent. It helps teams turn those raw inputs into normalized prototype artifacts that downstream design work can inspect explicitly instead of treating the prototype itself as unquestioned final truth.

What it does

• Reads prototype inputs under _hirmos/inputs/prototype-ingestion/prototypes/.
• Produces normalized prototype artifacts under _hirmos/artifacts/sot/.
• Stores ingestion traces and supporting context under _hirmos/artifacts/context/prototype-ingestion/.
• Supports downstream design work through hook-based integration with system-design-agent.
• Keeps prototype interpretation reviewable instead of letting raw mockups act as hidden requirements.

Why software teams use it

• It gives prototype-driven projects a disciplined way to preserve what prototypes actually imply.
• It prevents raw screens and flows from being treated as unquestioned final truth.
• It makes prototype-derived meaning easier for downstream design work to inspect and challenge.
• It helps human teams and AI agents work from normalized evidence instead of ambiguous visuals.

Fast mental model

Key outputs

• Normalized prototype artifacts under _hirmos/artifacts/sot/
• Ingestion traces and runtime context under _hirmos/artifacts/context/prototype-ingestion/
• Specialized signals that can enrich system-design-agent when prototype evidence matters

Best fit: projects where prototypes are important evidence and should influence design through a governed interpretation step.

How this extension looks inside HIRMOS

FAQ

When should I use prototype-ingestion?
Use it when prototypes, screen flows, or mockups are meaningful design evidence and should be normalized before design continues.

Where it fits in the Software Development Lifecycle?
– After prototypes exist: it starts once screens, mockups, clickable flows, or other prototype artifacts are available.
– Before system design is finalized: it extracts prototype-derived meaning so downstream design work can review it explicitly.
– At design integration: it provides governed prototype artifacts that system-design-agent can consume when prototype evidence materially shapes the project.

Does it replace final design truth?
No. It produces governed prototype artifacts, not final authoritative system truth.

What does it produce?
Its core outputs are normalized prototype artifacts under _hirmos/artifacts/sot/ and ingestion traces under _hirmos/artifacts/context/prototype-ingestion/.

Who uses its outputs?
Its outputs are mainly consumed by system-design-agent, maintainers, and teams that want prototype evidence preserved in a governed form before design continues.