Implemented in Core
Documented models, workflows, customer APIs, billing framework and audit records.
ALTAPOST LAB / ENGINEERING NOTES
A practical guide to the parcel lifecycle, the decisions behind it and the boundaries of AltaPost Core.
Conceptual architecture · not a live system monitor
CHOOSE YOUR STARTING POINT
Start with an operational question. Follow it to the domain, the architectural decision or the integration boundary.
Understand what the current state means—and who needs to act next.
See how workspaces and external providers meet at the Core.
Inspect the access conventions and a deliberately small public fixture.
FOLLOW THE DECISION
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.
Receiving links the parcel to its expected record.
A missing value becomes an operator-owned task.
The reviewed result carries forward with the package.
Customer and pre-alert associated.
package.status = receivedDeclared item value is missing.
next_action = operator_reviewReviewed information and outcome stay linked.
Explanatory sequence, not an exported audit log.
READ THE EVIDENCE CLEARLY
Use these labels to evaluate what the public material can—and cannot—establish.
Documented models, workflows, customer APIs, billing framework and audit records.
Fictional browser examples and sanitized fixtures, with no live customer or warehouse data.
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
Bring one handoff, the people involved and the information that keeps going missing. Start there.
Local brief · No account required