The sharingu guide
Your tools.
One shared understanding.
Get to know the company brain: how work connects to people, decisions and goals.
See it in action
A bigger picture.
Work carries its why.
Make the work add up.
A company has goals. People and agents contribute work toward them. sharingu brings the work, its sources, its evidence and the decisions around it into a shared record.
The useful question is not just “what happened?” It is “what does this establish, which goal does it serve, and what do we do next?”
The model: goal · contribution · evidence · human decision · supported progress · context for the next contribution.
Agent R connects the context.
You bring the work.
Agent R serves your organization’s console and MCP connection. It helps connect, grade and explain contributions. People and their tools perform the work; humans retain decision authority.
This is an organizational context model. It does not mean every agent is hosted, scheduled or managed by sharingu.
Every claim needs its context.
A contribution may be a design, an engineering change, a finding or a proposal. Keep what was contributed, who supplied it, why it matters, the relevant references and the evidence together.
- Supported: evidence establishes a particular claim within a stated scope.
- Needs a person: a question requires human judgment.
- Incomplete: something required is still missing.
The homepage uses plain-language example labels. They illustrate these distinctions rather than reproduce every production status or screen.
A decision stays with its reasons.
In our fictional pilot workspace, a launch draft claims general availability. Its rollout note only supports a pilot. Maya records a decision to use pilot-only wording. The wider claim stays unproven.
A decision can settle what the team should do without making every underlying claim true. Keep the ruling and the evidence separate, and preserve unresolved questions for the next reader.
Shared understanding has boundaries.
The product model is organization-based, with project context and personal access. Your administrator provides your organization URL and access key.
Confirm the current beta’s permissions, key handling and operational fit during onboarding. For larger organizations, bring your requirements around identity, retention, export and deployment to the walkthrough. We do not imply certifications or capabilities that have not been established.
Share the work that belongs in the record.
Contribute relevant references and evidence deliberately. Do not include passwords, personal access keys or information you are not authorized to share.
Shared organizational memory means retained context for future work. It is not a claim that models are retrained on your contributions, or that every member can access every record.
Your tools. One company brain.
sharingu is a universal company harness: shared context and a contribution process that works with your native tools. Your chosen AI does the work; sharingu connects it to goals, evidence and human decisions through MCP.
The deployment model is one cloud-hosted worker per organization, with bound storage and project scopes. A compatible client connects with the organization’s MCP URL and a person’s access key. You do not need sharingu’s internal development pipeline to contribute.
Bring a compatible client.
Examples of tools with MCP support include ChatGPT, Claude and Gemini CLI. Their connection options, account requirements and authentication support differ. These links document client capabilities, not a completed sharingu integration test or a partnership.
Onboarding confirms the supported client, authentication and access scope for your organization. Model access remains with your provider. Hosting, storage and provider terms are confirmed separately during onboarding.
Close the loop, whatever the work.
A useful contribution begins with a goal and ends with a better starting point for the next person. The same pattern can support design, research, engineering, operations or go-to-market work.
- Brief: agree on the goal, scope and evidence needed.
- Contribute: attach the work, its author, sources and unresolved questions.
- Review: let the responsible person record the decision, its reason and limits.
- Carry forward: retain the context and turn the remaining question into the next brief.
Download the contribution loop starter templates. This Markdown pack includes a goal brief, contribution record, human decision and next-step template. Adapt it as an instruction manifest for your chosen tools. It describes a process; it does not execute agents or grant them authority.
Connect the cost.
Understand the outcome.
Follow the resources behind a contribution, the person responsible and the goal it supports. Choose the measures that help your organization make its next decision.
What went in?
Tokens, time and review cycles, attached to the work they supported.
Where did it go?
Model charges, partner costs and other expenses, with a named budget owner.
What moved forward?
The human judgment, its reasons and the next contribution it makes possible.
What changed?
Progress against the goal, supported by evidence and a meaningful baseline.
Explore the people and finance view
How to read a measurement
Each measure needs a source, unit, time window and status: observed, reported, estimated or unknown. If a tool does not report usage, the record remains unknown rather than zero.
Keep an attributed model charge separate from the complete cost of an outcome. ROI needs a measured outcome, a baseline, attribution and all relevant costs. Until those are available, it is not established.
Fields, collection methods and integrations are confirmed during beta onboarding. The website’s sample records do not represent live cross-provider metering.
A shared goal across organizations.
The company model brings employees, partner organizations and their agents into scoped projects. A person can hold several roles: contributor, project lead, finance owner or decision maker. Contributions retain both the person and the role they acted in.
Slack and Telegram are collaboration surfaces in this product direction, alongside native AI tools and web/mobile access. A channel conversation can supply context for a contribution; project membership and authorization govern what is shared. Available channel connections and cross-organization access are confirmed during setup.
From budget to person to outcome.
Map company goals to project budgets, accountable people and funded contributions. Separate model usage, external partner costs and other expenses. Finance can follow the source of a charge while management reviews its purpose and the outcome it supports.
The public product walkthrough uses authored scenarios and sample records. They show the intended relationships and process, rather than customer activity. Available views, measurement collection and integrations are confirmed for each beta setup.
Start with your organization.
- Request beta access or a walkthrough.
- During onboarding, confirm the supported client and organization setup.
- Receive your organization’s MCP URL and your personal key from its administrator.
- Configure the supported client and contribute a real piece of work with its references.
Private beta: the website’s example workspace is fictional. Goal mapping is part of the product direction; exact goal views, owner/deadline fields and workflow capabilities are confirmed during onboarding. Never paste an access key into the website request form.