Engineering & workflow notes

ALTAPOST LAB / ENGINEERING NOTES

Understand the work.
Then evaluate
the system.

A practical guide to the parcel lifecycle, the decisions behind it and the boundaries of AltaPost Core.

Public technical overviewReviewed 27 Oct 2026
SYSTEM AT A GLANCE01
Operator workspace Customer cabinet
ALTAPOST CORE

One operational record.

Domain actionsPermissionsWorkflow states
Transactional data Queues & audit

Conceptual architecture · not a live system monitor

CHOOSE YOUR STARTING POINT

Three ways into the system.

Start with an operational question. Follow it to the domain, the architectural decision or the integration boundary.

FOLLOW THE DECISION

The exception is part
of the workflow.

A parcel arrives without a declared item value. A useful system needs to preserve the gap, assign the next action and record the reviewed answer.

  1. 01
    Observe

    Receiving links the parcel to its expected record.

  2. 02
    Review

    A missing value becomes an operator-owned task.

  3. 03
    Continue

    The reviewed result carries forward with the package.

Try the browser walkthrough
AP-DEMO-0042 Fictional example

An event with context.

Package received

Customer and pre-alert associated.

package.status = received
Information review required

Declared item value is missing.

next_action = operator_review
Operator decision

Reviewed information and outcome stay linked.

Explanatory sequence, not an exported audit log.

READ THE EVIDENCE CLEARLY

Implementation is one layer.
Deployment is another.

Use these labels to evaluate what the public material can—and cannot—establish.

SOURCE

Implemented in Core

Documented models, workflows, customer APIs, billing framework and audit records.

ILLUSTRATION

Explained on these sites

Fictional browser examples and sanitized fixtures, with no live customer or warehouse data.

IMPLEMENTATION

Reviewed per deployment

Provider configuration, migration, hosting, permissions and operator acceptance.

A working codebase or seeded demonstration does not establish production adoption, revenue or carrier partnerships.

START WITH THE WORK

A real scenario.
A useful technical conversation.

Bring one handoff, the people involved and the information that keeps going missing. Start there.

Local brief · No account required