01 / Inspection
Portal Audit reads. It does not implement fixes.
The audit evaluates portal configuration and produces scored evidence, findings and a branded report or PDF. A finding does not authorize a change. Your team decides what belongs in a separate implementation.
02 / Human decisions
Generation and deployment have separate approvals.
In Projects, review the plan before approving generation. Review generated assets and the proposed deployment before approving portal changes. A plan, an AI response and a deployment receipt are different artifacts—not interchangeable assurances.
03 / Access & scope
A workspace for the team. A portal for the Project.
Jetstack access is scoped to the signed-in organization. A Project is bound to a HubSpot portal, and the implementation works in that context. Review the active workspace, connected portal and destination before approving work; do not assume access to one portal authorizes another.
04 / Execution record
Inspect the run, not just the proposal.
Projects uses durable runs, dependency-aware execution and receipts with read-back verification. Check the actual result and any failed or incomplete work. An accepted plan is not evidence that all of its assets are live.