Look at: Report coverage, risk/action matrix, publish readiness.
Next: Review owner summary and budget exposure.
Published roof record preview for owner, consultant, contractor, facility, and insurer decisions.
Workspace controls the source record. Portal receives published, permission-filtered views when future publish gates are approved.
Look at: Report coverage, risk/action matrix, publish readiness.
Next: Review owner summary and budget exposure.
Look at: Roof Walk locator, field photo queue, selected evidence.
Next: Confirm access and field condition.
Look at: Report-linked evidence, uncertainty, sample/photo gaps.
Next: Review report page and field confirmation.
Look at: Selected map finding, affected area, access/staging, before/after proof.
Next: Define repair method and closeout evidence.
Look at: Baseline/report links, claim support, source matrix.
Next: Review approved packet evidence only.
Look at: Source confidence, missing evidence, role outputs.
Next: Lock/publish after verification.
Map-linked findings, report pages, zones, and verification gates from the packaged roof record.
Static export models the future role view without Portal API calls, auth, persistence, or backend writes.
Report-linked findings can be reviewed now.
Field verification remains the next decision gate.
Contractor scope starts from selected map finding.
Use report pages and the evidence map before portal publishing.
Use the map-selected finding to guide field review, photos, core sample decisions, and stakeholder next steps.
Technical review, scope, and stakeholder translation stay tied to the roof evidence map.
Evidence is review-ready where report links and mapped findings align.
Field verification remains the next gate before final decisions.
Consultant review should start with report-linked findings.
Contractor scope should start from the selected map finding.
Missing priority metadata does not block map-led triage.
Final decision waits on verification and closeout evidence.
Confirm finding type, interpret moisture/anomaly evidence, link report page, note uncertainty, recommend next action, and flag warranty or claim relevance.
Define repair method, material/system note, access/logistics, crew/photo needs, SF/SQ confirmation, and punch or warranty follow-up.
Add core/sample reference, field verification note, attachment label, zone/finding link, initials/date, and before/after photo.
Published views are read-only by default and remain traceable to the Workspace-controlled source record.
Review baseline imagery, comparison imagery, traced evidence overlays, and focused roof zones in one locked client viewport.
Focus the map on a selected zone or elevation class without leaving the evidence viewport.
Operational summary, affected area, context, and supporting record detail for the currently selected map item.
Per-anomaly roof walk records for status, moisture, core samples, attachments, role notes, and local field packet export.
Field verification additions stay in this browser unless exported.
Convert selected anomaly verification into repair, warranty, claims, work-order, and closeout records.
Repair closeout additions stay in this browser unless exported.
Mobile-first anomaly guidance, GPS marks, photo references, quick core samples, and field packet export.
All-anomaly field status, moisture, core sample, attachment, and export controls from local verification records.
Local repair status, warranty impact, claim context, ticket ownership, and closeout packet exports across all anomalies.
Capture maintenance, warranty, contractor, and claim context locally while reviewing the roof record.
Local viewer notes stay in this browser unless exported or shared.
Practical next-step prompts for technical review, repair planning, maintenance, and claim-support decisions.
Immediate roof condition context for consultants, contractors, facility teams, insurers, and property managers.
Role-ready roof record status, report coverage, field readiness, and decision context.
Offline preview only. No Billing-Core submission is performed.
Local readiness target only. No Billing-Core submission is performed.
Selected target is not published until a future approved publish workflow exists.
Selector controls are shown for layout proof only until the runtime selector phase.
{"packet_type":"mas_roof_record_publish_packet_preview","packet_version":"0.1","generated_at":"2026-06-07T01:11:42.923Z","source":{"workspace_export_id":"2026-06-07T01:11:37.613Z","inspection_id":"2026-04-13"},"target_placeholders":{"org_id":null,"client_id":null,"roof_client_account_id":null,"property_id":null,"building_id":null,"roof_section_id":null},"counts":{"anomalies":34,"evidence_records":181,"attachments":0,"report_page_assets":28,"field_verifications":0,"repair_closeouts":0},"readiness":{"status":"blocked","gates":[{"key":"asset_hierarchy_selected","label":"Asset hierarchy selected","status":"fail","detail":"Target hierarchy is incomplete. Missing: org_id, client_id, roof_client_account_id, property_id, building_id, roof_section_id."},{"key":"roof_section_linked","label":"Roof section linked","status":"fail","detail":"No roof section layer was found and no Billing-Core roof_section_id is selected."},{"key":"inspection_identity_present","label":"Inspection identity present","status":"pass","detail":"Inspection 2026-04-13 is available for packet identity."},{"key":"anomaly_stable_ids_present","label":"Anomaly stable IDs present","status":"pass","detail":"34 anomaly IDs are stable and unique."},{"key":"evidence_references_present","label":"Evidence/media references present","status":"pass","detail":"62 evidence or report references are available."},{"key":"report_package_ready","label":"Report package ready","status":"pass","detail":"28 report page assets are packaged."},{"key":"field_verification_classified","label":"Field verification classified","status":"warning","detail":"Field verification is not classified in the offline packet preview yet."},{"key":"repair_closeout_classified","label":"Repair closeout classified","status":"warning","detail":"Repair closeout records are absent; this can remain warning-only until repairs are in scope."},{"key":"no_local_path_leakage","label":"No local file path leakage","status":"pass","detail":"Packaged references avoid local absolute paths."},{"key":"no_orphan_anomalies","label":"No orphan anomalies","status":"pass","detail":"All anomaly rows carry stable IDs."},{"key":"no_orphan_media","label":"No orphan media","status":"pass","detail":"Attachment rows have packaged references when present."},{"key":"audit_proposal_present","label":"Audit proposal present","status":"pass","detail":"Offline packet preview includes gate results for the future Billing-Core audit event."}],"missing_requirements":["Asset hierarchy selected","Roof section linked"]},"exclusions":["No live backend call is included.","No binary media is embedded beyond packaged export references.","Browser-local verification and closeout records must be exported explicitly."],"note":"Offline preview only. No Billing-Core submission is performed."}
Offline packet controls are intentionally inactive until the runtime handler phase.
Tune next-step prompts and export packet suggestions for the current roof-record user.
Review focus, missing data, next action, and export packet for the active role.
Add local-only inspection, warranty, contact, maintenance, and attachment-manifest data to the standalone roof record.
Local record additions stay in this browser unless exported.
Chain-of-evidence status for report pages, map evidence, field notes, core samples, photos, warranty, contacts, and export history.
Download role-specific JSON packets from the packaged roof record plus local enrichment data.