ADVANCED STUDIO · INTEGRATOR
Plan a migration without duplicating rules
Paste a proposed catalog in JSON. The studio checks responsibilities, schemas, lifecycle, risk, and migration evidence.
01 · Contract
Name, title, description, and uniqueness.
02 · Schema
Types, properties, required fields, and limits.
03 · Operation
Cancellation, risk, confirmation, and output.
LOCAL INPUT
Catalog in JSON
Use an array of descriptors. Since functions don't exist in JSON, declare executeBehavior and operational evidence separately.
Nothing is sent to a server, registered in document.modelContext, or executed.
0out of 100
No diagnosis
Catalog quality
Load the example or paste your JSON to get started.
0
Passed
0
Considerations
0
Failures
Findings will appear here, prioritized by impact.
What this scanner doesn't prove
- • native browser support;
- • backend authorization;
- • security of the execute code;
- • real quality without execution tests.
Next scanners in the course
- • Integrator: multipage crawler and sitemap;
- • Agent Developer: discovery and controlled execution;
- • Expert: security, evals, and observability.