JRI.AI Amplify

Turn a company objective into accountable work.

Amplify plans the work, gathers the right company context, assigns agents, records every step, and brings consequential changes back for review.

Canvas Workspace

Playbooks

Reusable agent capabilities, supporting files, and assignment coverage.

Back to canvas  ×

Library

Skills and reusable instructions

Skills are durable instructions any assigned agent can reuse. Open a skill to read its full prompt, supporting files, and assignment coverage before routing it into work.

1Skills
0Supporting files
1Assignments
Weekly-compliance-sweep-checklist0 files

4-step weekly checklist for sweeping compliance obligations—review instances, check due dates, verify evidence, and escalate blockers.

# Weekly Compliance Sweep Checklist
## Step 1 — Review open compliance instances and due dates…
1 assigned agentOpen skill

One operating loop

From a brief to a result you can inspect.

Amplify does not replace the systems where company records belong. It coordinates work around those records and makes the plan, context, execution, review, and result visible.

01

Intent

A founder describes the outcome, asks a question, or starts from a roadmap milestone, support ticket, source record, or schedule.

02

Plan

A planner chooses the relevant domains, tools, skills, and model tier. If important context is missing, it asks before work begins.

03

Context

Controlled tools fetch only the source records needed from Business, Console, Compliance, Contracts, Growth, Offerings, Support, and files.

04

Run

A task is claimed with a lease, assigned to an agent or group, and executed with a step-by-step runtime and tool trail.

05

Review

Artifacts, questions, proposed changes, and exceptions return to a visible queue. Sensitive writes wait for the required approval.

06

Result

The result, source links, files, logs, and any confirmed changes stay attached to the task and project history.

Three doors

Simple at entry. Detailed when needed.

Mission Control

See work by state, not by software module.

Mission Control is the default Amplify view. It groups work into Ready to review, Running, Done, and Blocked, with department filters derived from the agents doing the work.

Tasks and proposed actions in one operational view
Department-level focus without losing the company-wide picture
A review queue for approvals, questions, and completed artifacts

The work system

Projects, agents, and memory that stay connected.

The visible interface is backed by durable work objects. A chat can become a task; a task can belong to a project; a result can become a file; a repeated workflow can become a skill or Autopilot.

Projects

Dynamic workstreams connected to company stages, source records, tasks, files, support, and accountable owners.

Tasks

Durable briefs with assignment, context markdown, lifecycle status, attempts, results, logs, and source links.

Agents and groups

Specialist agents can work directly or as a lead-and-subagent group with explicit instructions, skills, and model settings.

Files and skills

Durable company notes and artifacts live in the Library; reusable playbooks can be selected by the planner and attached to agents.

Autopilots

Paused or active routines can run on schedules, webhooks, or API events and create traceable tasks instead of invisible background actions.

Runtime and recovery

Task claiming, leases, heartbeats, retries, cancellation, reflection, and recovery make execution inspectable and resilient.

The living roadmap

Plan company progress as milestones that agents can maintain.

Onboarding creates stages, milestones, and tasks. Amplify can read the roadmap, execute a milestone, update progress, add a task, attach relevant support, and ask before an ambiguous or destructive change.

OnboardingFoundationOperationsGrowthScaleGovernance
Launch first recurring revenue workflow
Confirm offer and audience
Prepare customer list
Draft campaign and review
Track replies and next actions
Linked to Growth, Offerings, and one Support service

Controlled context

Amplify reads the company. It does not become a second company record.

The business modules remain authoritative. Amplify fetches bounded context through controlled tools and preserves links back to the records used for the task.

Business
Console
Compliance
Contracts
Growth
Offerings
Support
Workplace files

Consequential work stops at a visible review boundary.

01Guidance and internal preparation can complete with an audit trail.
02Missing information becomes an ask-user checkpoint.
03Sensitive legacy changes become proposed actions.
04External sends, payments, filings, signatures, and authority outcomes retain their own confirmation state.

Inside Amplify

Build the operational app the team needs next.

Apps is a complete product inside Amplify: describe an app, build it conversationally, inspect code and problems, connect data, manage versions, and publish it on JRI hosting.

Explore the Apps System

App dashboard

Conversational builder

Versions and diffs

Publish and host

Give the next objective a plan, a trail, and an owner.

Amplify is plan-gated. Available agents, connectors, tools, and write scope depend on the workplace configuration and the review required for each action.