sponsor-tech-thesislisted

# The technology thesis One sentence saying why *this* technology, phrased so that a competitor using a different technology could not claim it. "We used Aurora PostgreSQL" is not a thesis; it is a fact. "Caregiving is relational, transactional and access-controlled, so authorization belongs in the database — a key-value store cannot enforce it" is a thesis: it names a property of the domain, connects it to a property of the engine, and excludes the alternative. ## The form Every H0 winner in `../winning-ideation/references/winner-corpus.md` has one — that hackathon's table is the one with a Thesis column — and they share a shape: an inversion that names the excluded alternative: - Sammy: the model is stored inside Aurora and inference runs in the VPC, so "nothing ever leaves that private network boundary" — the model goes to the data, not the data to the model. - Sonar: "DynamoDB for speed, Aurora DSQL for record" — the database is chosen by the access pattern, not the data model. - Waylo: four progressively cheaper detection layers before vision ever runs, so "most steps resolve in under 50ms at zero marginal cost" — vision is the last resort, not the first tool. - Relay: Aurora DSQL for multi-region active-active writes and strong consistency on irreversible actions. Write it as: **[property of the domain] → [property of this engine] → [what the alternative cannot do].** ## Placement decides how many judges read it This is the finding the skill exists for.