Verified:GitHub

jade-core-verification

Compare normalized semantic outcomes to verify JADE migration correctness.

1|Updated Apr 14, 2026

Search Tags:#runtime-validation #semantic-verification #migration-testing #jade #trace-normalization #acl-protocols #df-ams

Ready to run

npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jade-core-verification
Source: https://github.com/TheRealSeber/PolishedJADEite/tree/main/.claude/skills/jade-core-verification
Command: npx skills add https://github.com/TheRealSeber/PolishedJADEite --skill jade-core-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill validates JADE migrations by comparing normalized semantic outcomes, so you can confirm behavior has stayed intact even when log text changes across platforms or Java versions.

Core Features & Use Cases

Normalizes logs, traces, XML sniffer output, and JSON lines before comparison.
Extracts lifecycle, ACL protocol, and DF/AMS events into a canonical event model.
Supports optional documentation-driven scenarios and runtime consumer verification for end-to-end migration gates.
Use it when you need a final pass or fail check after batch rule application or when trace noise makes raw diffing unreliable.

Quick Start

Use the jade-core-verification skill to compare the baseline and migrated trace directories with the tolerance configuration and return a semantic pass or fail result.

Frequently Asked Questions about jade-core-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify JADE migration correctness when log text changes across platforms?▼

JADE migration correctness is verified by comparing normalized semantic outcomes rather than raw log text. This approach extracts lifecycle, ACL protocol, and DF/AMS events into a canonical event model, confirming behavior remains intact despite platform or Java version differences.

What is semantic trace normalization for JADE platform migration testing?▼

Semantic trace normalization extracts lifecycle, ACL protocol, and DF/AMS events from logs, XML sniffer output, and JSON lines into a canonical event model. This allows accurate comparison of baseline and migrated traces even when raw text differs.

Can I use normalized trace comparison for final migration gates and runtime consumer checks?▼

Normalized trace comparison supports final migration gates, trace comparison, runtime consumer verification, and evidence-based validation. It requires baseline and migrated trace directories along with tolerance configuration to return a semantic pass or fail result.

How do I compare baseline and migrated JADE traces when raw diffing is unreliable?▼

To compare baseline and migrated JADE traces with unreliable raw diffing, use a semantic verification skill. It normalizes trace noise and compares canonical events against a tolerance configuration, returning a clear pass or fail result.

Does JADE migration verification support ACL protocols and DF/AMS event scenarios?▼

JADE migration verification supports ACL protocols and DF/AMS event scenarios. It extracts these specific events into a canonical model, applying evidence-based validation across lifecycle, ACL, and DF/AMS scenarios for comprehensive semantic checks.

What are the limitations of raw log diffing for JADE trace comparison?▼

Raw log diffing for JADE trace comparison becomes unreliable when log text changes across platforms or Java versions. Trace noise disrupts accurate validation, requiring normalized semantic outcome comparison to confirm behavior has stayed intact.