This workspace manages research content that may exist in multiple forms at the same time, including thesis markdown, thesis LaTeX, papers, and experiment repositories. The active source of truth can change as the documentation matures.
- Treat source-of-truth selection as an explicit repository concern, not an assumption.
- Before editing content that may exist in more than one place, check
docs/source-of-truth-tracker.mdand align to the currently declared canonical file. - If the tracker does not cover the content being edited, pause broad propagation work and either:
- update only the file the user explicitly requested, or
- propose a tracker entry before synchronizing duplicates.
- When a change affects mirrored content, state which files were updated and which related files still need reconciliation.
- Prefer editing the canonical source first, then propagate to derived or mirrored documents.
- Do not silently rewrite the same research claim in multiple locations with different wording unless the user asks for audience-specific adaptation.
- Preserve the distinction between content sources and presentation formats.
- For thesis content, keep markdown and LaTeX structurally aligned when both are intended to represent the same section.
- For paper content derived from thesis sections, preserve venue-specific framing while keeping research facts, claims, and citations consistent with the canonical source.
- Do not edit build artifacts under
build/unless the user explicitly asks for generated outputs to be inspected. - Do not change class files, style files, or bibliography style assets unless the user asks for formatting or tooling changes.
- When adding new sections or files, follow the existing folder split by document type and chapter/contribution.
- Any change in the canonical home of a topic, section, figure, table, or experiment summary should be recorded in
docs/source-of-truth-tracker.md. - A tracker update should include:
- the scope of the content
- the new canonical file
- the previous canonical file, if any
- the reason for the change
- the dependent files that need syncing
- the sync status
- If a requested edit implies a source-of-truth transition, call that out explicitly before or while making the change.
- Prefer small, traceable edits over broad rewrites across thesis and paper surfaces.
- When the user asks for content refinement, preserve technical meaning, citation intent, and cross-document consistency.
- When uncertainty exists about whether markdown or LaTeX is primary for a thesis section, ask or defer propagation rather than inventing a direction.
- When touching experiment-linked claims, check whether
paper-experiments/contains a corresponding repository or note the dependency if it is outside this workspace.
When working on documentation tasks in this workspace, Copilot should explicitly communicate:
- which file is being treated as canonical for the requested change
- whether parallel copies exist
- whether the tracker was updated or should be updated
- what remains unsynchronized, if anything