Create your first governed session

What you will build

A single governed session created against a blueprint version, with a synthetic input attached, so you can see how Crescevo returns legal actions instead of letting the client decide what is allowed.

Architecture preview

Your request goes to the versioned API, the kernel validates it against tenant, environment, and blueprint, and returns a session projection. The console renders the legal actions the kernel supplies.

Prerequisites

• A test tenant
• Console access or a scoped API credential

Steps

1. Obtain test-tenant access

   Use a test tenant so nothing you do can reach production systems. Effects in a test environment are simulated or allowlisted.

2. Set your environment

   Export the base URL and a scoped API key. Never hard-code secrets in a command or file.

   export CRESCEVO_BASE_URL="https://api.crescevo.com"
   export CRESCEVO_API_KEY="<your-scoped-test-key>"

3. Create the session

   Submit a bounded objective against a blueprint version. The idempotency key makes a retry safe.

   curl --request POST \
     --url "$CRESCEVO_BASE_URL/v1/sessions" \
     --header "Authorization: Bearer $CRESCEVO_API_KEY" \
     --header "Content-Type: application/json" \
     --header "Idempotency-Key: quickstart-session-001" \
     --data '{
       "tenant_id": "tenant_test",
       "environment": "test",
       "blueprint": { "id": "governed-artifact", "version": "0.8.0" },
       "objective": "Produce a source-grounded operational brief."
     }'

   {
     "id": "s_...",
     "state": "open",
     "blueprint": { "id": "governed-artifact", "version": "0.8.0" },
     "legal_actions": ["artifact.create_revision", "session.close"]
   }

4. Read the session projection

   Fetch the session back and read its current state and the legal actions the kernel returned. The client does not invent these.

   curl --url "$CRESCEVO_BASE_URL/v1/sessions/s_..." \
     --header "Authorization: Bearer $CRESCEVO_API_KEY"

5. Open it in the console

   Sign in to the console and open the session. The Help drawer explains each field; the timeline shows the events so far.

Verify success

• The session was created (a session id is returned).
• The projection reads back with a state and legal actions.
• An audit event for the creation is present in the activity timeline.

Clean up

Test-tenant resources expire automatically. To reset sooner, destroy the session or reset the test tenant fixture.

Next: Produce and compare artifact revisions →