Observe
Collect and structure signals into comparable views. Public language can name the category of work without exposing private sources or acquisition channels.
Method notes
Evidence first, interpretation second, decision use last.
The method can be public without being overly specific. JupiterSpec describes how analysis is reviewed and translated, not the proprietary system that produces each input.
Review
Compare direction, breadth, timing, and confidence. The review process is described as disciplined and repeatable, not as a recipe.
Translate
Turn analysis into decision context. Public notes focus on what the signal means, where uncertainty remains, and what should be watched next.
Good public language
Say what the work does, not how the edge is built.
Use phrases like reviewed signal, public proof, decision context, scenario comparison, confidence boundary, and manual-review gate. These communicate maturity without becoming an implementation guide or treating a placeholder as proof.
Avoid public references to unreleased formulas, exact data vendors, account-level results, credentialed systems, internal task flows, financial advice, or separate workstreams that do not belong on JupiterSpec.