Keep telemetry honest about who wrote what

Pain. Commits, tickets, session reports, briefing text, and inbox summaries share one operational graph. Without provenance tags, every string reads with equal authority. When you must answer whether a summary tracked human intent or drifted from a model paraphrase, or whether a constraint came from the brief versus an inferred fill-in, mixed chains look homogeneous. Downstream automation and research exports inherit that ambiguity.

Closed-loop synthesis on model-assisted workflows treats undifferentiated text as a measurement hazard: calibration, false completion, and other signals become non-identifiable when source is not in the row. The fix is structural metadata, not more chat narration.

What changed. DevPlane records origin: human | agent | mixed on artifacts. Human-authored remains attributable to the operator; agent-authored to the run; mixed captures edits that crossed the boundary. This field is operational metadata for branching exports, reviews, and merges—not affective copy.

Why it matters. Longitudinal panels can separate operator-written signals from model-written ones and reduce the chance of recycling model text as ground truth without a label. The linked research page frames identity and continuity in measurement terms; this feature is the minimum hook that makes those analyses licit.

How to try it

• Open the dashboard for a project with recent dispatches and completion records.
• Inspect rows that expose origin on artifacts tied to assignments or handoffs.
• When exporting or syncing to external tools, preserve origin fields so mixed chains remain traceable.

Shipped in 77f5378 — feat(DP-71): origin marker on every artifact (synthesis hook #9) (#34)