Aspiration before analysis

Find the work inside the words.

Test purpose, audience, evidence, and scope—then turn the result into a clearer statement and three honest horizons.

Runs locally by default. Uploaded context stays in this browser.

Six Filipino and Asian adults of mixed ages walk together beside the sea at dawn, looking toward a bright horizon. — WHY THIS MATTERS
A mission statement is useful when people can see the future it points toward—and recognize their part in reaching it.
Shared future before analysis · Static editorial image; not a score or chart.

Workbench

One statement. A visible chain of reasoning.

Organization category

Profit type

Changes stakeholder and sustainability language—not scoring standards.

Mission statement

Look for purpose, audience, and contribution.0 words

Add supporting context

Empty fields stay unknown. The analyzer will not invent missing content.

Drop supporting contextTXT and MD work offline. PDF and Word are best effort. Choose files

Safe examples:

From statement to responsible next steps

Use the analyzer without outsourcing judgment.

Use the analyzer to inspect wording, compare rewrite choices, and draft planning questions without treating a heuristic score as organizational truth.

Privacy boundary

Offline mode processes text in this browser. History stores analysis records locally, not uploaded file bodies. This is local storage, not encryption. Optional LLM mode sends the entered content to the endpoint you configure.

Score boundary

Scores are heuristic feedback on the statement's wording. They do not measure organizational health, alignment, faithfulness, impact, leadership quality, or probability of success.

Goal boundary

Do not publish or operationalize generated targets as approved goals until responsible leaders validate the baseline, owner, evidence, resources, and review date.

01
Choose the statement type
- Mission — present purpose, audience, and contribution.
- Vision — desired future and who/what changes.
- Operating Principles — observable decision rules and behaviors.
- Core Beliefs — commitments and their implications.
- Strategic Plan — priorities, owners, measures, constraints, and cadence.
- Integration — how purpose, future, values, and priorities connect.
Choose the closest mode. Switching mode preserves text but requires re-analysis after results exist.
02
Add context carefully
- Category changes cue interpretation, not scoring standards.
- Profit type changes stakeholder and sustainability language, not quality expectations.
- Supporting fields remain optional and unknown when blank.
- TXT and MD work offline.
- PDF and Word are best effort and may be unreadable.
- Unreadable file content is excluded and reported honestly.
- File bodies are used transiently and are not saved in browser history.
03

Analyze the statement

Minimum valid input is five normalized words. Analysis runs through six named stages. Stage progress is not a completion percentage. Offline output is deterministic for the same inputs and selectors. If optional LLM output fails validation, the offline result remains available.
04
Read scores safely
- Overall — weighted summary of wording quality.
- Clarity — readability and coherence.
- Specificity — named purpose, audience, contribution, and evidence.
- Feasibility — bounded claims, constraints, and plausible delivery language.
- Ambition — meaningful outcome without unsupported superlatives or guarantees.
- Analysis confidence — evidence completeness, not statistical certainty.
Scores are heuristic feedback on the statement's wording. They do not measure organizational health, alignment, faithfulness, impact, leadership quality, or probability of success. Use them to compare revisions of the same statement—not to rank organizations.

Read the score evidence, detected/missing components, risks, and first-principles notes before acting on the number.
05

Choose a rewrite, not “the answer”

The concise rewrite is best for recall, speaking, or a short public line. The expanded rewrite is best when audience, method, boundaries, or outcome need context. Neither is final, perfect, or automatically approved.

Bracketed details are unresolved facts the user must confirm. Preserve intended meaning, sector language, and values; edit anything that changes intent. Copy the version that best fits the use case, then review it with stakeholders.
06

Turn the result into validated goals

Three honest horizons are planning prompts, not commitments or forecasts. Generated goals must not be adopted until an accountable owner validates scope, baseline, target, metric, dependency, resources, and review cadence.

Baseline · first 90 days means measure before setting a target. Output metrics are not the same as outcome evidence. Long-horizon language must not imply certainty, guarantees, or causation the statement cannot support.

Do not publish or operationalize generated targets as approved goals until responsible leaders validate the baseline, owner, evidence, resources, and review date.
07
Save, export, restore, or start again
- History is stored locally in the browser, newest first, with a maximum of 25 records.
- Restore returns a saved analysis to the workbench.
- Export downloads a JSON record; it excludes settings, tokens, and extracted file content.
- Delete removes one record; Clear history requires confirmation.
- Reset local data is destructive and states its scope.
- A browser or device change does not sync history.
- Re-analyze after changing input; stale results remain visible but must not be mistaken for current results.

Troubleshooting

Analyze is disabled

Add at least five words; confirm text is in the primary editor.

A file was not included

TXT/MD are reliable offline; paste relevant text when PDF/Word extraction reports a warning.

Results say Needs re-analysis

Inputs changed after the last run; select Re-analyze.

A score seems surprising

Read score evidence, missing components, category/profit context, and the heuristic disclaimer; revise and compare again.

The rewrite includes brackets

Confirm the missing detail; the app intentionally did not invent it.

A generated goal lacks a number

Establish a baseline first; do not invent a target.

Optional model failed

Use the preserved offline result or verify endpoint/model/session-token settings.

History is missing

History is local to this browser; storage may have been cleared, unavailable, or opened on another device.

Export did not download

Retry from the result or History row and check browser download permissions; no cloud copy exists.

Find the work inside the words.

One statement. A visible chain of reasoning.

Privacy boundary

Score boundary

Goal boundary

Choose the statement type

Add context carefully

Analyze the statement

Read scores safely

Choose a rewrite, not “the answer”

Turn the result into validated goals

Save, export, restore, or start again

Troubleshooting