gonuShared rules, memory & audit
Keep team conventions and decisions available in the right scope, alongside recorded changes.
WHEN IT HELPS
Put it to work.
Carry project context between tasks and constrain tools/models consistently across a team.
Before you begin
- The appropriate Organization capabilities.
- A clear choice of personal, organization, team, project or supported repository scope.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Open Organization → Rules & policies. Select the audience/project and review supported model, tool and protected-resource restrictions.
In Shared memory, add a concise fact or architecture decision with the intended scope. Update the existing record when the decision changes.
Inspect available Audit history and the task’s actual use of context. Keep facts current and verify that important policies were applied.
Rules / Example project policy
THE USEFUL RESULT
What you should leave with.
Scoped reusable context and explicit controls with an audit trail where supported.
Know the boundaries.
- Free-form instructions are guidance, not proof of perfect model compliance; verify the output.
- Repository files, retrieved content and memory cannot grant permissions that the account or server policy denies.
IF SOMETHING DOESN’T WORK
A rule or memory is not visible.
Check scope, selected workspace/project and access capability. Review the current revision rather than creating conflicting duplicates.
Contact support