Examples designed for inspection¶
The examples in this site are fictional and representative. They contain no real HCP, employee, customer, or patient data. Their purpose is to show the shape of an input, the decisions in a workflow, the form of an output, and the review boundary—not to promise a particular result.
What every example will include¶
A small, readable starting artifact
Only the fields needed to understand the workflow, with fictional identities and values clearly marked.
FICTIONALA representative output excerpt
Enough structure to inspect traceability, assumptions, limitations, and the decision the artifact supports.
REPRESENTATIVEA machine-readable manifest
The immutable artifact-generation source commit, distribution and capability versions, fictional-data declaration, and validation status.
PINNEDAn explicit human checkpoint
What a qualified reviewer should verify before the pattern is adapted to operational data or materials.
REQUIREDThe six example sets¶
HCP Intelligence¶
A fictional account request paired with a compact, cited profile excerpt. The review focuses on identity disambiguation, source coverage, confidence, and data minimisation.
Competitive Intelligence¶
A fictional competitor watch question paired with evidence-run, briefing, and timeline excerpts. The review distinguishes complete, partial, failed, and not-configured source coverage.
Territory Alignment¶
A small fictional territory scenario paired with assignment and comparison excerpts. The review checks workload, continuity, movements, unassigned records, and manager judgement.
Next-Best-Engagement¶
A fictional, consent-aware HCP universe paired with a plan excerpt. The review checks eligibility, channel permissions, capacity, gaps, assigned ownership, and unassigned reasons.
Field Training¶
A fictional approved-document excerpt paired with learning and role-play material. The review checks exact source references, claims, fair balance, source-set isolation, and qualified MLR review status.
Campaign Studio¶
A fictional campaign brief and claims set paired with channel and review-package excerpts. The review checks claim traceability, fair balance, jurisdictional elements, validation freshness, and rendered-asset fidelity.
Every set is pinned and inspectable
Each guide links one pinned fictional input, one output artifact, and one YAML manifest. The manifest records
immutable artifact-generation provenance: capability version, distribution 2.2.1, source commit
6bfc6ce43491d66b4ef45b1d3934a58648e1afc6, validation status, and whether the output is a representative
illustrative artifact or a runtime-generated result from a pinned fictional fixture. A newer site release does
not rewrite these fields or imply that the sample was regenerated.