What are we working on?
Read-only access to simulated inventory, lease, route, and asset-status resources. Customer contact fields remain masked.
Read-only access to simulated service health, integration dependencies, and portfolio metadata. No customer or employee records are included.
Read-only access to simulated model metadata, evaluation summaries, and aggregate spend. Customer records and prompts are not exposed.
Illustrative policy trace
| Step | Enforced policy | Status |
|---|---|---|
| Request resource | Starts with no access; request is limited to Rental Operations | Approved read-only |
| Run deterministic query | Typed capability; credential remains isolated | Logged |
| Render app | Observed resources stay attached to the output | Bound |
| Share | Viewer permissions are checked at open time | Human controlled |
Read-only access to simulated inventory, lease, route, and asset-status resources. Customer contact fields remain masked.
Resource boundaries
CORT - Connected Fulfillment Operating Brief
Purpose
Create resilient visibility from location-aware availability and lease commitments through white-glove delivery, return, refurbishment, and repurpose decisions.
Jobs to be done
| Priority | Journey moment | Required review |
|---|---|---|
| Unified local availability | Select by market and duration | Product + operations review |
| Lease and route orchestration | Schedule delivery or pickup | Architecture + service review |
| Circular asset identity | Inspect, refurbish, or resell | Data + controls review |
Operating principles
- Start with a measurable job to be done, not a new tool.
- Use curated company context before model knowledge.
- The human owner remains accountable for every output.
- An agent never receives more permission than the person using it.
Delivery sequence
Days 1-30: Map customer promises, service owners, and critical dependencies.
Days 31-60: Pilot one market with deterministic exception handling.
Days 61-90: Measure availability, delivery reliability, reuse, and support outcomes.
Control alignment
Consumer privacy, payment security, role-scoped warehouse access, service continuity, and approval for customer-facing changes remain mandatory.
Workspace sources
Plan a governed platform spanning digital selection, leases, warehouses, delivery, and circular reuse.
Read-only access to simulated service health, integration dependencies, and portfolio metadata. No customer or employee records are included.
Resource boundaries
Workspace sources
Prioritize forecasting, design assistance, and service workflows with evaluation, cost, and access controls.
Read-only access to simulated model metadata, evaluation summaries, and aggregate spend. Customer records and prompts are not exposed.
Resource boundaries
Integrations
Organization-wide connections for CORT OS. Gatekeepers hold credentials, scope resources, and log each action.
Illustrative remote services available to authorized workspaces.
Organization Context
Shared, curated knowledge that grounds every CORT OS workspace. Context is versioned and read-only to agents.
Skills
Reusable workflows for every function. The human requester owns the result.
| Name | Description | Group | Source |
|---|---|---|---|
| meeting-prep | Build an agenda and briefing from authorized calendar, CRM, and document context | General | Shared library |
| weekly-operating-review | Create a cross-functional summary with decisions, owners, and open risks | General | Shared library |
| incident-response | Assemble evidence, draft updates, and preserve human approval for containment | Security | Shared library |
| vendor-risk-review | Compare due-diligence evidence with security and privacy standards | Security | Shared library |
| control-evidence-pack | Map authorized evidence to control requirements and identify gaps | Security | Shared library |
| architecture-review | Review a proposal against architecture principles and decision criteria | IT & Architecture | Shared library |
| change-impact | Map dependencies, affected services, stakeholders, and rollback requirements | IT & Architecture | Shared library |
| service-health-review | Summarize service levels, incidents, changes, and capacity risks | Operations | Shared library |
| runbook-builder | Turn a procedure into a deterministic workflow with approval gates | Operations | Shared library |
| ai-model-review | Summarize ownership, evaluations, drift, risk tier, and release readiness | Data & AI | Shared library |
| data-quality-report | Assess freshness, completeness, lineage, and policy compliance | Data & AI | Shared library |
| budget-variance | Compare actuals with plan and draft a finance-reviewed variance narrative | Finance | Shared library |
| procurement-brief | Summarize requirements, alternatives, risk, and approval status | Finance | Shared library |
| job-description | Draft an accessible role description from approved job architecture | HR | Shared library |
| onboarding-plan | Create a role-based onboarding plan without expanding system permissions | HR | Shared library |
| contract-intake | Extract terms, route issues, and prepare a legal review checklist | Legal | Shared library |
| privacy-assessment | Map a proposed workflow to data categories and privacy obligations | Legal | Shared library |
| account-brief | Create a customer briefing from authorized CRM and public information | Sales | Shared library |
| proposal-draft | Build a first draft using approved claims, pricing, and brand context | Sales | Shared library |
| executive-update | Turn project evidence into a concise decision-oriented update | General | Shared library |
Profile
Illustrative account information for this public prototype.
AI Gateway
Illustrative demo data. Visibility and controls across every AI provider CORT uses — one console.
Models in Use
This month| Model | Route | Tokens | Spend | Share | p50 latency |
|---|---|---|---|---|---|
| Llama 3.3 70B | Workers AI | 156M | $2,140 | 310 ms | |
| Claude | via AI Gateway | 98M | $3,980 | 720 ms | |
| GPT-4o | via AI Gateway | 61M | $2,510 | 640 ms | |
| Workers AI embeddings (bge) | Workers AI | 27M | $190 | 40 ms |
Spend vs. Budget
9 days remainingUsage by Workspace / Team
342M tokens totalGovernance
Guardrails enforced by Gatekeepers + AI Gateway, with resource-scoped access, audit trails, and human approval.
Per-team allowed models
Restrict which providers each workspace can call.
Monthly spend caps
Hard limits per team; agents stop before overrun.
PII redaction
Strip sensitive fields from prompts before they leave.
Prompt / response logging
Full request logs retained for audit & review.
Rate limits
Per-team request ceilings to protect budgets.
Raise Data & AI cap to $6,000
Change queued by an agent — needs a human sign-off.
Requires approval