TaskContext

TaskContext is the shared issue tracker: projects, issues, dependencies, comments, and evidence, for a team that shares one workspace. People and their assistants use the same users account, so the person an issue is assigned to is the same identity the assistant acts as.

The browser reader at / is read-only. Changes go through the records API. The first version is a fresh team workspace: no import from other tools, no private projects, no sprints, and no in-app notifications. A note to a colleague is NotifyContext.

A project has a short key, such as APP. Issues in it are numbered APP-1, APP-2, and so on. An update sends the revision the assistant last read. If someone else saved first, the write comes back as a conflict and the assistant reads again. Issues are archived or cancelled. They are not deleted, so the history keeps its number.

The records

flowchart TB
  project[Project]
  issue[Issue]
  dep[Depends on another issue]
  comment[Comment]
  evidence[Evidence reference]
  history[Change history]

  project --> issue
  issue --> dep
  issue --> comment
  issue --> evidence
  issue --> history

sequenceDiagram
  participant Agent as Person's assistant
  participant SQL as SQL
  participant API as Records API

  Agent->>SQL: list open issues in the project
  SQL-->>Agent: rows, including dependencies
  Agent->>API: comment, or attach evidence, as that user
  API-->>Agent: saved record

user_directory shows ids and display names to signed-in people. It does not show email addresses or login fields.

Google sign-in can create the account when just-in-time provisioning is on. Operators can also require specific accounts at startup. Deletion is blocked. Disable the account to remove access and keep assignments pointing at a real person.