Atlan Fact Verification Gate
Create a lightweight verification checkpoint before behavior-changing decisions.
Workflow
- •Classify task as
build,modify,test,review, orrelease. - •Read source guide:
../_shared/references/verification-sources.md. - •Verify only what is required for the current decision:
- •SDK behavior for runtime/data-path decisions.
- •CLI behavior for scaffold/run/test/release commands.
- •Resolve SDK evidence using portable fallback order:
- •local checkout (if present)
- •installed package source
- •remote source/docs
- •For build tasks, classify app quality tier (
quickstart-utilityorconnector-standard) using../_shared/references/app-quality-bar.md. - •Create
verification_manifest.jsonusing../_shared/assets/verification_manifest.jsonas template. - •Validate manifest:
python ../_shared/scripts/validate_verification_manifest.py verification_manifest.json - •Continue if status is
ready; otherwise resolve unknowns or ask user. - •If CLI mismatch is found, append proposal entry to
../_shared/references/cli-change-proposals.md.
Output Contract
- •Produce
verification_manifest.jsonfor non-trivial behavior changes. - •Record what was inspected, including exact command/flag facts when command behavior matters.
- •Never edit SDK or CLI repositories.
References
- •Checklist:
references/checklist.md - •Artifact schema:
../_shared/references/artifact-templates.md - •Quality bar:
../_shared/references/app-quality-bar.md - •Multi-agent compatibility:
../_shared/references/agent-surface-compatibility.md