Coordinator

needs verification

A coordinator manages relationships with researchers and can create an LT Work about another person. The institutional interpretation, such as a communications office or project lead, is still candidate knowledge in the stack glossary.

A coordinator group lets the team organize coordination work around a group. Changing the acting context is an administrator-only function, not a step coordinators need to learn.

A Connection has its own lifecycle, separate from an LT Work. Both approval timestamps make a connection active. Cancellation removes the link through soft deletion; decline records the researcher's refusal. Blocking overlays the previous state, so unblocking does not always make a connection active.

Connection states

100%

Drag to pan. Scroll or pinch to zoom. Keyboard: + / −, arrows, 0 to fit, Escape to close.

When a coordinator submits a work, the subject researcher approves before processing starts. A draft researcher receives an email link. Final confirmation still requires a real researcher account and an accepted connection for a coordinator-owned work.

The diagram shows the principal user paths. Code derives state from timestamps, including blocking and soft deletion, rather than storing one mutable status field.

For maintainers: source references

These references require repository access. Everything needed to understand this page is explained above.

• stack glossary
• acting-context resolver
• connection state calculation
• connection actions
• submission
• final publication gate