PNZ’s workflow layer.
Source references, validation rules, saved geometry, interface and review workflow connect the model to the work.
Inside P+Z / storage & operations
Behind your
next move.
From our racks.
To your destination.
Each work considered.
Follow three stored works from a release request in New York to receipt in London, with the records and decisions connected along the way.
AURA / The work, connected64 seconds · silent
Request
A client requests release of three stored works for delivery to London.
AURA / IN USE Connected records · PNZ review
Explore how AURA worksEach work.
Considered.
A release request becomes a physical journey: locate the works, inspect condition, agree the protection, prepare the shipment and verify receipt. AURA connects the records; PNZ reviews and coordinates the work with you.
About this demonstration
This fictional New York-to-London shipment uses PNZ application components and a three-work sample plan rendered with PNZ’s 3D planning components. The storage scene follows PNZ’s saved warehouse spatial model; displayed works, package dimensions, placements and public bay labels are illustrative. The model includes estimated rack envelopes and is not an as-built survey. No actual customer work or stock position is shown. AURA’s responses and the shipment stages are scripted. Rack retrieval, condition inspection and transport handoffs are simplified illustrations, not live tracking or an automated condition scan. The crate view separates artwork, protection and construction layers for inspection; it does not show a fabrication sequence. No actual shipment, customer approval or delivery is represented.
Read the film story
- Request. A fictional client asks PNZ to ship three sample works from New York to London.
- Locate and retrieve. Select Work B from the three works linked to the sample crate plan, then bring it out for review.
- Inspect. AURA brings the selected work and its example condition record together. PNZ inspects physical condition, records photographs and identifies suitable support and contact points.
- Plan and review. Separate the framed face, three works and protection layers of the same sample crate in 3D, then return them to their saved positions. PNZ and the client review protection, scope and estimate before proceeding.
- Prepare and ship. Build to a reviewed plan. Link the crate identification, packing list and transport documents through dispatch, air freight, clearance and delivery.
- Receive. Check condition on arrival, record receipt and update the client. AURA connects the records; PNZ remains responsible for the decisions.
AURA / the system behind the view
A decision.
With a traceable basis.
A client’s words. A saved packing plan. A detail still unresolved. AURA brings them into the same workspace so our team can see what a decision rests on.
THE CONNECTED SYSTEM
One request. A traceable path.
Questions return for review.
02 / INTERPRET
Intelligence with context.
AURA uses the request and permitted source material to help our team interpret the work. PNZ’s tools connect model reasoning to correspondence, records and the saved plan.
- Source material
- Permitted records
- Open questions
- Kept visible
- Final judgment
- PNZ team
Select a stage to inspect it. Motion illustrates the flow of information; it is not a live job, inference trace or automated approval.
OPTIONAL / SOURCE CHECKSee what supports the plan
Try the source check
Would the source
support that?
Choose a passage. See why it can—or cannot—be shown as a quotation.
Client reply / 03
Please plan to pack the works on site. We will send the condition notes and photographs for your review.
Fictional sample correspondencePassage submitted for validation
“Please plan to pack the works on site.”Exact source match
The exact passage is present in this message. It establishes the requested scope; it does not approve protection.
This example runs AURA’s source-quote validator locally on fictional text. It checks passage membership and source eligibility. It does not run a model, measure AI accuracy or establish that a client’s statement is physically correct.
AURA in use.
Production sample responses and usage metering were checked on September 21, 2026. This establishes connectivity, not operational accuracy.
A defined validation scope.
12 deterministic validation checks pass. A measured evaluation on representative PNZ jobs is still needed before publishing an AI accuracy or productivity claim.
TECHNICAL OVERVIEWExplore the architecture
This overview describes PNZ’s internal AURA workspace: PNZ-developed orchestration, retrieval and spatial presentation connected to a provider foundation model. The customer Portal assistant uses a separate model and service configuration.
Permission scopeSource retrievalModel reasoningValidated presentationPNZ judgment
Reasoning, with explicit limits.
- Model integration
- OpenAI GPT-6 Astra
- Reasoning effort
- max
- Transport
- Responses API · streaming
- Response token ceiling
- 65,536, including reasoning
Relevant conversation text, attachments and retrieved records can be sent to the external model provider for reasoning. The adapter retains native reasoning and tool-call items within the current turn. Response storage is disabled in the API request; provider retention policies still apply. A conversation uses bounded recent history and attachment budgets rather than treating the model’s capacity as unlimited application memory.
The account defines the reach.
Server-side account roles and permitted views determine the available tool registry. Source handlers enforce the application’s access rules. Retrieved correspondence, job records and documents enter the answer as evidence; instructions embedded in that content are not authority to change the workflow.
Images and PDFs can accompany a request. File metadata, extracted text and verified physical facts remain distinct.
From a claim to its source.
Exhibits retain record, message and attachment identifiers. The scene director selects typed references and quoted passages; application validators check source membership, excerpt matching and requested scope before compiling the presentation.
A bounded repair pass can correct an invalid selection. These validation rules constrain selected evidence; they do not guarantee that every generated answer is correct.
Saved geometry. Inspectable layers.
3D packing uses stored dimensions, placement transforms and distinct artwork, protection and construction layers. Selection, focus, rotation, separation and section views act on that geometry.
The language model does not fabricate the displayed crate dimensions. A digital fit does not certify condition, safe contact, structural performance or physical clearance.
Visible work in progress.
Durable run records retain the request, stage, state and result. The application prevents duplicate active runs for the same job and can monitor several requests together.
Preparation supports a reviewed proposal: PNZ interprets each work’s condition, protection, handling and scope before providing a client quote.
Admission before generation.
The application uses a shared monthly budget ledger across application AI routes. Token counting may send the input to the provider before the budget reservation; atomic reservations then account for concurrent requests before model generation. Provider usage settles the recorded cost afterward.
Uncertain requests retain their reservation until reconciled. An unavailable model or insufficient budget produces an explicit failure rather than a silent model substitution. The application ledger is separate from provider account billing.
Different components. One workspace.
Speech recognition and synthesis are separate API components; AURA’s optical core and device are software-rendered interface elements. They are not a physical optical processor or a PNZ-trained foundation model.
Source correspondence can reopen in its application workspace. The same evidence can be read as text or inspected through the spatial presentation.
Judgment remains with P+Z.
Condition, permitted contact points, packing method, movement, pricing and release require the appropriate review and authorization. The system helps expose the details that inform those decisions.
Warehouse views show recorded positions. Staff verify identity and location on site and reconcile exceptions against the supporting records.
Implementation overview · September 2026. Demonstration timing is edited and sample responses are scripted. The architecture is not a benchmark result or a claim of autonomous art handling. Model provider documentation.
The review behind the view
A clear picture.
A record to check.
Match the work.
Compare the physical package label with the inventory record and the works listed inside it.
Check the change.
Review the current 3D layout against a saved baseline. A planned position still needs confirmation on site.
Follow the difference.
Investigate mismatches and unfinished movements. Keep the supporting record with the resolution.
Internal review, made visible.
The film uses a PNZ warehouse layout study with illustrative packages. In operations, the digital record helps identify what needs checking; staff confirm package identity and location on site, then reconcile differences against supporting records.