Message integrity workspaceReview evidence before an authorized publication decision
APAlertProofControl Center
Local deterministic engine / prepared data
METHOD / 01

The generator is not allowed to grade itself.

AlertProof treats a notice like a versioned source artifact: extract source-grounded fact candidates, confirm the claims that cannot drift, manage language and channel drafts, then expose rule evidence before an accountable human makes any publication decision.

Typed factsProtected tokensIndependent checksHuman approval
01 / Architecture

Evidence moves in one direction

The current build uses a deterministic local analyzer, editable drafts, exact-value rules, English rule-based coverage, and qualified-review flags for other languages. Prepared evaluation datasets cover the interface without a network connection.

Source revisionFact registryDraft libraryRule evidenceQualified review handoff
02 / Typed facts

Claims become inspectable objects

Each locked fact carries a category, source span, normalized value when applicable, polarity, severity, and mandatory channels. That makes a changed time a checkable failure instead of a vague feeling.

Criticalhazard / location / start / action / prohibition
Importantcontact / URL / authority
Supportingaudience / context
03 / Verification

Four signals, transparent rules

01
Protected tokens

URLs, phone numbers, dates, times, timezones, and quantities are detected before drafting and checked after reinsertion.

02
Deterministic checks

Normalized dates, numbers, phone digits, URL domains, negations, and modal strength can hard-fail a draft.

03
Semantic checks

Paraphrases can pass, but missing scope, weakened obligations, changed timing, and contradictions return fail or review.

04
Supporting readability

English shows reading ease and grade estimates. Other languages require language-specific review rather than a pretend English score.

04 / Responsible AI

Sources ground. Rules check. People decide.

Today, arbitrary source analysis is local and deterministic; custom translations are never fabricated. A future live provider can sit behind the documented server-side boundary, but it is not configured in this build and would never become the sole judge of exact high-risk values.

Current local enginesource candidates / exact values / English rules
Planned provider seamserver-side drafting / schema validation / explicit metadata
Human ownedsource authority / language approval / publication decision
WORKED EXAMPLE

One word can change the result

Source fact: "Do not use unboiled tap water." A fluent draft that drops "not" can still look polished. The prohibition check treats that polarity loss as a hard failure and points to the exact output span.

PASS

Do not use unboiled tap water.

FAIL

Use unboiled tap water.

OPERATIONAL BOUNDARIES

What AlertProof does not claim

It does not publish alerts, replace qualified translators or interpreters, certify language accuracy, guarantee safety, or establish official alert authority or system integration.

Reference outputs are prepared evaluation data. Operational adoption requires authorized source integrations, qualified language review, security assessment, accessibility testing, and an accountable approval policy.