Context stays within the right permissions
People and tools see only the context their role and task allow. A connected AI tool never receives more than the person using it.
When engineering work changes hands, people need to know where the information came from and who can rely on it. That’s the starting point for our approach to Collab.
Principles
People and tools see only the context their role and task allow. A connected AI tool never receives more than the person using it.
Team members, and the AI tools the organisation approves, can add evidence, notes and proposals to the work.
Only a person in the Context Approver role can turn working context into approved organisational knowledge. AI tools cannot approve context.
Every conclusion keeps a link to the code, ticket, document or session it came from, so anyone can check it.
Open questions, assumptions and disagreements are recorded as what they are, rather than presented as settled facts.
Repositories, editors, trackers, CI and communication tools remain the systems of record. cRUD Collab connects them rather than replacing them.
A governed memory model
Keep sources, observations, tests and unresolved questions visible while the team investigates.
Record what people accepted, which alternatives they rejected and which uncertainty still remains.
Carry approved context forward with its source, scope, access rules and responsible people still attached.
Human authority
A source, observation, model response, test result, proposal and approved decision do not carry the same authority. The system must preserve those differences instead of flattening them into one answer.
Approved AI tools can participate inside an authorised workflow, but people review conclusions, resolve conflicts and decide what becomes reusable organisational knowledge.
Human authority stays explicit
People and AI tools can help the team understand the work without gaining authority they were never given. Roles, approval scope and policy remain visible from the organisation level down to the context being reviewed. Teams defined around a product make access easier to manage, while Project membership, Context Approver assignments and explicit exceptions keep sensitive work bounded.
| Role in the work | What they can contribute | What they can approve | What remains visible |
|---|---|---|---|
| Participant | Questions, observations, source evidence and session input within the access they have been granted. | Nothing by default. Participation does not turn a suggestion into organisational truth. | Identity, activity, source references and the relationship between the contribution and the Session. |
| Contributor | Evidence, analysis, working context, proposed knowledge, draft decisions and recommended actions. | A contributor cannot approve their own proposal unless an explicit, scoped policy grants that authority. | Source, version, authorship, changes, uncertainty and every review state the proposal passes through. |
| Context Approver | Review comments, requested changes, conflict resolution and a documented approval decision. | Only the context categories, Products or Projects assigned to their approval scope. | The evidence reviewed, applicable policy, decision, rationale, approver and time of approval. |
| Product or Project Owner | Membership, context policy, inheritance rules, exception boundaries and accountable ownership. | Ownership does not automatically make one person the sole approver. Approval still follows the configured policy. | Role changes, policy changes, exceptions, approval assignments and the audit trail behind them. |
Questions
The cRUD Collab website explains how teams work with it, the principles behind it and the thinking that shaped it.