Design & delivery
standards.

01 / Standard

Brand positioning: a specialist professional practice

• Address architects, engineers, facilities leaders, municipalities and sophisticated property stakeholders. Present JS Imaging as a specialist visual-documentation practice, not a commodity drone-services offer. The Rochford real-estate product remains a delivery reference, not a change in the broader professional market positioning.
• Retain an immersive full-screen film with a carefully placed text overlay on the marketing opening. Use deep charcoal, subtle panel differences and restrained brass across digital surfaces. White paper is appropriate for printed reports, not a default marketing-site background.
• Choose distinctive, licensed typefaces through actual desktop and phone specimens. Use character in display typography and clarity in body text, estimates and controls. Avoid trend-led font pairings, repetitive card grids, decorative gradients, oversized slogans and ornamental luxury effects. Refinement comes from proportion, alignment, deliberate line breaks, legibility and source imagery.
• Preserve the complete original logo. Do not crop, distort, recolor, redraw, recompress or optimize it. Keep evidence imagery unfiltered and limitations readable; visual minimalism must not remove context.
• Approved 2.0 pair: IvyPresto Display Light headings with Neue Haas Unica body and interface text. Preserve the complete original logo, full-screen film, Observatory orbit video, existing sections and functional deliverables. Apply styling to maintained source; never replace a complete published experience with the shortened design study.

02 / Standard

One identity, across every surface

• Keep the full company logo intact and legible. Minimum intended display width: 96 CSS pixels on phones, 120 on desktop; allow more width when the artwork requires it. Never force the artwork into a shallow cropping box.
• Use serif headings, sans-serif body and interface text, and monospace only for meaningful technical values. Body copy should normally be 16 pixels, interface text 14 pixels, metadata at least 12 pixels.
• Use brass for primary actions and brand emphasis, teal for active data selections, and amber for cautions. Color must not be the only indicator of state.
• Use consistent 2-pixel button corners, clear borders, visible keyboard focus, and 44-pixel minimum touch targets. Keep the imagery neutral; grading belongs to marketing footage, not evidence views.

03 / Standard

Real estate: the Rochford House reference product

• Rochford House is the approved real-estate reference: preserve its complete client-delivery experience rather than replacing it with a generic map template. Project-specific availability and contracted scope govern which datasets are supplied.
• Provide a branded property workspace with project identity, capture date, interactive 3D, available orthophoto and surface/relative-relief layers, corresponding site photography, client files, replayable tutorial, feedback, fullscreen, and Information & Limitations.
• Present a property orbit video while the 3D model prepares. Use muted inline playback, a poster/fallback, and reduced-motion handling. Never require all finest-detail tiles before the user can enter a usable settled view.
• Reveal the usable property view and refine detail in the background. Retain a clear slower-load escape route, usable alternate imagery, and explicit errors rather than an endless loader. Preserve memory-aware phone profiles and higher-detail desktop inspection.
• Offer the approved property deliverable set through Client files with readable names, formats and sizes. Keep source/archive files distinct from lightweight browser presentations. Never promise unavailable deliverables or include another client's files.
• Match Rochford's navigation, layer/photo/file panels, roof-detail workflow, status communication, and guided tutorial. Keep technical diagnostics behind Help. Preserve desktop and phone interaction patterns and all documented performance fixes.

04 / Standard

Public demonstrations and private workspaces

• Show the project name and clear Public demonstration or Client workspace identity. Put software versions in Help, not the primary brand header.
• Use a stable desktop toolbar and task panel. On phones, use readable selectors and aligned Tools, Menu and Layers controls; panels must not conceal their own close controls or primary actions.
• Allow browser page zoom and keyboard operation. Keep map gesture handling confined to the map. Do not let sticky estimate bars or overlays cover focused fields or anchor headings.
• A styling release must not change client-link authentication, saving, privacy masks, data crops, original model assets or dataset permissions. Private references, credentials, client file URLs and precise locations must never enter this public standards document.

05 / Standard

Estimated references and limitations

• Retain approved Information & Limitations language and contextual notices. Every displayed measurement and annotation remains an estimate requiring appropriate field verification. This is not a survey or an engineering/construction document.
• Use estimated relative delta Z in the selected units rather than displaying absolute MSL elevations. Retain permitted private location data; exclude location identifiers from public demonstrations and screenshots according to their established privacy rules.
• Thermal tools distinguish estimated radiometric source-pixel results from palette-derived visual estimates. Neither is a certified temperature or diagnosis. Never derive calibrated temperatures solely from displayed colours. Preserve the screening-only notice and visible/thermal comparison.
• Never remove limitations for visual minimalism. Establish a readable short notice and accessible full information, with applicable limitations carried into PDF, image, print and tabular exports.

06 / Standard

Thermal delivery: the Rochford House standard

• Use the maintained Rochford thermal workflow for published projects with thermal imagery, subject to authorized dataset availability and reliable registration. Offer Visible / RGB and Thermal model appearance with honest preparation, readiness, coverage and fallback states. Record imagery-only or unregistered projects as outstanding capabilities, not completed thermal-model deliveries.
• Open Thermal with the approved rainbow palette and a tight documented range selected for that project's data. Share the display range across comparable captures; do not copy another property's temperatures or silently rescale each frame. Palette changes affect appearance, not source values.
• Review corresponding source imagery from supported thermal model surfaces, using double-click or double-tap in navigation mode and an accessible source-review control. Preserve camera manipulation, basic measurements, saved notes, geometry, loading orbit and public/private access.
• Keep Estimated ΔT (thermal difference) distinct from Estimated ΔZ (relative height). Extend the locked measurement toolkit with supported thermal statistics and estimated roof-face area, stating the source basis, planar assumptions, no-data coverage and units. Do not display absolute MSL elevations or fabricate thermal values.
• Include the maintained delta guide explaining thermal contrast, relative height and material/capture limitations. Thermal is screening only: no universal temperature threshold proves moisture or another defect. Carry estimate and field-verification notices into the interface, guide and exports.
• The complete reusable requirements and release gate are in /thermal-delivery-standard.json version 1.0.0. Verify RGB-first thermal activation, repeated switching, source pixels, loading failure and actual supported browsers/devices before recording each edition as complete.

07 / Standard

Basic measurements: one recognizable toolkit

• Measurement standard 1.0.0 is the locked baseline for every new and maintained deliverable. Present Estimated distance, Estimated plan area and Estimated ΔZ in that order, with consistent labels, selected-state styling and Imperial/Metric units. Specialty tools extend this core; they do not rename or replace it.
• Distance is horizontal on a map and straight-line between selected points in 3D; identify that basis beside the result. Plan area is horizontal projected area, not roof surface area or a mesh-following surface measurement. ΔZ is signed B minus A between two supported surface points, not an absolute elevation or MSL value. All values are estimates requiring field verification.
• Provide Finish, Undo point, Cancel and Clear measurements. Finish validates the required points and returns to navigation after success. Cancel or Escape discards only the unfinished measurement and returns to navigation; Clear measurements removes only measurement results and exits drawing. Never clear saved specialty annotations with the basic-tool clear action.
• Use genuine dataset picks, not globe, background or guessed-height fallbacks. Where suitable geometry, vertical reference or permitted scope is unavailable, show a clear unavailable explanation for the affected tool rather than fabricate a value. Calibrated tabletop/local-space deliverables must identify their own scale and vertical basis.
• Store numeric geometry independently of formatted labels. A unit change refreshes all existing results and exports. Reject self-intersecting, duplicate/degenerate outlines; handle valid concave plan areas correctly. Do not imply enclosed mesh volume or detailed surface area from corner-only approximations.
• Preserve approved 3D orbit, pan, pinch, zoom, set-center, loading video and progressive refinement. A drag must never place a measurement point. Use a precision cursor only during placement, explicit active states including aria-pressed, live point-count instructions, visible focus and at least 44-pixel touch targets. On phones keep a compact dock and readable results without obscuring the model.
• Carry estimate, unit, calculation-basis and field-verification limitations into tutorials, help, reports and exports. Preserve public location restrictions and authorized private data. Availability of a tool does not authorize surveying, engineering or construction reliance.
• Before release test desktop and phone layouts, empty/incomplete Finish, Undo, Cancel/Escape, Clear isolation, repeated measurements, unit changes, simple known geometry, invalid picks, concave and invalid outlines, rendered exports, and unchanged navigation/loading/privacy/saving. Record the measurement version, source, release, rollback and any explicitly unavailable capability.

08 / Standard

The document family

• Use white-paper print layouts with the approved original logo, clear project title, capture date, issue/revision, units and page identity. Keep the same typography and restrained brand accents as the interface.
• Map and object-register exports must derive names and dates from project configuration, never a hard-coded prior client. Preserve estimates, disclaimers, provenance and private/public differences.
• Give evidence images room and keep essential annotations visible. Use readable tables and footnotes, repeat table headings on additional pages, and verify actual rendered pages before release.
• Pricing sheets, reports and disclaimers should look related but retain their distinct purposes. A design change does not authorize changes to prices, scope, technical claims or legal text.

09 / Standard

Release and replication checklist

• Begin each project from its approved product template; for real estate use the maintained Rochford property-client-delivery template. Set project identity, datasets, capture dates and access policy explicitly.
• Record source location, release ID, deployment target and rollback reference. Verify the current source before publishing; do not redeploy an older workstation snapshot over newer work.
• Test desktop and phone layouts, keyboard focus and zoom, model startup and fallback, units and estimated tools, files, exports, feedback, and edition-specific saving. Inspect console/network errors and render printable outputs.
• Verify logo bytes against the approved master. Keep secrets out of published files. A 2.0 design prototype remains labeled and separate from production until approved.
• Update this versioned standards reference and deployment inventory with every approved product change. This public document describes reusable rules only, not client access details.

10 / Standard

Fast complete opening; quality preserved

• Prioritize loading speed and the client first impression in new projects whenever original quality, authored opening, tools, source values and access are preserved. Follow /performance-standard.json.
• Reveal a stable complete original-geometry view promptly, retain it while finest detail refines, and never wait for unrelated detail or an arbitrary timer. Use a renderer-specific opening strategy.
• Prefer direct exact-byte static delivery of necessary opening data where access allows. Keep private optimization behind authorization. Version changed code; verify byte ranges, coverage, final detail, failure escape and timings with cache conditions stated.

Property product / Version 1.6

The complete real-estate delivery pattern.

The maintained Rochford reference includes the following deliverables and behaviors. Each new property must have its own authorized datasets and agreed scope.

• Clean orthophoto. Compare competing reconstructions at matching roof locations and select the clearest result. Sampling is recorded without claiming certified accuracy.
• Surface model and hillshade. Deliver the digital surface model and its hillshade. Offer multidirectional, northwest and southeast illumination with an orthophoto underlay. Structures and vegetation remain part of surface relief.
• Property model. Stream an upright, property-centered model with an authored opening view and the approved retained footprint. Keep useful roof and client-area overviews.
• Thermal model and source review. For projects containing suitable authorized thermal data, follow thermal-delivery-standard.json: RGB / Thermal appearance, tight dataset-specific rainbow default, supported source-image review, estimated ΔT / area / ΔZ tools, client delta guide and clear no-data coverage. Track absent registration or data as outstanding, never fabricate a texture.
• Native detail preview. Provide a deliberately small inspection section using original finest-detail geometry and textures. The full property remains the opening scene.
• Source-photo collection. Include the complete authorized set: thumbnails, review previews, full resolution and individual original downloads. Provide arrows, thumbnails and filename, flight and viewing-angle filters.
• Capture context. Show the selected camera position and direction on the map or in the model when metadata supports it. Cluster dense map markers and keep the roof visible.
• Orbit video. When supplied, use the owner-rendered orbit during loading and offer the unchanged original as a downloadable file.
• Client files and quality report. Show authorized original imagery, surface products, derived hillshade, processing report and video with names, dates, types, sizes, search and resumable transfers. Do not promise an archive or absent source product.
• Review notes and exports. Allow local visual observations, estimated distance and plan area, note import/export and branded PDF views. Explain local browser storage and the need to export a copy.

Property product / viewing

Opening and detail behavior

• Open at a useful property-level angle chosen from the actual data. Drag or use one finger to orbit; wheel or pinch zooms; right-drag or two fingers pans. Home view restores the authored camera. Roof focus and Client area provide separate useful views.
• The compact, muted, inline orbit loops while a settled opening pass is prepared. Reveal a usable property overview before demanding every finest subpixel tile. Continue sharpening the same model in the background, retaining original native detail for closer inspection.
• The reference loading player caps display at 360 pixels on desktop and 280 pixels on phones. Half-speed playback is the default when appropriate to the supplied export. Validate the real frame count and duration, preserve source frames when retiming, avoid upscaling weak footage, respect reduced motion and provide a play control when autoplay is blocked.
• After 20 seconds, offer Open available view only when rendered geometry exists. Do not force a partial scene on the client. Layers must cancel a delayed loading cover and return to imagery. Recover memory pressure beneath the cover; retry transient failures within a bounded policy and clear stale failure state on a new model visit.
• Use capability and measured-performance adaptation for memory, parallel decoding, screen detail and pixel density. Preserve geometry and texture dimensions during supported GPU texture conversion. Do not select a browser budget solely by its name or viewport. Record real browser coverage; a simulated phone profile is not native Safari verification.

Property product / brand

Brand and usable controls

• Keep the unchanged full JS Imaging LLC logo, linked to the main website. Use the dark frame, gold accents and approved canonical typography: IvyPresto Display Light headings, Neue Haas Unica body and controls, and IBM Plex Mono technical labels. The imagery remains the subject.
• The delivery header offers Layers, Photos, Files, Tutorial, Feedback and fullscreen. Use readable labels and at least 44-pixel primary phone targets. Audit overlays, controls, safe areas, scrolling and portrait/landscape layouts. Photo camera context moves below the review area on phones.
• Tutorial begins once per browser session after a usable view is ready and remains replayable. Point gold arrows at visible controls, await asynchronously opened views, and move the card away from its target. Support Back, Next, Skip, Finish, Escape, keyboard focus and reduced motion. Restore the starting view type and clear temporary highlights without creating notes, measurements, downloads or messages.
• Preserve the shared Feedback control and its clear problem-reporting purpose. Keep sanitized feedback context and a visible accepted/submitted state. Preserve the working photo review, file library and viewer functions while updating documentation.

Property product / limits

Estimation notices and access

• Keep the persistent notice: ALL MEASUREMENTS ARE ESTIMATES · VISUAL REFERENCE ONLY. Provide full Information & Limitations, including applicable notes in prints and exports. Plan area does not include roof pitch. Surface sampling, camera metadata and photogrammetry are visual references rather than certified survey or roof-condition diagnosis. Confirm apparent concerns through appropriate field inspection.
• Select access from the owner’s instruction. Unlisted, noindex, no-password delivery is accessible to anyone with the link; it is not authenticated confidentiality. Keep project storage isolated and originals allowlisted. Documentation must not expose client identifiers, imagery, coordinates, catalogs, credentials, source folders or private service addresses. Retain the deployment’s existing access and indexing policies.

Property product / quality

Release verification and reuse

• Inventory and reconcile the complete source; document visual orthophoto selection, source references, footprint, authored camera, applicable tools and deliberate omissions. Derive each new property’s metadata and geometry rather than inheriting another client’s values.
• Verify MIME types, originals and selected model bytes, complete and partial video responses, seek/resume behavior, video-to-model transition, memory-pressure recovery and loading escape. Test fresh network fetches and a high-density phone resource profile, and inspect actual opening quality as well as timing.
• Complete desktop and phone layout, all tutorial navigation, first-session/replay, source-photo browsing and original downloads. Confirm no overlay obscures its target, no blank model can be opened, and original finest detail remains accessible. Do not send feedback or create client notes as a documentation test.
• Confirm the stable client domain and ready deployment, retain release evidence and rollback targets, update the approved production registry and remove temporary upload services/tokens. A source package must exclude client datasets, secrets and hosting attachments. Reference processing scripts require parameterization before execution.