Skip to main content
Open DevTown and its town interface.

​
Inspect the deployed source

This read-only request checks application identity and the reported runtime revision:
Compare runtimeEpoch.gitSha with the approved deployment source. A missing revision or a healthy process is insufficient to accept a different consumer or integration. Use the existing DICC allocation and canonical launcher for local development. Keep application startup and heavy builds within that governed execution path.

​
Verify an authenticated workflow

Use DevTown’s real sign-in once its Eyedbase consumer is connected. Confirm the server-issued session, returned identity and DevTown scope. Upstream Google credentials and a rendered sign-in page do not by themselves establish a product session. Marketplace, payment, newsletter and runtime mutation requests have external effects. This guide uses read-only checks; accepted commerce and message delivery require separate scoped receipts. Read integration status before treating a response as a completed external workflow.