Architecture decision
Connect the decision to the relevant project and issues.
A product datasheet buyers can share without rewriting the story.
Context Linker brings together its scenario, Atlassian surface, compatibility, permissions, data, limitations, and verification links. Its concept status stays visible in print and exports.
Concept datasheet
Printable and exportable
No price, customer, review, installation, or badge is added to make this datasheet look artificially commercial.
Confluence · Context panel
Context Linker
Find related projects and decisions without leaving the page.
- Host product
- Confluence
- App surface
- Context panel
- Audience
- Knowledge, delivery, and governance teams
- Status
- Concept · unpublished
Problem, use cases, and observable capability.
The panel brings surrounding context into a dedicated area so the document stays readable and its links remain verifiable.
Launch file
Keep the brief, risks, and Jira tracking within reach of the page.
Knowledge base
Show related documents without cluttering the content.
Expected outcome
Find related projects and decisions without leaving the page.
A compatibility record that starts with what is not yet known.
Each app concept has a stable record for its intended host, proposed surface, distribution state, latest verification, degraded behavior, source, owner, and evidence status. Empty evidence stays explicit instead of becoming a compatibility claim.
- Schema version
- 1
- Registry reviewed
- Current scope
- 1 app concepts · no distributed versions
Compatibility record
Context Linker
Find related projects and decisions without leaving the page.
Evidence status: Absent before launch
- Product state
- Concept only — not published or distributed
- Concept revision
- 0.3
- Intended host channel
- Confluence · Cloud target only — not a tested compatibility statement · Connected Jira context intended — not tested
- Host edition or release
- No tested edition or release recorded
- Proposed surface or module
- Confluence context panel concept with intended Jira context — no published module manifest
- Distributed app version
- No app version is distributed
- Distribution channel
- No package, Marketplace listing, or installation channel
- Latest compatibility verification
- Never — no versioned build exists to test
- Verification result
- Not tested
- Technical support status
- Unverified — no supported host or app version range
- Test environment
- No compatibility test environment recorded
Degraded behavior
Not defined. It must be implemented and tested for each distributed version before launch.
- Record owner
- Product owner to assign before launch
- Record reviewed
- Stable record ID
- compatibility:context-linker:concept-0.3
This register inventories product intent and missing verification evidence. It does not prove Marketplace availability, Atlassian approval, a Forge manifest, supported scopes, or compatibility with any host release.
Context Linker data path, with every unknown left visible.
This app-specific view separates the browser demonstration that can be inspected today from a production path that has not been distributed, tested, or approved. It is an evaluation aid, not a deployed architecture.
Production path · not validated
Absent before launchEvery production node is derived from the current permission, data, and compatibility registers. No hosting region, provider, scope identifier, storage service, recipient, or retention period is inferred.
- Host contextNeeds confirmation
Confluence access remains a functional intention.
Read the current page · Search authorized spaces · Read selected Jira context · Save a confirmed relationship
- Intended Forge surfaceAbsent before launch
The placement is named; its distributed implementation is absent.
Confluence context panel concept with intended Jira context — no published module manifest
- Processing, storage, and egressNeeds confirmation
Each data category keeps its unresolved boundaries attached.
Authorized Confluence and Jira context · Confirmed relationships
- Intended return and deletionNeeds confirmation
The expected purpose is visible; production deletion still needs confirmation.
Authorized Confluence and Jira context · Confirmed relationships
Local demonstration · inspectable now
AvailableThe available path stays in the visitor’s browser.
This lane describes only the public showcase and its fictional dataset. It does not prove how a future Marketplace app will process customer data.
- Input
- Fictional dataset embedded in the public showcase
- Purpose
- Make the scenario interactive without customer data
- Storage
- Local demonstration-interface state
- Egress
- No remote product service connected in this showcase
- Deletion
- Demo reset or session close
- Execution location
- Viewer’s browser
Owner: addly showcase owner · Reviewed: · Inspect
Host context
Needs confirmation
Read the current page
- Intended scope
- Page content and metadata the person can already view
Search authorized spaces
- Intended scope
- Accessible pages in explicitly included spaces
Read selected Jira context
- Intended scope
- Jira projects and issues already accessible to the person
Save a confirmed relationship
- Intended scope
- An app-owned typed link between two authorized content items
- Source
- Read the current page
- Owner
- Product owner to designate before launch
- Reviewed
Intended Forge surface
Absent before launch
Confluence context panel concept with intended Jira context — no published module manifest
- Product truth
- Concept only — not published or distributed
- Distribution
- No package, Marketplace listing, or installation channel
- Verification environment
- No compatibility test environment recorded
- Source
- Product source
- Trust source
- Owner
- Product owner to assign before launch
- Reviewed
Processing, storage, and egress
Needs confirmation
Authorized Confluence and Jira context
- Purpose
- Search for and explain relevant relationships
- Storage
- Production architecture to be defined
- Egress
- To be confirmed with the published architecture and manifest
Confirmed relationships
- Purpose
- Restore explicit, auditable context
- Storage
- Planned app storage; architecture not finalized
- Egress
- No production recipient defined
- Source
- Authorized Confluence and Jira context
- Owner
- Product owner to designate before launch
- Reviewed
Intended return and deletion
Needs confirmation
Authorized Confluence and Jira context
- Intended result or purpose
- Search for and explain relevant relationships
- Deletion
- To be defined for removed content and uninstall
Confirmed relationships
- Intended result or purpose
- Restore explicit, auditable context
- Deletion
- Link deletion and uninstall need specification
- Source
- Authorized Confluence and Jira context
- Owner
- Product owner to designate before launch
- Reviewed
Permission intents
- 01Read the current page
- 02Search permitted spaces
- 03Read Jira only for accessible projects
Data and limitations
- 01Demonstration relationships
- 02No remote indexing active
- 03Host permissions still need validation
Every statement keeps a path to verification.
The demo shows the nominal behavior. Documentation, trust evidence, and known limitations cover what this datasheet alone cannot prove.
A shareable datasheet never replaces the source.
Use it to guide internal review, then open the demo, documentation, and evidence links before making a decision.