Loading your workspace
Checking session state, onboarding progress, and live backend data.
Syncing calendars
Checking the latest availability and conflict data.
Preparing copilots
Loading the agent and chat context from the backend.
Verifying session
Confirming your access and onboarding status.
Documentation hub
The docs experience now mirrors the same calm, premium atmosphere as the landing page while giving visitors a clearer path into architecture, workflows, and implementation details.
System
FastAPI + Next.js
Scheduling
Atomic booking flow
Automation
AI with fallbacks
Reader mode
POST /api/v1/bookings
X-Idempotency-Key: calm-flow-001
{
"event_type_id": "strategy-intro",
"timezone": "America/Los_Angeles",
"attendee_email": "guest@example.com"
}Documentation tracks
Instead of splitting the experience into disconnected dark microsites, the documentation now behaves like a guided surface with crisp hierarchy, motion, and stronger wayfinding.
Product flow
Understand how public links, availability, confirmation, reminders, and rescheduling fit together as one journey.
System shape
See how the FastAPI backend, worker queue, frontend shell, and calendar sync layers stay coordinated under load.
Trust layer
Review the operational defaults that keep scheduling flows protected, rate-limited, and auditable.
Build surface
Jump from product docs into implementation guidance, code examples, and API-oriented thinking without losing context.
Implementation note
GraftAI’s strongest documentation isn’t just a reference list. It ties UI choices, API behavior, background task expectations, and security rules into one readable system so contributors can make changes confidently.
Frontend conventions
Use the singleton API client, prefer server components by default, and keep public routes visually calm and fast to scan.
Backend conventions
Use async sessions, explicit HTTP exceptions, idempotency on booking creation, and Celery for durable background work.
Automation model
Treat AI as one layer in a fallback chain, not the only decision-maker. Every automated action should remain explainable later.
Next stop
The developer hub now inherits the same public theme, but it goes deeper into examples, architecture surfaces, and implementation-ready entry points.