# Shared Context Template

This is the team’s compact source of current truth. The orchestrator owns structure and version; specialists update only the fields affected by their work.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

~~~markdown
# Shared Project Context

## Context Version
[VERSION / DATE / OWNER]
## Project Name
[PROJECT NAME]
## Project Objective
[MEASURABLE FINAL OUTCOME]
## Target Users
[PRIMARY AND SECONDARY USERS]
## Current Phase
[PHASE + ENTRY/EXIT EVIDENCE]
## Scope
In: [IN SCOPE]
Out: [NON-GOALS]
## Requirements
[P0/P1 IDS + ACCEPTANCE]
## Constraints
[TIME, COST, PLATFORM, POLICY]
## Technical Decisions
[DECISION + REASON]
## Design Decisions
[DECISION + REASON]
## Completed Tasks
[TASK + EVIDENCE]
## Active Tasks
[TASK + OWNER + FILE/RESOURCE SCOPE]
## Blocked Tasks
[TASK + BLOCKER + REQUIRED DECISION]
## Known Issues
[DEFECT + SEVERITY + OWNER]
## Assumptions
[ASSUMPTION + CONFIDENCE + VALIDATION]
## Risks
[RISK + PREVENTION/DETECTION/RECOVERY]
## Files Changed
[PATH + AGENT + PURPOSE]
## Pending Approvals
[EXACT DECISION + APPROVER]
## Final Acceptance Criteria
[CRITERION + EVIDENCE SOURCE]
~~~

## Context Rules

- Prefer references and summaries over repeatedly copying entire files.
- Preserve decisions and supersede them explicitly; do not silently rewrite history.
- Never store secrets, unnecessary sensitive data, hidden reasoning, or unverified agent claims.
- Mark stale sections and conflicts. The current verified external state overrides memory.
- For this team, keep visible the outcomes communicate the offer within ten seconds, reach primary content in two navigation decisions, submit a contact request with verified confirmation, pass responsive, accessibility, SEO, and performance gates and risks unclear positioning, broken mobile navigation, silent form failure, oversized assets, missing semantic and search metadata.