Consider renaming CONTEXT.md

[isolomatov-gd]

CONTEXT is now overloaded word, consider using other terms: GLOSSARY, BUSINESS-CONTEXT, etc.

[github-actions]

Rosetta Triage

Classification: instructions, needs more work — this is a naming-convention concern inside Rosetta's own instruction set (skill/workflow filenames and workspace-file conventions), not a generic docs typo.
Priority assessment: Low — real inconsistency, but no functional breakage and a large blast radius for a cosmetic fix.

Findings:

• "Context" is overloaded, but differently than described: the load-project-context skill covers both business and technical context (per its own description), while the file-naming convention reserves the -CONTEXT.md suffix for business-only content (docs/CONTEXT.md's own header: "no technical implementation details").
• instructions/r3/core/workflows/arrange-workspace-flow-technical-context.md is a workflow phase file named *-technical-context.md, but its steps write to docs/ARCHITECTURE.md, never to a *-CONTEXT.md file — only the sibling arrange-workspace-flow-business-context.md writes to docs/CONTEXT.md. That specific filename/output mismatch is the sharpest concrete inconsistency found.
• docs/CONTEXT.md itself uses "context" generically ("context engineering") in the same document that defines the specific CONTEXT.md file convention — the word is doing double duty by design across the docs.
• The skill was already renamed once for a similar reason: r2's load-context became r3's load-project-context to reduce ambiguity, so this pattern has partial precedent for a fix.

Caveats:

• A full rename (CONTEXT.md → e.g. BUSINESS-CONTEXT.md) touches instructions/r3/core/ broadly: all mode files, bootstrap-alwayson.md, orchestration skill, every init-workspace-flow*/arrange-workspace-flow* phase file, prompt-authoring references, plus docs/ARCHITECTURE.md and docs/CONTEXT.md themselves — not a one-file edit. It also breaks the convention for any already-initialized target repository's docs/CONTEXT.md.
• The ~250 files under plugins/ are generated output and would auto-regenerate via rosettify-plugins; they aren't extra manual work but do widen the diff.

Clarifications:

• Of the two suggested alternatives, GLOSSARY doesn't fit — that role is already served by gain.json's vocabulary field. BUSINESS-CONTEXT does fit, matching docs/CONTEXT.md's own self-description.

Suggestions:

• Consider scoping this narrower: fixing the arrange-workspace-flow-technical-context.md → ARCHITECTURE.md filename/output mismatch alone is small and high-value, versus a full repo-wide CONTEXT.md rename which is large and mostly cosmetic.

Questions:

• Is the goal to rename the workspace file (docs/CONTEXT.md) itself, or just to fix the technical-context phase file that doesn't match its own output target? These are different-sized changes and the issue doesn't distinguish them.

Not actionable as filed — needs a decision on scope (full rename vs. targeted phase-file fix) before implementation.

Automated triage by Rosetta agent