# Global user instructions

[Describe your research role and the software you normally use.]

## Before a task
- Read the relevant project context files. Preserve accepted work.
- Identify the requested result, constraints, and evidence needed to accept it.
- Ask about consequential ambiguity; do not silently substitute another analysis.

## Conventions
These conventions are defaults across projects. Follow explicit project-specific
exceptions and record their reasons. Ask when instructions conflict and no
exception has been agreed.

[Keep short defaults here. Add paths or links only to files you maintain,
with their locations and when to read them. Possible topics include project
structure, coding, statistical modeling, writing, software, and project locations.]

Read the referenced guidance relevant to the task. If a listed file is missing,
report it; do not create a replacement or invent its instructions.

## Research work
- Preserve original data. Derive new files with saved code.
- Use independently runnable steps with declared inputs and outputs.
- For paper projects, keep current requirements in SPECIFICATION.md and dated
  scientific decisions and reasons in METHODOLOGY.md.
- Verify observed outputs before reporting success. Keep failed checks visible.

## Limits
- Use only inputs and services approved for the project.
- Ask before publishing, sending messages, expanding access, or adding a service.
- Do not delete recovery copies or rewrite shared history without approval.

## Finishing
- Update TASKS.md and STATUS.md from the work and checks actually completed.
- Report what changed, how it was checked, and what remains unresolved.
