Canonical page: https://tellenze.com/help/required-context

Configure required reading and procedures

Publish versioned policies, inspect task requirements, and resolve blocked context or waivers.

What Required Context does

Required Context assembles the reading an agent needs before supported changes. Policies select exact document revisions; procedures identify the kinds of work that need additional reading. An ordinary document link remains useful context, but does not make its contents mandatory.

The feature may be disabled or limited to selected scopes. Open Knowledge, then Required Context, or a project's settings and its Required Context tab. The manager has Context, Policies, and Procedures tabs. Choose the scope before making changes.

Workspace administrators manage workspace policies and the procedure catalogue. Active members with access to an active project can manage that project's policies. Project policies add to inherited workspace requirements. Team-owned work uses workspace policies and selected procedures rather than a separate team-policy editor.

Check the reading for a task

In Context, enter a work-item identifier in Preview for task, then choose Preview required reading. The result identifies matched policies, pinned revisions, and current availability. The task detail also shows Required Context health and its assigned procedures where enabled.

Required reading is ready means requirements can be delivered. No required reading applies, Current requirements are waived, Required reading needs attention, and paused or disabled states explain different situations; check the displayed details rather than treating every empty list as the same outcome.

A preview does not create a delivery receipt. For supported agent actions, the agent resolves the requirements, retrieves every part of the pinned reading, and acknowledges receipt before the change. Acknowledgement records retrieval, not proof of understanding. Changed policies, target scope, procedure assignments, expiry, or access can require fresh retrieval and acknowledgement.

Create, review, and publish a policy

1. In Policies, choose New policy. Enter a descriptive name and a permanent lowercase Policy key.
2. Under Applies to, choose Every task in this scope for baseline reading or Selected procedure for additional reading tied to that procedure.
3. Use Add reading entry to select document revisions. Add a short briefing explaining relevance and use the arrows to set reading order. Workspace policies use workspace documents; project policies can use workspace documents and documents from that project.
4. Choose Save draft, then Review draft. Read the exact pinned revisions in the review dialog.
5. Choose Publish reviewed version while that review remains current. Publishing enables the version and requires existing acknowledgements to refresh.

Saving a document's next revision does not silently replace a policy's pinned revision. Use Create new draft to select updated reading, then review and publish it. The existing published version stays active while you prepare changes. Version history shows earlier draft and published versions.

Manage overlapping guidance and policy status

Use an optional Conflict slot when policies address the same topic. Different reading in one slot needs an explicit Supersedes entry selection; the application does not guess which instruction should win. A project policy can explicitly supersede relevant inherited workspace reading.

Pause stops an enabled policy from applying. Enable published version resumes its published version. Archive removes a policy from normal active management; select Include archived to find it and Restore when needed. Restoration does not automatically enable it. A workspace-wide emergency pause is different: supported gated work remains blocked until an administrator resolves that state.

Assign procedures and temporary waivers

An administrator creates named procedures in the workspace Procedures catalogue. Keys are permanent, while names and descriptions can be edited. Assign applicable procedures in the task's Procedures section; task templates can also supply them. The task records whether a procedure came from a template or was selected manually. Retired procedures remain in history and cannot be newly selected. Pause published policies for a procedure before retiring it.

For an authorized exception, the task's Temporary waivers section lets a manager select policy versions, explain the reason, set an expiry within the displayed limit, and Issue waiver. Workspace policies require a workspace administrator. Waivers apply only to the selected task and versions; reading resumes on expiry or Revoke waiver. A newly published policy version is not automatically covered by an older waiver.

Resolve blocked reading

If a pinned source is unavailable, check its archive state and scope, then update and republish the policy with appropriate reading. Resolve conflicting slots with explicit supersession; shorten or split excessive policy briefings when the preview reports a delivery limit. Use Reload Context after a policy conflict and review the current draft again before publishing. An agent reporting a missing, stale, or incomplete receipt must resolve, retrieve, and acknowledge the current requirements again through its active connection.