Client delivery

atlas_delivery_engagements_acceptance_blockers_list

List everything stopping a deliverable from being accepted: unmet criteria, open review notes, missing reviews and missing sign-off. An empty list means it can be accepted.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/deliverables/{childId}/acceptance-blockers

Example prompt

What is stopping the operating model deliverable from being accepted?

Arguments

atlas_delivery_engagements_acceptance_check_terms_update

Change the terms a check runs under: the export control restrictions and the enhanced due diligence facts. Send only the fields that change. Returns the check.

Scope

delivery:write

Calls

PATCH /v1/engagements/{engagementId}/acceptance/checks/{childId}/compliance

Example prompt

Record that only US persons may work on the export control check.

Arguments

atlas_delivery_engagements_acceptance_checks_create

Add an acceptance check to an engagement, for example a sanctions screen on a named party. Returns the check.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/acceptance/checks

Example prompt

Add a sanctions check on Northwind Holdings.

Arguments

atlas_delivery_engagements_acceptance_checks_list

List the acceptance checks of one engagement, such as conflicts, sanctions and anti-money-laundering checks, with their state and expiry.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/acceptance/checks

Example prompt

Which acceptance checks are still outstanding on Northwind?

Arguments

atlas_delivery_engagements_acceptance_create

Open the client acceptance record for an engagement, with the facts the risk assessment rests on. The checks those facts require are created with it. Returns the record.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/acceptance

Example prompt

Open client acceptance for Northwind as a high-risk, cross-border engagement.

Arguments

atlas_delivery_engagements_acceptance_get

Read the client acceptance record of one engagement: its risk tier, the facts it was assessed on, its checks and the decision.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/acceptance

Example prompt

Show me the client acceptance record for Northwind.

Arguments

atlas_delivery_engagements_acceptance_review

Move the client acceptance record into review, so the decision can be taken. Returns the record.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/acceptance/review

Example prompt

Move the Northwind acceptance into review.

Arguments

atlas_delivery_engagements_acceptance_update

Change the facts of the client acceptance record. The checks are brought in line with the new facts. Send only the fields that change. Returns the record.

Scope

delivery:write

Calls

PATCH /v1/engagements/{engagementId}/acceptance

Example prompt

Record that the Northwind work will use subcontractors.

Arguments

atlas_delivery_engagements_access_grants_list

List the access grants on an engagement: who holds access, the reason recorded, when it expires and which workstreams it is limited to. Requires administrator access to the engagement.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/access-grants

Example prompt

Who has access to the Northwind engagement?

Arguments

atlas_delivery_engagements_access_grants_revoke

Revoke one access grant on an engagement, so its holder no longer reaches the engagement through it. This removes access and cannot grant any. Returns the revoked grant.

Scope

delivery:write

Calls

DELETE /v1/engagements/{engagementId}/access-grants/{childId}

Example prompt

Revoke the access grant for the contractor who left the Northwind engagement.

Arguments

atlas_delivery_engagements_access_provisions_list

List the client system access the team holds on an engagement: each system, access level, team member, when it was granted, whether credentials were issued, when it expires, and whether it has been revoked.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/access-provisions

Example prompt

Which client systems does the team still have access to on Northwind?

Arguments

atlas_delivery_engagements_access_provisions_record

Record that the client gave a team member access to one of its systems, with the access level, dates and whether credentials were issued. This is the register of access already given; it does not grant access to anything. Returns the record.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/access-provisions

Example prompt

Log that the client gave Omar read-only access to their SAP system today.

Arguments

atlas_delivery_engagements_access_provisions_revoke

Record that access to a client system has been removed, with the evidence of its removal, such as the client ticket reference. Returns the updated record.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/access-provisions/{childId}/revoke

Example prompt

Record that Omar's SAP access was removed under ticket INC-4412.

Arguments

atlas_delivery_engagements_ai_drafts_deliverable_qa_generate

Ask for an AI quality pre-check of a deliverable. The result is a proposed draft of findings that a person reviews. Returns the draft.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/ai-drafts/deliverable-qa

Example prompt

Pre-check the final report before it goes to review.

Arguments

atlas_delivery_engagements_ai_drafts_get

Read one AI draft with its proposed content and the keys that can be accepted.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/ai-drafts/{draftId}

Example prompt

Show me the draft minutes for the steering meeting.

Arguments

atlas_delivery_engagements_ai_drafts_health_explanation_generate

Ask for an AI explanation of the current health ratings of an engagement, drawn from its registers. Returns the proposed draft.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/ai-drafts/health-explanation

Example prompt

Explain why this engagement is amber.

Arguments

atlas_delivery_engagements_ai_drafts_list

List the AI drafts proposed on an engagement, optionally by kind and status. A draft changes nothing until a person accepts it.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/ai-drafts

Example prompt

Which AI drafts are waiting for review?

Arguments

atlas_delivery_engagements_ai_drafts_minutes_generate

Ask for AI draft minutes of a governed meeting. The minutes are a proposal until a person accepts them. Returns the draft.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/ai-drafts/minutes

Example prompt

Draft the minutes for yesterday's steering meeting.

Arguments

atlas_delivery_engagements_ai_drafts_raid_items_generate

Ask the AI to propose RAID items from up to ten meetings and twenty threads. The proposals are a draft until a person accepts them. Returns the draft.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/ai-drafts/raid

Example prompt

Suggest risks from the last three steering meetings.

Arguments

atlas_delivery_engagements_ai_drafts_reject

Reject an AI draft, with an optional note, so it is not applied. Returns the updated draft.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/ai-drafts/{draftId}/reject

Example prompt

Reject the draft status report, the tone is wrong.

Arguments

atlas_delivery_engagements_ai_drafts_status_report_generate

Ask for an AI draft of the narrative of a status report. The narrative is a proposal until a person accepts it. Returns the draft.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/ai-drafts/status-report

Example prompt

Draft the narrative for this week's status report.

Arguments

atlas_delivery_engagements_analyses_blocked_mark

Mark an analysis as blocked, with the reason. Returns the updated analysis.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/structuring/analyses/{childId}/block

Example prompt

The churn analysis is blocked waiting on the CRM extract.

Arguments

atlas_delivery_engagements_analyses_complete

Complete an analysis with its finding summary and so-what, and optionally its confidence and actual effort. Only a completed analysis counts as evidence behind a storyline page. Returns the updated analysis.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/structuring/analyses/{childId}/complete

Example prompt

Complete the churn analysis: churn is concentrated in year-one SME customers.

Arguments

atlas_delivery_engagements_analyses_create

Plan an analysis on an engagement: what it is, which hypothesis it tests, its type, owner, reviewer and dates. Returns the created analysis.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/structuring/analyses

Example prompt

Plan a customer churn analysis to test hypothesis 2, owned by Sam, due in two weeks.

Arguments

atlas_delivery_engagements_analyses_list

List the analyses on an engagement, optionally by status, hypothesis or workstream. Each carries its type, owner, dates and findings.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/structuring/analyses

Example prompt

Which analyses are blocked?

Arguments

atlas_delivery_engagements_analyses_start

Start a planned analysis, moving it from planned to in progress. Returns the updated analysis.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/structuring/analyses/{childId}/start

Example prompt

Start the pricing benchmark analysis.

Arguments

atlas_delivery_engagements_analyses_update

Change the fields of an analysis, including its findings, so-what and confidence while it is in progress. Only the fields sent change. Returns the updated analysis.

Scope

delivery:write

Calls

PATCH /v1/engagements/{engagementId}/structuring/analyses/{childId}

Example prompt

Update the churn analysis finding to say retention is worst in the SME segment.

Arguments

atlas_delivery_engagements_analytical_assumptions_create

Record an analytical assumption: the statement, the variable, its basis, its base, low and high values, and where it is used. Returns the recorded assumption.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/analytical-assumptions

Example prompt

Record the assumption that churn stays at 8 percent, based on client data.

Arguments

atlas_delivery_engagements_analytical_assumptions_list

List the analytical assumptions of an engagement: each variable with its base, low and high case, basis, validation status and which models use it.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/analytical-assumptions

Example prompt

What assumptions drive the business case?

Arguments

atlas_delivery_engagements_analytical_assumptions_update

Revise the basis, disclosure deliverable or expiry of an analytical assumption. Returns the updated assumption.

Scope

delivery:write

Calls

PATCH /v1/engagements/{engagementId}/analytical-assumptions/{assumptionId}

Example prompt

Change the basis of the churn assumption to benchmark.

Arguments

atlas_delivery_engagements_analytical_assumptions_void

Record that an analytical assumption no longer holds, with a note, and whether figures that rely on it must be restated. Returns the updated assumption.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/analytical-assumptions/{assumptionId}/invalidate

Example prompt

The churn assumption is wrong, invalidate it and flag a restatement.

Arguments

atlas_delivery_engagements_approvals_list

Read the approval history of one record with its current position: whether the version as it stands is approved. A record can have approvals against earlier versions and still not be approved as it stands.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/approvals/{subjectType}/{subjectId}

Example prompt

Is the current version of the operating model approved?

Arguments

atlas_delivery_engagements_archive

Archive an engagement. It leaves the default lists but keeps every record, and it can be restored. Returns the archived engagement.

Scope

delivery:write

Calls

POST /v1/engagements/{id}/archive

Example prompt

Archive the finished Contoso pilot engagement.

Arguments

atlas_delivery_engagements_assets_consent_record

Record that the client has consented to reuse of an asset, with the evidence. Returns the updated asset.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/assets/{assetId}/consent

Example prompt

Record the client consent to reuse the case study, evidence attached.

Arguments

atlas_delivery_engagements_assets_create

Harvest a reusable asset from an engagement: its kind, title, classification, tags, attachment, and whether client consent is required before reuse. Returns the asset.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/assets

Example prompt

Harvest the pricing model template as a reusable asset.

Arguments

atlas_delivery_engagements_assets_list

List the reusable assets harvested from an engagement with their kind, classification, consent and sanitisation state.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/assets

Example prompt

What reusable assets came out of this engagement?

Arguments

atlas_delivery_engagements_assets_reuse_record

Record that an asset has been reused. The API refuses reuse of an asset that still needs consent or sanitisation. Returns the updated asset.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/assets/{assetId}/reuse

Example prompt

Record that we reused the pricing template.

Arguments

atlas_delivery_engagements_attachments_delete

Delete a file attached to an engagement, removing it from the engagement file list. Use this only when the person asks to delete it.

Scope

attachments:delete

Calls

DELETE /engagements/{engagementId}/attachments/{attachmentId}

Example prompt

Remove the outdated org chart from the Northwind files.

Arguments

atlas_delivery_engagements_attachments_download

Get a short-lived download URL for a file attached to an engagement. Returns the URL and when it expires.

Scope

attachments:read

Calls

GET /engagements/{engagementId}/attachments/{attachmentId}/download

Example prompt

Give me a download link for the Northwind statement of work.

Arguments

atlas_delivery_engagements_attachments_finalize

Finish an upload started with atlas_delivery_engagements_attachments_upload, once the bytes have been sent. Returns the attachment.

Scope

attachments:write

Calls

POST /engagements/{engagementId}/attachments/{attachmentId}/finalize

Example prompt

Finish attaching the statement of work I just uploaded.

Arguments

atlas_delivery_engagements_attachments_list

List the files attached to one engagement, with their names, sizes and who can see them.

Scope

attachments:read

Calls

GET /engagements/{engagementId}/attachments

Example prompt

What files are attached to the Northwind engagement?

Arguments

atlas_delivery_engagements_attachments_share_revoke

Take an engagement file back from the client portal, so only the firm sees it. The change is audited and recorded on the timeline.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/attachments/{childId}/unshare

Example prompt

Take the draft org chart back from the Northwind client portal.

Arguments

atlas_delivery_engagements_attachments_upload

Start uploading a file to an engagement. Returns an upload URL and an attachment id: send the file bytes to the URL, then call atlas_delivery_engagements_attachments_finalize with the id.

Scope

attachments:write

Calls

POST /engagements/{engagementId}/attachments/ticket

Example prompt

Attach this statement of work to the Northwind engagement.

Arguments

atlas_delivery_engagements_authority_chain_get

Work out who must approve a decision of a given kind and value on an engagement, from its delegation of authority, including the bands that apply to the whole workspace. Returns the approval chain and how many bands were considered. Use this to answer "who has to sign off a write-off of this size".

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/authority/derive-chain

Example prompt

Who has to approve a 12,500 write-off on Northwind?

Arguments

atlas_delivery_engagements_authority_list

List the delegation of authority that applies to an engagement: for each kind of decision and value band, the approver role or person and whether a second approver is required.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/authority

Example prompt

What is the delegation of authority on this engagement?

Arguments

atlas_delivery_engagements_barriers_crossings_close

Close an open wall crossing, so the person it admitted is outside the information barrier again. This restores the wall; it cannot admit anybody. Returns the crossing id and whether it was closed.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/barriers/crossings/{crossingId}/close

Example prompt

Close the wall crossing for Sam on Project Falcon now that the call is over.

Arguments

atlas_delivery_engagements_barriers_crossings_list

List the open wall crossings on an engagement: who was brought over an information barrier, for what purpose, on whose approval and until when. Closed crossings are not included, because they need no action.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/barriers/crossings

Example prompt

Who has been brought over the wall on Project Falcon, and until when?

Arguments

atlas_delivery_engagements_barriers_insiders_add

Add a person to the insider list of an engagement, recording that they hold inside information, their function and the reason, and when they obtained it. This records a fact; it does not admit the person through any barrier. Returns the entry.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/barriers/insiders

Example prompt

Add Priya to the Project Falcon insider list; she joined the valuation call today.

Arguments

atlas_delivery_engagements_barriers_insiders_list

List the insider list of an engagement: every person recorded as holding inside information, why, when they obtained it, and whether they have been notified of their obligations and acknowledged them.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/barriers/insiders

Example prompt

Show me the insider list for Project Falcon.

Arguments

atlas_delivery_engagements_barriers_insiders_obligation_record

Record one step of an insider list obligation: that the person was notified of their duties, or that they acknowledged them. The two are separate steps under market abuse rules, so each is recorded on its own, and only once it has happened. Returns the entry.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/barriers/insiders/{entryId}/obligation

Example prompt

Record that Priya was notified of her insider obligations.

Arguments

atlas_delivery_engagements_barriers_list

List the information barriers on an engagement: each barrier type, reason, the parties on each side, the excluded parties, the enforcement points, any code name and the dates it is in force. Use this to answer "is there an ethical wall on this engagement".

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/barriers

Example prompt

Is there an ethical wall on the Northwind engagement?

Arguments

atlas_delivery_engagements_barriers_name_get

Ask which name the caller may use for an engagement under a code-named barrier. Pass the real name; the answer is the real name for a person inside the wall and the code name for anybody else, with a flag saying which it is. Use this before writing about a deal that may be code named.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/barriers/name

Example prompt

Which name should I use for the Acme deal in my notes?

Arguments

atlas_delivery_engagements_baseline_variance_get

Compare the plan with one named baseline rather than the current one. Use this to answer "what did the last replan cost".

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/baselines/{childId}/variance

Example prompt

What did the last replan cost against the original baseline?

Arguments

atlas_delivery_engagements_baselines_capture

Capture the plan as it stands as a named baseline: the original, a rebaseline after a change, or a what-if. Returns the baseline.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/baselines

Example prompt

Capture a what-if baseline before we replan.

Arguments

atlas_delivery_engagements_baselines_delete

Delete a baseline that is no longer needed, such as a what-if. The current baseline cannot be deleted.

Scope

delivery:write

Calls

DELETE /v1/engagements/{engagementId}/baselines/{childId}

Example prompt

Delete the what-if baseline we no longer need.

Arguments

atlas_delivery_engagements_baselines_get

Read one baseline with the dates of every plan item it captured.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/baselines/{childId}

Example prompt

Show me the original Northwind baseline.

Arguments

atlas_delivery_engagements_baselines_list

List the baselines of one engagement, marking which is current.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/baselines

Example prompt

Which baselines does Northwind have?

Arguments

atlas_delivery_engagements_benchmarks_create

Record a benchmark: the metric and its definition, the peer set, the data source and vintage, the quartiles, the client value and gaps, and licence and anonymisation constraints. Returns the recorded benchmark.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/benchmarks

Example prompt

Record the cost-to-serve benchmark against the 12 peer banks.

Arguments

atlas_delivery_engagements_benchmarks_delete

Delete a benchmark recorded in error. Returns the result of the deletion.

Scope

delivery:write

Calls

DELETE /v1/engagements/{engagementId}/benchmarks/{benchmarkId}

Example prompt

Delete the duplicate benchmark.

Arguments

atlas_delivery_engagements_benchmarks_link

Attach a benchmark to a deliverable, so it is shown and checked as part of it. Returns the updated benchmark.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/benchmarks/{benchmarkId}/attach

Example prompt

Attach the cost-to-serve benchmark to the final report.

Arguments

atlas_delivery_engagements_benchmarks_list

List the benchmarks on an engagement, optionally only those without a competition law review or those attached to one deliverable.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/benchmarks

Example prompt

Which benchmarks still need a competition law review?

Arguments

atlas_delivery_engagements_benchmarks_unlink

Detach a benchmark from the deliverable it is attached to. Returns the updated benchmark.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/benchmarks/{benchmarkId}/detach

Example prompt

Take the cost-to-serve benchmark off the final report.

Arguments

atlas_delivery_engagements_benchmarks_update

Change the fields of a benchmark. Only the fields sent change; send null to clear a field that allows it. Returns the updated benchmark.

Scope

delivery:write

Calls

PATCH /v1/engagements/{engagementId}/benchmarks/{benchmarkId}

Example prompt

Update the client value on the cost-to-serve benchmark to 41.2.

Arguments

atlas_delivery_engagements_beneficial_owners_add

Add a beneficial owner of the client to an acceptance check, with how they control it, their ownership share, their details, their screening results and the registry the information came from. Returns the owner.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/beneficial-owners

Example prompt

Add Jane Doe as a 30 percent shareholder beneficial owner on the acceptance check.

Arguments

atlas_delivery_engagements_beneficial_owners_assessment_get

Apply the fifty percent rule to the beneficial owners of an acceptance check: add up the holdings of every owner recorded as blocked and say whether the client is itself blocked. The result is also written onto the latest screening run.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/beneficial-owners/{checkId}/ownership-assessment

Example prompt

Is Acme Holdings blocked under the fifty percent rule?

Arguments

atlas_delivery_engagements_beneficial_owners_discrepancy_record

Record that a discrepancy between the beneficial owner the firm found and the public register has been reported to the register. This records the report; it does not send one. Returns the owner.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/beneficial-owners/{uboId}/discrepancy

Example prompt

Record that we reported the Companies House discrepancy for Jane Doe.

Arguments

atlas_delivery_engagements_beneficial_owners_list

List the beneficial owners recorded on an engagement: each owner, how they control the client, their ownership share, their screening status and whether a register discrepancy was reported.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/beneficial-owners

Example prompt

Who are the beneficial owners recorded for Acme Holdings?

Arguments

atlas_delivery_engagements_benefits_create

Add a benefit to the register: its type, name, measure, unit, baseline and target values, attribution percentage and currency. Returns the benefit.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/benefits

Example prompt

Track a cost reduction benefit of 2 million pounds against a 10 million baseline.

Arguments

atlas_delivery_engagements_benefits_list

List the benefits register of an engagement: each benefit with its type, measure, baseline, target, attribution and readings.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/benefits

Example prompt

What benefits are we tracking for the client?

Arguments

atlas_delivery_engagements_benefits_readings_record

Record a reading of a benefit at a date, with its source. Returns the reading.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/benefits/{benefitId}/readings

Example prompt

Record a reading of 1.2 million on the cost benefit as of 30 June.

Arguments

atlas_delivery_engagements_billing_milestones_create

Add a billing milestone to an engagement, with what makes it billable and the amount. Returns the milestone.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/commercials/billing-milestones

Example prompt

Add a 50,000 billing milestone triggered by acceptance of the operating model.

Arguments

atlas_delivery_engagements_billing_milestones_disputed_mark

Mark a billing milestone as disputed by the client, with the reason. Returns the milestone.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/commercials/billing-milestones/{childId}/dispute

Example prompt

The client disputes the design milestone invoice.

Arguments

atlas_delivery_engagements_billing_milestones_held_mark

Put a billing milestone on hold, with the reason. Returns the milestone.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/commercials/billing-milestones/{childId}/hold

Example prompt

Put the build milestone on hold until the purchase order arrives.

Arguments

atlas_delivery_engagements_billing_milestones_invoiced_mark

Mark a billing milestone as invoiced, with the invoice reference. Returns the milestone.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/commercials/billing-milestones/{childId}/mark-invoiced

Example prompt

Mark the design milestone as invoiced on INV-2291.

Arguments

atlas_delivery_engagements_billing_milestones_list

List the billing milestones of one engagement with their trigger, amount and state: planned, earned, invoiced, paid, disputed or on hold.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/commercials/billing-milestones

Example prompt

Which Northwind billing milestones are not yet invoiced?

Arguments

atlas_delivery_engagements_billing_milestones_paid_mark

Mark an invoiced billing milestone as paid. Returns the milestone.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/commercials/billing-milestones/{childId}/mark-paid

Example prompt

Mark the design milestone as paid.

Arguments

atlas_delivery_engagements_change_approvals_list

List the approval steps of a change request with each approver and their decision.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/change-requests/{childId}/approvals

Example prompt

Who still has to decide on the second workshop change?

Arguments

atlas_delivery_engagements_change_approvers_add

Add an approver to a change request at a given step, as a member, a client contact or an external party. Returns the approval step.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/approvals

Example prompt

Add the Northwind sponsor as an approver on the workshop change.

Arguments

atlas_delivery_engagements_change_requests_complete

Mark an approved change request as implemented. Returns the change request.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/implement

Example prompt

Mark the approved workshop change as implemented.

Arguments

atlas_delivery_engagements_change_requests_create

Raise a change request against an engagement. It is created as a draft with no impact assessed and no approvers, which is deliberate: assessing the impact and deciding the change belong to people. Use this to capture that a change has been requested, not to approve one.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests

Example prompt

Raise a change request for the extra migration run.

Arguments

atlas_delivery_engagements_change_requests_deferred_mark

Defer a change request to be considered later, with the reason. Returns the change request.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/defer

Example prompt

Defer the reporting change request until phase two.

Arguments

atlas_delivery_engagements_change_requests_delete

Delete a change request that is still open. A decided change is part of the record and is refused; withdraw an open change instead when its history should stay.

Scope

delivery:write

Calls

DELETE /v1/engagements/{engagementId}/change-requests/{childId}

Example prompt

Delete the change request I raised twice.

Arguments

atlas_delivery_engagements_change_requests_drift_get

Cumulative drift from approved changes, measured against the ORIGINAL baseline rather than the current one. This is the number that catches ten changes each comfortably under the approval threshold whose sum has moved the engagement thirty percent from what was signed.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/change-requests/drift

Example prompt

How far has Northwind drifted from its baseline?

Arguments

atlas_delivery_engagements_change_requests_get

Read one change request with its impact assessment, approval steps and history.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/change-requests/{childId}

Example prompt

Show me the change request for the second workshop.

Arguments

atlas_delivery_engagements_change_requests_list

Read the change register for one engagement: every change request with its type, status, schedule impact in days and cost impact.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/change-requests

Example prompt

What changes have been raised on Northwind?

Arguments

atlas_delivery_engagements_change_requests_review

Start the review of a submitted change request, so its approvers can decide. Returns the change request in its new state.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/review

Example prompt

Start the review of the second workshop change request.

Arguments

atlas_delivery_engagements_change_requests_share_revoke

Take a change request back from the client portal, with the reason. The change is audited and recorded on the timeline.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/unshare

Example prompt

Take the pricing change request back from the client portal.

Arguments

atlas_delivery_engagements_change_requests_submit

Submit a change request for review. Returns the change request in its new state.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/submit

Example prompt

Submit the second workshop change request for review.

Arguments

atlas_delivery_engagements_change_requests_summary_get

Summarise the change register of one engagement: the count in each status, and the value sitting in the approval chain that has not landed yet.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/change-requests/summary

Example prompt

How much change value is waiting in the approval chain on Northwind?

Arguments

atlas_delivery_engagements_change_requests_update

Change the title, description, type, urgency or flags of a change request. Send only the fields that change. Returns the change request.

Scope

delivery:write

Calls

PATCH /v1/engagements/{engagementId}/change-requests/{childId}

Example prompt

Make the second workshop change request high urgency.

Arguments

atlas_delivery_engagements_change_requests_withdraw

Withdraw a change request, with the reason. The record stays. Returns the change request.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/change-requests/{childId}/withdraw

Example prompt

Withdraw the second workshop change request; the client dropped it.

Arguments

atlas_delivery_engagements_closure_items_generate

Create the standard closure checklist for an engagement. An engagement that already has one is left unchanged. Returns the checklist.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/closure/items/seed

Example prompt

Create the closure checklist for Northwind.

Arguments

atlas_delivery_engagements_closure_items_list

List the closure checklist of one engagement with the state of each item.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/closure/items

Example prompt

What is left on the Northwind closure checklist?

Arguments

atlas_delivery_engagements_closure_items_reopen

Reopen a closure checklist item that was done or waived. Returns the item.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/closure/items/{itemId}/reopen

Example prompt

Reopen the archive closure item; the files were not all moved.

Arguments

atlas_delivery_engagements_closure_readiness_get

Answer "can this engagement close". Returns whether it is ready, every blocker and warning at once, and the closure checklist it was judged against.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/closure/readiness

Example prompt

Can the Northwind engagement close yet?

Arguments

atlas_delivery_engagements_comments_create

Post a comment on an engagement, or a reply to another comment. Returns the new comment.

Scope

comments:write

Calls

POST /engagements/{engagementId}/comments

Example prompt

Comment on the Northwind engagement that the kickoff moved to Tuesday.

Arguments

atlas_delivery_engagements_comments_list

List the comments on one engagement, oldest first, one page at a time. Use this to read the discussion on an engagement.

Scope

comments:read

Calls

GET /engagements/{engagementId}/comments

Example prompt

Show me the discussion on the Northwind engagement.

Arguments

atlas_delivery_engagements_commercial_terms_create

Record a commercial term from the contract. Send the term type and the fields that apply to it: caps, intellectual property, warranty, service levels, key personnel, acceptance, audit, step-in, benchmarking and so on. Returns the term.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/commercial-terms

Example prompt

Record a liability cap of 1 times fees paid over a rolling 12 months.

Arguments

atlas_delivery_engagements_commercial_terms_delete

Delete a commercial term recorded in error. Returns the result of the deletion.

Scope

delivery:write

Calls

DELETE /v1/engagements/{engagementId}/commercial-terms/{termId}

Example prompt

Delete the duplicate warranty term.

Arguments

atlas_delivery_engagements_commercial_terms_list

List the commercial terms recorded from the contract of an engagement: liability caps, intellectual property, warranties, service levels, key personnel, acceptance, audit, benchmarking and others.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/commercial-terms

Example prompt

What is the liability cap on this engagement?

Arguments

atlas_delivery_engagements_commercials_effort_get

Read the effort of one engagement: actual, billable and non-billable effort in minutes, utilisation and leverage.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/commercials/effort

Example prompt

How much of the effort on Northwind has been billable?

Arguments

atlas_delivery_engagements_complaints_acknowledge

Acknowledge a complaint, which stops its acknowledgement clock. Returns the updated complaint.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/complaints/{complaintId}/acknowledge

Example prompt

Acknowledge the CFO complaint.

Arguments

atlas_delivery_engagements_complaints_close

Close a resolved complaint with its root cause and preventive action, optionally linked to the RAID item that records the underlying problem. Returns the updated complaint.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/complaints/{complaintId}/close

Example prompt

Close the late reports complaint: root cause was a missing review step.

Arguments

atlas_delivery_engagements_complaints_create

Record a client complaint: its severity, category, description, who raised it, the owner and the target resolution date. Returns the complaint.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/complaints

Example prompt

Log a high severity complaint from the CFO about late reports.

Arguments

atlas_delivery_engagements_complaints_escalate

Escalate a complaint to the next level of the firm. Returns the updated complaint.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/complaints/{complaintId}/escalate

Example prompt

Escalate the CFO complaint.

Arguments

atlas_delivery_engagements_complaints_list

List the client complaints on an engagement with their severity, category, owner, status and target resolution date.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/complaints

Example prompt

Are there any open complaints on this engagement?

Arguments

atlas_delivery_engagements_create

Create an engagement for a client account. It starts in the pipeline state; apply a playbook afterwards to set up its phases, deliverables and registers. Returns the new engagement with its id and reference. Use this when a person asks to open or set up a new engagement.

Scope

delivery:write

Calls

POST /v1/engagements

Example prompt

Open a new advisory engagement for the Northwind account.

Arguments

atlas_delivery_engagements_critical_path_get

Read the critical path of the plan in the order it runs, as last computed. It does not recompute; use the refresh tool for that.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/plan/critical-path

Example prompt

What is on the Northwind critical path?

Arguments

atlas_delivery_engagements_critical_path_refresh

Recompute the critical path and the float of every plan item. Returns the new critical path.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/plan/recompute

Example prompt

Recompute the Northwind critical path.

Arguments

atlas_delivery_engagements_custom_fields_get

Read the custom field values of one engagement, with the field definitions the workspace uses. Use this before writing values, to learn which keys exist.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/custom-fields

Example prompt

What custom fields are set on the Northwind engagement?

Arguments

atlas_delivery_engagements_custom_fields_set

Write custom field values on one engagement. Only the keys sent are written, and a null clears a value. Returns every value after the write.

Scope

delivery:write

Calls

PUT /v1/engagements/{engagementId}/custom-fields

Example prompt

Set the Northwind sector field to Retail.

Arguments

atlas_delivery_engagements_data_dispositions_create

Record a client dataset and the client instruction for it at the end of the engagement: its classification, locations, return format and any conflict with the firm retention obligations. Returns the record.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/data-dispositions

Example prompt

Record that the client wants the customer extract destroyed, held in two locations.

Arguments

atlas_delivery_engagements_data_dispositions_list

List the data dispositions of an engagement: each client dataset, where it is held, what the client instructed, and whether it has been returned or destroyed.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/data-dispositions

Example prompt

What client data do we still hold for this engagement?

Arguments

atlas_delivery_engagements_data_dispositions_outstanding_list

List the data dispositions not yet carried out. Use this to answer "what client data must still be returned or destroyed".

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/data-dispositions/outstanding

Example prompt

Which client datasets have not been returned or destroyed yet?

Arguments

atlas_delivery_engagements_delete

Delete an engagement. It leaves every list and its code is released for reuse; the record is kept only for audit. Requires the administrator role. Archive it instead when it should only be put away, and use this only when the person explicitly asks to delete it.

Scope

delivery:write

Calls

DELETE /v1/engagements/{id}

Example prompt

Delete the duplicate Northwind engagement I created by mistake.

Arguments

atlas_delivery_engagements_deliverable_certificates_get

Return the API path of the acceptance certificate for a deliverable, in the format asked for. Compose it with the API base URL and an Authorization header to download the document.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/deliverables/{childId}/acceptance-certificate

Example prompt

Get the acceptance certificate for the operating model deliverable as a PDF.

Arguments

atlas_delivery_engagements_deliverable_criteria_create

Add an acceptance criterion to a deliverable. Returns the criterion.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/deliverables/{childId}/criteria

Example prompt

Add an acceptance criterion that every process has an owner.

Arguments

atlas_delivery_engagements_deliverable_criteria_list

List the acceptance criteria of a deliverable with whether each is met, not met or waived.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/deliverables/{childId}/criteria

Example prompt

Which acceptance criteria on the operating model are still unmet?

Arguments

atlas_delivery_engagements_deliverable_reviews_list

List the reviews of a deliverable, one per gate, with their reviewer and outcome.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/deliverables/{childId}/reviews

Example prompt

Which reviews has the operating model been through?

Arguments

atlas_delivery_engagements_deliverable_reviews_request

Request a review of a deliverable at a gate, for example quality review or legal review. Returns the review.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/deliverables/{childId}/reviews

Example prompt

Request a quality review of the operating model from Priya.

Arguments

atlas_delivery_engagements_deliverable_versions_capture

Record a new version of a deliverable, with what changed and the file it lives in. Returns the version.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/deliverables/{childId}/versions

Example prompt

Record version two of the operating model with this change log.

Arguments

atlas_delivery_engagements_deliverables_create

Add a deliverable to an engagement, with its due date, owner, review tier and acceptance criteria. Returns the new deliverable.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/deliverables

Example prompt

Add the target operating model as a contractual deliverable due in May.

Arguments

atlas_delivery_engagements_deliverables_get

Read one deliverable with its stage, versions, reviews, criteria and sign-off.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/deliverables/{childId}

Example prompt

Show me the target operating model deliverable.

Arguments

atlas_delivery_engagements_deliverables_list

Read the deliverable register for one engagement: what the firm owes the client, and which review gate each piece is sitting at. Use this to answer "what is late" or "what is waiting on the client".

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/deliverables

Example prompt

What deliverables are late on Northwind?

Arguments

atlas_delivery_engagements_differences_of_opinion_list

List the differences of opinion on an engagement, resolved ones included: the nature of each, the escalation path used, the resolution and any dissent recorded.

Scope

delivery:read

Calls

GET /v1/engagements/{engagementId}/differences-of-opinion

Example prompt

Are there any open differences of opinion on the Acme audit?

Arguments

atlas_delivery_engagements_differences_of_opinion_record

Record a difference of opinion on an engagement, with its nature and the escalation path used. An open difference holds the report date until a person resolves it. Returns the record.

Scope

delivery:write

Calls

POST /v1/engagements/{engagementId}/differences-of-opinion

Example prompt

Record a difference of opinion on the revenue recognition judgment, escalated to the technical panel.