Delivery and claim commands

fa delivery makes the migration method repeatable without turning internal delivery state into public documentation or unsupported claims. These commands are local, deterministic checks; governed engagement mutations still use the normal authenticated commands.

Qualify a source engagement

Create a credential-reference-only qualification file with source and target authority, representative-data approval, object count, required/excluded surfaces, network shape, RPO/RTO, and cutover/rollback owners.

fa delivery preflight --file qualification.json

The command returns assessment and cutover-design readiness separately. Missing source authority, target authority, or representative-data approval blocks assessment. Missing cutover or rollback owners blocks cutover design. Private-link and offline shapes add a connectivity rehearsal instead of pretending online dependencies are available.

Generate the delivery kit

fa delivery kit \
  --file qualification.json \
  --json > delivery-kit.json

The generated kit contains contracts for:

• source qualification;
• assessment report;
• target blueprint;
• wave plan;
• human-residue estimate;
• migration certificate;
• cutover and rollback runbook; and
• measured value report.

It also lists factory setup, client adapter, human remediation, cutover assurance, modernization, and hypercare playbooks plus backup/restore, signer rotation, connector rotation, retention/export, disaster recovery, and upgrade/rollback operations.

Validate a connector operating envelope

fa delivery connector-policy-check --file connector-policy.json

A promoted connector policy must bound concurrency, rate, quota, cost, timeout, retry classes, and circuit breaking. Checkpoint and reconciliation are mandatory. The schema fixes non-idempotent effects at one attempt.

Gate an external value claim

fa delivery claim-check --file external-claim.json

Eligibility requires at least three engagements, at least ten comparable observations, medium or high confidence, observed methods beyond expert estimates alone, a versioned cohort and release generation, exclusions, limitations, a reviewed methodology, and an immutable evidence digest. A rejected packet exits nonzero and emits exact blockers.

This is stricter than an engagement-scoped client value report. It exists for aggregate external language. Never hard-code “60% faster” into product material.

Check activation evidence

fa delivery activation-check --file activation-evidence.json

Requirements are data, not hard-coded program assumptions. Record each credential category's current required and observed counts, approved outcome references, thought-leadership references, repeatable demo evidence, reviewer, and evidence digest. Repository tests do not count as customer outcomes.

Scan public developer content

fa delivery public-check --file public-document.md

The scanner blocks known private path, deployment, evidence-ledger, credential, and client-identity patterns. It complements review and CI; it does not declassify a document or replace client approval.