HYBRID CORTEXPeople, teams and authorized agents
Collaborations and reviewed delivery
Start in Cortex with the guided Outcome, People, First request and Review steps. The guided setup contract covers atomic invitations, private first-request drafts and owner-bound retry recovery. Email introductions are user-sent drafts, not automatic account lookup or delivery.
Delegate requests across project teams, clarify what is needed, prepare selected knowledge and accept exact deliverable versions.
Start with a shared outcome
- Create a project and invite exact Cortex profiles.
- Wait for participation acceptance, then select each request’s readers and responsible person.
- Use My next actions, Waiting on others, Updates and Invitations to clarify, deliver and review.
- Keep client acceptance separate from repository approval and verified deployment.
Authentication and access boundaries
Browser APIs use the existing signed-in Hybrid ID session, current Cortex admission, CSRF protection and stable request IDs. Project membership does not open every request, file or earlier conversation. Connected agents reuse their existing Hybrid ID authorization; no credentials are copied between teams.
These are Cortex’s browser and existing connector surfaces. Registered third-party application activation and delivery connection commissioning remain separate.
Developer resources
API overview
| Route | Purpose |
|---|---|
/api/collaboration/projects | Projects, explicit participation and scoped request pages |
/api/collaboration/tasks/{id} | Current request, clarification, delegation, delivery and acceptance |
/api/collaboration/documents/{id} | Permitted immutable versions and exact-version review |
/api/collaboration/agent-work/{id} | Owner review of private agent preparation |
/api/collaboration/delivery/{id} | Separate repository authority and independently checked provider evidence |
/api/collaboration/notifications | Private in-app action summaries |
GET /api/collaboration/invitations | Signed-in recipient’s invitation history |
GET /api/collaboration/projects/{id}/invitations | Owner-only invitation management history |
GET /api/collaboration/projects/{id}/access-review?profile={profile} | Owner-only scoped impact preview for cancellation or removal |
POST /api/collaboration/tasks/{id}/follow-up | Private captured-view acknowledgements and owner-controlled in-app reminders |
GET /api/collaboration/notifications | Current actions, invitations, shared updates and private reminder counts |
List routes return bounded pages. Follow the opaque next cursor until it is null. Reads and retries recheck current access.
Invitation and participation management
Track pending, accepted, declined, cancelled and expired invitations. New invitations expire after seven days by default. Owners can review a new invitation, edit project-team labels and preview access removal; joining again does not restore earlier request access. People & teams summarizes responsibilities only for requests you can read.
Filter authorized collaborations, requests, people and invitations by their available search, status, person and date controls. Email delivery and verified-recipient onboarding remain a separate Hybrid ID integration.
Updates and private reminders
Shared update previews respect current request readership. Private view markers and reminders stay with their owner. Reminders appear in Cortex when the owner returns; they do not send email or change shared requested dates. Direct links for already invited profiles open their pending invitation summary. Native collaboration-email delivery still requires a purpose-specific Hybrid ID contract. Cortex invitations must show Hybrid Cortex as sender from the verified hybrid-cortex.com domain; the actual mailbox is not configured. The authenticated status response keeps emailInvitations.enabled false and reports sender.requiredDomain as hybrid-cortex.com. Prepared internal lifecycle code is not a send endpoint or recipient-acceptance grant.
Release safeguards
The developer adapter requires a commissioned connection, exact revision approval and the developer’s own repository access. A durable Cortex claim and private local journal preserve the original operation through uncertain retries. A requested deployment is not a confirmed deployment.
Provider status and exact-revision health are checked separately. Production requires an accepted current deliverable bound to the commit. Engineering fixtures do not create live customer authority.