Product in Sharely.ai
Product is the part of the Knowledge app that keeps the content describing your product in step with the product itself. It watches the systems where the product is built, works out what each change means for your website, documents and sales material, and hands a person a specific edit to approve.
Why it exists
Product and engineering run on one clock: commits, branches, releases, backlogs. The content that represents the product runs on another. Keeping the two aligned is usually done by hand, in spreadsheets and emails, and it lags, because the source of truth for what the product does is the code, and the people maintaining the content do not read it.
Product closes that gap one change at a time. Rather than auditing everything you have published, it starts from what just changed and asks what that change made wrong.
How it works
- Connect the systems. GitHub for the code, and Asana or Jira for the plan.
- A change arrives. A pull request is merged, a release is tagged, or a task or issue ships.
- The agent reads it and decides what it did in product terms. A change no customer can see is recorded as internal and notifies nobody.
- The agent compares it with your content. Every page, document and resource in your workspace is a candidate.
- Your team is told. If Slack is connected, Sharely posts a blocker as soon as it is found, a digest when you ship, and a roll-up of what is waiting.
- A person decides. The result waits in Changes or Gaps until someone accepts, edits or dismisses it. Nothing is published automatically.
The building blocks
| Concept | What it is |
|---|---|
| Connection | One GitHub account, Asana workspace or Jira site linked to your workspace, with the roles that may see what it produces. |
| Change | Something that happened in a connected system: a merged pull request, a commit on a watched branch, a release or tag, or a task or issue that shipped. |
| Work item | An Asana task or Jira issue. It says what was meant to ship, and is matched to the code that references it. |
| Change report | What the agent found for one change: the page affected, the sentence that is now wrong, a proposed edit, and the code it is cited to. |
| Gap | A user-facing change no content describes yet, with the nearest page and a draft paragraph. It is a finding, not silence. |
| Capability | Something your product can do, in product language. The agent names them as it reads changes, and they accumulate into your product's vocabulary. |
| Coverage | For each capability, whether your content describes it and whether the description is still true. |
| Release | A tag or release on a watched repository, with the changes that shipped in it and what is outstanding before you announce it. |
Where to find it
Product sits in the Knowledge app's navigation, with one screen for each part of the work:
| Screen | The question it answers |
|---|---|
| Connect | What is linked to this workspace? |
| Repositories | What is happening in the code? |
| Work | What is happening in the plan? |
| Changes | Which reports need a person? |
| Gaps | What shipped with nothing written about it? |
| Ask | What changed this week, and which pages does it touch? An agent answers across changes and content, citing both. |
| Capabilities | What can the product do, according to the changes read so far? |
| Coverage | Which capabilities does the content describe, and is it still right? |
| Releases | What shipped in each release, and is it ready to announce? |
| Slack | Where do the findings get posted? Opened from Connect, it sets the channel and previews each kind of message. |
How it relates to the rest of your workspace
- It reads your knowledge. Changes are compared with the content already in the workspace, so an empty workspace produces only gaps.
- It writes back. Reports and the capability vocabulary are stored as workspace knowledge, so the Ask screen and your workspace agents can retrieve them.
- It respects roles. Everything a connection produces carries the roles chosen for that connection, by default Product truth. A person holding none of them sees none of it, and visitors to your public sites never hold them.
What it is not
- Not an autopilot. The system finds and drafts; a person decides and publishes.
- Not a copy of your code. Sharely reads your repository through GitHub's API when a change arrives, and keeps only metadata and short excerpts. See Data and privacy.
- Not a sales tool. It covers what is happening in product and engineering. Your CRM and your sales conversations are not read.
- Not yet a full map of your product. Capabilities are learned from changes rather than from reading the whole codebase, so a capability no change has touched is not listed, and Coverage only counts pages a change report has looked at. See Coverage for exactly what it can and cannot see today.