Navan Offline-First CI Contract

Overview

Gate Navan integration changes with deterministic fixtures and an isolated optional live smoke. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Required pull-request checks must not depend on a Navan tenant, credentials, paid services, or private traveler data. A live smoke belongs only in a trusted event with protected secrets and a fixed read-only budget.

Authentication

Run required jobs without Navan secrets and deny network access. Resolve a non-production credential only inside the separately approved live environment; never expose it to fork code.

Instructions

1. Enumerate contract, mapping, privacy, and side-effect regressions.
2. Add sanitized fixtures for each enabled surface and failure class.
3. Require schema, mapping, redaction, reconciliation, and rollback tests.
4. Deny sockets and assert no secret is available in ordinary jobs.
5. Define an optional trusted live smoke with one bounded read and no retry.
6. Publish content-free receipts and preserve artifacts without sensitive payloads.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Protected secrets, network, live tenant reads, fixture refreshes, and required-check changes need explicit repository and data-owner approval.

Error Handling

• A skipped required test is not a pass.
• Never combine untrusted checkout with privileged pull-request secrets.
• Do not snapshot a live traveler response into CI.

Output

Return job names, trust matrix, fixture coverage, network policy, live budget, artifact policy, and rollback. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Run booking schema fixtures on every pull request.
• Schedule one synthetic non-production metadata read after merge.

Validation

Test fork PRs, missing secrets, attempted network, malformed fixtures, vendor outage, and artifact scanning. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Contract Failure Triage

Overview

Triage Navan integration failures without exposing travel or payment data or applying blind retries. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Classify failures by layer: local configuration, identity, tenant enablement, contract/schema, transport, vendor availability, destination, or reconciliation. Status codes alone do not establish safe retry behavior.

Authentication

Never ask for or reproduce credentials. Confirm only secret presence, source, age, scope label, target host, and last rotation using content-free evidence.

Instructions

1. Freeze retries and preserve the first sanitized failure receipt.
2. Identify tenant, environment, surface, operation, and contract revision.
3. Check configuration and identity metadata without printing values.
4. Compare request and response envelopes against fixtures using redacted structure only.
5. Check Navan status and destination health before attributing cause.
6. Select retry, reconcile, credential rotation, contract update, or escalation with an owner.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Replays, secret rotation, backfills, file retransmission, traveler-data inspection, and write retries require explicit approval and an impact bound.

Error Handling

• Do not retry a possibly accepted write without idempotency evidence.
• HTML or a login page means wrong contract or authentication path.
• Redact names, emails, itineraries, payment data, receipts, and tokens from support bundles.

Output

Return failure layer, evidence timeline, affected window, retry safety, data exposure check, owner, and next action. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Distinguish expired transfer credentials from a changed file schema.
• Pause a destination load after a Navan read succeeded but acknowledgement failed.

Validation

Reproduce only with approved synthetic data and prove both safe-retry and unknown-outcome paths. Record expected and observed results, including fail-closed behavior.

Reso…

Navan Booking Data Ingestion

Overview

Implement a governed downstream booking-data workflow from Navan into an approved system. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan publicly describes its Booking API as a way for downstream systems to access booking data. Endpoint shape, booking lifecycle states, pagination, correction behavior, and delivery cadence must come from the tenant documentation.

Authentication

Use a dedicated read-only integration identity or transfer credential scoped to booking data. Traveler itinerary data is personal information and must remain within the approved destination and retention boundary.

Instructions

1. Define the booking fields and business decisions the destination actually needs.
2. Capture the source schema, identifiers, timestamps, lifecycle states, and correction semantics.
3. Land immutable raw evidence in an access-controlled staging area.
4. Normalize time zones, currencies, traveler references, and status without losing source values.
5. Upsert or append according to documented semantics and quarantine conflicts.
6. Reconcile counts, sums, late changes, deletions, and destination acknowledgements.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Require data-owner approval for itinerary access, new destinations, backfills, retention changes, or any operation that could modify a Navan booking.

Error Handling

• Never treat a missing page as an empty successful dataset.
• Quarantine unknown lifecycle states instead of coercing them.
• Freeze publication when reconciliation exceeds the agreed threshold.

Output

Return source revision, extraction window, rows read/landed/rejected, reconciliation deltas, sensitive-field handling, and next checkpoint. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Reconcile yesterday's booking changes into a duty-of-care warehouse.
• Backfill a bounded period after a destination outage.

Validation

Exercise empty windows, duplicate delivery, late correction, cancellation, partial page, currency variance…

Navan Expense Data Reconciliation

Overview

Implement reconciliation of contracted Navan expense data with an ERP or finance control plane. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan publicly confirms an Expense API for custom ERP systems and direct accounting integrations. Transaction, receipt, reimbursement, approval, and settlement schemas are tenant-specific and must not be guessed from marketing pages.

Authentication

Separate read-only reconciliation access from any approval, reimbursement, card, or accounting write capability. Limit downstream access to finance roles with an explicit business purpose.

Instructions

1. Define the accounting period, entities, currencies, and source record classes.
2. Capture documented identifiers, amount semantics, lifecycle timestamps, and correction behavior.
3. Land source records and evidence hashes without exposing receipt contents in logs.
4. Map accounts, cost centers, tax, projects, and currencies through versioned rules.
5. Reconcile totals and record-level lineage before posting or export.
6. Route exceptions to a human queue and publish only after finance approval.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Any posting, approval, reimbursement, card action, policy change, or release of receipt data requires explicit authorized-human approval.

Error Handling

• Do not convert currency without a named rate source and effective time.
• Never infer approval from the presence of a transaction.
• Stop when entity, period, or total controls do not reconcile.

Output

Return the period, entity matrix, source and ledger totals, exception classes, lineage receipt, and approval state. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Reconcile approved expense data to a staging ledger.
• Quarantine a transaction whose currency or entity mapping is missing.

Validation

Test duplicates, reversals, partial reimbursements, late receipts, multi-currency records, closed periods, and denied posting approval. Record expected and observed results,…

Navan T&E Cost Control

Overview

Analyze Navan travel, expense, integration, and operating costs without freezing mutable prices. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan publicly describes policy controls, real-time spend visibility, analytics, travel, expense, and enterprise offerings. Actual fees, savings definitions, program terms, and tenant entitlements come from the current agreement and account.

Authentication

Use read-only reporting access for analysis. Policy, card, reimbursement, booking, contract, or budget changes remain separate privileged actions.

Instructions

1. Define the business period, entities, currencies, and decision owner.
2. Separate vendor fees, travel spend, expense spend, payment costs, integration operations, and exception handling.
3. Capture current agreement terms and account reports as dated evidence.
4. Normalize currencies and distinguish forecast, authorized, booked, incurred, reimbursed, and settled amounts.
5. Model savings options with traveler impact, control risk, and implementation cost.
6. Approve changes separately and measure realized outcomes against the baseline.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Pricing negotiations, policy changes, booking restrictions, card controls, reimbursement rules, or production architecture changes require authorized owners.

Error Handling

• Do not treat marketing savings claims as tenant results.
• Never mix booked, incurred, and settled amounts.
• A cheaper control that harms duty of care or compliance is not an optimization.

Output

Return the cost model, evidence dates, currency method, options, risks, approvals, and measurement plan. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Compare integration operating cost with manual exception handling.
• Measure policy changes using approved aggregate analytics.

Validation

Reconcile totals to authoritative reports and test currency, cancellations, refunds, late charges, and incomplete periods. Record expected and observed results, inc…

Navan Travel and Expense Data Governance

Overview

Manage Navan personal, corporate, travel, payment, receipt, profile, and location data across integrations. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan's privacy policy distinguishes Corporate Customer Data from other information and names itinerary, profile, passport, loyalty, payment, receipt, location, support, and usage data. Corporate customers remain responsible for lawful instructions and user rights where they act as controller.

Authentication

Restrict access by purpose, role, tenant, environment, and data class. Third-party AI or MCP connections can process Navan personal information and therefore require an explicit approved boundary.

Instructions

1. Inventory fields from source through every processor, store, artifact, and human workflow.
2. Classify controller/processor role, purpose, legal basis, jurisdiction, and sensitivity with counsel or privacy owner.
3. Minimize collection and separate business travel from personal travel information.
4. Set retention, deletion, access, portability, correction, and incident procedures.
5. Redact logs, fixtures, prompts, analytics, support bundles, and test artifacts.
6. Verify downstream contracts, access reviews, deletion propagation, and evidence.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

New purposes, processors, AI/MCP use, cross-border transfers, sensitive fields, longer retention, or external sharing require data-owner and privacy approval.

Error Handling

• Do not assume employer access to personal travel data.
• Opaque identifiers can still be personal data when linkable.
• Deletion requests need downstream and backup handling, not only source deletion.

Output

Return a data inventory, role/purpose matrix, minimization decisions, retention schedule, rights workflow, and control evidence. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Exclude passport and loyalty data from an analytics feed.
• Review whether a support assistant may receive itinerary details.

Valida…

Navan Multi-Surface Data Synchronization

Overview

Synchronize Navan booking, expense, identity, and file-delivered data according to each documented source contract. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Do not assume bookings are weekly full refreshes, transactions are append-only, or generic webhooks exist. Record snapshot, incremental, correction, deletion, ordering, and delivery semantics independently for every enabled API, file, or managed integration.

Authentication

Use distinct read identities or transfer credentials per surface and tenant. Keep destination write credentials separate from Navan access and from any privileged write-back identity.

Instructions

1. Build a surface ledger with contract revision, keys, timestamps, cadence, and correction semantics.
2. Capture a durable source checkpoint without advancing it before destination acknowledgement.
3. Land immutable raw records with hashes and sensitivity controls.
4. Normalize through versioned mappings while preserving source lineage.
5. Apply idempotent destination writes and quarantine unknown or conflicting records.
6. Reconcile source windows, destination acknowledgements, totals, late changes, and deletion obligations.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Backfills, new surfaces, historical access, file retransmission, destination changes, checkpoint resets, and write-back require explicit approval.

Error Handling

• Never compare opaque IDs lexicographically as a time watermark unless documented.
• Do not advance a checkpoint after a partial load.
• Freeze on unexplained source-to-destination drift.

Output

Return the surface ledger, checkpoints, rows and hashes by stage, reconciliation deltas, quarantine, and recovery plan. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Synchronize booking and expense feeds with independent checkpoints.
• Recover a missed file window without duplicating accepted records.

Validation

Test snapshot, incremental, duplicate, late correction, deletion, partial page/…

Navan Sanitized Support Bundle

Overview

Assemble a content-free Navan integration support bundle for operators or vendor escalation. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

A useful bundle proves configuration shape, contract revision, timing, counts, checksums, and failure class without containing credentials, traveler identity, itinerary, payment, receipt, or free-text content.

Authentication

Record credential source, age band, and scope label only. Never include tokens, client secrets, cookies, file-transfer keys, authorization headers, or raw identity responses.

Instructions

1. Define the incident window and minimum evidence questions.
2. Collect version, tenant alias, environment, surface, operation, and contract revision.
3. Add redacted request/response schemas, counts, timings, status class, and correlation identifiers.
4. Hash artifacts and scan them for credentials and sensitive fields.
5. Generate a manifest showing every included and excluded item.
6. Require review before transmitting the bundle outside the approved boundary.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Reading local sanitized evidence is allowed; collecting live data or sending any bundle to Navan or another party requires data-owner and incident-owner approval.

Error Handling

• Do not solve redaction by replacing only obvious email addresses.
• Free-text support fields can contain passports, receipts, or itineraries.
• If sensitivity cannot be established, keep the artifact local and escalate.

Output

Return a bundle manifest, checksums, redaction report, evidence gaps, intended recipient, and approval record. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Share a schema mismatch with field names but no values.
• Prove repeated transfer failures using timestamps and content hashes.

Validation

Run secret, personal-data, archive-path, and recipient-boundary checks before release. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Integration Deployment

Overview

Deploy a Navan integration with tenant isolation, canary controls, and reversible data flow. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Deployment binds the application adapter to a documented Navan surface and an approved destination. Separate ingestion, normalization, publication, and write-back so each can stop without losing evidence.

Authentication

Inject a production secret by reference at runtime; bind tenant, host, scope, destination, and environment. Verify revocation and break-glass procedures before traffic.

Instructions

1. Pin the reviewed artifact, contract revision, and configuration manifest.
2. Deploy dark with network or scheduling disabled.
3. Verify secret binding, egress allowlist, storage, redaction, and alert routing.
4. Enable a bounded tenant/window canary and collect reconciliation evidence.
5. Increase scope only after thresholds and owner review pass.
6. Keep rollback, replay protection, checkpoints, and raw evidence until acceptance.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Production enablement, egress, data movement, scheduling, scope expansion, and write-back require explicit service and data-owner approval.

Error Handling

• Stop on tenant or destination mismatch.
• Do not roll forward through unexplained count or total drift.
• Rollback must preserve the ability to reconcile ambiguous deliveries.

Output

Return artifact and contract IDs, canary scope, controls, metrics, reconciliation, approvals, and rollback receipt. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Dark-deploy a booking ingestion worker before scheduling it.
• Canary one legal entity for an expense export.

Validation

Exercise disabled mode, revoked secret, egress denial, partial delivery, process restart, and rollback. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Enterprise Access Governance

Overview

Map Navan account roles and integration privileges to application-owned enterprise controls. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Public integration listings confirm identity and user-management options, but exact Navan roles and entitlements are account-specific. Capture them from the current tenant and never invent universal role names or assignment APIs.

Authentication

Separate human login, organization administration, provisioning, data ingestion, finance reconciliation, write-back, and support access. Bind automation identities to one purpose and tenant.

Instructions

1. Inventory human roles, groups, integration identities, and current privileges.
2. Map each business action and data class to least-privilege access.
3. Document SSO, SCIM, HRIS, manual, and break-glass authority paths.
4. Identify toxic combinations across booking, expense, payment, approval, and export.
5. Define joiner, mover, leaver, periodic review, and emergency revocation controls.
6. Test denied paths and reconcile Navan assignments with the enterprise source of authority.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Admin grants, provisioning changes, finance or payment privileges, break-glass use, service identities, and cross-tenant access require named approvers.

Error Handling

• A corporate title is not proof of a Navan entitlement.
• Do not let the same automation approve and reconcile its own writes.
• Fail closed when the identity source and Navan assignment disagree.

Output

Return a role-action-data matrix, identity sources, toxic combinations, review cadence, revocation path, and unresolved tenant facts. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Separate expense review from ERP posting.
• Reconcile a SCIM-managed user with a manually granted admin entitlement.

Validation

Test joiner, mover, leaver, dormant account, revoked service identity, break-glass expiry, and tenant isolation. Record expected and observed results, including fail-…

Navan Workforce and Organization Lifecycle

Overview

Govern workforce, organization, and access lifecycle changes across Navan and enterprise identity sources. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan publicly lists HRIS integrations, HR-SFTP, Okta SCIM, SSO, OpenID Connect, SAML, and user-management integrations. Exact attributes, roles, group rules, activation states, and deprovision behavior are tenant-specific.

Authentication

Provisioning identities are privileged and must be separate from ordinary data-read integrations. Bind one identity source as authority and document manual exceptions.

Instructions

1. Inventory authoritative people, employment, organization, and access attributes.
2. Map identifiers and lifecycle states without using email alone as an immutable key.
3. Define joiner, mover, leave, rehire, guest, contractor, and exception behavior.
4. Stage changes and review role, policy, manager, entity, and traveler-impact deltas.
5. Apply only through the enabled integration and record acknowledgements.
6. Reconcile source authority, Navan state, downstream systems, and manual grants.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Privileged role grants, bulk changes, authority-source changes, reactivation, manual exceptions, and destructive deprovisioning require explicit approval.

Error Handling

• Do not delete or disable on an ambiguous identity match.
• Preserve legal and financial records while removing access.
• A provisioning success response still requires state reconciliation.

Output

Return identity mappings, proposed changes, approvals, acknowledgements, exceptions, and reconciliation results. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Offboard access while preserving required expense records.
• Reconcile a mover whose department changed but email did not.

Validation

Test duplicate names, email change, rehire, manager cycle, terminated admin, manual grant, partial bulk failure, and rollback. Record expected and observed results, including fail-c…

Navan Read-Only Connectivity Proof

Overview

Prove one contracted Navan integration can authenticate and return a bounded read-only response without inventing a universal API. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

The public site confirms downstream Booking API access and an Expense API for custom ERP integrations, but it does not publish a universal route or response schema. The selected tenant's current contract is the only execution authority.

Authentication

Resolve the approved non-production credential at runtime and bind it only to the documented host. Redact headers, query values, traveler identities, booking details, and expense data from evidence.

Instructions

1. Select the smallest documented read operation for the enabled surface.
2. Copy its method, host, path, parameters, and response schema into a dated local contract fixture.
3. Set a short timeout, response-size bound, and zero automatic retries.
4. Run only after network and data-access approval is explicit.
5. Validate status, content type, required fields, pagination envelope, and redaction.
6. Store a content-free receipt and revoke temporary credentials when required.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Network access, a real credential, and any response containing traveler or expense information require explicit approval; no write or booking action belongs in this proof.

Error Handling

• Treat redirects or HTML as contract mismatch, not success.
• Do not print response bodies on authentication or schema failure.
• Stop on an undocumented host, method, pagination rule, or write effect.

Output

Return the contract revision, operation identifier, bounded result metadata, redaction result, elapsed time, and rollback or revocation status. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Validate a one-record Booking API read defined in the tenant docs.
• Confirm an Expense API metadata response without downloading receipts.

Validation

Re-run with a missing secret, wrong tenant, timeout, oversize…

Navan Integration Incident Command

Overview

Manage containment, reconciliation, and recovery for a Navan integration incident. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

The source of truth spans Navan, the integration, and downstream systems. Recovery is incomplete until credentials, data windows, financial totals, traveler impact, and destination acknowledgements are reconciled.

Authentication

Use break-glass access only under the documented incident process. Never paste tokens or traveler data into chat, tickets, status updates, or unapproved AI tools.

Instructions

1. Declare commander, scope, severity, timeline, and communication boundary.
2. Contain schedules, writes, transfers, credentials, or destinations without erasing evidence.
3. Preserve sanitized logs, checkpoints, schemas, counts, hashes, and approvals.
4. Determine source, destination, traveler, privacy, security, and finance impact.
5. Reconcile the affected window before replay or reopening writes.
6. Recover gradually, monitor, close temporary access, and assign follow-ups.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Credential rotation, replay, backfill, write enablement, customer communication, legal notification, and evidence sharing require the authorized incident roles.

Error Handling

• Containment comes before reproduction.
• Do not replay an unknown-outcome write blindly.
• Vendor status alone does not prove local recovery.

Output

Return incident state, timeline, affected windows, containment, exposure assessment, reconciliation, recovery gates, and owners. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Rotate a suspected transfer key and reconcile missed files.
• Pause expense publication after a tenant-mapping error.

Validation

Tabletop credential leak, personal-data exposure, vendor outage, schema drift, duplicate replay, and destination corruption. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Integration Access Intake

Overview

Establish a Navan integration access contract without guessing endpoints, grants, or scopes. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan publicly confirms Booking API, Expense API, SFTP, direct integrations, SCIM, SAML, and OpenID Connect surfaces. Exact hosts, credentials, scopes, schemas, and enablement are tenant- and contract-specific; copy them from the current in-account source.

Authentication

Record the credential type, issuer, audience or destination, scopes or permissions, expiry, rotation owner, and storage location from the tenant contract. Never infer OAuth client credentials or reuse interactive session cookies.

Instructions

1. Choose one integration surface and its business owner.
2. Capture the current tenant documentation URL, revision date, and access prerequisites.
3. Request least-privilege non-production credentials through the approved secret channel.
4. Create a redacted connection profile with no credential values.
5. Plan one read-only or metadata-only validation allowed by the contract.
6. Record rotation, revocation, escalation, and production-promotion gates.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Require the Navan admin and data owner before credential issuance, scope expansion, production access, SSO/SCIM changes, or any traveler-data read.

Error Handling

• A public product page is not an endpoint contract.
• A login redirect is not proof that an API route exists.
• Missing scope or tenant enablement must fail closed and go to the Navan administrator.

Output

Return an access matrix, evidence links, credential owner, allowed environments, read-only validation, rotation plan, and unresolved tenant questions. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Prepare Expense API access without placing a secret in the repository.
• Document an Okta SCIM handoff while leaving provisioning disabled.

Validation

Verify the evidence date, tenant, credential provenance, least privilege, secret storage, revocat…

Navan Offline Development Loop

Overview

Develop Navan integrations against sanitized contract fixtures with networking denied by default. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Local development should exercise the application-owned contract, not depend on a live tenant. Fixtures must preserve structural edge cases while removing traveler, payment, itinerary, and credential data.

Authentication

Local tests require no Navan credential. An optional live smoke uses a separate non-production secret and must be explicitly enabled outside the normal test command.

Instructions

1. Capture a schema from authorized documentation or a sanitized response.
2. Build minimal success, empty, paginated, corrected, denied, throttled, and malformed fixtures.
3. Validate fixtures against local types and sensitivity rules.
4. Run the adapter with networking blocked and a deterministic clock.
5. Exercise mapping, deduplication, checkpoint, and rollback behavior.
6. Keep live smoke configuration separate, bounded, and disabled by default.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Live tenant access, new fixtures derived from real data, dependency changes, and fixture publication require explicit approval.

Error Handling

• Never commit raw tenant responses.
• A fixture that contains plausible personal data still needs review.
• Fail when an offline test unexpectedly opens a socket.

Output

Return fixture provenance, covered contracts, test results, network-denial evidence, uncovered fields, and optional live-smoke plan. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Model a late booking correction with synthetic identifiers.
• Test an expense reversal without a real receipt.

Validation

Scan fixtures for secrets and personal data, run twice for determinism, and verify a network attempt fails. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Platform Migration Reconciliation

Overview

Migrate travel or expense data flows to Navan with staged cutover and financial and traveler reconciliation. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Migration must reconcile legacy and Navan concepts rather than forcing field-for-field equivalence. Booking lifecycle, traveler profile, policy, card, expense, receipt, currency, approval, and accounting meanings require explicit mapping.

Authentication

Use separate migration identities and time-bound access. Avoid copying legacy secrets, personal data, or administrator privileges into steady-state integration accounts.

Instructions

1. Inventory legacy workflows, data, owners, obligations, integrations, and open items.
2. Capture Navan tenant contracts and map concepts with loss and ambiguity labels.
3. Define historical migration, open-item transition, and future-state interfaces separately.
4. Rehearse with synthetic and approved bounded data.
5. Dual-run or shadow-process a controlled period and reconcile travelers, bookings, expenses, cards, and totals.
6. Cut over with freeze, communication, rollback, legacy retention, and decommission gates.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Historical data movement, traveler communication, policy conversion, card or payment change, production cutover, and legacy deletion require authorized owners.

Error Handling

• Do not manufacture missing legacy meaning.
• Keep unresolved open items visible through cutover.
• No legacy deletion before legal, finance, privacy, and rollback gates close.

Output

Return the concept map, data disposition, dual-run evidence, open-item register, cutover plan, rollback, and decommission record. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Move booking reporting while preserving legacy trip lineage.
• Transition expense reconciliation without duplicating reimbursements.

Validation

Reconcile representative historical, open, cancelled, corrected, refunded, personal, and multi-currency cases. Record exp…

Navan Tenant and Environment Isolation

Overview

Separate Navan development, test, staging, and production identities, data, and destinations. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Not every Navan customer has equivalent sandbox, API, file, or identity surfaces. Record the real environment model from the account, then simulate absent capabilities locally instead of relabeling production as test.

Authentication

Give each available environment and tenant distinct credentials, secret paths, host allowlists, destinations, schedules, and revocation owners. Never select production by default.

Instructions

1. Inventory real tenants and vendor-provided environments.
2. Map each integration surface, identity, destination, and data class.
3. Create fail-closed configuration with explicit tenant and environment labels.
4. Use synthetic fixtures where a vendor sandbox is unavailable.
5. Define promotion evidence without copying secrets or personal data.
6. Test cross-tenant denial, revocation, rollback, and configuration drift.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Creating credentials, enabling a surface, copying data, adding destinations, changing schedules, or promoting to production requires explicit approval.

Error Handling

• A URL suffix is not sufficient environment isolation.
• Never use production traveler data as a test fixture.
• Reject missing or contradictory tenant labels before network access.

Output

Return the environment matrix, configuration contract, secret ownership, data policy, promotion gates, and drift checks. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Use fixtures when Booking API has no sandbox entitlement.
• Block a staging worker configured with a production destination.

Validation

Prove no credential, host, destination, schedule, or artifact crosses the tenant/environment matrix. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Integration Observability

Overview

Observe Navan integrations with content-free signals that support reconciliation and incidents. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Operational signals should identify tenant alias, environment, surface, contract revision, window, stage, counts, timing, status class, and reconciliation state without exposing travel, payment, receipt, credential, or free-text content.

Authentication

Telemetry backends receive no Navan secrets or authorization metadata. Restrict sensitive correlation mappings and raw evidence to the approved incident boundary.

Instructions

1. Define freshness, completeness, correctness, latency, and recovery objectives.
2. Emit structured stage events with bounded labels and content-free identifiers.
3. Measure source reads, accepted records, quarantine, destination acknowledgements, and reconciliation deltas.
4. Alert on stalled checkpoints, repeated denial, contract drift, queue age, and unexplained totals.
5. Link alerts to status checks, runbooks, owners, and evidence locations.
6. Test dashboards and paging with synthetic failures.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

New telemetry processors, raw payload capture, sensitive label expansion, production tracing, and on-call routing changes require approval.

Error Handling

• Do not use traveler email or booking detail as a metric label.
• HTTP success without reconciliation is not pipeline health.
• Suppressions must expire and retain an owner.

Output

Return objectives, event schema, metric and alert catalog, redaction policy, dashboards, owners, and test receipts. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Alert when a booking window is read but not acknowledged downstream.
• Track expense quarantine by reason code without transaction content.

Validation

Inject stale checkpoint, source denial, schema drift, destination failure, reconciliation mismatch, and redaction canaries. Record expected and observed results, including fail-closed behavior.

Navan Pipeline Performance Tuning

Overview

Tune a Navan data pipeline against measured vendor, destination, privacy, and deadline constraints. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Optimize after measuring time in authentication, source wait, transfer, parsing, mapping, destination, and reconciliation. Preserve correctness and sensitive-data controls before increasing pages, batches, concurrency, or cache duration.

Authentication

Benchmark with non-production or approved synthetic data and least-privilege credentials. Do not expose tenant data in profilers, traces, or third-party performance tools.

Instructions

1. Define latency, freshness, throughput, and reconciliation objectives.
2. Measure each stage with content-free timings and counts.
3. Identify the narrowest documented source or destination constraint.
4. Reduce fields, windows, transformations, or round trips before adding concurrency.
5. Tune bounded queues, checkpoints, backpressure, and destination batches.
6. Canary changes and compare correctness, privacy, and cost alongside speed.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Load tests, production traces, cache or retention changes, higher concurrency, new infrastructure, and deadline tradeoffs require approval.

Error Handling

• Do not optimize by dropping reconciliation or redaction.
• A faster partial sync is a failure.
• Roll back when errors, queue age, or unexplained totals worsen.

Output

Return baseline and candidate measurements, bottleneck evidence, chosen controls, correctness deltas, and rollback threshold. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Reduce an oversized extraction window before raising concurrency.
• Batch destination writes while keeping source checkpoints durable.

Validation

Run cold, steady, burst, throttled, destination-slow, restart, and rollback scenarios with identical fixtures. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Production Readiness Gate

Overview

Audit whether a Navan integration is ready for production using evidence and rollback criteria. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Production readiness binds one documented tenant contract to one identity, destination, data purpose, operating window, and rollback plan. A successful sandbox or fixture test is necessary but not sufficient.

Authentication

Confirm production credential provenance, least privilege, rotation, revocation, host binding, break-glass ownership, and separation from non-production.

Instructions

1. Freeze the approved contract revision and change scope.
2. Review security, privacy, retention, accounting, and traveler-impact controls.
3. Prove offline tests, non-production smoke, reconciliation, monitoring, and alert routing.
4. Define canary scope, success thresholds, stop conditions, and rollback owner.
5. Verify runbooks for credential, schema, vendor, destination, and data incidents.
6. Collect named approvals and record the exact release receipt.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Require service, Navan admin, security, data, and finance owners as applicable; no checklist completion can self-authorize production writes or traveler impact.

Error Handling

• A missing owner or rollback signal is a no-go.
• Do not accept aggregate totals without record-level lineage controls.
• Unknown contract drift blocks release.

Output

Return GO, CONDITIONAL GO, or NO-GO with evidence, owners, canary, monitoring, rollback, and expiry of the decision. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Approve a read-only booking feed with a one-day canary.
• Block an expense posting workflow whose reversal path is untested.

Validation

Conduct a tabletop for credential revocation, partial delivery, schema drift, destination outage, and rollback. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Capacity and Backpressure Control

Overview

Configure Navan integration concurrency and retry controls from the tenant contract and observed responses. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

No universal public numeric quota should be frozen into code. Treat account limits, file windows, vendor responses, destination capacity, and business deadlines as dated evidence with independent bounds.

Authentication

Capacity testing uses the least-privilege non-production identity. Never discover limits by flooding a production travel or expense tenant.

Instructions

1. Capture documented limits and escalation contacts for the enabled surface.
2. Classify reads, writes, transfers, and reconciliation work by side-effect risk.
3. Set application concurrency below the narrowest vendor or destination bound.
4. Honor documented retry signals with capped delay, jitter, and deadlines.
5. Checkpoint pages or files durably and reconcile after ambiguous outcomes.
6. Alert on queue age, throttle rate, deadline risk, and sustained capacity loss.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Load tests, quota-change requests, deadline overrides, write retries, and production concurrency increases require explicit approval.

Error Handling

• A numeric limit copied from another tenant is not evidence.
• Do not retry authentication or contract failures as throttling.
• A timed-out write remains unknown until reconciled.

Output

Return documented limits, chosen concurrency, retry classes, queue/deadline model, reconciliation plan, and escalation threshold. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Throttle a backfill behind daily production extraction.
• Pause when destination latency would exhaust the source window.

Validation

Simulate throttling, long delay, destination slowdown, process restart, deadline exhaustion, and unknown write outcome. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Governed Integration Architecture

Overview

Design a Navan integration architecture with explicit trust, data, identity, and accounting boundaries. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

A durable design separates vendor access, intake, immutable staging, normalization, policy, publication, write-back, reconciliation, and audit. It supports the tenant's actual API, SFTP, SCIM, SSO, or direct-integration contracts without assuming one universal transport.

Authentication

Place secrets at the ingress boundary, bind each identity to one tenant and purpose, and keep administrative, ingestion, and write-back privileges separate.

Instructions

1. Inventory Navan surfaces, owners, data classes, consumers, and side effects.
2. Draw trust zones and every network, storage, AI, and human boundary.
3. Define canonical identifiers, money, time, lifecycle, and lineage models.
4. Add queues, checkpoints, deduplication, quarantine, and reconciliation.
5. Specify redaction, retention, encryption, access, deletion, and incident controls.
6. Document scaling, failure, deployment, rollback, and contract-upgrade paths.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

New processors, sensitive destinations, cross-border flows, AI/MCP access, write-back, production identities, and retention changes require architecture and data-owner approval.

Error Handling

• Do not couple acknowledgement to downstream success without durable receipt.
• Avoid a shared credential across tenants or purposes.
• No diagram is complete without failure and reconciliation paths.

Output

Return a component map, data-flow and trust boundaries, identity matrix, control owners, failure paths, and decision log. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Separate booking intake from duty-of-care publication.
• Isolate expense reconciliation from privileged ERP posting.

Validation

Walk success, duplicate, late correction, credential theft, vendor outage, destination outage, data request, and rollback. Record expected …

Navan Contract-Bound Adapter

Overview

Design an application-owned Navan adapter pinned to the tenant's actual integration contract. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Do not assume a public SDK, base URL, pagination model, or error envelope. Preserve the vendor payload at the boundary, then map it into versioned application types backed by captured schemas and fixtures.

Authentication

Accept a secret-provider callback or file-transfer credential reference, never a literal secret. Bind credentials, tenant identity, and host allowlist together so configuration cannot cross environments.

Instructions

1. Inventory the enabled operation or file contract and record its revision.
2. Define transport-neutral input, result, page, and error types.
3. Implement authentication, timeout, size limit, and redacted telemetry at one boundary.
4. Preserve raw identifiers as opaque strings and money with explicit currency.
5. Add fixture tests for success, empty data, pagination, denial, throttling, and drift.
6. Expose writes only as separate methods with idempotency and approval requirements.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Reading docs and fixtures is local; live calls, secrets, package additions, generated clients, file transfers, and state changes need explicit approval.

Error Handling

• Unknown fields should be preserved or quarantined, not silently discarded.
• Do not guess retryability from status alone; follow the current tenant contract.
• Reject tenant/host mismatches before opening a connection.

Output

Return adapter interfaces, contract revision, fixture inventory, redaction policy, retry classification, and unsupported operations. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Wrap a contracted booking export behind an async iterator.
• Map expense money fields into amount-plus-currency values.

Validation

Test offline first, then use one separately approved non-production read to compare the captured schema with reality. Record expected and observed result…

Navan Integration Security Boundary

Overview

Threat-model a Navan integration across identity, travel, expense, payment, file, and downstream systems. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan states that its APIs undergo security testing and that data in transit and sensitive data at rest are encrypted. Those vendor controls do not replace customer-side least privilege, downstream encryption, retention, monitoring, or third-party AI governance.

Authentication

Use dedicated integration identities, scoped access, approved secret storage, host binding, rotation, and revocation. Keep interactive admin and automation credentials separate.

Instructions

1. Draw trust boundaries from Navan through every processor and destination.
2. Classify credentials and traveler, itinerary, payment, receipt, profile, and location data.
3. Minimize fields, purposes, destinations, retention, and human access.
4. Model credential theft, tenant mix-up, injection, replay, exfiltration, and confused-deputy paths.
5. Add deny-by-default network, logging, artifact, and AI-tool policies.
6. Test detection, containment, revocation, reconciliation, and notification paths.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Any new processor, third-party AI or MCP connection, broader scope, production secret, cross-border transfer, or sensitive-data export requires security and data-owner approval.

Error Handling

• Do not put traveler or receipt content in prompts or logs by default.
• Certification badges are not authorization for a new use.
• Fail closed on tenant, host, identity, or destination ambiguity.

Output

Return a data-flow diagram, threat register, control owners, residual risks, approval boundaries, and verification plan. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Review a Booking API feed into a duty-of-care vendor.
• Constrain an MCP assistant to a minimal approved itinerary view.

Validation

Exercise tenant isolation, revoked credentials, malicious fields, log redaction, unauthorized desti…

Navan Contract Upgrade Control

Overview

Upgrade a Navan API, file, identity, or direct-integration contract without silent data loss. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Treat the tenant documentation, delivered schema, and enabled feature set as versioned evidence even when no public semantic version exists. Separate additive drift from breaking field, identity, lifecycle, or delivery changes.

Authentication

Reconfirm scopes, host, credential format, rotation requirements, and environment separation; do not carry forward obsolete credentials merely because old calls still succeed.

Instructions

1. Inventory current operations, fields, mappings, consumers, and controls.
2. Capture old and new contract evidence and classify every delta.
3. Update fixtures and adapters before live traffic.
4. Dual-read or shadow-process a bounded window without duplicate writes.
5. Reconcile records, totals, sensitive fields, and downstream acknowledgements.
6. Cut over with explicit stop conditions and retain a tested rollback window.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Scope changes, new fields, credential replacement, dual-running costs, write cutover, and rollback expiry require named owner approval.

Error Handling

• Do not silently default a newly required field.
• A successful request can still produce a semantically broken mapping.
• Freeze cutover on unexplained reconciliation deltas.

Output

Return a contract delta, consumer impact map, fixture changes, dual-run evidence, cutover plan, and rollback deadline. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Migrate a booking file after a column and status change.
• Rotate an identity integration while proving tenant isolation.

Validation

Replay historical fixtures through both versions and test rollback after a partial cutover. Record expected and observed results, including fail-closed behavior.

Resources

• …

Navan Event Delivery Contract Verification

Overview

Validate and operate the event or change-delivery mechanism actually enabled for a Navan tenant. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Navan's public pages confirm APIs, SFTP, and direct integrations but do not establish a universal webhook endpoint, event taxonomy, or signature header. Use only the tenant's documented delivery mode and keep polling or reconciliation as a recovery path.

Authentication

For callbacks, use the documented verification scheme and secret lifecycle; for polling or files, use the corresponding read-only identity. Never invent a generic vendor-signature header.

Instructions

1. Confirm whether the tenant surface supports callback, poll, file, or managed delivery.
2. Capture event or record identifiers, ordering, duplication, correction, and replay semantics.
3. Authenticate before parsing and enforce body or file size limits.
4. Journal receipt before acknowledgement and deduplicate durably.
5. Process idempotently with quarantine for unknown types or schemas.
6. Reconcile periodically against the source-of-record contract.

Tool Discipline

Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion.

Approval Boundaries

Registering destinations, issuing verification secrets, enabling new event classes, replaying deliveries, or applying state changes requires explicit approval.

Error Handling

• A fast acknowledgement must not precede durable receipt.
• Unknown events go to quarantine, not the default handler.
• A delivery gap requires source reconciliation, not blind replay.

Output

Return delivery-mode evidence, authentication, ordering model, dedupe key, acknowledgement rule, reconciliation cadence, and replay approvals. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

• Choose polling because no callback contract is enabled.
• Reconcile a managed accounting integration after a delivery gap.

Validation

Test invalid authentication, duplicate, out-of-order, unknown schema, crash before acknowledgement, replay, and gap recovery. Record expected an…