Requirements workspace · schema v2 · APK-F46VNREV

Build solar trust
into every step.

Shape an installable, offline-capable PWA around the real homeowner and installer journey—not a list of disconnected features.

Start the brief

Reference trust spineWeb + field

Assessusage + roof

Verifyinstaller identity

Matchfit + capacity

Reserveagreement + fee

Provegeo evidence

Approverelease escrow

Every sensitive action is attributable, time-bound, and auditable.

Ownership & status

Record who owns this brief

A brief without an accountable owner and an explicit status cannot be approved. This block is exported at the top of the PDF.

Brief titleStatus

Approved briefs should not be edited — duplicate instead.

Accountable decision ownerApprovers (security, privacy, operations, field, engineering)Decision rationale and linked evidence

Product intent

Define the outcome

What must this PWA make easier, safer, or faster than today's GCP application?

Problem to solve

Observable, non-solution language. Describe what goes wrong today.

What does success look like after 90 days?

State a baseline and a target. Do not invent product numbers.

Primary product priorityMeasurement window and metric source

Personas & access

Choose who we serve first

The reference flow supports homeowners, installers, operations, admins, and utility handoffs.

Launch persona

Avoid a multi-persona launch unless one end-to-end journey requires it.

Most important job to completeRoles, permissions, or exceptions

Reference journey

Scope the first release

Select the stages the PWA must cover. Unselected stages are exported as explicit non-goals.

Where does the journey begin and end?How are excluded stages handled today?

PWA behavior

Design for imperfect connectivity

Decide what works offline, what queues safely, and how users understand synchronization.

Must work with no signalConflict and retry behavior

Queued payments, approvals and consents must never look complete before server confirmation.

Zero-trust controls

Prove every critical action

The reference prototype verifies identity, documents, consent, payments, evidence, and milestone approval.

Highest-risk actionsEvidence required before approval

Data & integration

Draw the system boundary

Capture the smallest useful integration set for a Cloudflare-hosted PWA.

Systems of record

Keep PostgreSQL behind authenticated services — the PWA must not connect directly.

Privacy, residency, and retention constraints

Delivery decisions

Set the release guardrails

Clarify launch constraints now so architecture follows product reality.

Target date or milestoneBudget, team, or technology constraintsExplicit non-goalsSupported browsers, devices, and lowest tolerated network

Registers

Record risks, assumptions, and dependencies

Unresolved assumptions need an owner and a review date. These export as structured rows, not prose.

Risks

None recorded yet.

Assumptions to test

None recorded yet.

Dependencies

None recorded yet.

Non-functional & acceptance

State how this will be judged

Every selected journey stage needs at least one acceptance criterion before implementation starts.

Non-functional requirements

None recorded yet.

Acceptance criteria

None recorded yet.

Your working brief

Turn decisions into a buildable PWA.

Export the structured JSON for machines and the PDF for review. Where the two disagree, the JSON is authoritative.

Build solar trustinto every step.

Reference trust spineWeb + field

Record who owns this brief

Define the outcome

Choose who we serve first

Scope the first release

Design for imperfect connectivity

Prove every critical action

Draw the system boundary

Set the release guardrails

Record risks, assumptions, and dependencies

State how this will be judged

Turn decisions into a buildable PWA.

Build solar trust
into every step.