Blog
OperationsMarch 28, 2026 · 6 min read
Catalog and runtime: how we think about legal posture
The short version: the public catalog should publish facts about schemas, while execution happens through explicit local or authenticated hosted paths.
by Everfetch Team
The operating principle
Everfetch should publish facts about schemas and their health in the public catalog. Execution should happen through explicit local tooling or authenticated hosted API calls, not through anonymous public catalog pages.
What that means in practice
We optimize for:
- transparency
- explicit user accountability
- public documentation of exclusions and trust decisions
What it does not mean
It does not mean the platform avoids hard problems. It means we choose system boundaries that are easier to reason about and easier to explain.
That is also why the exclusion list and takedown policy are public pages rather than buried support documents.