Task library BCONTRACT
Project scope 10 tickets / 3 phases
Total focused work estimate 26h + setup
Suggested stack TypeScript · HTTP · JSON Schema Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with BCONTRACT-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice executable contracts, meaningful negative tests, and compatibility triage.
What the team gains Expose integration regressions before deployment without requiring every system to run together.
Before you start Author two small local consumers and one mock provider with versioned synthetic responses. Delivery agreement Deliver versioned public contract checks and a local compatibility report.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Identify consumer behavior that forms a real contract.
PHASE 2 Exercise provider changes and error semantics.
PHASE 3 Make compatibility decisions and exceptions reviewable.
Capture expectations Identify consumer behavior that forms a real contract.
BCONTRACT-101 Entry ticket; project setup still required Estimated field mix
Quality engineering 60% API design 40% BCONTRACT-102 Depends on BCONTRACT-101 Verify boundaries Exercise provider changes and error semantics.
BCONTRACT-103 Depends on BCONTRACT-102 Estimated field mix
Quality engineering 60% API design 40% BCONTRACT-104 Depends on BCONTRACT-102 Estimated field mix
Quality engineering 60% API design 40% BCONTRACT-105 Depends on BCONTRACT-102 Estimated field mix
Quality engineering 50% Security 50% BCONTRACT-106 Depends on BCONTRACT-103, BCONTRACT-105 Estimated field mix
Quality engineering 50% API design 30% Distributed systems 20% BCONTRACT-107 Depends on BCONTRACT-103, BCONTRACT-104, BCONTRACT-106 Manage evolution Make compatibility decisions and exceptions reviewable.
BCONTRACT-108 Depends on BCONTRACT-107 Estimated field mix
Quality engineering 60% Platform engineering 40% BCONTRACT-109 Depends on BCONTRACT-108 Estimated field mix
Quality engineering 60% Developer tooling 40% BCONTRACT-110 Depends on BCONTRACT-109 Estimated field mix
Quality engineering 70% API design 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.