Rated factory or platform

Factory.ai (Droid + Missions + QA)

Ratings 2026-10

Droid Missions, AutoWiki and connected QA provide feature plans, freshness indicators and pull-request test evidence.

Assessed configuration Droid with Missions, AutoWiki, the generated QA skill, the documented GitHub Actions pull-request QA workflow and pull-request review configured. Factory Enterprise Airgap is a separate runtime; the complete connected QA workflow is not established there. The private-preview Software Factory dashboard and Release stage are excluded.

Ratings

Evidence: 7 of 7 ratings cite primary sources; 1 are unverified (?).

• Lifecycle traceability

  L2 met: Mission feature criteria link to commits and each feature is validated; L3 maintained version-aware lifecycle links remain unproven.

• Versioned system design

  L2 met: an approved, resumable integrated feature/milestone target is maintained; L3 selected-version states and delivered-code design binding are missing.

• Tracked drift resolution

  L1 met: AutoWiki shows freshness indicators and version history; L2 retained affected-area finding, correction and repeat review are missing.

• Change impact and alternatives

  L1 met: Mission planning defines constraints, features and success criteria before code; L2 scoped impact plus constrained alternatives are not documented.

• Requirement test results

  L2 met: documented success criteria generate executable test flows and PR reports; L3 passed/failed/missing/unverified requirement states for tested code are missing.

• Delivery audit trail

  L2 met: PR-triggered QA artifacts/reports and PR reviews are associated with workflow commit; L3 governing requirement/design versions and waiver references are missing.

• Process portability ?

  Droid airgap runtime is documented but continuity of the complete connected QA workflow is not; Private Preview dashboard and Release are excluded.