Context organised the way engineering work happens.

See how an engineering team could start with a problem, capture what it learns and leave enough context for someone else to continue.

The context model

From the Organisation to the Session.

Every piece of context has a clear home, so it reaches the people who need it and nobody else.

LEVEL 01

Organisation

The account that owns members, permissions and the knowledge the organisation has approved.

LEVEL 02

Products and Projects

Durable homes for engineering work. Context is scoped to the Product or Project it belongs to.

LEVEL 03

Rooms

Focused spaces where people and approved AI tools work through a problem, a review or a decision.

LEVEL 04

Sessions

Individual working periods inside a Room, each with its own participants, consent and record.

Three kinds of context

Evidence, working context and approved context stay distinct.

01

Evidence

Source material such as code, tickets, documents and session records, kept linked to where it came from.

02

Working context

What a team is exploring now, including open questions, options and draft conclusions.

03

Approved context

Knowledge a human Context Approver has reviewed and accepted as something the organisation can rely on.

How the context continues

Start with a problem. Keep what the team learns.

The workflow keeps the problem, evidence, decision and reviewed explanation connected from the first investigation to the next handoff.

Bring the context

Start with the technical problem and a permission-scoped Context Package containing the relevant code, prior decisions and evidence.

Work together

Use a persistent Room or instant Session to investigate assumptions, discuss the code and keep open questions visible.

Make the decision

Connect the chosen action to its source evidence, alternatives, trade-offs and responsible people.

Review what remains

Separate working evidence and proposals from conclusions the team has reviewed and approved.

Return with context

Let the next person, session or approved tool begin from what the team already knows.

What a useful handoff preserves

Leave enough context for the work to continue.

01

The decision

State what changed, what remains unresolved and who owns the next action.

02

The evidence

Keep the relevant code, tests, observations and alternatives connected to the decision they informed.

03

The boundaries

Record the access, approval and guardrails that still apply when another person or approved tool returns to the work.

A governed cRUD Collab handoff from a defined request and evidence through collaboration, human review and a trusted continuation state.
A handoff carries purpose, evidence, authority and the next action together, so work continues from a reviewed state.

Questions

Carrying a decision into the next Session

How do a Room and a Session fit together?
A Room is the continuing place for related work. A Session is a specific period of work in that Room, with its own participants, activity and outcomes.
What should the next person be able to find after a handoff?
They should be able to find the decision, the evidence that informed it and what remains unresolved. Include who owns the next step and any access or approval boundaries that still apply.
Where should a team begin when it returns to a problem?
Start with the latest reviewed context for the work. Check which sources or assumptions have changed, then continue from the open question rather than reconstructing the entire discussion.

Product status

cRUD Collab is in development.

The product has not been released. Explore the current design and product thinking, or contact the team about the direction.