What is built: Built-in services

The errors this page describes are built with the feature they belong to.

Feature	Status
Email	Built: email's templates, the shared layout, `email:`, sending after commit through the SMTP driver, attachments and parking (Email templates and sending). The SMTP conversation runs in the driver, over the host's transport and its TLS upgrade (How it is built, "TLS through the transport").
Jadpo's own magic-link email	Built: at all five levels, worded by Jadpo or reworded by the app, wrapped in the app's layout, the app's own email filled with the link and the code, or the app's own sending given them (Jadpo's own magic-link email, Your own magic-link email).
The privacy emails	Not built yet. They come with data requests (Data requests).
Mail packages	Built: a mail package as the connection, partials and `email.sent` (Mail packages, partials and `email.sent`).
The dev inbox and the health score	Built: the dev inbox, `jadpo email`, the health score, `email.health_problem` and `jadpo email check-domain` (The dev inbox and the health score), with SpamAssassin's rules in the score (SpamAssassin in the health score). Not built yet: the inbox page as part of the developer console, and its link to each mail's trace, which comes with `jadpo trace`.
Rate limits	Built: default rate limits with routes, and their store on Workers, Cloudflare's rate-limiting binding (Rate limits on Workers). Not built yet: Redis's driver, which comes with caches. Until then a deployable whose store is Redis counts in its own memory, which on Workers is the judgement call `rate_limits.counted_in_memory`. The binding's windows and the Wrangler entries aren't yet checked against the real edge.
The capability seam	Built: the seam every capability's calls go through, with a delivery that hands its event to a capability, parked as `outcome_unknown` when a send without a key may have acted (The seam every outside call goes through).
Files	Partly built. Built: the `files` capability's first part on that seam: `Driver.disk` connections, `File` fields, `store.put`, `store.read` with its whole-read cap and its two errors, the disk driver `jadpo dev` keeps files with and the in-memory store a test's are in, which the file helpers' reads walk (Data formats; Files: `put`, `read` and the disk driver in development); the pieces the file helpers' writes put, joined into one file or dropped by the store (Files: an export's pieces); and a gzip file unpacked as the file helpers read it, up to `max_unpacked_size:` (Reading gzip). Not built yet: upload slots, multipart ones included, downloads, deleting and erasing a file's bytes, the S3 driver, a deployable's disk driver at its `path:` and `free_space_floor:`, the error for a disk driver's root inside the project, checking a stored file against its field's `max_size:`, `types:` and `store:` as it is written, `fixture_file` and telling the store to fail from a test, and image variants and scanning when an app needs them.
Flags	Not built yet.
Audit	Not built yet.
Search	Not built yet.
Documents	Not built yet.
Bot protection	Not built yet.
Outgoing webhooks	Not built yet.
The `telemetry:` section	Not built yet, nor telemetry in the developer console.
Path IDs	Not built yet for requests. Each body's ways are numbered, and the differential run compares the paths each test's bodies took, but no request carries a `path` or a `path_key`.
Monitoring thresholds	Not built yet.

The roadmap says when.

Related