Skip to content

Knowledge and context

Good knowledge
gets around.

Keep guides, decisions and discussions beside the work. The next person—or agent—gets the context, without asking you to explain it all again.

Explore Required Context

A good report
starts here.

Reporting guidelines

Give it a clear purpose.

Explain the decision this report should help someone make.

Keep the evidence close.

Link the source and record what still needs to be checked.

Illustrative guidance · knowledge ready for the next step

A home for what you know

The guide you need.
Where you need it.

Find the guide in the project. See who wrote it, follow the discussion and return to an earlier revision when you need to.

Example workspace · Synthetic content

Open full-size desktop view Open full-size mobile view
Tellenze Knowledge document, Release notes review guide, with Sam Rivera fixture author metadata and instructions for reviewing a draft.
The shipped Knowledge document view with synthetic review guidance in a disposable example workspace. The visible author and date are example fixture metadata.

Living documentation

Write it down.
Talk it through. Do something with it.

A document can be the start of a conversation, and a conversation can become the next task.

01 / WRITE

A shared place to start.

Create project and workspace documents. Organize them in folders, find them through search or Spotlight, and keep their revisions.

02 / DISCUSS

Keep the question in context.

Anchor a comment to a passage. Bring a teammate into the conversation and resolve the thread where it started.

03 / ACT

Give the decision a next step.

Turn a document thread into a work item. Keep the original discussion, outcome documents and evidence linked to the work.

Required Context

Give the next task
its reading list.

Choose the reviewed guidance a task needs. Required Context gives supported agent actions a clear set of documents and procedures to follow.

Agents retrieve and acknowledge the required material. Supported actions recheck current context and access before proceeding.

  1. 1

    Start with a shared baseline.

    Apply common guidance across the workspace, then add the context specific to a project.

  2. 2

    Choose the procedure that fits.

    Attach the procedure a task needs, such as a release or onboarding process. Carry that choice into repeatable work through templates.

  3. 3

    Keep the version that mattered.

    Review a policy before publishing it. Preserve the exact document revisions and a clear history when guidance changes.

Know where it came from

Who changed this?
Now you can see.

Work items, comments and document revisions retain their origin. See whether a contribution came from a person, an agent or an automated process, together with the member behind it.

Follow the source, the conversation and the decisions that shaped the current state. Give the next contributor more than a handover.

Access stays specific. A relation, milestone link or workshop invitation does not silently share private source material.

The next loop starts here

Save the lesson.
Spare the next person.

Bring the outcome of a review or retrospective into your documentation and required context. Give the next effort a better starting point.

See how learning becomes action

COME TAKE A LOOK

A little less busy.
A lot more together.

Curious? Leave your email. We’ll keep you posted on early access and what’s new.