Builder workspace

1. Builder access

Builder controls locked — a verified enterprise session is required.

Local session/storage behavior is tested only. Production identity configuration, storage reliability and execution isolation remain unproven.

2. Requirements and scope

The fixed work-request profile remains available. New briefs use a bounded local language interpreter; unsupported statements block generation.

R1–R3 are required. R4 (dashboard) may be removed in an explicit scope version.

4. Limitations and handoff

• Fixed mock planner for the supported work-request brief only. Genuinely new-brief generation is NOT PROVEN.
• Generated application tests are INCLUDED, NOT EXECUTED. Inspection checks validate structure and a mock model, not a running application.
• Generated application authentication uses a shared demonstration password and role selection. NOT production authentication.
• Generated JSON storage is NOT certified for concurrency, corruption recovery, backups or customer data.
• Execution isolation, real providers, deployment and production readiness are NOT PROVEN. No execution is performed by Builder.
• Imported package hashes prove content consistency, not original author identity or trust. Use synthetic data only.

A ZIP contains one selected version with its parent digest, not the complete server project history. Imports must use this generator version and its exact source format.

5. Reopen a project

Saved projects use the server session’s owner and tenant. ZIP imports validate content; they never run it. Checksums do not establish authorship.