What we tested in Orbit /
The tests behind Orbit: inputs, actions, observed results and the limits of that evidence.
A plum review room puts the artwork at the centre, with a project-file rail, version history, numbered pins and threaded feedback. The public interface is an interactive example of a full-stack creative-review app.
Internal local testing, using synthetic inputs and owned assets. The results below establish the observed software behavior in those scenarios. They do not establish customer ROI, uptime or external deployment readiness.
A complete image review
Browser QA created an independent synthetic workspace and review room, uploaded an original Lumia image and confirmed that the image rendered. A pin was placed on the image, a note was posted, the note was resolved and the current version was approved. Reloading retained the approval and zero open notes.
Revision replacement changed the decision
A second original PNG of 2,788,838 bytes was uploaded after the first version had been signed off. The new image rendered as version two and the room returned to review. This directly checked that approval belonged to the earlier file. The tested upload also verified the corrected multipart limit after a server restart.
The record left the browser
The actual decision-log PDF was downloaded, its text extracted and its page visually inspected. It contained the resolved note and approval with the file digest. Desktop and 390-pixel mobile screenshots were captured. The mobile document had no page-level horizontal overflow during the tested review flow.
Access checks were exercised separately
Recorded HTTP checks covered original-file fidelity, invalid anchors, workspace boundaries and approval blocking. Nine share checks verified the limited anonymous projection, expiry timestamp, allowed file bytes and denial of unrelated files or writes. These are local synthetic tests; they do not establish client adoption, notification delivery or elapsed-time expiry behaviour.
What this evidence does not establish
This is an original Lumia product demonstration using owned media and synthetic review records, with no claim of external client work.
The browser acceptance flow covered still images. PDF pages and MP4 timestamps have server fields, but their full browser review journeys were not verified in this pass.
Expiring share timestamps and access scope were checked; passage of the full expiry period was not simulated.
No external notification or inbox delivery is claimed. A stored review decision is not proof that a recipient read it.
A similar problem in your business?
Bring a real workflow, representative inputs and the result that needs to be reliable.
Shape a project brief