Record the exact inputs behind a generated client
A checked-in client cannot be traced to its schema revision.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reproducibility
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional partner platform publishes TypeScript clients. Generator upgrades create noisy diffs, occasional runtime mismatches, and uncertainty about which schema was packaged.
Setup prerequisites
- Create a small public API schema and two local mock server versions; use a temporary local package registry or archive files.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Record schema digest, generator version, and options.
- Keep the manifest stable across machines.
- Fail when a required input is missing.
Implementation constraints
- Avoid absolute paths and timestamps in generated content.
Verification to include
- Compare manifests from two directories.
- Remove the schema and verify a clear failure.
Deliverables
- Generation manifest.
Rollout and recovery
Introduce manifests before enforcing them; keep the previous complete client.
Value of the work
For the engineer: Practice reproducible generation, compatibility reviews, and package provenance.
For the team: Reduce partner integration surprises with reviewable clients and recoverable releases.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.