Follow activity and improve document quality
Use Activity to understand what happened. Use Lint queue to find document issues and unanswered knowledge needs. These are useful even if you do not write code: “lint” means checking content against the enabled rules.
Follow recent work
- Open Activity and check the workspace.
- Choose a Period, Type, and optional Sub-type, such as Context, Review, Library, or Jobs.
- Read Pending, Advisory, and History.
- Follow a target link to the page, review, chat, or job involved.
Pending events may need review; advisory events need attention; history contains completed changes. These groups organize activity and do not replace a target's actual state. For example, check the Context published version before concluding that everyone can read a change.
The overview shows a limited window of newest events. Open a lane and use Load more to inspect older activity. “No matches on this page” is not proof that there is no older event.
A background job can show progress, stage, or an error. A failed attempt with a scheduled retry differs from a completed conversion. If Library remains stuck, capture the job's visible error and ask the administrator.
Inspect quality findings
- Open Lint queue and choose Findings → Open.
- Filter by Layer or Severity if the list is long.
- Open the target and read the finding and Suggested next step.
- Correct the actual page or source where needed.
- An Editor or Owner can run checks and update the finding's status.
Viewers can read permitted findings but cannot run lint or resolve them.
| Action | What it does |
|---|---|
| Mark reviewed | Records that the finding was acknowledged. |
| Record as fixed | Changes the finding's status. It does not edit the page. |
| Ignore finding | Removes it from the unresolved queue and keeps a record in resolved history. |
Read the confirmation before a bulk action. Some selected findings can succeed while others fail; check the result rather than assuming all were updated.
Fill knowledge gaps
Choose View → Coverage gaps to inspect queries that did not find usable evidence. For example, repeated questions about the launch reviewer can reveal that the plan never names one.
Open the linked finding if present, locate the right source, and write or update a Context page. Search or ask again to check whether the new material answers the question. A coverage gap identifies missing retrieval evidence; it is not an automatic instruction to invent an answer.
AI suggestions, when present, are proposals to inspect. They do not mean the content was automatically corrected or its factual accuracy certified.
Next: Context pages, Search and Ask, or Review.
Implementation reference: Activity labels and filters, Lint actions and status-only fixes.