Skip to content

WATCHLIST.md

Latest commit

 

History

History
75 lines (53 loc) · 2.5 KB

WATCHLIST.md

File metadata and controls

75 lines (53 loc) · 2.5 KB

Watchlist

Status: Draft 1
Last updated: 2026-03-07

This file tracks candidates that may belong in the AI Capability Reference but are not yet clearly in scope.

The watchlist exists to keep scope decisions explicit.

Use it for:

  • borderline consumer products
  • rising model families
  • open/local tools that may deserve first-class treatment later
  • products used in teaching or demos before they clearly meet the broader inclusion bar

Do not use it as a dumping ground for everything interesting.

How To Use This File

Add a watchlist entry when:

  • the thing may belong, but evidence is still incomplete
  • public usage or visibility is unclear
  • the ontology placement is not settled
  • the product is relevant to teaching, but the long-term case for inclusion is still uncertain

Move an item out of the watchlist when one of these becomes true:

  • it clearly belongs in the ontology and active data
  • it clearly does not belong in scope
  • it was a transient curiosity with no lasting relevance

Decision Standard

A watchlist item should usually answer these questions:

  1. What kind of thing is it?
  2. Can an ordinary person sign up for it, access it, or run it locally?
  3. Is there evidence of meaningful public usage, visibility, or teaching relevance?
  4. Would adding it help users compare capabilities, access, or deployment choices?
  5. What evidence is still missing?

Suggested Workflow

  1. Add a short entry below.
  2. Gather sources with Perplexity or another research workflow.
  3. Compare the findings against SCOPE.md and ONTOLOGY.md.
  4. Promote to active records only when the case is clear enough to maintain.

Entry Template

## Candidate Name

- Entity type:
- Why it might belong:
- Why it might not:
- User path:
- Evidence to collect:
- Current decision:
- Notes:

Current Watchlist

Intelligent Internet

  • Entity type: Provider or product, not yet settled
  • Why it might belong: Potentially relevant to local/open model teaching and demos
  • Why it might not: Product boundary, public usage, and ontology placement are not yet clear
  • User path: Needs clarification on whether an ordinary person signs up for a product, accesses a model endpoint, or uses it as part of a local workflow
  • Evidence to collect: Official product pages, access path, pricing/access model, whether it is consumer-facing, whether it materially changes deployment choice
  • Current decision: Watch
  • Notes: Good example of why the watchlist should exist before adding a provider or product record