Get Started

Choose the path for the work

Start with one task and the people it affects

TritonAI can support work that stays with you in Harness or a service that other people rely on. Begin with the task, the sources it needs, the person who reviews the result, and the audience that will use it.

Describe the work

Step 1: Define the task

The access request gives the service team enough context to identify the right starting point. You can describe personal work in Harness or an application that will serve a wider audience.

Work in Harness

Use Harness when you want an AI workspace for your own work. It can help you work across selected files, approved browser sources, and productivity connections you choose to use.

Examples: a morning briefing, meeting preparation, document comparison, or a repeatable reporting workflow.

Build a shared service

Choose a developer path when a department needs an application, integration, or workflow that other people will use.

The intended audience and task
Data and system connections
Business and technical owners
Review and support responsibilities

Submit the access request

Include your UC San Diego credentials, department or sponsor, intended outcome, and the data the task requires. Review timing depends on the use case and any privacy, security, accessibility, or service-owner review.

Request Developer Access

Confirm the route

Step 2: Confirm the access path

The service team will confirm which workspace, model routes, skills, and integrations fit the reviewed task. The decision also covers data handling, usage allocations, and any additional review.

Harness path: Confirm the installer, approved models, available skills, and connections you may use for the task.
Shared service path: Confirm API access, hosting needs, service ownership, and the support plan for the intended audience.

The Model Hub is the source for the current model catalog and published rates. Harness is an early pilot, so available capabilities depend on the approved service path.

Try one workflow

Step 3: Build a bounded prototype

Start with one repeatable task, a narrow set of sources, and a visible review point. Harness can support work such as:

Plan the day

Turn selected calendar events, messages, and notes into a source-linked briefing that you check before acting.

Prepare working materials

Compare selected files, summarize a long document, or draft a meeting brief with links back to the source.

Analyze and create

Clean a spreadsheet, build a chart, prepare slides, or assemble a status report from approved data.

Reuse a campus skill

Run a documented checklist, collect evidence, and produce the same review package each time the task returns.

Research in the browser

Gather information from approved sites, compare source claims, and save citations for a person to review.

Prototype a tool

Turn a validated workflow into a small local tool, then plan hosting and support if other people will depend on it.

Run the prototype in a reviewable cycle

1Choose one taskWrite down the input, output, and intended user.
2Connect what it needsUse only the approved sources and permissions required for the task.
3Run and inspectCheck sources, test failure cases, and review consequential actions.
4Save the evidenceRecord quality, accessibility, cost, and limitations before expanding the scope.

Prepare for use

Step 4: Plan for operation

Before more people depend on the workflow or you connect additional data and systems, confirm:

Named business and technical owners
Accessibility, security, privacy, and support responsibilities
Monitoring, escalation, and incident handling
An approved allocation or billing arrangement for expected usage

Bring the prototype evidence back to the service team. They can help identify the approved hosting, integration, and support path for the next audience.