Attestation is all you need

Source context: Joseph Perla original.

Policy matters, but policy alone is not enough for high-value prompts. A router should make it possible to verify what code is receiving the request and whether that code matches the open source release.

That is why TrustedRouter treats attestation as part of the product surface. A user or agent can check the trust page, compare source commits and release digests, and then decide whether a route meets the workload's privacy bar.

The practical split

• The control plane manages accounts, keys, billing, docs, and status.
• The API plane handles prompt traffic through the attested gateway.
• Provider pages show upstream retention and confidential-compute posture separately.
• Legal and procurement pages state what is ready now and what still requires a signed agreement.

This makes the system legible. A lawyer can read the DPA and subprocessor list. An engineer can inspect the code. An agent can verify attestation before routing sensitive work.