Starting point
One owned project could create duplicate branch and merge-request pipelines. Moving image tags and a moving CI include made exact reproduction harder.
OWNED-PROJECT DEMONSTRATION · NOT A CLIENT CASE STUDY
What a CI pilot evidence report shows.
This is a redacted example of the report structure. It combines checks on two projects we own with a separate, intentionally failing demo job. The source repositories are private, so a prospect cannot independently inspect their pipelines. No client result, time saving or financial impact is claimed.
EXAMPLE RECORD
A finding, a check and a boundary.
Reviewable change
A bounded change guarded pipeline creation, pinned critical dependencies and added compact failure categorization. Production deployment remained a separate customer-controlled decision.
Observed check
Applicable merge-request checks passed on the exact source commit. After an authorized merge, Gate, tests, audits and builds passed on the main commit; a staging job succeeded. The overall pipeline remained manual because production deployment was waiting for approval.
Controlled failure
A separate demo job was intentionally failed. The collector returned script_unknown and a compact diagnostic artifact. This only proves the collector path for that synthetic fault.
EVIDENCE LIMITS
The report separates observation from inference.
- Exact commit, pipeline and job identifiers are retained in the private internal evidence register and shared only with authorized access.
- A successful job is evidence for that job and commit, not proof that a website is publicly available or that a customer saved time.
- An intentional demo failure is not a live customer incident. Low incident volume produces an inconclusive before/after comparison.
- Each paid pilot receives its own baseline, agreed change, exact checks, remaining risks and next action. Raw traces and credentials are excluded from the buyer-facing report.
Observed on owned projects on 1 October 2026. This example is a format and method demonstration; actual scope and outcome depend on the customer's project and approved access.