Example: Linear ticket to project context.
Updated 2026-06-07 · Agent-readable markdown available
How a Linear issue becomes scoped Ambience project memory.
A Linear ticket can produce a project-scoped decision memory that future engineering agents retrieve before implementation.
- The ticket remains the source of record.
- Ambience stores the implementation constraint.
- Project scope prevents accidental org-wide generalization.
Source to memory
Source artifact
Linear issue AMB-184
Use WorkOS org membership as the access boundary for the new connections surface.
Use WorkOS membership for connections access
The connections surface uses WorkOS org membership as its access boundary unless an admin access decision supersedes it.
Controls
- Source
- Linear ticket remains the planning record
- Scope
- Project scoped to avoid turning a product constraint into an org rule
- Freshness
- Review when the admin model changes
Future reuse
- A coding agent retrieves the access decision before editing the route.
- A PM can inspect the source ticket when revisiting the connections roadmap.
Source
Linear issue: use WorkOS org membership as the access boundary for the new connections surface.
Memory
Decision: Use WorkOS org membership as the access boundary. Scope: project. Source: Linear issue. Future agents should preserve this unless an admin access decision supersedes it.