PowerOn / change preparation
Understand the change.
Prepare the next decision.
Compare a permitted source portfolio before and after a proposed revision. Inspect exact changes, potential consumers and the questions a qualified reviewer should resolve.
Candidate paths come from literal filename matches. This tool does not compile, execute, connect to a core, approve or deploy a change.
01 / Supplied inputs
Two snapshots. One proposed change.
Use PowerOn Portfolio Studio input JSON or its complete handoff. Saved results are discarded and the current engines rerun. Match files by the same normalized supplied ID (surrounding whitespace trimmed) on both sides; this does not verify source identity or rights.
Entries stay in browser memory. Full sources travel in exports. Use your approved storage and sharing process.
02 / Reviewable preparation
A change your reviewer can inspect.
Potentially affected source
These are direct changes and reverse-reachable candidate consumers in the union of the two supplied graphs. They are not a verified runtime impact assessment.
Dependency additions and removals
Complete candidate edge-evidence registry
Reviewer follow-ups
Regression preparation
Complete input and both reports
Includes every supplied source. Do not share outside an approved route.
From preparation to an accepted pilot
Give the reviewer a bounded decision.
Agree the permitted corpus, actual environment, qualified reviewer and acceptance evidence. Record real preparation, review and correction effort before making a value claim.