Charter, Issues, and Decisions

Review Context in the Application

Scopture presents the charter, issues, and decisions beside the drawing they describe. The charter states what the review should evaluate, issues capture what needs attention in the work, and decisions preserve the resolved project direction.

The Duc format defines these records and their relationships. For their fields, statuses, anchor structures, and format-level traceability model, see Charter & Issues in the Duc documentation.

Start with the Charter

Open the charter before arranging or reviewing project evidence. In Scopture, it provides the maintained brief for the drawing: its objective, current phase, requirements, constraints, responsible stakeholders, and recorded decisions.

Keeping this context visible allows reviewers to judge an artifact against stated acceptance conditions instead of reconstructing intent from filenames, annotations, or messages.

Capture Issues Where They Occur

Create an issue from the canvas or during model inspection so the discussion retains its visual context. Scopture can return participants to the relevant canvas position, element, or model location rather than relying on a detached written description.

Use the issue thread for discussion and supporting material, then manage the same issue set through the list, board, or timeline according to the review task. Assignments, followers, reminders, and due dates help coordinate action without changing what the issue refers to.

Carry the Outcome into a Decision

Closing an issue records that its immediate review work is complete. When the outcome changes or confirms the project direction, record the result as a charter decision and link the issues that informed it.

A practical Scopture workflow is:

1. Review an artifact against the charter.
2. Anchor an issue at the source of a question or requested change.
3. Resolve the discussion in the issue thread.
4. Record a consequential outcome as a linked decision.
5. Preserve the accepted drawing state with a checkpoint.

This keeps the application focused on the review process while Duc preserves the portable relationships underneath it.