At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Source artifact | Assign a stable artifact identity | Shared artifact record | Source identity must remain recoverable |
| Immutable source revision | Create a revision record and hash | Revision-bound evidence | Mutable aliases are not sufficient |
| Observed term or implementation | Normalize it as a subject and usage | Searchable evidence relationship | Parser and indexing limits apply |
| Imported or approved relationship | Add a typed trace edge | Governed cross-source path | Candidate links remain separate |
How it works
- Confirm the source path is production-enabled.
- Capture its stable artifact and revision identities.
- Preserve source provenance and availability state.
- Normalize supported subjects and usages.
- Review declared relationships.
- Deposit only approved or imported links as governed evidence.
Example
A Confluence page and an uploaded DOCX file can each retain their own source identity while using shared artifact and revision fields. Their evidence can be searched under one model. A generic connector contract alone does not make an additional provider production-enabled.
What this does not mean
A shared schema is not a connector catalog. Every public integration claim needs deployed runtime wiring, manifest permissions, a user-visible workflow, and verified source behavior.
Related questions
Next step
Require stable revision identity before adding a source to the evidence model.
View on Atlassian Marketplace