1. Request access
A public request enters as a server-recorded access request. It does not expose workspace data or create automatic approval.
How it works
From request access to review URL.
The live D1 path starts with access intake, moves into a private workspace, creates case and artifact refs, then sends sanitized review URLs for feedback and reception.
2. Create a workspace case
Inside /me, the founder creates a case for a real room such as QuoteOps, then adds artifact metadata and manual Drive/Data Room refs.
3. Send a review URL
A tokenized review link exposes only title and safe summary. It is not login, raw access, payment or provider execution.
4. Track feedback and reception
Reviewer feedback updates D1 state. Reception records what was drafted, sent, received, reviewed, accepted or blocked.
Public boundary
- Founder auth traversal is still the active acceptance gate.
- Public catalogue/search stays empty until real items are released from the workspace.
- High-risk, regulated, legal, tax, payment, provider and CFE actions require separate gates.