Urgency across different conditions.
The earthquakes in Venezuela renewed my urgency to help households prepare across different institutions, infrastructure, language, and connectivity.
Check in when one happens. Practice together before the next. Ready Together explores how households can turn preparedness guidance into a shared, repeatable practice.
Ready Together is not an earthquake alert, early-warning, or emergency-response service.
Local prototype · Downloads are not available yet.

Knowing what to do is not enough. Everyone needs to practice it.
Why this, why now
One renewed the human urgency. The other clarified the product boundary. Neither is evidence that Ready Together already works.
The earthquakes in Venezuela renewed my urgency to help households prepare across different institutions, infrastructure, language, and connectivity.
After a magnitude 7.4 earthquake near San José del Palmar, the official facts were available. They still could not answer how one private circle would respond together.
Earthquake apps inform. Chats communicate. Guides teach. Written plans record intent. None normally coordinates a short multi-device household practice and reveals what remains unresolved.
Real earthquakes provide context, never conversion pressure. Ready Together does not claim it could have prevented harm.
Designed for a circle, not a crowd
Protocols change by location. Preparedness always starts at home. These are the three product questions the prototype is testing.
Connect reported earthquakes with the broad areas your circle chooses—without turning the app into an alert system.
Keep event-scoped responses focused on the people and responsibilities your circle already understands.
Run a shared drill, compare what happened, and carry one concrete improvement into the next practice.
Evidence before adjectives
Ready Together is a Kotlin Multiplatform local prototype. Android and iOS interfaces exist; automated coverage supports the shared-practice flow. The final physical Android–iPhone validation gate remains open.
Field notes
Founder context, architecture, and workflow—separated from claims the evidence cannot support.
How Sismos México, Venezuela, Colombia, and a missing coordination layer shaped the product question.
Read the founder story →PLANNED TECHNICAL NOTEThe shared domain, the native boundaries, and why architecture supports the product question.
View the outline →PLANNED PROCESS NOTEA repository-first workflow designed to keep agents, implementation, and public claims aligned.
View the outline →One honest question
Feedback should test the problem, not flatter the solution.