Glossary

Quick reference for Aptli-specific terms used throughout the platform and this guide.

Data & Records

Versioned model

Records that go through a draft → diff → commit cycle before changes become permanent. Versioned records support offline editing, undo/redo, conflict detection, and a full version history. In Aptli, map features (points, linestrings, polygons, layers, schematics) and jobs use the versioned model.

Contrast with: Real-time model

Real-time model

Records that save immediately to the server with no staging step. Changes are visible to all users instantly. Work orders, reports, validations, transactions, and sites use the real-time model.

Contrast with: Versioned model

Draft

A set of local changes to versioned records that have not yet been committed to the server. Drafts are stored in the browser and persist across page refreshes without network access. A user can have one active draft per version. Drafts can be uploaded to the server for admin review before going live.

Commit

The act of applying a draft's changes permanently to the live dataset. Commits create a new immutable entry in the version history. Only users with the allowCommits admin right can commit.

Version conflict

Occurs when two users have edited the same feature in separate offline drafts. Aptli detects conflicts on commit by comparing the base version each draft was built from against the current live version. Conflicting commits are flagged for admin review and cannot be applied until resolved — no silent overwrites.

Inventory

Resource

A definition of a material, consumable, equipment type, or labor category. Resources define their units of measure and pickup policy, and are what a job consumes. The work performed on resources is catalogued separately as an activity. Examples: 500 m fiber cable, concrete anchor bolt, installation crew hour.

Activity

A definition of a type of work a crew performs — splicing, pulling cable, excavating, inspecting. Activities are the work-side sibling of resources: a standalone registry with its own units of measure (§193), referenced by a work order's activity line, either picked from the catalogue or entered ad-hoc. Optional — a work order need not name one. Examples: fusion splice, pull fibre (m), directional bore (m). Managed under administration → Activities (activitiesCreate / activitiesUpdate / activitiesDelete).

Stock Item

The current balance of a specific resource at a specific site. Stock items are updated exclusively by transactions — they are never edited directly. A resource can have stock items at multiple sites simultaneously.

Site

A physical or logical location that holds inventory. Sites include warehouses, storage yards, field depots, individual worker "personal sites," and vehicles. Each user can have a personal site that receives inventory from QR pickup scans.

Transaction

An immutable ledger entry recording every inventory movement. Transactions cannot be edited or deleted — corrections are always made by creating a new adjustment transaction. Transaction types:

Pickup Code

A time-limited, tamper-resistant QR code issued when a work order is assigned. Field workers scan the pickup code at a warehouse to authorize and receive their allocated materials. Pickup codes encode the authorized resource quantities, the assignment they belong to, and an expiry time. Only the assigned worker — or a user with the canFacilitatePickups right — can scan them.

Transfer Code

A tamper-resistant QR code that authorizes a peer-to-peer stock transfer between sites. Unlike pickup codes, transfer codes are not tied to a work order. They can be generated for any site-to-site movement and scanned by the recipient to execute the transfer and record the transaction automatically.

Holding Resource

A temporary "staging" designation used when receiving a shipment containing items that don't yet exist in the resource catalog. Field staff accept the shipment into the holding resource so work isn't blocked; office staff later reclassify the stock to a proper resource once it's defined. Prevents the "I can't receive this because it's not in the system" dead-end.

Pickup Policy

The single control-level setting on a resource that governs who may dispense or pick it up, in every flow (job pickup, self-checkout, transfer). One of three values:

Facilitated Pickup

The behaviour of a resource whose pickup policy is set to facilitated. A worker cannot self-dispense it; instead warehouse staff (a holder of the canFacilitatePickups right) perform the pickup on the worker's behalf while the worker is present. The transaction records both parties and which scan method was used.

Work Fulfillment

Job

A geospatially-located unit of planned work with optional resource requirements. Jobs are versioned — they go through draft → commit like map features. A job can be located at a point (a manhole), a linestring (a road segment), a polygon (a subdivision), or left unlocated for office work. Jobs belong to projects and are fulfilled through work orders; the work performed is captured on the work order's activity line.

Work Order

An allocation of a job to a team, with a due date, an optional activity line (the work to perform), and an optional pickup code for materials. Work orders track status (pending → in-progress → completed) in real time. Also referred to as an assignment.

Assignment

Used interchangeably with Work Order throughout Aptli. Some UI surfaces still label the concept "assignment," but the underlying record and its admin rights are named work order (workOrdersCreate, workOrdersUpdate, workOrdersDelete). They refer to the same thing.

Report

A field worker's record of completed work. Reports capture what was done, GPS location, resources actually consumed, and photos. Reports can be submitted against a formal job or ad-hoc for unplanned maintenance. Submitting a report triggers automatic stock deductions and notifies supervisors.

Validation

A supervisor's QA review of a submitted report. Validations record the outcome (pass / fail / needs-revision / approved-with-notes) and any findings. A failed or needs-revision validation returns the report to the worker; an approved validation can trigger payment release calculations.

Project

A group of related jobs sharing a due date and team assignment. Projects provide a high-level progress view across all their jobs and reports.

Security & Access

Admin Rights

Permissive grants that control what a user can do. Aptli provides granular admin rights covering every create, read, update, and delete action in the system. Examples: workOrdersCreate, reportsDelete, allowCommits, canFacilitatePickups, auditView. Admin rights are additive — a user with no rights can only read their own assignments.

Role Restriction

Restrictive field-level filters that control what data a user cannot see. Role restrictions are enforced server-side: unauthorized data is never sent to the client, not merely hidden in the UI. Example: a restriction on assignedTo = currentUser limits a contractor to seeing only their own work orders. Role restrictions and admin rights operate as two independent layers.

Access Request

A pending account created when someone self-registers through the login page. Access requests wait in Admin → Access Requests until an administrator approves or declines them. On approval the account becomes a regular user; on decline the request is soft-deleted.

Single Active Session

Aptli's session model permits one active sign-in per account across all devices at any time. Signing in on a new device ends the previous session; the evicted device sees a one-time notice and is returned to the login page. Two tabs in the same browser profile share a session and do not evict each other.

Hard Lock

An account state that prevents sign-in via any method. Triggered automatically after repeated failed login attempts (default: 10 consecutive failures) or set manually by an administrator. Cleared only by an admin with the usersUpdate right.

Maintenance Mode

An administrator-toggled mode that blocks non-admin writes and shows a banner to all users. Intended for brief windows when a migration or batch job is running and user writes would interleave with operational work. Administrators retain full access.

Audit Log

An append-only record of meaningful actions across the deployment — logins, record creates and edits, file uploads, status transitions, admin-rights grants. Visible per-record in the embedded timeline on detail pages, and globally at Admin → Audit History (requires auditView). Exportable as CSV for external review (requires auditExport).

Archived (soft-deleted)

A record marked deleted but physically retained. Archived records are hidden from normal lists and queries; users with the viewDeleted right can reveal them and undelete if needed. Aptli rarely hard-deletes — archival preserves audit and operational history.

Map & GIS

Layer

A named collection of map features sharing a geometry type (points, linestrings, or polygons) and a visual style (icon, color, line weight). Layers define what a feature is — for example, a "Telephone Poles" layer or a "Duct Routes" layer. Layers are versioned.

Schematic

A relationship diagram that models connections between map features or abstract objects. Schematics use a graph editor (nodes and directed edges) to represent network topology, cable paths, conduit fill, or any other relationship that is difficult to express on a geographic map alone. Schematics are versioned.

Draw Staging

A temporary editing area where geometry is drawn and refined before being committed to permanent map features. Draw staging allows complex edits — freehand drawing, snapping, multi-feature operations — to be reviewed before they go live.

Field Records

The name of the map surface in Aptli's navigation — where geographic features live and are drawn, edited, and traced. (The map's tools open as windows from its toolbar.)

Window

A floating, draggable panel opened from the map toolbar. Each window toggles a tool: Selected Features, Search, Data Transfer, and Layer Manager are always present; Projects, Layer Relationships, and Builder appear when their feature is licensed. A window can be popped out into a separate browser window for multi-monitor work.

Execution Lens

A map overlay that recolours existing features by their derived work status, so an area's state is readable at a glance. Several can be active at once. Lenses include Progress, My work orders, Needs validation, Failing, Validated, Needs revision, Approved with notes, and Unassigned. Turned on from Layer Manager → Overlays.

Presence Lens

A companion to execution lenses that highlights features carrying a particular kind of attached record: Has job, Has schematic, Has site.

Universal Search

The app-wide command palette, opened with Cmd/Ctrl-K from any page. Searches your records across the app and jumps you to a result. Distinct from the map's Search window, which finds features and flies to them.

Working from Device

The read-source switch (formerly "Offline Mode") that makes list pages and the map serve from a local device copy instead of the live server, so you can keep working without a connection. Paired with Auto save to device (the local-write cadence) and the Version Manager. See Version Management.

Automations & Monitoring

Hook

A signed outbound destination subscribed to the events you choose: give it a URL and a signing secret, and every matching event is POSTed there. The simplest outbound integration. See Automations & Monitoring.

Event Trigger

An automation rule following a trigger → conditions → actions model — when an event fires and the conditions pass, one or more actions run (notify, create a work order, call a webhook, write to Postgres, and more).

Ingest Connector

An external data source that feeds sensor/device readings into Aptli — either pull (Aptli polls a vendor API on a schedule) or push (the sender POSTs to a connector endpoint using an ingest API key).

Station

A map feature that a sensor reports against. Once readings arrive, the feature's record shows each metric's latest value and a 7-day sparkline.

Alarm

A record raised when a monitored reading crosses a threshold (with hysteresis, so it doesn't flap) or when a source goes silent (dead-sensor detection). Alarms move through Active → Acknowledged → Resolved, notify recipients, and can escalate to a second tier if not acknowledged in time.

Outcome

On a project, a chart of monitored metric series against completed-work milestones — readings shown alongside the work that may have influenced them (correlation for context, not a causal claim). Can be published as a read-only, revocable share link.

Connection Allowance

The commercial meter for automations: each ingest connector, API key, and reusable hook consumes one unit from a shared pool (internal event-trigger rules are unmetered). Automations itself is included in every plan.

Public Intake (Service Portal)

Submission

A record created when a member of the public files a request through a public service portal — no login required. Carries a public reference number, optional geometry, and attachments. Staff triage it and can convert it into a work order, report, or map feature.

Reference Number

The short, shareable code a submitter receives. It carries no internal identifiers and is the durable way to track or reply to a submission — and, on the submitter's device, to list all of their submissions ("My submissions").

Forward for Follow-up

Handing a submission to an external system as an honest one-way hand-off, carrying a single-use, expiring callback link so the external system can post its result back once. Does not change the submission's status; shows as Forwarded → Awaiting response → Responded (or Expired / Revoked).

Reply-to-act

Dispatching a work order by email or SMS so the recipient can file the completion report by replying to the message — no login. The reply links are single-use and expire.

Collaboration & Sustainability

Multiplayer Session

A live, real-time co-editing session (the co-design add-on) keyed by a 6-digit code: two or more people edit the same map or record together with visible cursors, and the host commits the agreed result to the mainline. See Multiplayer.

Commission Asset / Emission Profile

The Carbon add-on affordance (on a map feature's record) that attaches an emission profile — linking the feature to what it consumes at some rate — so its greenhouse-gas footprint is tracked against standard emission factors. See Carbon.

Rate-load Chip

A small in-app meter showing how close you are to the request-rate limit — amber as you approach it, red at the ceiling, with a "Catching up…" state when the app is deliberately pacing requests. Informational; it protects responsiveness under heavy use.