ADR-0027: Accept complete workflows using fictional, reproducible evidence¶

• Status: Accepted — baseline and owner workflow direction.
• Recorded: 2026-09-29. This is the recording date, not an invented original approval date.
• Authority and implementation boundaries: see Evidence below and the register conventions.

Context¶

Many passing helpers can coexist with an unusable installed workflow. Private data absence and proposed integrations can also be mistaken for accepted coverage.

Decision¶

Use fictional fixtures and normal product paths. Inspect supplied scripts before isolated baseline/candidate execution; do not monkeypatch product safeguards to manufacture a pass. Missing private data or unavailable integrations remain unverified, not passed.

Tie claims to exact environment/artifact/SHA and distinguish unit, private integration, installed user workflow and public artifact acceptance. Run relevant tests for changed scope and full gates at milestones; do not replay unchanged successes or launch overlapping work. Report complete user-visible outcomes and residual gaps, not helper counts as release readiness.

Alternatives and consequences¶

Always running the whole suite wastes time; relying only on unit success misses packaging/interfaces. Future feedback cannot be invented as a requirement. AI review evidence is independent from human GitHub approval and cannot replace it.

Evidence¶

Sources: client acceptance, CSV scale evidence, release process, owner instructions in this conversation. Executable anchors: installed package, client modes, publication acceptance.

Revisit when¶

Before adding a new release gate, identify the accepted requirement it proves; do not invent stronger guarantees or reduce scope to an intermediate pass.