Discovery, Ranking & Currentness
Discovery must reflect the current truth of a specific Product version.
Listing states
AIPS Marketplace uses the following conceptual listing states:
| State | Meaning |
|---|---|
| Active | Current, trusted, and available for normal discovery/acquisition |
| Restricted | Current but access or consumption is policy-restricted |
| Suspended | Temporarily unavailable for acquisition/consumption |
| Historical | Retained for lineage, audit, reproducibility, or prior-version discovery |
| Retired | End-of-life and unavailable for new consumption |
Current AI Product eligibility
An AI Product listing cannot be Active or Restricted as a current AI Product when AI Qualification is STALE, REVALIDATION_REQUIRED, or INVALID.
Likewise, an invalid, revoked, or materially stale trust state must not be hidden behind a positive marketplace badge.
Historical semantics
AIPS preserves version history rather than rewriting it.
If Product A v1 qualified as an AI Product through Qwen and Product A v2 becomes a non-AI deterministic Product, then:
- the historical
v1AI Product listing remains discoverable as historical evidence; v2must be classified according to its own PIN and current constitution;- the marketplace must not transfer the
AI Productlabel fromv1tov2by identity continuity alone.
Search and ranking
Search ranking may use Product relevance, quality, adoption, cost, or organizational policy, but trust semantics must remain explicit.
A marketplace should support filters for:
- listing kind;
- APT;
- IC;
- PU;
- MO;
- IE;
- AR;
- EM;
- RT;
- qualification status;
- trust status;
- availability/access policy.
Invalid or historical records should not be silently mixed into current-product results unless the consumer explicitly requests them.
COVP consumer evidence
Stage 9 permits an optional marketplace consumerEvidenceSummary linked to an authoritative COVP record. The summary may expose observation window, intended-use fitness, value-evidence currentness, usage-evidence currentness and feedback count. It is evaluative context for consumers, not Product ontology.
A marketplace must not rank or reclassify Product Family, APT or R0-R4 risk from popularity, usage or ratings.