Problem

Teams can see that agents produced code, but not why the work was chosen, which decision shaped it, what contract it had to satisfy, or whether the checks that gate delivery actually ran. Every change is reviewed from scratch because the chain from intent to evidence is missing.

Why It Matters

Nucleus runs agentic engineering as a governed factory. Its unit of work is an issue that stays connected to its approach, human decisions, execution contracts, supervised work, deterministic checks and delivery evidence. This issue is written the way every Nucleus issue should be, so read it as both the tour and the standard.

Primary Surfaces

• Issue overview: title, description, status and priority, with the workflow status strip above the description.
• Workflows tab: the workflows attached to this issue and the state each one is in.

Scope

• Follow this issue from the overview into its workflows.
• See Approach Research ready to run as the first governed step.
• Keep the rest of the product visible but locked, so the tour shows the real interface rather than a mock.

Non-Goals

• Running a workflow, editing this issue or opening other issues. The tour stops once Approach Research is ready.
• Connecting to a live workspace. Everything shown here is a deterministic scenario.

Acceptance Criteria

• A reader can say what problem the issue solves, why it matters and where it will show up before any agent starts.
• Scope and non-goals are explicit enough that an agent cannot silently widen the work.
• Each criterion is checkable by a person or a workflow, and the result stays attached to the issue.