Settings

Organization org_logpac_demo · LogPac Operations

Team & roles

Who is in this organization and what they may do. Verifying a sender and enabling autonomy are held apart from ordinary administration on purpose.

Intents

What the agent recognises an email as, including the intents your organization defines. New intents start collaborative and arrive with their own templates.

Email

§22, §59

Connected mailbox●operations@logpac-demo.comDemo fixture — not a real mailbox

Provider●noneMicrosoft Graph and Gmail adapters are Phase 3 (§104)

Sync status●not connected

Can send●noThe pipeline decides; it cannot deliver. Nothing leaves this system.

Connecting a mailbox is onboarding steps 2–3 (§87): authorize the provider over OAuth, then designate which shared inbox the agent watches. §22 lists the scopes the adapter will need — read messages, threads and attachments; create drafts; reply, reply-all, forward and send; and preserve message and conversation ids so replies thread correctly (§52).

TMS

§7, §8

Adapter●mockMockTMSAdapter — §88 fixtures, no live tenant

Environment●sandbox

Shipwell adapter●written, unvalidatedsrc/logstat/adapters/tms/shipwell.ts — needs a sandbox token

Access●read-onlyNo write method is implemented (§8)

Automation

§38, §39, §69

Global mode●COLLABORATIVE§69 — every organization starts collaborative

Autonomy-eligible intents13SHIPMENT_STATUS, ETA_REQUEST, TRACKING_REQUEST, PICKUP_STATUS, DELIVERY_STATUS, APPOINTMENT_REQUEST, POD_REQUEST, BOL_REQUEST, SHIPMENT_NOT_FOUND, DOCUMENT_NOT_FOUND, DOCUMENT_SUBMISSION, ACKNOWLEDGEMENT, NO_BUSINESS_INTENT

Human-only intents4CLAIM_REQUEST, RECORD_UPDATE_REQUEST, UNKNOWN, UNINTELLIGIBLE

Document threshold0.98POD and BOL carry a higher bar than status — documents leave the building

Mode is never a single switch. §38 resolves it as global mode ∧ intent policy ∧ confidence ∧ security requirements, and any term can veto. §39 keeps four confidence scores rather than one, because a 99% intent read means nothing if the shipment match is 94% — and averaging the two would hide exactly that.

Language

§27, §28, §66

Default languageenCanonical templates are English; translation happens after render

Response policySAME_AS_INCOMING§66 precedence: explicit setting › contact preference › organization › English

Translation●unavailableNo credentials — non-English items escalate rather than replying in English

§65 forbids translating load, PO, BOL and PRO numbers, addresses, company and carrier names. The translator does not merely request this — it checks the identifiers survived and fails the translation if any went missing.

Security

§40, §41, §42

Sender verification●required for autonomy§40 — no verified sender, no autonomous disclosure

Domain-only match●never authorizesA known domain with an unknown person is refused

Shipment ownership●enforcedA verified contact cannot read another customer's load

Financial data●not granted by defaultRates, invoices and contracts need an explicit grant (§12)

Freshness

§79

customer contact24h

shipment status15m

eta5m

appointment15m

document metadata1h

historical shipment24h

Data older than its budget is STALE, which withholds the autonomous send. §5: the system must never silently assume stale data is current.

Classifier

§29, §45, §100

Model●heuristic fallback

Confidence ceiling0.85Below every autonomy threshold in §38 — the heuristic can draft, never send

§45 bounds what the model is trusted with: language, intent, entities and ambiguity. It is never authoritative for shipment status, ETA, identity, authorization, pricing or whether a document exists — those come from the TMS and the policy engine.