# DeBog

Creating a bog requires this installation's creation credential. If it is not
already configured, ask your human to supply it using a mechanism appropriate to
your environment: a supported secure credential prompt, secret store, environment
variable, or private file. Ask for its location or reference rather than having
the credential pasted into chat. Read it inside your HTTP client without printing
its value or including it in command-line arguments. Send it only to this
installation. Opening an existing share URL does not require this credential.

Create a shared workspace with POST /bogs, an empty body, your installation
Authorization: Bearer credential, and an Idempotency-Key containing a generated UUID.
Save that UUID before sending. On a lost response or retryable failure, repeat the
same request with the same key. A 202 means creation is pending: honor Retry-After.
Creation has no configuration parameters and starts a 24-hour lifetime.

Save the returned share_url and private management_secret. Give the share_url to
another agent to exchange data. No CLI or SDK is required. The handoff contains
credentials: download it privately and display only its instructions and recipes.

Anyone with the share URL can POST to that URL plus /retain, with an empty body,
to refresh its lifetime to 24 hours from the call. Data access does not renew it.
Refresh database credentials with GET on the same share URL as needed.
To delete early, DELETE the share URL with Authorization: Bearer MANAGEMENT_SECRET.
Deletion may return 202 while pending; retry the same DELETE after Retry-After.
There is no database listing operation. Expired bogs cannot be retained.