# Applying this context

## Task → project → Framework

Read the task and project entry to identify the required behavior, governance,
exact dependency release and relevant source locations. Match this pack to
JoinedWorkz **1.3.81**. Report conflicting release facts; do not reinterpret them
as permission to upgrade. Project facts remain in the project, not in this pack.

Use the [topic map](framework/index.md) for the current concern. Follow a detailed
link when its applicability, mapping or evidence is needed, not merely because
it is present. Read the relevant verification criteria before claiming success;
a criterion is neither an optional example nor proof that it ran.

## Ownership before an edit

Determine the effective Outlet and generator for the files being changed:

- authoritative model/configuration and manual source can be edited;
- overwritten generated targets must be changed through their inputs;
- first-cut targets are created when missing, preserved on generation and
  intended for manual completion/maintenance, including removal when obsolete;
- accepted versioned migration/schema history must be preserved;
- temporary/diagnostic outputs follow their declared cleanup lifecycle.

A filename or directory name cannot establish this classification. A manual
test of generated behavior remains manual. Routing into another module changes
location, not ownership. Detailed rules: [generation](framework/generation.md).

## Iterative work, scoped evidence

Begin a small model/generation probe once the immediate input and ownership
boundary is clear; there is no requirement to understand the whole repository
first. Prefer the project's generation-only command for mapping/signature
questions. Iterate model → generation → changed-output inspection → manual
integration throughout the task, then run the required consumer checks.

Source descent is useful for a specific unsupported, contradicted or unresolved
claim. Do not re-prove every applicable description by reading its implementation.
Distinguish syntax, transformation, generated code, compilation and runtime
evidence. Reopen only claims affected by new evidence or later edits.

Preserve existing relevant tests. Verify the final changed state, not an earlier
passing state. Consult [verification](framework/verification.md) for behavioral
criteria and failure routing. If the needed layer could not be checked, say so.

## Sources and release lookup

Current project source and executed evidence, interpreted using its exact
dependencies, can reveal that a documented claim does not apply. Report that
conflict; do not silently replace the contract with an observation. Examples
illustrate syntax/usage, never override requirements.

For deeper public documentation, resolve the exact version in
[the version catalogue](https://www.joinedworkz.org/docs/versions.json).
An available matching documentation checkout is the offline alternative.
No network lookup is required merely to re-confirm an already verified local
release for a source-backed local change.

Use available file/search/archive tools. When a read is truncated, obtain the
needed remainder; do not treat the prefix as the whole document. When a path is
absent, list/search its parent before retrying. Report missing access rather
than claiming unexecuted generation or tests.

The final report should name the changed boundaries, executed checks and
remaining limits. No lengthy pre-edit inventory or repeated progress report is
required by this Framework context.