Turn a file structure into a schema proposal without letting guessed relationships reach production.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

For authorized work involving authorized spreadsheet columns, proposed database structures, and validation notes, prepare a proposed database schema and field description from an authorized spreadsheet for an engineer to review. Column names and sample values may expose personal data, and an inferred schema can misread units or relationships. Minimize sample data, validate types and constraints against business rules, scan generated scripts, test away from production, and require a database owner to approve migrations and writes. Explain information use and retention, obtain required consent, respect source and reuse rights, verify important details, and keep external or consequential actions under human approval.

Actual availability depends on published steps, supported connections, permissions, and provider approval.