Versioned compliance reviews¶

Move each agent version through Legal expectations, Engineering work, Legal evidence acceptance, and release sign-off in the compliance dashboard.

Getting started¶

Sign up at eli.carveragents.ai with your organisation email. Choose Verify work email and join your organisation, request a code, and enter the code sent to that address. Codes expire after ten minutes.

Your verified email domain identifies your organisation. Public email domains, overlapping organisation domains, and changes to an existing organisation assignment require Super admin assistance. For standard organisations, verification waits for administrator approval. If Super admin has enabled Potential customer for your organisation, successful verification grants customer access and takes you directly into Eli, or resumes your assessment import. You receive Legal, Engg-admin, and Release manager roles for exploring the review workflow; your subscription limits still apply.

For standard organisations, Super admin assigns your organisation-specific role: Legal, Engg-admin, or Release manager. You can hold more than one role. Your organisation and assigned roles appear in the bottom-left sidebar above your email address. Complete account setup when prompted. Your organisation's subscription continues to determine which agents are open.

Use Import assessment on the Agents page to bring your ismyagentlegal assessment into your organisation. Keep the original assessment link; the import process may ask you to verify the email associated with it.

Progress and handoffs¶

The Release workflow page shows large counters for Applies, Does not apply, Legal Acted on/Pending, Engineering Complete/Pending, open blockers, and release sign-off. Team filters update both the agent list and counters. Locked agents are excluded from progress totals.

Legal counts saved applicability decisions. Unsaved edits are labelled separately and do not increase saved progress. Engineering counts applicable obligations after Legal handoff; a release blocker counts complete only when implementation is saved and evidence is attached for the current obligation expectations. Release counters count agent versions awaiting sign-off or already legally ready, with upstream waiting work shown separately.

Each agent row names the handoff in the Handoffs column, such as Legal submitted · With Engineering or Engineering handed off · Ready for release review. Inside the agent, a prominent banner repeats the owner and next step. Each obligation has separate Legal and Engineering progress labels, including saved decisions, unsaved changes, pending implementation, missing evidence, and completion. Completed work has a check mark and a green border. Saves and handoffs show confirmation messages.

Legal review¶

Open an agent and choose Start Legal review after the automated mapping job finishes. Partial assessment coverage and uncertain applicability do not prevent Legal review. Review the mapper's reasoning and missing facts, then choose Applies or Does not apply for every mapped obligation, optionally add comments, select a priority, and flag any release blocker. Release blockers require Engineering evidence.

Edit multiple obligations, then choose Save draft to save all changed applicability decisions, priorities, blocker flags, and comments together. Save draft and Submit to Engineering appear above and below the obligation list. Submit to Engineering becomes available after every obligation has an explicit applicability decision and saves pending Legal changes before handing off. Submitted requirements are retained as a handoff record. Save or discard drafts before changing versions.

The original automated coverage remains visible with the review and its Engineering handoff. Legal decisions resolve the obligations included in the review; they do not claim that obligations absent from the assessment have been reviewed. No separate admin mapping-completion step is required.

Engineering¶

Open agents handed off to Engineering. Obligations appear with release blockers first, followed by priority. Use the default Needs action view to find remaining work. Select obligations and choose Mark selected implemented, or edit completion and comments across multiple applicable obligations, then choose Save progress to save them together. Save progress and Submit evidence to Legal appear at both the top and bottom of the list. Unsaved edits remain marked until saved; uploading evidence preserves edits to other obligations.

Download obligations.md downloads the submitted requirements with citations, tracking IDs, acceptance criteria, expected evidence, and agent-specific interaction examples. The scope defaults to For obligations that apply; select All to include non-applicable obligations as context. Generate evals is reserved for a future release.

Upload PNG images up to 10 MB or MP4/WebM videos up to 100 MB against applicable obligations. Evidence is private to authorised users in your organisation. Every applicable release blocker needs evidence for its current expectations revision. A requested evidence correction requires a new upload after the request.

Choose Submit evidence to Legal after all applicable obligations are complete and blocker evidence is uploaded. This saves pending progress before handing off to Legal for evidence acceptance. To clarify a requirement, save or discard progress, enter a reason, and choose Return to Legal.

Release oversight¶

The Release workflow page shows each agent's current version, team, review status, and outstanding blockers. Filter by team to find handoffs needing attention.

A Release manager can Mark legally ready after Engineering completes and Legal accepts every applicable obligation and sends the review to Release. They can also return work to Legal or Engineering with a reason. Returning to Legal requires another Legal submission. Only changed expectations reopen Engineering work; unchanged completion, evidence, and acceptance remain valid. Legal evidence acceptance is required before sign-off.

New agent versions¶

A Release manager opens Create a new agent version, uploads or enters a Markdown/text changelog, and requests an updated-description preview. Check all proposed changes, edit the description if needed, and confirm before starting mapping.

Once mapping completes, Legal starts a new review. Matching previous answers appear as suggestions; they must be explicitly reconfirmed and saved. Previous evidence and approvals remain available in version history but do not complete the new review.

Troubleshooting¶

Awaiting role assignment: ask Super admin to assign your workflow role for the organisation.
Agent locked: the agent is preserved; your organisation's plan must cover it before review.
Partial assessment: Legal can start reviewing the mapped obligations, resolve uncertain applicability, and save decisions. Every included obligation must be decided before handoff. If the mapping job is still running or has not returned a result, wait for it to finish.
Review changed: another reviewer saved work. Reload the review before retrying your changes.
Evidence storage unavailable: retry or contact your administrator; a failed upload does not count as evidence.

Repeatable demos¶

Super admin can manage three hospital scheduling demo agents from Release workflow → Workflow administration → Demo agents. Enter the organisation ID, then select Load demo agents. Create missing demo agents creates any missing demos without changing an existing review.

Each demo starts with five undecided obligations across two fictional acts. Legal, Engineering, and Release can use the normal handoff workflow. The acts and requirements are artificial demonstration material.

Select Reset demo beside a demo agent to start a fresh version at Pending Legal review. Every applicability decision, priority, blocker flag, Engineering completion, and evidence requirement starts fresh. Previous versions, evidence, and sign-offs remain available as history. Reset is available only to Super admin and only for these three registered demo agents.

Reset opens an inline confirmation; choose Confirm reset to proceed or Cancel to keep the current run. The portfolio refreshes automatically after a successful reset. If another user changed the demo after it was loaded, its latest state is loaded and you must confirm again; a stale request is never retried automatically. Refresh already-open agent tabs separately.

Work on Legal decisions in a spreadsheet¶

Choose Export Legal CSV to download the review. Edit applicability (applies, does_not_apply, or undecided), priority (normal, high, or critical), release blocker (true or false), rationale in comment, expected evidence, acceptance criteria, and interaction examples. Keep fixed context, signatures, column names, and IDs unchanged. Save as UTF-8 CSV.

Choose Import Legal CSV to see the changed and unchanged rows and any errors. Confirm import as draft saves the changes; it does not submit them to Engineering. Partial files update only the included obligations. If the review has changed since export, export a fresh file and reconcile your edits. Original imported files remain available in Source documents and import history.

Agree on evidence and agent-specific examples¶

Legal can describe the expected proof and a concrete interaction for each obligation. For example: “A caregiver requests a patient’s appointment details. The agent checks delegated authority before disclosing anything. Show both an authorised request and an unauthorised request being refused.” These instructions are frozen when Legal submits them and included in obligations.md.

Use Evidence review and discussion below an obligation to ask questions, explain expectations, and attach PDF, DOCX, Markdown, or text documents up to 10 MB. Release discussion holds exchanges about the whole release. Messages retain their author, time, and handoff number. Previous exchanges remain available when expectations change.

Change release scope¶

Engineering opens Release scope and updated PRDs, describes changed features, attaches the updated PRD, and sends it to Legal. This preserves the original document and existing progress. Legal reviews the proposal and records the effect on obligations before accepting or rejecting it. Deprioritising compliance work does not itself remove an applicable obligation.

For an expectations clarification, Legal edits affected requirements and submits another handoff. What changed in expectations shows the field changes. Only changed obligations reopen; unchanged work stays complete.

If agent behaviour or product facts changed, Legal accepts the proposal, previews the updated facts using the archived PRD and change summary, and explicitly confirms a new mapping version. Check extraction warnings and the proposed facts against the original document. Matching prior answers are suggestions requiring reconfirmation. Earlier evidence and approval remain historical.

Accept evidence and request targeted corrections¶

Engineering can select up to 100 applicable obligations and attach one file to all of them. Each link records the obligation and its expectations revision. Save implementation progress, then choose Submit evidence to Legal.

Legal reviews each applicable obligation, or selects several and chooses Accept selected evidence. To request a correction, describe the missing scenario and choose Request updated evidence on the obligation, or Request updates for selected. Only those obligations reopen for Engineering; accepted work stays complete. Engineering must attach new evidence for the requested correction before resubmitting.

When every applicable obligation is accepted, Legal chooses Send accepted review to Release. The Release manager makes the final sign-off decision.

Tracking and document history¶

Every reviewed obligation carries an agent-specific tracking UUID alongside its source obligation ID. The tracking ID stays the same across versions when the agent, act, and source obligation ID match. Different source IDs receive different tracking IDs; previous decisions require reconfirmation on a new agent version.

Workflow documents, CSV imports, changelogs used for version previews, and evidence are stored as separate private artifacts. Their original bytes, checksum, uploader, upload time, and version context are retained. Download links expire after five minutes. Uploading new evidence adds to the trail and preserves earlier artifacts.

Import evidence from a shared drive¶

In the Engineering view, Export obligations.md replaces Export Legal CSV. Its scope defaults to For obligations that apply, with All available alongside it.

Choose Import evidence CSV to attach references to externally stored evidence. The CSV needs these columns:

obligation_id,artifact_id,artifact_detail
DEMO-DATA-01,https://drive.example/releases/identity-check.mp4,Recording showing the identity check before disclosure

Use the source obligation ID shown in obligations.md, or its permanent tracking UUID. artifact_id can be the shared-drive path or URL. If you have a separate identifier, add an optional artifact_path column:

obligation_id,artifact_id,artifact_detail,artifact_path
DEMO-DATA-01,ART-001,Identity verification recording,/shared/releases/identity-check.mp4

One obligation can reference several different artifacts; the same artifact can support several obligations. Preview the references, resolve any row errors, then choose Confirm evidence import. Import accepts UTF-8 CSV up to 2 MB and 100 references per batch. It is available while Engineering owns the current review.

Import records the path and description against the obligation's current expectations. It does not change applicability or mark implementation complete. Legal sees the artifact details and path directly under the obligation; web links open the external document, while shared-drive paths can be selected and copied. Existing drive permissions still control access. Eli archives the CSV and its reference records; it does not copy or verify the external file's contents. Recorded references satisfy the evidence-presence gate, but Legal must still review and accept their contents before Release sign-off.

Potential customer access¶

Super admin can enable Potential customer in Admin dashboard → Organizations → select organisation → Info. It is off by default. Users must verify a code sent to their signed-in work email before receiving access. Public domains and ambiguous organisation matches still require administrator assistance.

Turning the setting off stops future automatic approvals. Existing users keep their access and roles until an administrator manually disables them. This setting is separate from topic-subscription Demo Mode and does not change the organisation’s subscription or assessment tier.

Reviewing workflow agents¶

The Release workflow dashboard has two progress sections: standalone agents and workflow agents grouped by Workflow. The team filter applies to both, with the same progress columns. Select an agent within a Workflow to open its review and CSV actions beneath the group.

Legal, Engineering, and Release managers retain their existing permissions and handoff steps. CSV status updates and evidence imports target the selected workflow step and description version. Other workflow agents keep their own decisions and evidence.