Documented today
The public starting point is an advisory local workflow for one exact validated build profile. It connects a prepared compiler snapshot to validation, a whole-program reachability scan, canonical JSON, and an explanation for one exact subject.
No public binary is offered yet. What is available today is the inspectable operating contract: how evidence enters, how outcomes stay distinct, and when the answer must remain unknown.
Validate one snapshot
doctor checks the manifest, toolchain, compiler data, analysis worlds, and requested capability before a scan is trusted.
Review canonical results
scan preserves stable identities, structured outcomes, and the evidence boundary in human output or canonical JSON.
Explain an exact subject
why follows the same immutable manifest and canonical subject instead of guessing from a name or source location.
Qualifying the next boundary
The next horizon is breadth with the same standard of proof. Additional build profiles, semantic relationships, and operating conditions must be tested as their own boundaries; confidence from the current profile is not silently transferred to them.
This work strengthens the local analyzer before any collaborative surface depends on it. Incomplete evidence must remain visible, and unknown remains a valid result.
Profile coverage
Qualify more toolchain, target, product, and build shapes without weakening snapshot identity.
Semantic coverage
Extend supported Swift relationships only with fixtures and explicit conservative boundaries.
Operational confidence
Measure performance, cancellation, recovery, and deterministic output under representative workloads.
Planned team workflows
Shared review and a hosted service remain planned, not available. The direction is to carry the same exact identity, evidence, explanation, and unknown semantics into collaboration rather than replace them with a bare pass-or-fail badge.
Accounts, billing, source upload, organization controls, retention, service boundaries, prices, and dates are intentionally absent until those systems and policies exist and can be reviewed.
Shared review
A future review surface would keep findings and explanations attached to the qualified snapshot that produced them.
Hosted analysis
A future service would need an explicit source, metadata, execution, retention, and deletion boundary before launch.
Customer controls
Any organization workflow would require real access, policy, audit, and lifecycle contracts—not placeholder screens.
How a capability becomes current
A roadmap label is not enough. Swift Analyzer treats availability as the end of a small evidence chain: define the behavior, qualify its boundary, then publish the same meaning across the CLI, documentation, and machine-readable output.
1. Define
State the exact input, output, identity, failure, and unknown semantics before implementation is presented as product behavior.
2. Qualify
Exercise the boundary with focused fixtures, representative corpora, and operational evidence proportionate to its risk.
3. Publish
Align human guidance, canonical JSON, status language, and limitations so no surface implies more maturity than another.
What this roadmap does not promise
Roadmap horizons express sequence and product intent. They are not selectable plans, commitments, or evidence that an unavailable capability is already being served.
No launch dates, pricing, signup, download, hosted analysis, or blocking CI defaults are promised here. Until a boundary is qualified and published, use only the current local documentation and preserve its advisory outcome.