Capture Project Constraint

Return only the constraint and its direct implications.

Workflow

1. Identify the proposed externally imposed fact or invariant.
2. Validate unstable or external claims against current primary sources.
3. Narrow the scope precisely: name the relevant product, environment, mode, or lifecycle boundary.
4. Separate confirmed facts from inference. Label an inference explicitly or omit it if it is not needed.
5. Separate the constraint from observations, candidate solutions, trade-off analysis, and open questions.
6. Write the result using the format below.

Accuracy rules

• State the constraint directly, without recounting the user's prior belief, any confusion, or the research journey.
• Do not turn a scoped limitation into a universal claim. For example, distinguish ephemeral sandbox state from persistent connected folders when that exception matters.
• Include scope and exceptions only when needed to keep the statement accurate.
• Add a compact structural example only when it materially clarifies the invariant.
• Keep implications concrete: describe what the project cannot assume, must preserve or provide, or must handle.
• Limit implications to two to four bullets. Do not drift into a long comparison of solutions.

Output format

# <Short, precise constraint heading>

## Constraint

<State the externally imposed invariant or confirmed fact directly. Distinguish any necessary inference. Include a compact structural example only when it clarifies the constraint.>

## Implications for <project or product>

- <What the project cannot assume, must preserve or provide, or must handle.>
- <A second concrete implication.>

Sources:

- [Authoritative source](https://example.com)

Include Sources: with authoritative links when research or validation was needed. Do not add citations that do not directly support the constraint.