Prepare your internal platform.
Prepare the workspace and standing rules once, then give teams an approved way to request applications. Start with the current installation; no application idea is needed here.
Check your team’s setup.
Use your current EmDash session to inspect the selected team, its standing rules and its configured app adapter. Then continue with the action that is available to you.
Check your signed-in workspace to see its next setup step.
Checks create no resources. Keep downloaded workspace and account observations private. The supported request uses fictional data on the existing runtime; it does not provision isolated staging infrastructure.
Prepare the prerequisites that affect this path.
- Repository and tools
- Your trusted operator agent checks the intended checkout, exact source, Node 22, Git and the reviewed EmDash
1.2.0toolchain. Local preparation and a live service remain separate checks. - Identity and membership
- Use the existing protected EmDash sign-in. Confirm the intended workspace and owner/editor assignments. A profile, report or exported specification never creates a permission grant.
- Account, runtime and resources
- The operator selects the existing Guestbook connection and runtime identity on the trusted host. The native plan shows its actual account and environment. Credentials and resource bindings stay on that host; this page asks for none.
- Standing policy and runner
- An owner enables the maintained visitor book recipe, synthetic previews and a bounded application quota. Routine allowed requests run through the connected adapter. Missing execution capability leaves a resumable request, not a completed service.
One supported resource path.
The current path uses an app-owned visitor book resource in the independently deployed Guestbook Worker and its existing database. “Preview” labels the synthetic application request; it does not create an isolated preview Worker or database.
Knowledge applications, production promotion and strict Australian-only processing/storage are unsupported by this automatic path. Do not enter internal or sensitive records. The request policy records unsupported or denied requirements instead of weakening them.
Reviewed Guestbook source 400fc2219ebb461acf6ea7abc3242a682192dd2c. Source qualification, current adapter connection and a verified application are separate evidence.
Preparing a separate installation?
Use the independent environment setup for the supported tools, source and first HTTPS application, then follow the operator documentation for the intended host. That setup report is an observation; it does not configure platform admission, server credentials or standing policy automatically.