Suggestions in service planned

Decision · Accepteddecisions/suggestions-in-service-planned

Context

The lock file records what a maintainer accepted or rejected, and the command line drafts a suggestion for every candidate expression (note: Candidate expression) it discovers. The first release of the service deferred suggestions: a reviewer read the candidates on the keyword page (note: Keyword page) and edited the lock file by hand.

Decision

The service drafts suggestions in its second release, on the suggestion review screen and under the same rule as the command line: a term the lock file rejects is never proposed again.

Consequences

  • The suggestion review screen reads the lock file before it lists a candidate
  • The first release keeps the manual review, so that nothing changes for a maintainer until the switch
  • The rejection rule becomes a contract of the service, versioned with it

Properties

Status
Accepted
Decided on

4 keys: the status and the date are authoritative.

See the neighbourhood map5 pages5Neighbourhood mapSuggestions in service planned

Neighbourhood map Suggestions in service planned

Distance1 hop

Neighbourhood map. The list below carries the same information as the map.existing pageword without a note

textual equivalent

Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.