Sample
Sample Delivery Pack
A public-safe example of the pilot deliverable shape: brief, evidence appendix, article excerpt, LinkedIn derivatives, and claim-boundary handling.
Sample Delivery Pack
This sample shows the delivery shape for the Evidence-Backed Technical Article Pilot. It uses only public, generic material and self-authored copy. It is a portfolio sample, not a client result, employer asset, or publication-performance claim.
1. Brief
| Field | Sample input |
|---|---|
| Audience | Technical marketing and product leaders at B2B technology companies |
| Objective | Turn a technical topic into credible long-form English content with reusable social derivatives |
| Topic | Why precision measurement errors often start before the ADC |
| Source boundary | Public datasheets, application notes, product pages, and client-approved notes only |
| Exclusions | Confidential roadmaps, non-public customer data, employer material, pricing intelligence, and unverified market claims |
| Approval owner | Client technical reviewer before publication or distribution |
2. Evidence and Source Appendix
| Public source | Supported use | Boundary kept visible |
|---|---|---|
| TI SLYT470 | Source resistance, amplifier noise, and input-stage review framing | The sample does not infer a customer's sensor architecture from generic examples |
| TI OPA388 | Representative zero-drift amplifier context for offset, drift, noise, and selection trade-offs | The sample does not claim one amplifier family is universally best |
| TI LPV821 | Representative low-power precision amplifier context for bias-current and source-impedance discussion | The sample keeps device choice application-specific |
This compact appendix shows traceability, not exhaustive design substantiation. Client projects map every material claim to an approved source or flag technical/bench verification.
3. Article Excerpt
A high-resolution converter cannot repair a measurement path that has already lost the signal. The useful review begins before part selection: what is the source impedance, how much input-referred error is allowed, which parasitic paths matter, and how quickly must the driver and reference settle under the real sampling pattern?
That frame changes the article from a component comparison into a decision tool. The reader sees which assumptions belong in the error budget, which claims are supported by public sources, and which conclusions still require bench validation.
4. Derivative LinkedIn Posts
Post A
A precision ADC is often asked to explain errors created upstream.
Before blaming resolution, review the path in order: source impedance, leakage, amplifier input range, filter behavior, driver settling, reference stability, acquisition timing, and layout.
The useful question is not "which ADC is best?" It is "which part of the measurement path is allowed to consume the error budget?"
Post B
Good technical content does not hide the boundary around a claim.
"A 1 MΩ source and 1 nA bias current creates 1 mV of input-referred error" is a useful example. "This architecture is accurate enough for every high-impedance sensor" is not.
The first claim is bounded arithmetic. The second needs an application, temperature range, leakage model, settling target, and validation plan.
5. Claim-Boundary Example
| Too broad | Claim-boundary rewrite |
|---|---|
| Zero-drift amplifiers solve precision front-end error. | Zero-drift amplifiers can reduce offset and drift in DC-sensitive front ends, but the article still evaluates noise, input current, common-mode range, switching artifacts, stability, settling, and verification conditions. |
| The pilot proves audience demand. | The pilot proves deliverable quality and evidence discipline. Audience response requires a separately measured distribution channel. |
Delivery Boundary
The final client pack would include editable article copy, a concise appendix, derivative posts, and a review checklist. This public sample intentionally excludes raw source dumps, private reviewer notes, confidential files, raw data exports, internal run identifiers, and publication analytics.