context-docs

Topics in the source

• Context Docs
• Choose the operation
• Visualize progress in Markdown
• Make the smallest useful update
• Optional event capture

Keep the project's Markdown useful to the next reader. Start with its instructions, README and context entry point, then follow relevant sources. Identify a project mismatch before editing; ask only when the target or a consequential decision is unclear. Preserve existing layouts and concurrent edits. Audit: report concrete gaps and source locations; leave project files unchanged. Initialize: reuse suitable files or sections. Read the standard for document roles. If an entry point is missing, adapt the template, remove unused prompts, and link shared context from the README or documentation index. For shared context, if neither exists, a short README pointing to the supported context is enough; it does not require inventing a broader project mission. For local-only context, use the local discovery route below instead. When initializing from earlier notes, check relevant project sources before importing claims about current implementation or configuration. Carry forward decisions and unresolved work without treating the notes as proof of current state. Maintain: update affected canonical sections from completed work and evidence. Consult the standard when roles, conflicting statuses

This is an excerpt. Refer to the complete source and its current requirements.