Designing an app · Lesson 8
Everything so far happened inside the app. Real apps also reach out: they call public APIs, use their users’ accounts elsewhere, collect data at scale, answer on Telegram or the phone, live on a phone. The manifest draws the boundary: what is reachable, with which keys, through which doors — and writes down what does not fit.
Use Next, or the ← → keys. Try paths, queries and hosts: the URL is built, or refused, by the runtime’s own function.
egress.hosts — the only external hosts; *.domain only for the users’ own hosts saved with their key; private addresses are always blocked.http tools — a fixed address; the agent fills query, path (if allowed) and body; method, host, headers and keys are never its choice.data.credentials — keys users connect (scope user) or admins set (scope org), encrypted, added by the runtime at the call.data.jobs — ETL pipelines on the platform: ref, inline YAML, built by an agent; schedule; ingestTo a collection or a search index.channels · serviceHours — web, Telegram, email, phone; the hours with fast answers.mobile — the Android and iOS shell, with only the declared capabilities and their reasons.extensions — the gaps, written down.Lesson 9 closes the path: what the app builder does with a description in plain words, and how its manifests pass these checks — with real runs.