File-over-App Philosophy

The file-over-app philosophy keeps every workflow portable. Instead of hiding history inside a vendor dashboard, Smart Environment writes configuration, prompts, and outputs to files you control.

Audit everything. Files commit to Git, sync with your storage, and survive app shutdowns.
Swap tools at will. Because data stays in open formats, you can edit with Obsidian today and a custom UI tomorrow.
Automate responsibly. Pipelines reference explicit files, so reviewers can diff and approve before anything ships.
Support longevity. Ten years from now a text file still opens; a proprietary API might not.

Technical flow for senior builders

Obsidian captures edits and exports a .smart-env/ snapshot for each workflow.
Adapters transform raw files into normalized structures consumed by Smart Plugins and Smart Actions.
Execution outputs artifacts (summaries, scripts, visuals) as markdown, JSON, or binary attachments stored locally.
Reviewers diff artifacts, promote changes, or roll back by deleting files—no hidden state.

Why it matters

Guarantees compliance for privacy-sensitive teams by avoiding silent uploads.
Lets developers branch workflows, test changes, and merge improvements like any other codebase.
Keeps supporters confident that Smart Environment will never lock them out of their own work.

How Smart Plugins embrace file-over-app philosophy

Smart Plugins store configuration, prompts, and history in plain text files so you can version, share, and back up workflows without vendor approval.
If you can sync it or audit it with the tools you already trust, it belongs in your vault—not locked behind someone else's UI.

Portability by default. Workflows travel with your vault, Git repo, or secure storage device.
Inspectable history. Every change can be diffed, audited, and rolled back with standard tools.
Composable design. Files feed automations, scripts, and Smart Actions without proprietary APIs.
No silent lock-in. Switching editors or devices never strands your data.