Engineering inside Aura /

Interface and interaction architecture

A Lit custom element handles finish selection and room-area exploration. The spatial workspace retains its dimensional model and saved specification flow.

Room data is normalised by the server

Room dimensions are validated within the supported 500 to 50,000 millimetre range. Area is computed from width multiplied by length, divided by one million to produce square metres. The server recomputes totals on edits. A successful save returns canonical room and title data to the interface, which then recognises the saved state immediately.

References are captured with the brief

The brief stores reference snapshots including the project name, description, credits and image identifiers. That gives an exported or submitted brief a record of the inspiration selected at that point. Project image references must belong to the workspace and be supported image files; a text upload cannot be substituted as a project photograph.

The visual layer and record layer have different jobs

A WebGL room scene provides spatial interaction, while structured room records remain the basis for totals, saving and PDF output. The workflow does not depend on treating a rendered screenshot as authoritative design data. The generated PDF uses the server's saved snapshot, including dimensions, requirements and referenced project names.

State transitions remain explicit

Independent local persistence, workspace-scoped references, version checks and request idempotency support the draft and submission lifecycle. Replaying a successful save or submit returns the recorded result. A later edit creates draft state again. File storage deduplicates identical content within the workspace without allowing another workspace to read it by reference.

Operating the product

Confirm dimensions against a real measurement before using the brief in a commission. Millimetres are the input unit; check that a value intended as metres has not been entered without conversion. Review each room's computed area as a useful error signal.

Preserve descriptive reference credits and explain what each image contributes. If an image is a fictional study or generated asset, retain that context when exporting or sharing the brief instead of allowing the visual alone to imply built work.

Wait for saved state before exporting or submitting. The interface now adopts the server's returned rooms and title after a save. If a version conflict occurs, reopen the current saved brief and compare it with the intended changes before trying again.

After editing a submitted brief, review and submit the new draft deliberately. Keep the earlier PDF when a record of the prior discussion is useful; a newly edited screen should not be substituted for evidence of an earlier agreement.

Use export as a portable briefing record, then establish a separate handover channel with the receiving studio. A local submission status confirms persistence in this application, not that another person has received or accepted the request.

Independent by construction

Aura has its own application source, build configuration, local server, database, object store and session cookie. The fifteen applications reuse copies of a common foundation, but their operational data and credentials are independent. A shared dependency cache on this Mac saves disk space; each product includes a lockfile and a command to install its own dependencies.

Mutations validate the workspace and current record version. Approval binds the reviewed content digest; an idempotency key prevents an identical retry from becoming a second action. These controls are implemented in the server, alongside the product-specific rules described above.