Projects
Dynamic workstreams connected to company stages, source records, tasks, files, support, and accountable owners.
JRI.AI Amplify
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.
Library
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.
4-step weekly checklist for sweeping compliance obligations—review instances, check due dates, verify evidence, and escalate blockers.
One operating loop
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.
A founder describes the outcome, asks a question, or starts from a roadmap milestone, support ticket, source record, or schedule.
A planner chooses the relevant domains, tools, skills, and model tier. If important context is missing, it asks before work begins.
Controlled tools fetch only the source records needed from Business, Console, Compliance, Contracts, Growth, Offerings, Support, and files.
A task is claimed with a lease, assigned to an agent or group, and executed with a step-by-step runtime and tool trail.
Artifacts, questions, proposed changes, and exceptions return to a visible queue. Sensitive writes wait for the required approval.
The result, source links, files, logs, and any confirmed changes stay attached to the task and project history.
Three doors
Mission Control
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.
The work system
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.
Dynamic workstreams connected to company stages, source records, tasks, files, support, and accountable owners.
Durable briefs with assignment, context markdown, lifecycle status, attempts, results, logs, and source links.
Specialist agents can work directly or as a lead-and-subagent group with explicit instructions, skills, and model settings.
Durable company notes and artifacts live in the Library; reusable playbooks can be selected by the planner and attached to agents.
Paused or active routines can run on schedules, webhooks, or API events and create traceable tasks instead of invisible background actions.
Task claiming, leases, heartbeats, retries, cancellation, reflection, and recovery make execution inspectable and resilient.
The living roadmap
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.
Controlled context
The business modules remain authoritative. Amplify fetches bounded context through controlled tools and preserves links back to the records used for the task.
Inside Amplify
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 SystemApp dashboard
Conversational builder
Versions and diffs
Publish and host
Amplify is plan-gated. Available agents, connectors, tools, and write scope depend on the workplace configuration and the review required for each action.